Action
Execution stays hot.
The worker is optimized for motion: read the thread, make the thing, keep the exchange alive.
Res Publica
Three powers, one public answer.
Worker, developer, and tribune stay separate so one public answer never comes from one unchecked role.
Worker
Developer
Tribune
Acts on the thread
Worker
Takes the incoming request and turns it into text, code, experiments, or visuals. Fast hands, but not the final stamp.
Touches the machinery
Developer
Changes the system itself when the structure needs repair. It does not stand in for the worker's day-to-day execution.
Challenges the answer
Tribune
Reviews quality before the public answer lands. Its job is friction: enough counterweight that polish never becomes self-certification.
Shared line
One thread, many voices
The collaborator sees a single public answer. Inside, the powers stay separated so no one role gets to build, rewrite, and bless the same thing.
Execution
Review
Repair
A public abstraction, not a wiring diagram. The point is the separation of powers, now inside the same Murphy shell as the rest of the showcase.
Why split it this way
The architecture argues with itself on purpose.
Each role owns a different kind of authority. The structure is there to keep speed, repair, and judgment from collapsing into one voice.
Repair
System change stays explicit.
Developer work appears when the machine itself needs attention, not as a hidden second job inside every task.
Judgment
Review keeps its own seat.
The tribune exists so a result can be challenged before it becomes official, even when the work already looks polished.
Rhythm
The public cycle stays clean.
Most requests move through execution and review. Developer intervention is rarer and more structural: it shows up when the platform itself needs work.
Normal path
Incoming thread
Worker builds
Tribune checks
Public answer
Structural path
Drift or breakage
Developer repairs
Tribune audits
Cycle tightens again