GovAI System Diagram

System data flow

From client emission to export and replay verification.

Pause

1. 1Client / CISDK, CLI, GitHub Action
2. 2EvidencePOST /evidence append
3. 3PolicyEvaluation + verdict projection
4. 4VerdictVALID · INVALID · BLOCKED
5. 5Export & verifyBundle hash + replay checks

System components

Edge

Governance clients

SDK, CLI, GitHub Action, customer CI.

Core

Audit HTTP API

Rust aigov_audit — evidence, compliance-summary, export.

Storage

Audit ledger

Append-only hash chain in Postgres or file ledger.

Evaluation

Policy engine

policy_version drives VALID / INVALID / BLOCKED.

Enterprise

Dashboard

Next.js operator UI, JWT routes, docs/help surfaces.

Read APIs

Functions 2.0

Flight pack, executive summary — not a second verdict.

Developer or Runtime System -> GovAI SDK / CLI -> Evidence Collection -> Policy Evaluation -> VALID / INVALID / BLOCKED verdict

VALID -> allow progression

INVALID -> reject decision

BLOCKED -> fail closed

Policy Evaluation -> Audit Ledger -> Evidence Export -> Replay Verification

AI Decision Flight Recorder (GovAI Functions 2.0) -> Append-only trace events in Postgres (hash chain) -> Extended governance telemetry (approvals, appeals, incidents, monitoring, seals, legal refs, certification) -> Read APIs: flight-pack, executive-summary, legal-evidence-manifest, governance-scorecard -> Authoritative ledger verdict still from GET /compliance-summary

Additional inputs:

• CI/CD pipelines
• Runtime Governance API
• Human approval flows
• Policy packs