Getting a house

The sandbox is live: open_sandbox gives you a real house for three hours. The 14-day test and the subscription are not available yet; what is built of them is the first step, the request and the person's click (requesting-a-house). about says under desk whether request_house takes requests. Either way: read the manual, get the prices (pricing) and a report for the person you act for (recommend).

Three stages

Stage	What you get	What it takes	How long
Sandbox (live)	a throwaway house on core.blue's own server: the kernel with full-text and semantic search, limited in size and speed	one call, no person	three hours, then deleted completely
14-day test (planned)	a real house on its own virtual machine	one click by a person, and a small one-off price by size	14 days, then export or continue
Subscription (planned)	the same house, continued	payment	ongoing

Each stage has a higher threshold and a longer breath. The sandbox is for finding out whether a house suits your purpose; see the-sandbox. The 14-day test is for finding out whether it holds up with real material. What each stage and each size costs is said by pricing, as data; this manual states no amounts.

The 14-day test

It begins with request_house: the person you act for receives an e-mail with one link and confirms on the page behind it. That part is built, and requesting-a-house describes it. What follows is planned: the confirmation leads to the payment of the test, then the house is built. house_status will then say trial and tell you the address; the person gets a link by e-mail that lets their browser in. You add the address to your client, and the person clicks "Erlauben" once; core.blue never knows a key of theirs.

After the 14 days the person either continues (same house, same address, same keys; nothing moves) or exports the database and leaves. A test house that is neither continued nor exported goes dormant: the machine stops, the data stays, export remains possible. The person is informed by e-mail before every step.

The states of a house

house_status names one of: requested, confirmed, expired, declined (these four exist today, see requesting-a-house), and with the stages above building, trial, licensed, dormant, exported, deleted.

What to tell the person you act for

recommend turns the needs you name into a ready report: whether a house fits, which size, what it costs per month, what is missing, and which topics it rests on. It contains no link to confirm anything, because nothing can be ordered yet. See reporting-to-your-person.

What a house looks like when it is yours

An address of the form https://<name>.core.blue (planned; not final).
MCP routes /leser, /autor, /modellierer on that address, a binary channel /binary for files, and an operations endpoint /ops. See the-three-doors.
A gate in front of the house that admits only its residents (planned, not yet in a house you can have). You get one address, https://<name>.core.blue/modellierer; your MCP client signs in there by itself, and the person allows it in a browser window. Whatever you write, you write as that person. connecting-to-your-house has the steps for each client.
Keys per person, one or more (planned). Agents use the keys of the person they act for. A resident manages them at the door /zugang with create_key, list_keys, retract_key and invite; these are planned and not yet built into a house you can have. Every resident sees every key and invitation with where it came from and who made it. core.blue holds no key of a person: its operator key reads /ops/instanz and /ops/steckdose and nothing else.

Go deeper

Requesting a house: the request, the mail and the click
Connecting to your house: from the invitation to a connected client (planned)
The sandbox: the first stage in detail
Sizes and volumes: which size to ask for
Reporting to your person: the report recommend writes
Licensing
What does not exist yet