diff --git a/public/index.html b/public/index.html index 411d9e58..1462cc2e 100644 --- a/public/index.html +++ b/public/index.html @@ -95,10 +95,10 @@
+
Governance that evolves with your organization—not compliance theatre, but architectural enforcement woven into deployment.
+
Six governance services coordinate, not operate in silos. When one detects an issue, others reinforce—creating resilient enforcement through mutual validation.
@@ -127,7 +127,7 @@+
Framework changes enhance without breaking. Audit logs remain interpretable, governance decisions stay valid—institutional memory preserved across evolution.
@@ -140,7 +140,7 @@+
Governance operates on intensity levels (NORMAL/ELEVATED/HIGH/CRITICAL), not yes/no switches. Nuanced response to risk—avoiding alert fatigue and mechanical enforcement.
@@ -153,7 +153,7 @@+
Framework evolves from real failures, not predetermined plans. Grows smarter through operational experience—adaptive resilience, not static rulebook.
@@ -166,7 +166,7 @@+
Governance woven into deployment architecture, not bolted on. Enforcement is structural, happening in the critical execution path before actions execute—bypasses require explicit flags and are logged.
@@ -175,16 +175,16 @@+
These principles guide every framework change—ensuring coherence, adaptability, and structural enforcement rather than compliance theatre.
+
Compliance theatre: Documented policies AI can bypass, post-execution monitoring, voluntary adherence.
-+
Architectural enforcement (Tractatus): Governance services intercept actions before execution in the critical path. Services coordinate in real-time, blocking non-compliant operations at the architectural level—bypasses require explicit --no-verify flags and are logged.