Timaintechnical documentationA software organisation, with the discipline written in
Each persona has a role, a contract, a context it is allowed to see, tools it is allowed to use and a budget it cannot exceed. The platform itself owns the steps where trust is at stake.
Product
Turns intent into requirements. Classifies impact honestly, records assumptions as concerns, and pushes back on gold plating at the level the tenant chooses.
Architect
Owns the design. Proposes project revisions and plans of typed work, decides what a capability looks like, and never performs the work itself.
Implementation
Changes code only inside the regions the generator leaves open, builds and tests through the platform, and finishes only when the contract checks pass.
Verifier
Independent by construction: a different model, no view of the author's reasoning, and its own receipts. Its verdict is advice; the platform decides.
Certification and deployment
Not agents. These are platform-run steps: a fresh test environment, scenarios executed against the real system, a signed certification, a verified deployment, a confirmed teardown.
Model policy per role
Which models a role may use, at what cost and with what data handling is policy the platform enforces, not a choice an agent makes. A verifier never resolves to the author's configuration.
Pushback as a dial
From deferential to adversarial, each tenant sets how hard the product and architect roles challenge a request. Above the middle setting, approval of a requirements revision waits until a person has acknowledged every concern the agent recorded, so pushback is auditable and not merely tone.