Governed Capability Model and Context Architecture¶

Thesis: Context is compiled operational state, not a document dump. An agent should receive the minimum sufficient trusted context for the next decision or action, assembled from governed sources at execution time.

Axiom: REPRESENTATION IS NOT REALITY. - A file is not an operating capability. - A declaration is not enforcement. - Source state != Deployed state != Runtime state != Verified state. - A running process is not a verified service. - A generated projection is not authority.

The Operating Loop¶

INTENT → CAPABILITY → PROCEDURE / SKILL → TOOL → POLICY → CONTEXT → EXECUTION → VERIFICATION → EVIDENCE

System Boundaries¶

Drupal / ContextControl: Business logic, human governance, and the governed capability surface.
Tool API: Typed, executable actions.
api_normalization: Normalizes external APIs into Drupal-managed representations.
MCP: External agent protocol boundary.
Drupal AI: Drupal-native AI integration and execution.
ECA: Drupal event and workflow automation.
Gas City: Durable multi-step agent orchestration.
Beads / Dolt: Durable commitment and work graph (WHAT).
Cedar / ContractPlane: Authorization (WHO may do WHAT).
QMD: Relevance discovery over Markdown.
CodeGraph: Structural code knowledge.
GitLab: Source, change, CI, and release evidence.
Context Compiler: Assembles the minimum sufficient trusted context (Context is bounded by applicability, freshness, authority, evidence, and state).

Capability Definition¶

A capability does not exist merely because an API exists. A capability exists when the organization can discover it, know who may use it, execute it in the right context, and prove what happened. It is a compiled organizational projection assembled from upstream sources, not a proprietary database.

Trust Equation¶

Relevance finds candidates. Trust requires evaluation of: AUTHORITY × APPLICABILITY × EVIDENCE_STATE × FRESHNESS × SCOPE × LIFECYCLE_STATE (adjusted by CONFLICT).