Communications and Corporate Affairs, run as an operating system rather than a service desk.
A Chief-of-Staff orchestrator, 26 task agents in six clusters, a seven-store truth substrate, five judgment gates and five end-to-end workflows — specified to the level of detail required to build it.
of workflow steps execute with no human in the execution path
0.0%
78 of 98 steps
task agents, each with a single output contract
0
a named failure mode and an evaluation set
judgment gates where every remaining human hour is concentrated
0
a gate is a decision, not a review
Canon stores holding the machine-readable corporate truth
0
the only layer the company actually owns
What comes out of it
Communications and Corporate Affairs is an output business
What leaves the department is language, campaigns, positions of record, risk judgments and relationships managed on the record. Those five classes are what the agents produce.
On file
8
finished specimens
Shown in full, not summarized — with the agents that produced each one, the gates it passed and the outcome it was measured against. 6 brief types, 9 triggers.
The five lines
Every situation runs on one of these
Each line has a fixed trigger, a fixed step count and a declared autonomy ceiling. Nothing enters the platform without being assigned to one.
98
Workflow steps
counted, not estimated
78
Autonomous steps
79.6% of the total
91
Handoffs routed
every one via the Chief of Staff
10
Chief of Staff steps
rule R1 — no agent-to-agent traffic
Operating posture
One switch changes every ceiling
Posture is a platform-wide variable. Moving it re-rates autonomy ceilings and compresses gate deadlines across all five lines at once.
Posture declaration
sign-in requiredTopic-scoped ceiling drops one level. Sensing cadence moves to continuous on the affected topic.
Output mix across all five lines
Live data
The floor on an ordinary day
Real records moving through the specified steps: the step each situation is sitting on, the agent holding it, the gate it is waiting for. Ceilings reduced one level on affected workflows. Gate deadlines compress to thirty minutes.
Foreign-object claim video, single restaurant, rising velocity
Step 14 of 23 · in flight
Maintain the live fact base as information changes; flag every statement now inconsistent with current facts
Produces next
Draft copy
Publishable language in the house voice.
Franchisee association disputes the value-menu economics
Step 09 of 22 · in flight
Draft the message house — claim, support, proof, and the "what we do not say" block, with every proof point ledger-bound
Produces next
Message house
What the company says, and why it is defensible.
Conduct allegation — senior market leader
Step 05 of 18 · in flight
Assemble the factual record from company systems — what is known, what is contested, what is under investigation, what is subject to legal privilege
Produces next
Canon write-back
The organization is permanently smarter for it.
Multi-jurisdiction campaign — menu labeling harmonization
Step 11 of 18 · in flight
Simulate regulator, legislator, coalition and franchise-association reaction to each filing
Produces next
Filing of record
A position of record with an external body.
Global position cascade — packaging transition targets
Step 06 of 17 · in flight
Localize across ~40 languages with a divergence report per market stating exactly what changed from source and why
Produces next
Localized variants
The same position, landed in-market.
Competitor value claim shifts share of voice on affordability
Step 03 of 22 · in flight
Resolve sentiment by cohort — franchisee by tenure band, crew, value-seeking customer, investor — with drivers named
Produces next
Cascade pack
The work reached the audience it was built for.
Supply interruption rumor — resolved, no statement issued
Step 23 of 23 · in flight
Update the scenario library and playbooks with what was learned
Produces next
Step record
The organization is permanently smarter for it.
Situations are live records in the platform database. The step text, autonomy level, owner and gate on each row are read from the workflow specification — not authored per situation.
Judgment queue
Decisions that cannot be delegated
Twenty of ninety-eight steps keep a human in the execution path. Each open one carries a recommendation, an alternative and the evidence. Deciding writes to the audit ledger.
The queue is readable by anyone. Deciding is not. A gate-holder is a named human — sign in to hold one.
CHORUS — One score, many voices.