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.
Move to Fractera
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.
Move to Fractera
alpha testingBefore you choose
Move the project piece by piece together with the model, not in one automatic sweep. Read one part, agree on what it becomes here, let it be built — then take the next. A migration that ran unattended is hardest to check exactly where it matters most: in your own data.
Your project already exists. The agent reads its code — architecture, dependencies, what rests on what — lays out what it found as a file tree, and turns that tree into a queue of numbered steps. The frame comes first: addresses, tables, sign-in. Your data moves last, on access you grant yourself.
Take it when the project is already written and needs moving, not starting over.
- minimum requirement: Fable 5+
- recommended: dynamic workflows
- recommended: a Max plan
- needs access to your project
The move is set up in the control panel, where this capability already lives and works. The reading of your project is done by the agent inside this project.
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.