GOVERN Internal

What is GOVERN Internal?

GOVERN Internal is the operational layer behind the customer-facing GOVERN platform. It provides two major surfaces:

Surface 01 — Testing Dashboard The pre-release validation environment where every GOVERN component is tested before it ships to customers. The Testing Dashboard runs unit tests, integration tests, Playwright visual regression, API spot-checks, and probe container verification.

Surface 02 — Internal Dashboard The infrastructure monitoring surface where the GOVERN civilization monitors itself. Build events, archetype skill evolution, convergence scoring, cost tracking, and deploy health are all visible here before they surface in customer-facing dashboards.

Audience

This documentation is for:

• Engineers — building and deploying GOVERN components
• QA — running test suites and quality gates before release
• Operations — monitoring infrastructure health and responding to incidents

Quick navigation

Section	Description
Testing Overview	Purpose and scope of the Testing Dashboard
Test Suites	Unit, integration, e2e, and visual QA structure
Playwright	Screenshot testing and regression detection
API Testing	Endpoint curl spot-checks and response validation
Probe Testing	Docker probe build and telemetry verification
QA Gates	Gate II (V(Q)) and Gate IV (polish) requirements
Internal Overview	Internal dashboard purpose and architecture
Pipeline	Sealed monitoring pipeline: EMIT → ROLLUP → INSCRIBE
Build Events	What was built, by whom, when, and at what quality
Skill Evolution	How archetype skills grow through build activity
Convergence	9-stage convergence loop and deploy gates
Cost Governor	Token consumption, USD spend, and budget alerts
Deploy Watchdog	Deploy health, rollback history, failure tracking
Runbooks	Deploy, rollback, and incident response procedures
Monitoring	Worker health, Supabase status, R2 storage
Secrets	Wrangler secrets, env vars, rotation procedures
Database	Migrations, RLS verification, backup procedures