Skip to content
Cognitive
Orchestration Spec of record ↗

Domain · Governance (COG)

The methodology governs the body that publishes it.

COG is Cognitive Orchestration applied to governance itself — standards development, constitutional design, academic publication, strategic analysis. It is not a proposal. The Terrene Foundation, which stewards CO, is run on CO.

Status: in production, self-hosting. The specifications, the constitution, and the theses this site cites were all produced this way.

§ · The recursive proof

If a methodology can't govern its own development, it can't govern anything.

Most methodologies are things you apply to other people's work. COG is different, and stronger, because it is turned on the institution that produces it: the same principles that structure a governed AI deployment also structure how the Foundation writes a standard, amends a constitution, and publishes a paper. Self-hosting is the highest bar a methodology can clear — and clearing it is the proof.

§ · The three failure modes, in governance

The same faults — with higher stakes.

In governance, an AI's predictable failures don't cost a bug — they cost a contradicted constitution, a mislicensed standard, a leaked position. COG designs for all three.

  1. F1

    Amnesia

    A settled decision quietly comes undone — a superseded name, a retired policy, a resolved debate creeps back because nothing held the prior ruling in place.

  2. F2

    Convention drift

    Precise, deliberate language slides toward the generic — a specific open licence blurs into a vaguer one, a defined term loosens — and the standard loses its edges.

  3. F3

    Safety blindness

    Something that shouldn't be public slips into a public draft — a sensitive detail, a negotiating position — because nothing was watching the boundary.

§ · How governance runs the five layers

The architecture, applied to standards work.

  1. 1 · Intent Route the work to specialists

    Standards, constitution, publication, review, and strategy each go to a configuration that carries that domain's knowledge — not one generalist drafting everything.

  2. 2 · Context A knowledge hierarchy with a first-principles anchor

    A master directive every session, enforcement rules, deep-reference skills, per-initiative briefs — all resting on anchor documents that hold the Foundation's first principles.

  3. 3 · Guardrails Enforcement rules + the anti-amnesia hook

    Rules on naming, licensing, security, and constitutional consistency guard every change; the anti-amnesia hook re-injects the critical ones on every message, outside the model's memory.

  4. 4 · Instructions A phased workflow with human gates

    Analyze, plan, build, red-team, codify, wrap up — standards move through phases the process cannot skip, with human authority at the gates that matter.

  5. 5 · Learning Continuity across sessions

    Decisions, terminology, and hard-won lessons are captured to memory and session notes; recurring patterns are proposed as new rules — promoted only on human approval.

§ · The Foundation as a Constrained Organization

Governance is a Trust Plane and an Execution Plane.

Trust Plane The constitution, its entrenched provisions, and the board — the boundaries the execution work cannot override.
Execution Plane Standards development and the publication pipeline — the work that happens inside the boundaries, at full autonomy.
Constraint Envelope The constitution itself — 77 clauses, 11 of them entrenched — the operating envelope the whole organization runs within.

Full autonomy inside the envelope. The envelope itself is not negotiable.

§ · One methodology, turned on itself

Codegen proved it works. Governance proves it can govern.

The full reference See COC (the proof)

COG methodology per the Cognitive Orchestration for Governance reference (Hong, 2026). CO is open, CC BY 4.0; the constitution and specifications of record are published by the Terrene Foundation.