b72a274a4f
Translation Infrastructure: - Created 15 new translation files (en/de/fr) for 5 pages - Enhanced i18n-simple.js to auto-detect page names - Added page detection logic mapping URLs to translation files - Supports researcher, leader, implementer, about, faq pages Translation Files Created: English (en/): - researcher.json (research foundations, empirical observations) - leader.json (governance gap, architectural approach, EU AI Act) - implementer.json (integration approaches, quick start, deployment) - about.json (mission, values, origin story, license) - faq.json (search modal, browse by audience, tips) German (de/): - researcher.json (Forschungsgrundlagen, Empirische Beobachtungen) - leader.json (Governance-Lücke, Architektonischer Ansatz) - implementer.json (Integrationsansätze, Schnellstart) - about.json (Mission, Werte, Ursprungsgeschichte) - faq.json (Häufig gestellte Fragen) French (fr/): - researcher.json (Fondements de Recherche, Observations Empiriques) - leader.json (Lacune de Gouvernance, Approche Architecturale) - implementer.json (Approches d'Intégration, Démarrage Rapide) - about.json (Mission, Valeurs, Histoire d'Origine) - faq.json (Questions Fréquemment Posées) Technical Changes: - i18n-simple.js: Added detectPageName() method - Maps URL paths to translation file names - Loads page-specific translations automatically - researcher.html: Added data-i18n attributes to header section Language Selector: - Already deployed on all 6 pages (mobile icon-based design) - Now backed by full translation infrastructure - Switching languages loads correct page-specific translations Implementation Status: ✅ Translation files: Complete (15 files, ~350 translation keys) ✅ i18n system: Enhanced with page detection ✅ Proof of concept: Working on researcher.html ⏳ Full implementation: data-i18n attributes needed on remaining pages Next Steps for Full i18n: - Add data-i18n attributes to leader.html (~60 elements) - Add data-i18n attributes to implementer.html (~70 elements) - Add data-i18n attributes to about.html (~40 elements) - Add data-i18n attributes to faq.html (~30 elements) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
67 lines
4.3 KiB
JSON
67 lines
4.3 KiB
JSON
{
|
|
"page": {
|
|
"title": "For Decision-Makers | Tractatus AI Safety Framework",
|
|
"description": "Structural AI governance for organisations deploying LLM systems at scale. Research framework addressing architectural gaps in AI safety."
|
|
},
|
|
"header": {
|
|
"badge": "Research Framework • Early Development",
|
|
"title": "Tractatus: Architectural Governance for LLM Systems",
|
|
"subtitle": "A governance framework addressing structural gaps in AI safety through external architectural controls. Designed for organisations deploying large language models at scale where conventional oversight mechanisms prove insufficient."
|
|
},
|
|
"sections": {
|
|
"governance_gap": {
|
|
"heading": "The Governance Gap",
|
|
"intro": "Current AI governance approaches—policy documents, training programmes, ethical guidelines—rely on voluntary compliance. LLM systems can bypass these controls simply by not invoking them. When an AI agent needs to check a policy, it must choose to do so. When it should escalate a decision to human oversight, it must recognise that obligation.",
|
|
"problem": "This creates a structural problem: governance exists only insofar as the AI acknowledges it. For organisations subject to EU AI Act Article 14 (human oversight requirements) or deploying AI in high-stakes domains, this voluntary model is inadequate.",
|
|
"solution": "Tractatus explores whether governance can be made architecturally external—difficult to bypass not through better prompts, but through system design that places control points outside the AI's discretion."
|
|
},
|
|
"architectural_approach": {
|
|
"heading": "Architectural Approach",
|
|
"three_layer_title": "Three-Layer Architecture",
|
|
"services_title": "Six Governance Services"
|
|
},
|
|
"governance_capabilities": {
|
|
"heading": "Governance Capabilities",
|
|
"intro": "Three interactive demonstrations showing governance infrastructure in operation. These show mechanisms, not fictional scenarios.",
|
|
"audit_trail_title": "Audit Trail & Compliance Evidence Generation",
|
|
"audit_trail_desc": "Immutable logging, evidence extraction, regulatory reporting",
|
|
"continuous_improvement_title": "Continuous Improvement: Incident → Rule Creation",
|
|
"continuous_improvement_desc": "Learning from failures, automated rule generation, validation",
|
|
"pluralistic_deliberation_title": "Pluralistic Deliberation: Values Conflict Resolution",
|
|
"pluralistic_deliberation_desc": "Multi-stakeholder engagement, non-hierarchical process, moral remainder documentation"
|
|
},
|
|
"development_status": {
|
|
"heading": "Development Status",
|
|
"warning_title": "Early-Stage Research Framework",
|
|
"warning_text": "Tractatus is a proof-of-concept developed over six months in a single project context (this website). It demonstrates architectural patterns for AI governance but has not undergone independent validation, red-team testing, or multi-organisation deployment.",
|
|
"validation_title": "Validated vs. Not Validated"
|
|
},
|
|
"eu_ai_act": {
|
|
"heading": "EU AI Act Considerations",
|
|
"article_14_title": "Regulation 2024/1689, Article 14: Human Oversight"
|
|
},
|
|
"research_foundations": {
|
|
"heading": "Research Foundations",
|
|
"org_theory_title": "Organisational Theory & Philosophical Basis"
|
|
},
|
|
"scope_limitations": {
|
|
"heading": "Scope & Limitations",
|
|
"title": "What This Is Not • What It Offers",
|
|
"not_title": "Tractatus is not:",
|
|
"offers_title": "What it offers:"
|
|
}
|
|
},
|
|
"footer": {
|
|
"further_info": "Further Information",
|
|
"technical_docs": "Technical Documentation",
|
|
"technical_docs_desc": "Complete architecture specifications, implementation patterns, API reference",
|
|
"system_architecture": "System Architecture",
|
|
"system_architecture_desc": "Runtime-agnostic governance layer design and integration approach",
|
|
"research_case_studies": "Research & Case Studies",
|
|
"research_case_studies_desc": "Academic foundations, failure mode analysis, governance research",
|
|
"implementation_guide": "Implementation Guide",
|
|
"implementation_guide_desc": "Integration patterns, deployment considerations, code examples",
|
|
"contact": "Contact:",
|
|
"contact_text": "For pilot partnerships, validation studies, or technical consultation, contact via"
|
|
}
|
|
}
|