Architect layer
Development mode
How work on this project is carried out. The agent reads this at the start of every session — said in a chat, it would not survive the conversation.
Use cases
The mode decides one thing: whether a confirmed use case and an open step are required before work begins. Everything else — the technical laws of the project — holds in all four.
Use cases
alpha testingBefore you choose
Go through the work with the model step by step rather than switching on a fully automatic run. Confirm one case, look at what the agent built from it, and only then hand over the next. An automatic pass is faster right up until it turns the wrong way — and then you pay for every step it took while nobody was watching.
The fullest order: the owner confirms use cases, they become products, products become a queue of steps. Nothing is built on a guess, and every step names the case it serves.
Take it when a product is being built, not patched.
- minimum requirement: Fable 5+
- recommended: dynamic workflows
- recommended: a Max plan
The surface of products and cases is still being moved into this layer. Until it lands, cases are edited in the control panel — the same files, the same data.
Products of this project
A product is the unit of work: one server carries several, and each lives at its own pace. The id (p1, p2) means nothing and never changes — paths hang on it.
No products yet
A product is not a page. It is a thing this server carries: a shop, a landing, a company brain — with its own cases, steps and address.
What the mode never changes.
Static public pages, size limits, translations instead of inline text, settings read from config — these hold in every mode. A law that a mode could switch off would not be a law.