Genesis Gate
Governance Control Plane
The operational boundary layer of the P31 stack. No deployment crosses without telemetry capture and governance hook clearance. v4.1.0 marks Gate Zero — the moment the system became self-governing.
01. Architecture
Four modules wired by the GenesisOrchestrator. Each module has a single responsibility; the orchestrator sequences them and enforces the governance contract at every event boundary.
RegExp[] patterns. Filters events before they reach the governance hook — configurable per deployment context.-
▸
TypeScript ESM, Node 20+ —
module: Node16,moduleResolution: Node16,isolatedModules: true. pnpm workspace underpackages/*. -
▸
Required env var —
BRIDGE_FUNDING_AMOUNT_USDthrows on startup if missing. CI sets??= 'TEST_OVERRIDE'injest.config.js. -
▸
ts-jest ESM preset —
@jest/globalsimport required for ESM compatibility. Tests excluded from tsc build via tsconfig. - ▸ 4 tests, all green — covers orchestrator init, telemetry capture, intercept pattern matching, and governance hook enforcement.
-
▸
Docs included —
docs/RUNBOOK.md(operational procedures) +docs/kofi-phase2-post.md(Ko-fi Phase 2 bridge post with${{BRIDGE_FUNDING_AMOUNT_USD}}placeholder).
02. Governance Model
Gate Zero deployed 2026-03-30. This marks the transition from ad-hoc operations to governed operations — every significant system event is now captured, filtered, and cleared before propagation.
The "gate" metaphor is literal: no deployment, no funding event, no social dispatch crosses the boundary without passing through the telemetry-intercept-governance pipeline. Silent failures are rejected by design — if the governance hook cannot clear an event, it throws.
The kofi-phase2-post.md document uses a ${{BRIDGE_FUNDING_AMOUNT_USD}} placeholder. Substitute the dollar target before publishing. This is the governance layer's connection to the funding circuit — every Ko-fi event fires telemetry here.
The InterceptModule's injectable RegExp[] pattern system means governance rules can be tightened or loosened without modifying core module code — the rules are configuration, not implementation.