System C
The Self-Starting Orchestrator
A meta-agent that owns a build rather than reporting on one. It holds meta-skills — it provisions its own tooling, starts work unprompted, and re-decides its workflow as new events arrive. Nothing waits on a human to type: schedules, webhooks and deltas fire it, a proactive scanner watches the vault and connected accounts for work worth doing before anything has gone wrong, and a canary trips when a job misses twice its expected cadence — low-risk repairs it re-runs itself. The discipline that makes that safe is a governor: every self-directed action is scored and has to clear a confidence bar, and anything touching money or sending on your behalf is hard-gated until you approve it. LLM proposes, deterministic disposes.
The part that compounds is learning how to learn. Three meta-skills ship on first boot. One governs acquisition: check the pool first and reuse rather than rebuild, decide learn-versus-do, sequence the gap that blocks the most work, stop researching once it can act, and archive skills nothing uses. The second learns a genuinely new subject the way a top performer would — trades journals for the edge cases practitioners actually hit, expert interviews for mechanism rather than summary, definitive books for the foundation, docs and case studies for currency — then distills the durable heuristics, the anti-patterns and the numeric thresholds into an installable skill with a measurable output. The third learns from its own lived experience: a task that fails twice gets diagnosed to root cause, fixed under a bounded retry budget, tested against a sibling input so the fix generalizes, and every dead end banked as a don't-rule. Failure is tuition, paid once. This is the holy grail of agentic builds.
- →Cron · webhook · delta · scanner · canary — never a prompt
- →Transport-agnostic by construction
- →Studies the top 1% of a field, then its own failures
- →No LLM in the send path — ever