q division · departments · roles · receipts
AI that does the work. On the record.
Q does the work in your systems. It asks before anything that matters. You keep the receipt.
- department
- finance
- role
- credit controller
- run
- 01HV3Q7KX2
- evidence
- 2/2
- approval
- version 3 · approved by principal
- spend
- USD 0.0412
specimen receipt · values are illustrative
01 · the division
Q Division equips the departments.
The workshop builds, tests and signs off the equipment. It does not go on the mission.
the structure
Organised the way a business is.
Q Division builds, tests and signs off the equipment. The departments do the work.
Departments.
Domains of authority: operations, finance, people, records. A department holds the authority its roles work under, and every receipt is filed in one.
Roles.
The credit controller. The lettings coordinator. The onboarding clerk. A role has a job description, works inside its department and keeps a performance record made of its receipts.
Mandates.
What a role may do, under what budget, until when. Today every protected action asks a person and the ask is bound to the exact action. Standing mandates, scoped and budgeted, are the next instrument on the bench.
Systems.
What a department is equipped with. Yours, connected as they are. Or ours, made by the same house. The receipt states which, and what each one could and could not confirm.
approval · bound to four things
Nothing dangerous happens on a vibe.
Approvals are bound to the tenant, the principal, the run and an immutable action version. A changed argument is blocked, even outside the display summary. Expiry is decided by the database clock. Required approval never turns into automatic approval.
approval · finance · run 01HV3Q7KX2 · action version 3
This run wants to send a second reminder for invoice 0417.
Evidence 2/2 attached: the invoice, the first reminder. Approve version 3, or reject.
systems · equipment for departments
Works with what you have.
The receipt says how well. A connected system acts through its own tools, with Q enforcing the approval on its side and delivery at least once. A first-class system enforces the action version itself, signs the receipt and carries the charge on the same invoice. No system is first class yet. Route Royal is closest.
| system | department | grade today |
|---|---|---|
| Route Royal | operations | acts · action binding in progress |
| Vellon | finance | metering built · billing not yet live |
| Wocha | people | identity live |
| Google Workspace | records · people | acts |
| ClickUp | operations | acts |
| SharePoint · Notion · Confluence | records | evidence only |
| Slack | operations | evidence only |
grades as recorded on 1 november 2026 · the capability registry is the authority
what the product actually does
Five commitments, each with its limit.
These are drawn from the behaviour of the running system and its contracts, not from a roadmap.
Evidence over assertion.
Answers carry sources, citations and a quality signal. Read the evidence before you show an answer as grounded; HTTP 200 does not establish accuracy.
Exact approval.
Protected actions stop the run and ask a person. The ask names the tenant, the principal, the run and the version. Any mismatch rejects.
Durable by design.
Runs are Temporal workflows. They survive restarts, resume from where they stopped and replay from the journal. Consumption authorises one dispatch, not exactly-once.
Spend on the record.
Cost is reserved before a model is called and settled after. It is reconciled against provider records. Qualification under representative load is still pending.
Honest qualification.
Local qualification, publication and production acceptance are different states. The capability registry says which operations are conditional and which are unavailable.
tenancy · audit · the auditor's view
Agents your auditor can read.
Row-level security in PostgreSQL. An event journal for every run. Approval records retained across restarts. The auditor reads the same receipt the operator did, filed by department.
