Writing
What we have written down.
We build by writing the document first, so there is a lot of it. These are the ones worth reading from outside the company, dated, versioned, and superseded in public when they change rather than quietly edited.
Capabilities
What the system promises, the mechanism behind each promise, and the dated proof. The sheet we leave behind after a walkthrough. Download · PDF
2 pages · September 2026
Security review pack
The control registry and the questions a reviewer asks, answered. Read it here
September 2026
Compounding context
Why a workspace that keeps its plans, its specialists and its receipts gets better at your work, and a thread does not. Ask for a copy
September 2026
Design system
The rulebook this site is built to. Tokens, the three moves, and the pre-flight every surface passes before it ships. Ask for a copy
v3.1.1 · 28 pages · September 2026
Security overview
How a deployment is protected, control by control, each one naming the code that enforces it and the check that keeps it true, with what is accepted or still pending said plainly. Ask for a copy
September 2026
Vendor questionnaire
The standard security questionnaire, answered, with the evidence beside each answer. For the reviewer who has their own form to fill in. Ask for a copy
September 2026
Security testing summary
Four adversarial engagements this year, what each one changed, and what has not been done, including that no third-party test has happened yet. Ask for a copy
September 2026
Pack authoring tutorial
From an empty folder to a running plan: a pack that reads a private database through an endpoint you host, uploaded, approved, signed and run. Ask for a copy
September 2026
User, admin and API guides
The day-to-day guide, the operator’s guide, the plan grammar reference, and the API reference for triggering a signed plan. Ask for a copy
September 2026
The nine example plans
Plans from our own use, with their phases, gates and line-ups. Read them here
September 2026
Why this page exists
If the argument is a written plan, the marketing should be written too.
Every claim on this site traces to one of the documents above, or to the posture page. When a claim stops being true, the document is superseded here rather than quietly edited.
Write to the assistant inbox
assistant@agenticensemble.ai