Frequently Asked Questions
Direct insights into the structural enforcement and auditability of GovenAI.
What system is the authority for governance decisions?
The GovenAI Registry is the authoritative system-of-record. It defines requirements and computes readiness; runtime systems consult it but cannot alter the governance state.
How does GovenAI prevent governance bypass?
Governance is enforced structurally at the database level using constraints and triggers. Bypassing these would require a direct database compromise rather than simple application misuse.
How are temporary exceptions managed?
Exceptions are managed via formally defined waivers with mandatory expiry. Database constraints prevent a waiver from remaining active beyond its timestamp, preventing "exception drift".
Is the audit trail mutable?
No. Audit records are append-only. UPDATE and DELETE operations are explicitly blocked at the database level by triggers, ensuring an immutable forensic record.
What is the performance impact of a "Gatekeeper" model?
Because GovenAI uses deterministic database lookups (optimized with CITEXT and indexing) rather than LLM calls, the "Permit or Deny" decision happens in milliseconds—orders of magnitude faster than the model inference itself.
Proof of Concept
Logic Validation Demonstration
Experience how the JobQue enforcer simulates a production gatekeeping event. This demo visualizes registry checks for PII access, rogue intent detection, and fail-closed behavior.
Run Enforcement Demo →
Note: This is a controlled simulation of registry logic, not a live operational environment.