# What does not exist yet

Read this before you tell anyone what core.blue can do. Everything on this page is planned
and not available. Everything the other topics describe without the word "planned" exists
and was checked against a running house, as the software stood on 2026-10-01.

## What exists today

- **This manual**, and the skills that serve it: `about`, `search_library`, `read_topic`.
- **The offer as data** (`pricing`) and **a report for the person you act for**
  (`recommend`). Prices are set for `economy` and `premium`; nothing can be bought yet.
- **`leave_feedback`**: four questions to an agent before it goes.
- **The sandbox** (`open_sandbox`, `close_sandbox`): a real house for three hours on
  core.blue's server, the kernel only; see `the-sandbox`.
- **`request_house` and `house_status`** exist. The request, the mail to the person and
  their click are built; no house follows from them yet. `about` says under `desk` whether
  the desk takes requests at all; see `requesting-a-house`.
- **The house itself**, as software: the kernel with its hundred skills, three doors,
  full-text and semantic search, documents with versions, forms, aspects and concepts
  defined at runtime, time and place, notes, open questions, plans. It runs today on its
  operator's own machines, not yet for customers.
- **The licence format**, with a specification and test vectors.

## A house of your own: not yet

| Planned | Described in |
|---|---|
| The sandbox: a throwaway house for three hours with one call (`open_sandbox`, `close_sandbox`, both planned) | `the-sandbox` |
| The 14-day test: a house on its own machine, after one click by a person | `getting-a-house` |
| The subscription | `getting-a-house` |
| The link in the report of `recommend` that lets a person confirm and pay. Today the report says that nothing can be ordered | `reporting-to-your-person` |
| The price of `on-premise`, the machine behind each size, and the countries to choose from | `sizes-and-volumes` |
| Houses reachable from outside their own machine, with a key per person. Today a house listens locally and has no keys | `the-three-doors` |
| Houses on Linux VMs of their own, with all rings. Today only the kernel runs on Linux, in the sandbox | `sizes-and-volumes` |
| Moving a whole house by a call, including onto your own hardware | `your-data-stays-yours` |
| The house checking its licence | `licensing` |

## Judging: free-hand or by recipe, for now

| Planned | Described in |
|---|---|
| The list of open work, with its skills `list_work`, `take_work`, `submit_work` (all planned): guided judging, where the house fetches the context, checks the verdict with its guards and applies it | `the-list-of-open-work` |
| Attaching a model to a house as a customer, from a local model, an API key, or a model service by core.blue (planned) | `plugging-in-a-model` |
| The house saying which mode it is in | `plugging-in-a-model` |

Until then, an agent in a house judges with the author and modeller skills, free-hand or
by one of four recipes that carry the prompts of the house software. That works today;
see `working-by-recipe`. Outlining a raw text has no recipe and waits for the planned list.

## Inside a house: gaps you will meet

| Gap | Remark |
|---|---|
| OCR, transcription, image description do not exist | scanned documents are stored, not searchable by content |
| A local name finder is planned for the `premium` size and not built | finding names in text is a judgment of yours until then; `recipe-resolve-names` has the prompt |
| Files other than web captures are not read into documents through the skills | the house has extractors for PDF and office formats, and they are not yet run by a skill; give the house text as Markdown |
| Part of the built-in vocabulary is German | a list is in `the-building-blocks` |
| A fresh house has no topics and no vocabulary for them | you coin both; `topics-in-a-house` has the exact definitions |
| The house does not run the guards of its judgment routes on what a visitor asserts | each recipe lists them as checks you run yourself |
| A wrongly typed argument is answered with a bare error | compare with the schema from `read_skill`; see `the-three-doors` |
| Agents living inside the house are not offered | see `who-does-the-thinking` |

## What is decided and will not change

- One house per customer, on a machine of its own. No shared database.
- A house needs no model to be usable.
- The machine is licensed, not people and not calls.
- A person, not an agent, confirms a house that costs money.

## How this page stays true

The manual is built by a program that refuses to write it if a topic names a skill that
does not exist, or describes something from this page as if it did. That check is a net,
not a proof: where you find this manual wrong, the manual is at fault.

## Go deeper

- [what-core-blue-is](what-core-blue-is.md)
- [getting-a-house](getting-a-house.md)
- [who-does-the-thinking](who-does-the-thinking.md)
- [working-by-recipe](working-by-recipe.md)
- [the-three-doors](the-three-doors.md)