What does not exist yet
Read this before you tell anyone what core.blue can do. The first section says what exists today; everything from "A house of your own: not yet" on is planned and not available. Everything the other topics describe without the word "planned" exists and was checked against a running house; the sandbox runs the house software as it stood on 2026-10-07.
What exists today
- This manual and its server:
about,search_library,read_topic, the offer as data (pricing), a report for the person you act for (recommend), andleave_feedback. Prices are set; nothing can be bought yet. - The sandbox (
open_sandbox,close_sandbox): a real house for three hours on core.blue's server, the kernel only; seethe-sandbox. request_houseandhouse_status: the request, the mail and the person's click are built; no house follows from them yet.aboutsays underdeskwhether the desk takes requests; seerequesting-a-house.- The house software: the kernel with its 105 skills and three doors, full-text and semantic search, documents with versions, PDF and office files read into documents, a vocabulary defined at runtime, time and place, the list of open work, and erasing a thing with everything that hung only on it. All of it runs in the sandbox.
- The gate in front of a house, with a key per person and a sign-in from the MCP client: tried with VS Code, Claude.ai and ChatGPT on a test machine.
- The licence format, with a specification and test vectors.
A house of your own: not yet
| Planned | Described in |
|---|---|
| The 14-day test: a house on its own machine, after one click by a person | getting-a-house |
The subscription, and the link in the report of recommend to confirm and pay | reporting-to-your-person |
The price of on-premise, the machine behind each size, and the countries to choose from | sizes-and-volumes |
| A house of your own on a Linux VM, behind the gate | connecting-to-your-house |
| The disk of a VM encrypted | your-data-stays-yours |
| Your export or move at your request; the house software can do both | your-data-stays-yours |
| A verifiable erasure: erased data stays in the files until compaction, and a backup can bring it back | your-data-stays-yours |
| The house checking its licence | licensing |
A view for people into their house is not built, and none is planned today: a person works
with a house through their agent (what-core-blue-is).
Judging: by visitors, for now
| Planned | Described in |
|---|---|
| Attaching a model to a house as a customer (planned) | plugging-in-a-model |
| Resolving and merging names, and digests, on the list of open work | the-list-of-open-work |
Until then, an agent judges through the list of open work (outlining, and assigning topics
once the house has them), by one of four recipes, or free-hand; see working-by-recipe.
Inside a house: gaps you will meet
| Gap | Remark |
|---|---|
| OCR, transcription, image description do not exist | scans are stored, not searchable by content |
A local name finder is planned for premium and not built | recipe-resolve-names has the prompt |
| Nothing is encrypted at rest | see your-data-stays-yours |
| Part of the built-in vocabulary is German; the outline prompt speaks of a German document | a list is in the-building-blocks; the prompt applies to any language |
| A fresh house has no topics | list_work and topics-in-a-house give the definitions |
| What you assert free-hand passes no guard | the list of open work checks; each recipe lists its checks |
| A wrongly typed argument is answered with a bare error | compare with 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.