john/tractatus
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(homepage): correct compliance violations (inst_017, inst_087)

Browse source 
Fixed 3 violations identified via ff framework audit:

1. Line 170: Changed "Cannot be bypassed" to evidence-based
   language acknowledging bypass flags exist but are logged

2. Line 210: Changed "technically impossible to bypass" to
   accurate description of architectural enforcement with
   explicit acknowledgment of --no-verify bypass mechanism

3. Line 319: Removed consultant language "best practices",
   replaced with specific "deployment patterns & operational
   procedures"

All changes maintain messaging integrity while complying with:
- inst_017: No absolute assurance terms
- inst_087: No consultant language
- inst_088: Candid about limitations

🔍 Framework Audit: audit_6903324e906599d519c8aae2
✅ Prohibited terms check: passed

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
TheFlow 2025-10-30 22:40:05 +13:00
parent 6be9db0d70
commit fc9b9510a8
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
public/index.html
View file

@ -167,7 +167,7 @@
<h3 class="text-lg font-bold text-gray-900">Not-Separateness</h3>
</div>
<p class="text-gray-700 text-sm leading-relaxed">
Governance <strong>woven into deployment architecture</strong>, not bolted on. Cannot be bypassed—enforcement is structural, happening in critical execution path before actions execute.
Governance <strong>woven into deployment architecture</strong>, not bolted on. Enforcement is structural, happening in the critical execution path before actions execute—bypasses require explicit flags and are logged.
</p>
</div>
@ -207,7 +207,7 @@
<strong>Compliance theatre</strong>: Documented policies AI can bypass, post-execution monitoring, voluntary adherence.
</p>
<p class="text-gray-700 leading-relaxed">
<strong>Architectural enforcement</strong> (Tractatus): Governance services intercept actions <em>before execution</em>—technically impossible to bypass. Services coordinate in real-time, blocking non-compliant operations at the architectural level.
<strong>Architectural enforcement</strong> (Tractatus): Governance services intercept actions <em>before execution</em> 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.
</p>
</div>
</div>
@ -316,7 +316,7 @@ Get hands-on with implementation guides, API documentation, and reference code e
</li>
<li class="flex items-start">
<svg aria-hidden="true" class="w-5 h-5 mr-2 mt-0.5 flex-shrink-0" class="text-service-instruction" fill="currentColor" viewBox="0 0 20 20"><path fill-rule="evenodd" d="M10 18a8 8 0 100-16 8 8 0 000 16zm3.707-9.293a1 1 0 00-1.414-1.414L9 10.586 7.707 9.293a1 1 0 00-1.414 1.414l2 2a1 1 0 001.414 0l4-4z"/></svg>
<span class="text-gray-700" data-i18n="paths.implementer.features.3">Deployment best practices</span>
<span class="text-gray-700" data-i18n="paths.implementer.features.3">Deployment patterns & operational procedures</span>
</li>
</ul>