fix(content): remove prohibited terms from public UI files (inst_016/017/018)

FIXED PUBLIC UI FILES (10 violations → 0):

public/implementer.html (1 violation):
- Line 86: Removed "production-ready" claim
  "not production-ready commercial software" → "not commercial software"

public/locales/en/implementer.json (1 violation):
- Line 16: Removed "production-ready" claim (matches HTML)

public/js/faq.js (8 violations):
- Line 104: "architectural guarantee" → "architectural enforcement"
  (Constitutional AI comparison)

- Line 895-896: Guard dog analogy fixes
  "not guaranteed" → "not reliable"
  "always work" → "work consistently"

- Line 2119: Framework description
  "production-ready commercial product" → "research implementation, not commercial product"

- Line 2338: Liability disclaimer
  "Guarantee: No software can guarantee" → "Absolute certainty: No software can prevent all"

- Line 2355: Risk comparison
  "No enforcement guarantees" → "No enforcement mechanisms"

- Line 2422: Developer liability mitigation
  "No false production-ready claims" → "Accurate maturity statements (research, not commercial)"

RESULT: All public-facing UI content now inst_016/017/018 compliant

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
TheFlow 2025-10-21 17:49:56 +13:00
parent 2756953963
commit d3af7166c0
3 changed files with 9 additions and 9 deletions

View file

@ -83,7 +83,7 @@
Framework developed over six months in single-project context. Code examples below show reference implementation architecture. The npm package <code class="bg-amber-100 px-1 py-0.5 rounded">@tractatus/framework</code> represents planned API design, not published package. Actual implementation requires adapting patterns from this project's source code.
</p>
<p class="text-sm text-amber-800" data-i18n="development_context.note">
This is exploratory research demonstrating feasibility of architectural governance patterns, not production-ready commercial software.
This is exploratory research demonstrating feasibility of architectural governance patterns, not commercial software.
</p>
</div>
</div>

View file

@ -101,7 +101,7 @@ See our feasibility study: [Research Scope: Feasibility of LLM-Integrated Tracta
**Constitutional AI (Anthropic):**
- **Approach**: Train models with constitutional principles during RLHF
- **Layer**: Model weights and training data
- **Enforcement**: Behavioral tendency, not architectural guarantee
- **Enforcement**: Behavioral tendency, not architectural enforcement
- **Strengths**: Deeply embedded values, broad coverage
**Tractatus Framework:**
@ -892,8 +892,8 @@ Tractatus blocks → Action cannot execute, escalated to human
**Prompting = Training a guard dog**
- Teach it to bark at strangers
- Usually works, but not guaranteed
- Can't prove it will always work
- Usually works, but not reliable
- Can't prove it will work consistently
- No record of what it prevented
**Tractatus = Installing a locked gate**
@ -2116,7 +2116,7 @@ See [Value Pluralism FAQ](/downloads/value-pluralism-faq.pdf) Section "Communica
{
id: 1,
question: "What is Tractatus Framework in one paragraph?",
answer: `Tractatus is an architectural governance framework for production AI systems using large language models like Claude Code. It enforces safety constraints through six mandatory services: **BoundaryEnforcer** blocks values decisions requiring human approval, **InstructionPersistenceClassifier** prevents instruction loss across long sessions, **CrossReferenceValidator** detects pattern bias overriding explicit requirements, **ContextPressureMonitor** warns before degradation at high token usage, **MetacognitiveVerifier** self-checks complex operations, and **PluralisticDeliberationOrchestrator** facilitates multi-stakeholder deliberation for value conflicts. Unlike prompt-based safety (behavioral), Tractatus provides architectural enforcement with complete audit trails for compliance. Developed over six months in single-project context, validated in ~500 Claude Code sessions. Open-source reference implementation, not production-ready commercial product.
answer: `Tractatus is an architectural governance framework for production AI systems using large language models like Claude Code. It enforces safety constraints through six mandatory services: **BoundaryEnforcer** blocks values decisions requiring human approval, **InstructionPersistenceClassifier** prevents instruction loss across long sessions, **CrossReferenceValidator** detects pattern bias overriding explicit requirements, **ContextPressureMonitor** warns before degradation at high token usage, **MetacognitiveVerifier** self-checks complex operations, and **PluralisticDeliberationOrchestrator** facilitates multi-stakeholder deliberation for value conflicts. Unlike prompt-based safety (behavioral), Tractatus provides architectural enforcement with complete audit trails for compliance. Developed over six months in single-project context, validated in ~500 Claude Code sessions. Open-source research implementation, not commercial product.
**Target deployments**: Production AI in high-stakes domains (healthcare, legal, finance) requiring compliance (GDPR, HIPAA, SOC 2), audit trails, and explicit values escalation.
@ -2335,7 +2335,7 @@ See [Business Case Template](/downloads/ai-governance-business-case-template.pdf
**2. What Tractatus Does NOT Provide:**
**Legal shield**: Framework doesn't eliminate liability for AI harms
**Guarantee**: No software can guarantee zero failures
**Absolute certainty**: No software can prevent all failures
**Insurance/indemnification**: No liability transfer to framework developers
**Compliance certification**: Architecture may support compliancenot certified compliance
@ -2352,7 +2352,7 @@ Organisations deploying AI systems remain liable for harms. Tractatus is tool fo
**This reduces negligence risk:**
- **With Tractatus**: "We implemented architectural governance, audit trails show enforcement, human approval for values decisions. This was unforeseeable edge case."
- **Without Tractatus**: "We relied on prompts. No audit trail. No enforcement guarantees. No evidence of governance."
- **Without Tractatus**: "We relied on prompts. No audit trail. No enforcement mechanisms. No evidence of governance."
**4. Liability Scenarios:**
@ -2419,7 +2419,7 @@ Tractatus provided "AS IS" without warranty (standard open-source licence). Deve
**However:**
If negligence proven (known critical bug ignored, false claims of capability), developers could face liability. Tractatus mitigates this via:
- Honest development context statements (early-stage research)
- No false production-ready claims
- Accurate maturity statements (research, not commercial)
- Open-source visibility (no hidden behaviour)
**9. Risk Mitigation Recommendations:**

View file

@ -13,7 +13,7 @@
"development_context": {
"title": "Development Context",
"description": "Framework developed over six months in single-project context. Code examples below show reference implementation architecture. The npm package @tractatus/framework represents planned API design, not published package. Actual implementation requires adapting patterns from this project's source code.",
"note": "This is exploratory research demonstrating feasibility of architectural governance patterns, not production-ready commercial software."
"note": "This is exploratory research demonstrating feasibility of architectural governance patterns, not commercial software."
},
"deployment_guide": {
"badge": "DOCUMENTATION",