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>
59 lines
3.9 KiB
JSON
59 lines
3.9 KiB
JSON
{
|
||
"page": {
|
||
"title": "For Researchers | Tractatus AI Safety Framework",
|
||
"description": "Research foundations, empirical observations, and theoretical basis for architectural approaches to AI governance. Early-stage framework exploring structural constraints on LLM systems."
|
||
},
|
||
"header": {
|
||
"badge": "Research Framework • Empirical Observations",
|
||
"title": "Research Foundations & Empirical Observations",
|
||
"subtitle": "Tractatus explores architectural approaches to AI governance through empirical observation of failure modes and application of organisational theory. This page documents research foundations, observed patterns, and theoretical basis for the framework."
|
||
},
|
||
"sections": {
|
||
"research_context": {
|
||
"heading": "Research Context & Scope",
|
||
"development_note": "Development Context",
|
||
"development_text": "Tractatus was developed over six months (April–October 2025) in progressive stages that evolved into a live demonstration of its capabilities in the form of a single-project context (https://agenticgovernance.digital). Observations derive from direct engagement with Claude Code (Anthropic's Sonnet 4.5 model) across approximately 500 development sessions. This is exploratory research, not controlled study."
|
||
},
|
||
"theoretical_foundations": {
|
||
"heading": "Theoretical Foundations",
|
||
"org_theory_title": "Organisational Theory Basis",
|
||
"values_pluralism_title": "Values Pluralism & Moral Philosophy"
|
||
},
|
||
"empirical_observations": {
|
||
"heading": "Empirical Observations: Documented Failure Modes",
|
||
"intro": "Three failure patterns observed repeatedly during framework development. These are not hypothetical scenarios—they are documented incidents that occurred during this project's development.",
|
||
"failure_1_title": "Pattern Recognition Bias Override (The 27027 Incident)",
|
||
"failure_2_title": "Gradual Values Drift Under Context Pressure",
|
||
"failure_3_title": "Silent Quality Degradation at High Context Pressure",
|
||
"research_note": "These patterns emerged from direct observation, not hypothesis testing. We don't claim they're universal to all LLM systems or deployment contexts. They represent empirical basis for framework design decisions—problems we actually encountered and architectural interventions that actually worked in this specific context."
|
||
},
|
||
"architecture": {
|
||
"heading": "Six-Component Architecture",
|
||
"services_title": "Framework Services & Functions",
|
||
"principle": "Services operate external to AI runtime with autonomous triggering. AI doesn't decide \"should I check governance rules?\"—architecture enforces checking by default. This addresses voluntary compliance problem inherent in prompt-based governance."
|
||
},
|
||
"demos": {
|
||
"heading": "Interactive Demonstrations",
|
||
"classification_title": "Instruction Classification",
|
||
"classification_desc": "Explore how instructions are classified across quadrants with persistence levels and temporal scope.",
|
||
"incident_title": "27027 Incident Timeline",
|
||
"incident_desc": "Step through pattern recognition bias failure and architectural intervention that prevented it.",
|
||
"boundary_title": "Boundary Evaluation",
|
||
"boundary_desc": "Test decisions against boundary enforcement to see which require human judgment vs. AI autonomy."
|
||
},
|
||
"resources": {
|
||
"heading": "Research Documentation"
|
||
},
|
||
"limitations": {
|
||
"heading": "Limitations & Future Research Directions",
|
||
"title": "Known Limitations & Research Gaps"
|
||
}
|
||
},
|
||
"footer": {
|
||
"additional_resources": "Additional Resources",
|
||
"for_decision_makers": "For Decision-Makers",
|
||
"for_decision_makers_desc": "Strategic perspective on governance challenges and architectural approaches",
|
||
"implementation_guide": "Implementation Guide",
|
||
"implementation_guide_desc": "Technical integration patterns and deployment considerations"
|
||
}
|
||
}
|