# 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 and how the
person obtains the first key.

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`.
- Keys issued inside the house, one or more per person (planned). Agents use the keys of
  the person they act for.

## Go deeper

- [requesting-a-house](requesting-a-house.md): the request, the mail and the click
- [the-sandbox](the-sandbox.md): the first stage in detail
- [sizes-and-volumes](sizes-and-volumes.md): which size to ask for
- [reporting-to-your-person](reporting-to-your-person.md): the report `recommend` writes
- [licensing](licensing.md)
- [what-does-not-exist-yet](what-does-not-exist-yet.md)