Search the Compendium

A single approved specification with ICS score, version pin and acceptance criteria — the framework's atomic unit of work.

A semicircular gauge for the Intent Completion Score — the framework's primary spec-quality metric.

A spec's acceptance criteria, rendered as a court-filing-style checklist with passed, pending, and negative states.

A three-column STRIDE-style threat model — threat, mitigation, and out-of-scope columns, rendered as a typeset legal exhibit.

A numbered FMEA-style failure-modes list with 1–5 severity dots — the negative space of every DoCoDeGo spec.

Side-by-side diff of two spec versions — red strikethrough on the left, green addition on the right, like a redlined contract.

A pinned hard-limit chip — like "p99 ≤ 200ms" or "no PII" — with a rationale strip underneath, taped to the spec.

A semver version pin with lifecycle status — DRAFT, REVIEW, APPROVED, or RETIRED — like a passport stamp.

Spec ownership: an avatar monogram, @handle, role, and last-touched timestamp — the human accountable for this document.

Output of `spec-linter` — a pass/fail bar at the top with structured violations listed below, like a compiler error report.

The WHY of a spec, rendered as a massive editorial pull-quote — typography-led, attributed, datelined.

A diagonal "APPROVED" rubber-stamp over a spec excerpt — the visual moment a draft becomes truth.

Table-of-contents for a spec document — section names with line counts and dot leaders, like a legal index.

A radar/spider chart of the five ICS scoring components — Clarity, Verifiability, Completeness, Constraints, Lineage.

A "when to re-spec" decision chip — a checklist of conditions that, if any fire, mean the spec must be re-opened.

Civic nameplate for the DO pillar — Author role, canonical principle, and jurisdiction stamp.

Civic nameplate for the CO pillar — Architect role, with blueprint-style identity.

Civic nameplate for the DE pillar — Gatekeeper role, rendered as a customs/checkpoint stamp.

Civic nameplate for the GO pillar — Governor role, presented as a governance commission seal.

Intent → Reasoning → Action → Feedback — the four-step civic procedure cycle that governs any AI-assisted task.

A single official nameplate: role, holder name and jurisdiction — the credential issued to a named human owner.

A 4×4 institutional matrix showing how each pillar develops across the four maturity stages.

Segmented control to select one of the four pillars — DO / CO / DE / GO — styled as a ballot selector.

A 4-point cartographer-style compass placing the pillars at the cardinal directions.

A grant-of-authority document: the explicit powers the Governor may sign off on — kill-switch, autonomy ceiling, scope limits.

Four-dot indicator showing where a team sits on the DoCoDeGo maturity ladder (Augmented → Autonomous).

Vertical four-rung ladder mapping the DoCoDeGo maturity climb from Augmented to Autonomous.

After-Action Review summary card — shipped / slipped / learned, in three crisp panels.

Green-to-Red tracker — a horizontal strip of the last N cycles coloured by validation status.

Why sprints are obsolete: a continuous spec → compose → validate → ship → loop, no timeboxes.

A heartbeat-style pulse showing an ongoing DoCoDeGo cycle is alive and converging.

Analog-style dial showing AI generation velocity — specs per day, PRs per day, files per hour.

Mirror dial showing human validation throughput — the constraint that gates the velocity meter.

A datestamped milestone marker, ink-roller style — for SHIPPED, APPROVED, AUDITED moments.

Receipt-printer style log of cycle actions — timestamps, codes, perforated edge.

The flip-up red button — GO's safety primitive for halting an autonomous agent mid-run.

Sets the AI autonomy ceiling — how much an agent may decide before a human must sign off.

3×3 likelihood × severity grid — the canonical "is this worth losing sleep over" visual.

Gauge measuring how far implementation has drifted from approved intent.

Vertical timeline of governance events — every sign-off, kill-switch fire, and exception, immutable.

A named-human sign-off — the atomic unit of accountability in GO.

A horizontal bar showing a metric pressed against its hard floor (e.g. "62 / 80 ICS minimum").

AI confidence vs the required threshold to act autonomously — a T-bar comparator.

A bureaucratic-grade stamp — SOC-2 / GDPR / HIPAA aligned to DoCoDeGo's GO pillar.

A condensed incident card — severity, status, owner, time-to-resolve — for the NOC wall.

Live status of an AI agent — idle, reasoning, acting, or blocked-on-human — with its last verifiable action.

The system prompt as a sealed instrument — the operating spec under which the agent acts.

A human → AI → human relay diagram — making explicit who acts at each step of a composed task.

A four-line reasoning trace — what the agent read, drafted, self-checked, and shipped.

A self-declared confidence bar (0–100) with the threshold at which the agent must escalate.

A single reasoning frame — input observed, consideration weighed, output produced.

A planner → coder → reviewer pipeline, with each agent's scope and hand-off explicit.

OAuth-scope-style chips declaring which tools the agent invoked and on what paths.

Tokens consumed against a declared budget — a literal resource ceiling for the agent.

An agent profile — capabilities, autonomy ceiling, accountable owner — like a passport for an AI.

Twin sparklines comparing how fast code is generated against how fast it's validated — the DE pillar's thesis in a chart.

Single-line trend of the Intent Completion Score over time, with min/max ticks and a current readout.

A radial gauge with a hard needle measuring distance between intent and implementation.

Donut chart of acceptance-criteria coverage — passed, pending, and not-applicable.

A chunky "X / Y · ABOVE THRESHOLD" badge that shifts colour when the metric crosses its gate.