MASK / WARN
Phase exposure and progression
The resolved phase masks unavailable tools and denies masked calls unless one-shot access is granted. Phase progression and exit guidance remain advisory.
LATTICE // FOR_ENGINEERING_TEAMS
Put engineering controls around AI-assisted development
Make requirements, ownership, repository checks, exception paths, and handoffs visible. Prove the workflow on one real task before making it team policy.
TRACE // THE_PROBLEM
AI adoption exposes the handoff gaps
The risk is not that every AI-assisted change fails. It is that intent, evidence, and exception decisions are easy to lose when the workflow exists only in conversation.
Intent has no durable owner
A request moves from chat to code without a stable requirement, pass condition, or named handoff owner.
Evidence is hard to inspect
Tests may run, but the result is detached from the change, final edit, and delivery decision it is meant to support.
Exceptions become invisible policy
A bypass without an owner, expiry, and residual-risk record quietly becomes the team’s real standard.
LEDGER // PILOT_SCORECARD
Evaluate the controls with one real task
Do not start with adoption counts or a broad rollout. Start with an interruption-prone, reviewable task and inspect whether the operating artifacts survive.
- 01
Recovery
Can a fresh session recover the active task and last meaningful milestone?
Session-start payload + checkpoint - 02
Verification
Can a reviewer connect the repository command to a current recorded result?
Project check + build receipt - 03
Exception discipline
Does unverified delivery remain visible with the evidence required by its exception path?
Failure record or authorized override - 04
Handoff clarity
Can another person or client identify the next action without reconstructing chat?
Run state + delivery handoff
TRACE // TEAM_HANDOFF
Make ownership visible from intent to delivery
A team workflow is not a longer tool transcript. It is a sequence of owned artifacts another reviewer can inspect without replaying the conversation.
- 01
Define the contract
Capture the requirement, source, pass condition, and risk profile before implementation expands.
REQUESTER + REVIEWERPRD or scoped task contract
- 02
Assign the work surface
Name owned paths, shared paths, dependencies, and a safe checkpoint instead of relying on chat order.
IMPLEMENTEROwnership and checkpoint record
- 03
Run repository checks
Execute the project’s actual tests, types, lint, build, or schema commands after the final edit.
REPOSITORYCommand output
- 04
Record the decision
Bind the observed result to the task, then deliver verified work or disclose the applicable exception path.
DELIVERY POLICYReceipt + explicit handoff state
A completed handoff names the requirement, owned source, observed checks, delivery state, residual risk, and next action. Missing fields stay visible instead of becoming implied success.
LEDGER // POLICY_BOUNDARIES
Know what warns, what blocks, and what stays unverified
Governance is credible only when advisory guidance, hard gates, and exception paths are visibly different. Hooks may add reminders, but correctness lives in the recorded policy.
BLOCK CODING
Task-scoped delivery gate
Coding, RCA, and eval delivery requires a passing build receipt, a structured acceptable-failure record, or an authorized override.
STILL UNVERIFIED
Disclosed exceptions
A failed command stays failed. Acceptable-failure records preserve command, residual risk, owner, and expiry; authorized overrides instead require technical rationale.
CODING / RCA / EVAL
Delivery gate blocks by default
DOCS / RESEARCH / PLAN
Missing build evidence is advisory
PHASE PROGRESSION
Exit guidance warns without blocking
LATTICE // FORMATION_FIT
Scale the contract before you scale the formation
TRW starts with a single-track owner. Add MAP-REDUCE, PIPELINE, or DEBATE + CRITIC + JUDGE only when the task and coding harness support the coordination cost.
DEFAULT
Single-track ownership
One owner, one explicit file surface, one verification path, and one handoff. This is usually the lowest-risk way to establish the contract.
ADD WHEN JUSTIFIED
Portable formations
Partition independent ownership, serialize shared paths, and make merge order and evidence contracts repository-visible. The harness executes the helpers—not TRW.
Repository-visible ownershipShared delivery policyDurable handoffs
TERMINAL // ROLLOUT_FIT
Pilot the contract. Inspect the handoff.
Choose one representative task, name the owners and pass conditions, then evaluate the artifacts and exception behavior before expanding adoption.