L3 · Execution
Watch the work move and the outputs appear.
Pick a line and press play. Each step names the agent that holds it, its autonomy level, the gate that can stop it and the artifact it produces. Gates halt the run until a human releases them.
Steps simulated
98
Handoffs
91
Artifact classes
12
Gate stops
15
Choose the situation
The situation
Operator forums and review platforms start carrying the same complaint about value in three US regions at once. Nobody has said it publicly yet.
Trigger
Divergence signal detected in owned and earned channels
Clock
Days to weeks — the window is before it reaches earned media
Ceiling rationale
A3. The system may detect, analyze, simulate, draft and cascade unattended. It may not settle a commercial dispute with an independent business owner.
Run state
Steps done
0/22
Artifacts
0
Gates cleared
0
Human touches
0
Canon stores written
0
Overrides
0
Autonomous so far
—
Detect divergence signal — operator forum threads, local price-comparison content, customer value complaints, review-platform language shift
Cluster into a single issue; resolve originating voices against the Stakeholder Graph; identify which operator segments are driving it
Resolve sentiment by cohort — franchisee by tenure band, crew, value-seeking customer, investor — with drivers named
Score materiality; business exposure driver pulls transaction data where integrated
Match precedent — prior value campaigns, prior franchisee pricing disputes, competitor value-war outcomes
Issue early-warning card with time-to-surface estimate and three options with projected consequences
DECISION — engage now, prepare and hold, or take no action. Recommendation attached with consequences of each.
Assemble the evidence base — actual price distribution by market, what was promised, what was delivered, what can be substantiated
Draft the message house — claim, support, proof, and the "what we do not say" block, with every proof point ledger-bound
Test message variants against franchisee and customer synthetic panels; return the objection each variant provokes
G1 POSITION — adopt the value position. Diff against current Canon shown; downstream artifact list shown; market impact shown.
Verify every claim against the Evidence Ledger with market-level scope; flag anything expired or out of jurisdiction
Simulate reaction across twelve personas — franchisee by tenure, crew, both customer segments, investor, analyst, business and food press
Red-team the position; produce the hostile headline and the three weakest claims
G3 RISK — proceed, proceed with mitigations, hold, or kill. Hostile simulations and franchise-law exposure attached.
Produce the artifact set — franchisee communication, operator-meeting materials, crew briefing, press Q&A, investor talking points, holding statement
Localize for all affected markets with divergence reports; apply jurisdictional pricing-language constraints
Build the cascade plan — sequence, channel and messenger per cohort, with franchisees ahead of external release
G5 RELEASE — timing against the earnings calendar, embargo state, conflicting releases in the window
Execute the cascade; monitor reception per cohort in real time; escalate divergence
Measure — cohort sentiment movement, franchisee pricing behavior change, traffic signal, coverage tone
Write back — prediction versus outcome, post-mortem drafted, precedent recorded for the next value cycle
Output shelf
0Everything the run has actually produced. Click an item to read the output contract the producing agent is held to.
Nothing produced yet. Run the situation.
Canon touched
No write-backs yet.
Architectural rule R2: no output leaves the system without a Canon write-back. That is the difference between a tool that produces content and an organization that gets smarter.
Output taxonomy
What a step actually produces
Every specified step leaves an output. Grouping them into classes shows what was produced, by whom, under which level, and what it changed.
The work reached the audience it was built for.
Publishable language in the house voice.
The organization is permanently smarter for it.
A judgment with its drivers attached.
What the company says, and why it is defensible.
The same position, landed in-market.
A position of record with an external body.
A claim is substantiated and traceable.
What it changed, counted rather than claimed.
A named human accepted the consequence.
Something in the world was noticed and named.
A human is prepared to act or answer.
Why the bench behaves this way
Three rules govern every run
The simulation obeys the same three architectural constraints the platform is specified under.
R1
No agent-to-agent coordination. Every handoff goes through the Chief of Staff.
Swarms that self-coordinate cannot be audited, debugged or governed. The cost is a small latency penalty; the benefit is that every decision has a traceable path.
R2
No output leaves the system without a Canon write-back.
This is what compounds. Without it, the platform is a very expensive drafting tool.
R3
The autonomy ceiling is data, not code.
Legal must be able to ratchet down a ceiling at 23:00 on a Friday without a deployment.