From a85505bc4fa6498bf6b6314851da6fa7118f7d1f Mon Sep 17 00:00:00 2001 From: TheFlow Date: Thu, 30 Oct 2025 23:26:13 +1300 Subject: [PATCH] fix(i18n): add missing data-i18n-html attributes to leader.html Alexander section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed malformed and missing i18n attributes: 1. Corrected malformed business_value attributes that appeared as text instead of proper HTML attributes (5 instances) 2. Added missing description attributes for all 5 principles 3. Added missing differentiator paragraph attributes (compliance_theatre, architectural_enforcement) 4. Added missing regulatory section paragraph attributes (intro, conclusion) Total: 26 i18n attributes now properly configured for full French/German translation support on leader page. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- public/leader.html | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/public/leader.html b/public/leader.html index be0e5997..63dd570a 100644 --- a/public/leader.html +++ b/public/leader.html @@ -134,10 +134,10 @@

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.

-

+

Architectural enforcement (Tractatus) weaves governance into deployment architecture. Services intercept actions before execution in the critical path—bypasses require explicit --no-verify flags and are logged. Audit trails prove real-time enforcement, not aspirational policy.

@@ -152,10 +152,10 @@
1

Deep Interlock

-

+

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

-

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

+

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

@@ -164,10 +164,10 @@
2

Structure-Preserving

-

+

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

-

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

+

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

@@ -176,10 +176,10 @@
3

Gradients Not Binary

-

+

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

-

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

+

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

@@ -188,10 +188,10 @@
4

Living Process

-

+

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

-

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

+

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

@@ -200,20 +200,20 @@
5

Not-Separateness

-

+

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

-

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.

+

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

Regulatory Positioning

-

+

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

-

+

Tractatus provides audit evidence of: (1) Governance services operating in critical path, (2) Actions blocked before execution, (3) Historical continuity of enforcement. This positions your organization ahead of "we have policies" baseline.