Governance-Driven Design

Appearance

GDD in the Semantic Intent Ecosystem ​

GDD was named after the pattern was already present. The ecosystem built it before anyone called it governance-driven design.

GDD is not separate from the Semantic Intent ecosystem. It is its origin point — the upstream source of the contracts that every downstream tool operates within.

The Architecture ​

GDD
 └─ produces: Governed Constraint Set
      └─ expressed as: Semantic Intent contracts
           └─ carried by: EMBER (.sil artifacts)
           └─ executed within: CAL / REACH / OCTO
           └─ gated by: Synthesis Gate
           └─ remembered by: TRACE
           └─ preserved in: CROC

Component Relationships ​

Semantic Intent Contracts ​

The governed constraint set produced by a GDD cycle is the raw material from which Semantic Intent (SI) contracts are derived.

EMBER ​

EMBER (.sil artifact files) carries constraints forward across agents. GDD produces the intent; EMBER makes it portable.

npm: @semanticintent/ember · DOI 10.5281/zenodo.19751387

CAL / REACH / OCTO ​

The execution layer. CAL provides deterministic cascade analysis. REACH + OCTO provides the local workflow practice and multi-arm orchestration. GDD defines the constraint boundaries each arm operates within before the orchestration is designed.

npm: @stratiqx/cal-runtime · REACH DOI 10.5281/zenodo.20680385

The Synthesis Gate ​

The moment ambiguity surfaces to human judgment. GDD designs that moment in deliberately — the human gate in the ICR cycle is a Synthesis Gate, placed upstream before any agent runs rather than encountered reactively mid-pipeline.

github: semanticintent/synthesis-gate · DOI 10.5281/zenodo.20684283

TRACE ​

TRACE is the append-only execution record — every decision, every artifact, every gate. Every gate decision recorded in .gdd/GATES.md is a TRACE event waiting to be formalized.

github: semanticintent/trace · DOI 10.5281/zenodo.20739404

CROC ​

CROC (Contextual Retrievable Organizational Corpus) preserves institutional knowledge before it walks out the door. The governed constraint set is exactly the kind of institutional knowledge CROC is designed to preserve.

github: semanticintent/croc-framework · DOI 10.5281/zenodo.20777675

Phoenix Runtime / Strata Runtime ​

GDD in practice. Phoenix is a 7-agent legacy modernization pipeline; Strata is a 5-agent database archaeology pipeline. Both include human gates before the pipeline runs — those gates are Synthesis Gates, and the governed constraint set GDD produces is the human gate checklist.

RECALL ​

RECALL is the machine-legible, intent-dense, COBOL-inspired language for authoring artifacts that both humans and models read. GDD is the thinking that precedes the .rcl file — the governed constraint set authored in RECALL is both human-readable and AI-composable.

npm: @semanticintent/recall-compiler · DOI 10.5281/zenodo.19463347

The Broader Context ​

GDD emerged from a body of work on methodology-as-infrastructure:

  • Methodology-as-Infrastructure — analytical methodologies compiled into deterministic execution layers. GDD is the methodology that, once formalized, becomes the governance infrastructure other systems build upon.
  • Intent-as-Infrastructure — when the compiler is Claude. GDD produces the governed intent that serves as the input to intent-as-infrastructure compilation.

All published work is part of the Semantic Intent research program by Michael Shatny.