From 18835c4a4540d3cba66cef12eb67da9b7e2b2bc0 Mon Sep 17 00:00:00 2001 From: TheFlow Date: Thu, 30 Oct 2025 23:10:01 +1300 Subject: [PATCH] feat(i18n): enable language switching for Alexander sections on all 3 pages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Added data-i18n attributes to connect HTML content with existing translations, enabling language switching functionality. Pages updated: - public/index.html (homepage Alexander section) - public/researcher.html (research focus Alexander section) - public/leader.html (leadership Alexander section) Changes: - Added data-i18n attributes to all headings, titles, descriptions - Added data-i18n-html attributes for content with HTML formatting - Mapped to existing JSON translation keys in EN, DE, FR Total i18n keys connected: - Homepage: ~19 keys (alexander_principles.*) - Researcher: ~23 keys (alexander_research.*) - Leader: ~31 keys (alexander_leadership.*) Language switching now functional for Alexander principles content across all three pages. Users can select DE/FR to see translated content via language selector. Translations were completed in previous commit (61bcf0e), this commit connects HTML to enable runtime language switching. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- public/index.html | 12 ++++++------ public/leader.html | 34 +++++++++++++++++----------------- public/researcher.html | 34 +++++++++++++++++----------------- 3 files changed, 40 insertions(+), 40 deletions(-) diff --git a/public/index.html b/public/index.html index dc94d7e1..411d9e58 100644 --- a/public/index.html +++ b/public/index.html @@ -112,7 +112,7 @@
đź”—
-

Deep Interlock

+

Deep Interlock

Six governance services coordinate, not operate in silos. When one detects an issue, others reinforce—creating resilient enforcement through mutual validation. @@ -125,7 +125,7 @@

🏛️
-

Structure-Preserving

+

Structure-Preserving

Framework changes enhance without breaking. Audit logs remain interpretable, governance decisions stay valid—institutional memory preserved across evolution. @@ -138,7 +138,7 @@

đź“Š
-

Gradients Not Binary

+

Gradients Not Binary

Governance operates on intensity levels (NORMAL/ELEVATED/HIGH/CRITICAL), not yes/no switches. Nuanced response to risk—avoiding alert fatigue and mechanical enforcement. @@ -151,7 +151,7 @@

🌱
-

Living Process

+

Living Process

Framework evolves from real failures, not predetermined plans. Grows smarter through operational experience—adaptive resilience, not static rulebook. @@ -164,7 +164,7 @@

⚙️
-

Not-Separateness

+

Not-Separateness

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. @@ -174,7 +174,7 @@

-

Architectural Principles

+

Architectural Principles

These principles guide every framework change—ensuring coherence, adaptability, and structural enforcement rather than compliance theatre.

diff --git a/public/leader.html b/public/leader.html index 6c326a83..be0e5997 100644 --- a/public/leader.html +++ b/public/leader.html @@ -121,11 +121,11 @@
-

+

Why Architectural Governance Matters

- Built on living systems principles from Christopher Alexander—governance that evolves with your organization + Built on living systems principles from Christopher Alexander—governance that evolves with your organization

@@ -133,7 +133,7 @@
-

Strategic Differentiator: Not Compliance Theatre

+

Strategic Differentiator: Not Compliance Theatre

Compliance theatre relies on documented policies, training programs, and post-execution reviews. AI can bypass controls, enforcement is voluntary, and audit trails show what should happen, not what did happen.

@@ -142,7 +142,7 @@

-

Five Principles for Competitive Advantage

+

Five Principles for Competitive Advantage

@@ -150,66 +150,66 @@
1
-

Deep Interlock

+

Deep Interlock

Six governance services coordinate in real-time. When one detects risk, others reinforce—resilient enforcement through mutual validation, not isolated checks.

-

Business Value: Single service failure doesn't compromise governance. Redundant enforcement layer.

+

data-i18n-html="alexander_leadership.principles.deep_interlock.business_value">Business Value: Single service failure doesn't compromise governance. Redundant enforcement layer.

2
-

Structure-Preserving

+

Structure-Preserving

Framework changes maintain audit continuity. Historical governance decisions remain interpretable—institutional memory preserved across evolution.

-

Business Value: Regulatory audit trail remains valid. No "governance migration" breaking compliance records.

+

data-i18n-html="alexander_leadership.principles.structure_preserving.business_value">Business Value: Regulatory audit trail remains valid. No "governance migration" breaking compliance records.

3
-

Gradients Not Binary

+

Gradients Not Binary

Governance operates on intensity levels (NORMAL/ELEVATED/HIGH/CRITICAL)—nuanced response to risk, not mechanical yes/no.

-

Business Value: Avoids alert fatigue and over-enforcement. Matches governance intensity to actual risk level.

+

data-i18n-html="alexander_leadership.principles.gradients.business_value">Business Value: Avoids alert fatigue and over-enforcement. Matches governance intensity to actual risk level.

4
-

Living Process

+

Living Process

Framework evolves from operational failures, not predetermined plans. Adaptive resilience—learns from real incidents.

-

Business Value: Continuous improvement without governance migration. System gets smarter through use.

+

data-i18n-html="alexander_leadership.principles.living_process.business_value">Business Value: Continuous improvement without governance migration. System gets smarter through use.

5
-

Not-Separateness

+

Not-Separateness

Governance woven into deployment architecture, integrated into the critical execution path. Not bolt-on compliance layer—enforcement is structural.

-

Business Value: Bypasses require explicit flags and are logged. Enforcement happens before actions execute, not after.

+

data-i18n-html="alexander_leadership.principles.not_separateness.business_value">Business Value: Bypasses require explicit flags and are logged. Enforcement happens before actions execute, not after.

-

Regulatory Positioning

+

Regulatory Positioning

Regulators increasingly distinguish between documented governance (policies, training, aspirational frameworks) and demonstrated enforcement (architectural constraints with audit trails proving real-time operation).

@@ -220,10 +220,10 @@
- See Technical Architecture → + See Technical Architecture → - Values & Principles → + Values & Principles →
diff --git a/public/researcher.html b/public/researcher.html index 8f0f01f8..63b51240 100644 --- a/public/researcher.html +++ b/public/researcher.html @@ -141,60 +141,60 @@
-

+

Current Research Focus: Christopher Alexander Integration

- Integrated: October 2025 | Status: Monitoring for Effectiveness + Integrated: October 2025 | Status: Monitoring for Effectiveness

-

+

The framework has integrated five architectural principles from Christopher Alexander's work on living systems, pattern languages, and wholeness (The Timeless Way of Building, A Pattern Language, The Nature of Order). These principles now guide all framework evolution:

- Deep Interlock: Services coordinate through mutual validation, not isolated enforcement + Deep Interlock: Services coordinate through mutual validation, not isolated enforcement
- Structure-Preserving: Changes enhance without breaking—audit logs remain interpretable + Structure-Preserving: Changes enhance without breaking—audit logs remain interpretable
- Gradients Not Binary: Governance operates on intensity levels (NORMAL/ELEVATED/HIGH/CRITICAL) + Gradients Not Binary: Governance operates on intensity levels (NORMAL/ELEVATED/HIGH/CRITICAL)
- Living Process: Framework evolves from real operational failures, not predetermined plans + Living Process: Framework evolves from real operational failures, not predetermined plans
- Not-Separateness: Governance woven into deployment architecture—enforcement is structural + Not-Separateness: Governance woven into deployment architecture—enforcement is structural
-

+

Research Question: Can architectural principles from physical architecture domain (Alexander) be faithfully adapted to AI governance with measurable effectiveness? We are monitoring framework behavior through audit log analysis and seeking empirical validation.

-

Research Collaboration Opportunities

+

Research Collaboration Opportunities

    -
  • Effectiveness Measurement: Do Alexander principles improve governance outcomes compared to baseline? Access to 2,900+ audit decisions for quantitative analysis.
    • -
  • Scholarly Review: Validating faithful application of Alexander's work—are we "directly applying" or "loosely inspired by"? Seeking Christopher Alexander scholars for formal review.
    • -
  • Cross-Domain Validation: How do architectural principles (wholeness, living process, not-separateness) translate to non-physical domains? What constitutes rigorous adaptation vs superficial terminology borrowing?
    • -
  • Pattern Analysis: Audit logs show service coordination patterns—do they exhibit "deep interlock" as defined by Alexander? Empirical validation of theoretical constructs.
    • +
  • Effectiveness Measurement: Do Alexander principles improve governance outcomes compared to baseline? Access to 2,900+ audit decisions for quantitative analysis.
    • +
  • Scholarly Review: Validating faithful application of Alexander's work—are we "directly applying" or "loosely inspired by"? Seeking Christopher Alexander scholars for formal review.
    • +
  • Cross-Domain Validation: How do architectural principles (wholeness, living process, not-separateness) translate to non-physical domains? What constitutes rigorous adaptation vs superficial terminology borrowing?
    • +
  • Pattern Analysis: Audit logs show service coordination patterns—do they exhibit "deep interlock" as defined by Alexander? Empirical validation of theoretical constructs.
-

+

Collaborate with us: We welcome researchers interested in studying this application of architectural principles to AI governance. We can provide audit log access, framework code, and integration documentation for empirical study.

- + Contact for Collaboration → - + Values & Principles →