The Orchestrator
Main-agent coordination
Owns the conversation, the plan, the delegation and the consolidated result. The only agent accountable to you.
The problem
Agents forget. Systems don’t.
You said it once, early, in message four. Two hundred messages later the constraint is gone — not refused, just quietly dropped. The work looks finished. It isn’t.
Every restart, retry, branch, compaction and provider switch is another chance to lose the thread. So you stop directing outcomes and start babysitting prompts, and the thing that was meant to give you leverage becomes another job.
CTROLL keeps intent as durable state, not model memory.
Every requirement is an ID with immutable original text, a change policy, a history and an explicit verdict. A worker cannot weaken it. A newer message cannot overwrite it. A later summary cannot forget it. When something must change, that change is a recorded decision with your name on it — not a paraphrase.
- Requirementsimmutable originals, explicit verdicts
- Exclusionsnamed non-goals that stay refused
- Decisionswho approved what, and when
- Evidenceartifact per requirement, or it is not done