/architect · Technical
CLI and the pinned engine.
Everything the web app does is a command first. The engine it reads, the Model Health Check and the grammar, is installed at pinned commits and recorded with its version and its test result.
Commands
- material
- What the reviewer reads: estate facts, graph, patterns with their statuses, longest formulas, actions, owner notes. Never the raw exports.
- review
- The written review: strengths, design decisions, which patterns matter, risks, options, the handover page, questions. With no key it writes the prompt for you to paste into any model; with a key it runs.
- ask
- One question against the estate, answered with citations.
- chat
- A conversation with the tools: find, explain, impact, lineage, patterns, rules, actions, validate a formula, set a status, remember.
- status
- Record the owner's status on a pattern, with the reason. The next run reads it.
- serve
- The web app: estates, snapshots, notes, conversations, dependencies, the action plan, size, the evidence drawer.
- users
- Create the owner from the console; hand out invite codes. Nobody creates an account from the web.
- backup, restore
- One zip per estate: register, snapshots with their export files, notes, conversations with their citations, decisions, proposals, transcripts, reviews. Restore keeps every id so every old citation still opens.
anaplan-architect ask ROOT "is S SYS05 Currency Conversion.Exchange Rate by GBP (month) safe to change?"
anaplan-architect review ROOT --prompt prompt.md # no key: paste into any model
anaplan-architect serve --data DATA --port 8765The pinned engine
The Architect runs in its own environment where the grammar and the Model Health Check are installed as copies at pinned commits, never as editable links. All three are built side by side, and the Architect must not see their half-saved edits. A bump tool reinstalls one at a chosen commit, records it, runs the tests and says when the server needs restarting.
{
"anaplan-estate": { "version": "0.2.0", "commit": "559f4fd 2026-09-30 Release 0.2.0", "tests": "passed" },
"anaplan-grammar": { "version": "0.1.0", "commit": "8a5683b 2026-09-24", "tests": "passed" }
}pins.json as it stood on 12 October 2026.
Where things live
- The store. SQLite plus content-addressed blobs. Estates hold a register of models and a history of snapshots, the export files the estate reads. An upload stages into a draft, is validated file by file, parsed on request, reviewed for coverage, then activated. A failed parse leaves the previous snapshot serving.
- The workspace. Statuses on patterns with the owner's reason, notes scoped to the estate, a model or a rule, transcripts, review runs. The next run reads them.
- The parse. Cached on disk, keyed on the files, the names and the engine version; run in a subprocess so Cancel really cancels.
- Identity. A closed system. A server bound to localhost with no accounts is open to that machine; one bound to the network serves nothing until the owner is created on the console.
Run Anaplan in-house?
Start with the Model Health Check on your own exports.
The 42 tests and the action plan run free, hosted or on your own machine, and nothing is stored. Then give me 30 minutes and bring the three questions you would ask about your estate.