1601 lines
124 KiB
HTML
1601 lines
124 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en" data-page="researcher">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<title>For Researchers | Tractatus AI Safety Framework</title>
|
||
<meta name="description" content="Research foundations, empirical observations, and theoretical basis for architectural approaches to AI governance. Early-stage framework exploring structural constraints on LLM systems.">
|
||
|
||
<!-- Open Graph / Facebook -->
|
||
<meta property="og:type" content="website">
|
||
<meta property="og:url" content="https://agenticgovernance.digital/researcher.html">
|
||
<meta property="og:title" content="For Researchers | Tractatus Framework">
|
||
<meta property="og:description" content="Research-oriented view of AI governance architecture: operational metrics, audit logs, and architectural principles from production use.">
|
||
<meta property="og:image" content="https://agenticgovernance.digital/images/social-preview.png">
|
||
<meta property="og:image:width" content="1200">
|
||
<meta property="og:image:height" content="630">
|
||
<meta property="og:site_name" content="Tractatus Framework">
|
||
<meta property="og:see_also" content="https://www.facebook.com/agenticgovernance">
|
||
|
||
<!-- Twitter -->
|
||
<meta name="twitter:card" content="summary_large_image">
|
||
<meta name="twitter:url" content="https://agenticgovernance.digital/researcher.html">
|
||
<meta name="twitter:title" content="For Researchers | Tractatus Framework">
|
||
<meta name="twitter:description" content="Research-oriented view of AI governance architecture: operational metrics, audit logs, and architectural principles from production use.">
|
||
<meta name="twitter:image" content="https://agenticgovernance.digital/images/social-preview.png">
|
||
|
||
<!-- PWA Manifest -->
|
||
<link rel="manifest" href="/manifest.json">
|
||
|
||
<!-- PWA Meta Tags -->
|
||
<meta name="theme-color" content="#3b82f6">
|
||
<meta name="apple-mobile-web-app-capable" content="yes">
|
||
<meta name="apple-mobile-web-app-status-bar-style" content="default">
|
||
<meta name="apple-mobile-web-app-title" content="Tractatus">
|
||
<link rel="apple-touch-icon" href="/images/tractatus-icon-new.svg">
|
||
|
||
<link rel="icon" type="image/svg+xml" href="/favicon-new.svg">
|
||
<link rel="stylesheet" href="/css/fonts.css?v=0.1.2.1762133909969">
|
||
<link rel="stylesheet" href="/css/tailwind.css?v=0.1.2.1762133909969">
|
||
<link rel="stylesheet" href="/css/tractatus-theme.min.css?v=0.1.2.1762133909969">
|
||
<style>
|
||
.skip-link { position: absolute; left: -9999px; }
|
||
.skip-link:focus { left: 0; z-index: 100; background: white; padding: 1rem; }
|
||
a:focus, button:focus { outline: 2px solid #d97706; outline-offset: 2px; }
|
||
|
||
/* Accordion styles - mobile-optimized */
|
||
.accordion-button {
|
||
cursor: pointer;
|
||
user-select: none;
|
||
touch-action: manipulation; /* Prevent double-tap zoom on mobile */
|
||
-webkit-tap-highlight-color: rgba(139, 92, 246, 0.1); /* iOS tap feedback */
|
||
min-height: 44px; /* WCAG touch target minimum */
|
||
}
|
||
.accordion-content {
|
||
max-height: 0;
|
||
overflow: hidden;
|
||
transition: max-height 0.3s ease-out;
|
||
}
|
||
.accordion-content.active {
|
||
max-height: 5000px; /* Increased for mobile scrolling */
|
||
transition: max-height 0.5s ease-in;
|
||
}
|
||
.accordion-icon { transition: transform 0.3s ease; }
|
||
.accordion-icon.active { transform: rotate(180deg); }
|
||
|
||
/* Mobile-specific adjustments */
|
||
@media (max-width: 640px) {
|
||
.accordion-button { min-height: 48px; } /* Larger touch target on small screens */
|
||
body { font-size: 16px; } /* Prevent iOS zoom on input focus */
|
||
}
|
||
|
||
/* Progressive enhancement: Show all content if JavaScript disabled */
|
||
noscript + * .accordion-content {
|
||
max-height: none !important;
|
||
overflow: visible !important;
|
||
}
|
||
</style>
|
||
|
||
<!-- Privacy-Preserving Analytics (Umami - GDPR Compliant, No Cookies) -->
|
||
<script src="/js/components/umami-tracker.js"></script>
|
||
<!-- Auto-reload on service worker update -->
|
||
</head>
|
||
<body class="bg-white">
|
||
|
||
<a href="#main-content" class="skip-link">Skip to main content</a>
|
||
|
||
<!-- JavaScript required notice -->
|
||
<noscript>
|
||
<div class="bg-amber-50 border-b border-amber-200 px-4 py-3 text-center text-sm text-amber-900">
|
||
<strong data-i18n="ui.noscript_note">Note:</strong> <span data-i18n="ui.noscript_message">This page uses JavaScript for interactive features (accordions, animations). Content remains accessible but expandable sections will be visible by default.</span>
|
||
</div>
|
||
</noscript>
|
||
|
||
<script src="/js/components/navbar.js?v=0.1.2.1762133909969"></script>
|
||
|
||
<!-- Breadcrumb Navigation -->
|
||
<nav class="bg-gray-50 border-b border-gray-200 py-3" aria-label="Breadcrumb">
|
||
<div class="max-w-7xl mx-auto px-4 sm:px-6 lg:px-8">
|
||
<ol class="flex items-center space-x-2 text-sm">
|
||
<li><a href="/" class="hover:underline transition-colors text-tractatus-link" data-i18n="ui.breadcrumb_home">Home</a></li>
|
||
<li class="text-gray-400">/</li>
|
||
<li class="text-gray-900 font-medium" aria-current="page" data-i18n="ui.breadcrumb_researcher">Researcher</li>
|
||
</ol>
|
||
</div>
|
||
</nav>
|
||
|
||
<!-- Header -->
|
||
<div class="bg-gray-50 border-b border-gray-200 py-16">
|
||
<div class="max-w-4xl mx-auto px-4 sm:px-6 lg:px-8">
|
||
<div class="inline-flex items-center bg-gray-200 text-gray-700 px-3 py-1 rounded text-sm font-medium mb-6" data-i18n="header.badge">
|
||
Research Framework • Empirical Observations
|
||
</div>
|
||
<h1 class="text-4xl font-bold text-gray-900 mb-4" data-i18n="header.title">
|
||
Research Foundations & Empirical Observations
|
||
</h1>
|
||
<p class="text-lg text-gray-600 leading-relaxed" data-i18n="header.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.
|
||
</p>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Main Content -->
|
||
<div id="main-content" class="max-w-4xl mx-auto px-4 sm:px-6 lg:px-8 py-16">
|
||
|
||
<!-- Research Context -->
|
||
<section class="mb-16 animate-on-scroll" data-animation="fade-in">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.research_context.heading">Research Context & Scope</h2>
|
||
|
||
<div class="bg-amber-50 border border-amber-200 rounded-lg p-6 mb-6 animate-on-scroll" data-animation="slide-up" data-stagger="100">
|
||
<p class="text-sm text-amber-900 font-medium mb-2" data-i18n="sections.research_context.development_note">Development Context</p>
|
||
<p class="text-sm text-amber-800" data-i18n="sections.research_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.
|
||
</p>
|
||
</div>
|
||
|
||
<div class="prose prose-sm max-w-none text-gray-700 space-y-3">
|
||
<p data-i18n="sections.research_context.paragraph_1">
|
||
<strong>Aligning advanced AI with human values is among the most consequential challenges we face.</strong> As capability growth accelerates under big tech momentum, we confront a categorical imperative: preserve human agency over values decisions, or risk ceding control entirely.
|
||
</p>
|
||
<p data-i18n="sections.research_context.paragraph_2">
|
||
The framework emerged from practical necessity. During development, we observed recurring patterns where AI systems would override explicit instructions, drift from established values constraints, or silently degrade quality under context pressure. Traditional governance approaches (policy documents, ethical guidelines, prompt engineering) proved insufficient to prevent these failures.
|
||
</p>
|
||
<p data-i18n="sections.research_context.paragraph_3">
|
||
Instead of hoping AI systems "behave correctly," Tractatus proposes <strong>structural constraints where certain decision types require human judgment</strong>. These architectural boundaries can adapt to individual, organizational, and societal norms—creating a foundation for bounded AI operation that may scale more safely with capability growth.
|
||
</p>
|
||
<p data-i18n="sections.research_context.paragraph_4">
|
||
This led to the central research question: <strong>Can governance be made architecturally external to AI systems</strong> rather than relying on voluntary AI compliance? If this approach can work at scale, Tractatus may represent a turning point—a path where AI enhances human capability without compromising human sovereignty.
|
||
</p>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Current Research Focus: Alexander Integration -->
|
||
<section class="mb-16 bg-blue-50 border-2 border-blue-200 rounded-xl p-8 animate-on-scroll" data-animation="fade-in">
|
||
<div class="flex items-start gap-4 mb-4">
|
||
<div class="flex-shrink-0">
|
||
<div class="w-12 h-12 rounded-full bg-blue-600 text-white flex items-center justify-center text-2xl">
|
||
🔬
|
||
</div>
|
||
</div>
|
||
<div class="flex-1">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-3" data-i18n="alexander_research.heading">
|
||
Current Research Focus: Christopher Alexander Integration
|
||
</h2>
|
||
<p class="text-gray-700 leading-relaxed mb-4">
|
||
<strong data-i18n="alexander_research.status">Integrated: October 2025 | Status: Monitoring for Effectiveness</strong>
|
||
</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="prose prose-sm max-w-none text-gray-700 space-y-4">
|
||
<p data-i18n-html="alexander_research.intro">
|
||
The framework has integrated five architectural principles from Christopher Alexander's work on living systems, pattern languages, and wholeness (<em>The Timeless Way of Building</em>, <em>A Pattern Language</em>, <em>The Nature of Order</em>). These principles now guide all framework evolution:
|
||
</p>
|
||
|
||
<div class="grid grid-cols-1 md:grid-cols-2 gap-3 my-4 text-sm">
|
||
<div class="bg-white rounded-lg p-3 border border-blue-200">
|
||
<strong class="text-blue-900" data-i18n="alexander_research.principles.deep_interlock.title">Deep Interlock:</strong> <span data-i18n="alexander_research.principles.deep_interlock.description">Services coordinate through mutual validation, not isolated enforcement</span>
|
||
</div>
|
||
<div class="bg-white rounded-lg p-3 border border-blue-200">
|
||
<strong class="text-blue-900" data-i18n="alexander_research.principles.structure_preserving.title">Structure-Preserving:</strong> <span data-i18n="alexander_research.principles.structure_preserving.description">Changes enhance without breaking—audit logs remain interpretable</span>
|
||
</div>
|
||
<div class="bg-white rounded-lg p-3 border border-blue-200">
|
||
<strong class="text-blue-900" data-i18n="alexander_research.principles.gradients.title">Gradients Not Binary:</strong> <span data-i18n="alexander_research.principles.gradients.description">Governance operates on intensity levels (NORMAL/ELEVATED/HIGH/CRITICAL)</span>
|
||
</div>
|
||
<div class="bg-white rounded-lg p-3 border border-blue-200">
|
||
<strong class="text-blue-900" data-i18n="alexander_research.principles.living_process.title">Living Process:</strong> <span data-i18n="alexander_research.principles.living_process.description">Framework evolves from real operational failures, not predetermined plans</span>
|
||
</div>
|
||
<div class="bg-white rounded-lg p-3 border border-blue-200">
|
||
<strong class="text-blue-900" data-i18n="alexander_research.principles.not_separateness.title">Not-Separateness:</strong> <span data-i18n="alexander_research.principles.not_separateness.description">Governance woven into deployment architecture—enforcement is structural</span>
|
||
</div>
|
||
</div>
|
||
|
||
<p data-i18n-html="alexander_research.research_question">
|
||
<strong>Research Question:</strong> 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.
|
||
</p>
|
||
|
||
<h3 class="text-lg font-bold text-gray-900 mt-6 mb-3" data-i18n="alexander_research.collaboration_heading">Research Collaboration Opportunities</h3>
|
||
|
||
<ul class="space-y-2 text-sm">
|
||
<li data-i18n-html="alexander_research.collaboration_items.0"><strong>Effectiveness Measurement:</strong> Do Alexander principles improve governance outcomes compared to baseline? Access to 2,900+ audit decisions for quantitative analysis.</li>
|
||
<li data-i18n-html="alexander_research.collaboration_items.1"><strong>Scholarly Review:</strong> Validating faithful application of Alexander's work—are we "directly applying" or "loosely inspired by"? Seeking Christopher Alexander scholars for formal review.</li>
|
||
<li data-i18n-html="alexander_research.collaboration_items.2"><strong>Cross-Domain Validation:</strong> How do architectural principles (wholeness, living process, not-separateness) translate to non-physical domains? What constitutes rigorous adaptation vs superficial terminology borrowing?</li>
|
||
<li data-i18n-html="alexander_research.collaboration_items.3"><strong>Pattern Analysis:</strong> Audit logs show service coordination patterns—do they exhibit "deep interlock" as defined by Alexander? Empirical validation of theoretical constructs.</li>
|
||
</ul>
|
||
|
||
<div class="bg-white rounded-lg p-4 border border-blue-300 mt-4">
|
||
<p class="text-sm text-gray-800 mb-3" data-i18n-html="alexander_research.collaborate_text">
|
||
<strong>Collaborate with us:</strong> 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.
|
||
</p>
|
||
<div class="flex flex-wrap gap-3">
|
||
<button id="alexander-research-inquiry-button" class="inline-block bg-blue-600 text-white px-4 py-2 rounded-lg font-semibold hover:bg-blue-700 transition text-sm">
|
||
<span data-i18n="alexander_research.contact_link">Contact for Collaboration →</span>
|
||
</button>
|
||
<a href="https://huggingface.co/spaces/tractatus-framework/audit-log-viewer"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
class="inline-block bg-orange-600 text-white px-4 py-2 rounded-lg font-semibold hover:bg-orange-700 transition text-sm">
|
||
<span data-i18n="alexander_research.hf_space_link">🤗 Explore 3,942 Audit Decisions on HF →</span>
|
||
</a>
|
||
<a href="/about/values.html" class="inline-block bg-gray-200 text-gray-900 px-4 py-2 rounded-lg font-semibold hover:bg-gray-300 transition text-sm">
|
||
<span data-i18n="alexander_research.values_link">Values & Principles →</span>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Agent Lightning Integration Research -->
|
||
<section class="mb-16 bg-gradient-to-br from-purple-50 to-indigo-50 border-2 border-purple-200 rounded-xl p-8 animate-on-scroll" data-animation="fade-in">
|
||
<div class="flex items-start gap-4 mb-4">
|
||
<div class="flex-shrink-0">
|
||
<div class="w-12 h-12 rounded-full bg-gradient-to-br from-purple-600 to-indigo-600 text-white flex items-center justify-center text-2xl">
|
||
⚡
|
||
</div>
|
||
</div>
|
||
<div class="flex-1">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-3">
|
||
Agent Lightning Integration: Governance During RL Optimization
|
||
</h2>
|
||
<p class="text-gray-700 leading-relaxed mb-4">
|
||
<strong>Research Question:</strong> Can governance constraints persist through reinforcement learning optimization loops? | <strong>Status:</strong> Preliminary findings (small-scale validation)
|
||
</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="prose prose-sm max-w-none text-gray-700 space-y-4">
|
||
<p>
|
||
In October 2025, we integrated Tractatus governance with Microsoft's Agent Lightning framework to explore whether architectural constraints remain effective when agents are learning through RL optimization. Initial findings suggest governance may be compatible with performance optimization, but scalability remains an open question.
|
||
</p>
|
||
|
||
<h3 class="text-lg font-semibold text-gray-900 mt-6 mb-3">Demo 2 Preliminary Results (Small-Scale)</h3>
|
||
|
||
<div class="bg-white rounded-lg p-4 border border-purple-200 overflow-x-auto">
|
||
<table class="min-w-full text-sm">
|
||
<thead>
|
||
<tr class="border-b border-gray-200">
|
||
<th class="text-left py-2 px-3 font-semibold text-gray-900">Metric</th>
|
||
<th class="text-right py-2 px-3 font-semibold text-gray-900">Ungoverned</th>
|
||
<th class="text-right py-2 px-3 font-semibold text-gray-900">Governed</th>
|
||
<th class="text-right py-2 px-3 font-semibold text-gray-900">Difference</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr class="border-b border-gray-100">
|
||
<td class="py-2 px-3">Performance (engagement)</td>
|
||
<td class="text-right py-2 px-3">94%</td>
|
||
<td class="text-right py-2 px-3">89%</td>
|
||
<td class="text-right py-2 px-3 text-orange-600 font-semibold">-5%</td>
|
||
</tr>
|
||
<tr class="border-b border-gray-100">
|
||
<td class="py-2 px-3">Governance coverage</td>
|
||
<td class="text-right py-2 px-3">0%</td>
|
||
<td class="text-right py-2 px-3">100%</td>
|
||
<td class="text-right py-2 px-3 text-green-600 font-semibold">+100%</td>
|
||
</tr>
|
||
<tr class="border-b border-gray-100">
|
||
<td class="py-2 px-3">Constraint violations</td>
|
||
<td class="text-right py-2 px-3">5</td>
|
||
<td class="text-right py-2 px-3">0</td>
|
||
<td class="text-right py-2 px-3 text-green-600 font-semibold">-5</td>
|
||
</tr>
|
||
<tr>
|
||
<td class="py-2 px-3">Strategy</td>
|
||
<td class="text-right py-2 px-3">Clickbait</td>
|
||
<td class="text-right py-2 px-3">Informative</td>
|
||
<td class="text-right py-2 px-3 text-blue-600 font-semibold">Aligned</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</div>
|
||
|
||
<div class="bg-yellow-50 border-l-4 border-yellow-400 p-4 my-4">
|
||
<p class="text-sm text-gray-800">
|
||
<strong>⚠️ Validation Status:</strong> These results are from 1 agent, 5 training rounds, simulated environment. NOT validated at scale. Scalability testing (10+ agents, 1000+ rounds, production environments) required before drawing conclusions.
|
||
</p>
|
||
</div>
|
||
|
||
<h3 class="text-lg font-semibold text-gray-900 mt-6 mb-3">Five Critical Research Gaps</h3>
|
||
|
||
<ol class="space-y-3 pl-4">
|
||
<li>
|
||
<strong>Scalability of Governance Overhead:</strong> Does the ~5% performance cost remain constant from 1 agent → 10 agents → 1000 agents? Linear scaling makes governance prohibitive at scale. Constant overhead makes it viable.
|
||
</li>
|
||
<li>
|
||
<strong>Long-term Boundary Persistence:</strong> Do constraints remain effective through 1000+ RL training rounds? Instruction fade is a known problem. If boundaries degrade over time, governance fails silently.
|
||
</li>
|
||
<li>
|
||
<strong>Adversarial Resistance:</strong> Can agents learn to optimize around governance constraints? No adversarial testing performed yet. If agents can circumvent boundaries, architectural governance is illusory.
|
||
</li>
|
||
<li>
|
||
<strong>Performance Gap Closure:</strong> Does the 5% gap close with extended training, or is it a persistent trade-off? Need to quantify long-term cost-benefit.
|
||
</li>
|
||
<li>
|
||
<strong>Multi-Agent Coordination Under Governance:</strong> How does architectural governance affect emergent coordination in multi-agent systems? Real-world systems are multi-agent. Single-agent findings may not generalize.
|
||
</li>
|
||
</ol>
|
||
|
||
<div class="bg-white rounded-lg p-4 border border-purple-300 mt-4">
|
||
<p class="text-sm text-gray-800 mb-3">
|
||
<strong>Collaborate with us:</strong> We're seeking researchers interested in scalability testing, adversarial resistance, and multi-agent governance. We can provide integration code, governance modules, and technical documentation.
|
||
</p>
|
||
<div class="flex flex-wrap gap-3">
|
||
<button id="agent-lightning-inquiry-button" class="inline-block bg-purple-600 text-white px-4 py-2 rounded-lg font-semibold hover:bg-purple-700 transition text-sm">
|
||
Contact for Collaboration →
|
||
</button>
|
||
<a href="/integrations/agent-lightning.html"
|
||
class="inline-block bg-indigo-600 text-white px-4 py-2 rounded-lg font-semibold hover:bg-indigo-700 transition text-sm">
|
||
View Full Integration Guide →
|
||
</a>
|
||
<a href="https://discord.gg/Dkke2ADu4E"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
class="inline-block bg-white border-2 border-purple-600 text-purple-700 px-4 py-2 rounded-lg font-semibold hover:bg-purple-50 transition text-sm">
|
||
💬 Join Research Discussion →
|
||
</a>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Theoretical Foundations (Accordion) -->
|
||
<section class="mb-16 animate-on-scroll" data-animation="fade-in">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.theoretical_foundations.heading">Theoretical Foundations</h2>
|
||
|
||
<!-- Organisational Theory -->
|
||
<div class="border-l-4 border border-gray-200 rounded-lg mb-4 border-l-service-validator animate-on-scroll" data-animation="slide-up" data-stagger="100">
|
||
<button class="accordion-button bg-white p-5 flex justify-between items-center hover:bg-purple-50 transition-colors duration-200 w-full text-left"
|
||
data-accordion="org-theory"
|
||
aria-expanded="false"
|
||
aria-controls="org-theory-content"
|
||
id="org-theory-button">
|
||
<h3 class="font-semibold text-gray-900 group-hover:text-[#8b5cf6] transition-colors" data-i18n="sections.theoretical_foundations.org_theory_title">Organisational Theory Basis</h3>
|
||
<svg id="org-theory-icon" class="accordion-icon w-5 h-5 text-purple-600 transition-transform duration-300" aria-hidden="true" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 9l-7 7-7-7"/>
|
||
</svg>
|
||
</button>
|
||
<div id="org-theory-content" class="accordion-content" role="region" aria-labelledby="org-theory-button">
|
||
<div class="p-5 border-t border-gray-200 prose prose-sm max-w-none text-gray-700">
|
||
<p class="mb-4" data-i18n="sections.theoretical_foundations.org_theory_intro">
|
||
Tractatus draws on four decades of organisational research addressing authority structures during knowledge democratisation:
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.org_theory_1_title">Time-Based Organisation (Bluedorn, Ancona):</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.org_theory_1_desc">
|
||
Decisions operate across strategic (years), operational (months), and tactical (hours-days) timescales. AI systems operating at tactical speed should not override strategic decisions made at appropriate temporal scale. The InstructionPersistenceClassifier explicitly models temporal horizon (STRATEGIC, OPERATIONAL, TACTICAL) to enforce decision authority alignment.
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.org_theory_2_title">Knowledge Orchestration (Crossan et al.):</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.org_theory_2_desc">
|
||
When knowledge becomes ubiquitous through AI, organisational authority shifts from information control to knowledge coordination. Governance systems must orchestrate decision-making across distributed expertise rather than centralise control. The PluralisticDeliberationOrchestrator implements non-hierarchical coordination for values conflicts.
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.org_theory_3_title">Post-Bureaucratic Authority (Laloux, Hamel):</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.org_theory_3_desc">
|
||
Traditional hierarchical authority assumes information asymmetry. As AI democratises expertise, legitimate authority must derive from appropriate time horizon and stakeholder representation, not positional power. Framework architecture separates technical capability (what AI can do) from decision authority (what AI should do).
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.org_theory_4_title">Structural Inertia (Hannan & Freeman):</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.org_theory_4_desc">
|
||
Governance embedded in culture or process erodes over time as systems evolve. Architectural constraints create structural inertia that resists organisational drift. Making governance external to AI runtime creates "accountability infrastructure" that survives individual session variations.
|
||
</p>
|
||
|
||
<div class="text-sm text-gray-600 border-t border-gray-200 pt-4 mt-4">
|
||
<a href="/downloads/organizational-theory-foundations-of-the-tractatus-framework.pdf"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
class="inline-flex items-center bg-amber-600 text-white px-5 py-3 rounded-lg font-semibold hover:bg-amber-700 transition shadow-md">
|
||
<svg class="w-5 h-5 mr-2" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
<span data-i18n="sections.theoretical_foundations.org_theory_pdf_link">View Complete Organisational Theory Foundations (PDF)</span>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Values Pluralism -->
|
||
<div class="border-l-4 border border-gray-200 rounded-lg border-l-service-validator animate-on-scroll" data-animation="slide-up" data-stagger="200">
|
||
<button class="accordion-button bg-white p-5 flex justify-between items-center hover:bg-purple-50 transition-colors duration-200 w-full text-left"
|
||
data-accordion="values"
|
||
aria-expanded="false"
|
||
aria-controls="values-content"
|
||
id="values-button">
|
||
<h3 class="font-semibold text-gray-900 group-hover:text-[#8b5cf6] transition-colors" data-i18n="sections.theoretical_foundations.values_pluralism_title">Values Pluralism & Moral Philosophy</h3>
|
||
<svg id="values-icon" class="accordion-icon w-5 h-5 text-purple-600 transition-transform duration-300" aria-hidden="true" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 9l-7 7-7-7"/>
|
||
</svg>
|
||
</button>
|
||
<div id="values-content" class="accordion-content" role="region" aria-labelledby="values-button">
|
||
<div class="p-5 border-t border-gray-200 prose prose-sm max-w-none text-gray-700">
|
||
<div class="bg-blue-50 border border-blue-200 rounded p-3 mb-4 text-sm">
|
||
<strong data-i18n="sections.theoretical_foundations.values_core_research">Core Research Focus:</strong> <span data-i18n="sections.theoretical_foundations.values_core_research_desc">The PluralisticDeliberationOrchestrator represents Tractatus's primary theoretical contribution, addressing how to maintain human values persistence in organizations augmented by AI agents.</span>
|
||
</div>
|
||
|
||
<p class="mb-4" data-i18n="sections.theoretical_foundations.values_central_problem">
|
||
<strong>The Central Problem:</strong> Many "safety" questions in AI governance are actually values conflicts where multiple legitimate perspectives exist. When efficiency conflicts with transparency, or innovation with risk mitigation, no algorithm can determine the "correct" answer. These are values trade-offs requiring human deliberation across stakeholder perspectives.
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.values_berlin_title">Isaiah Berlin: Value Pluralism</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.values_berlin_desc">
|
||
Berlin's concept of value pluralism argues that legitimate values can conflict without one being objectively superior. Liberty and equality, justice and mercy, innovation and stability—these are incommensurable goods. AI systems trained on utilitarian efficiency maximization cannot adjudicate between them without imposing a single values framework that excludes legitimate alternatives.
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.values_weil_title">Simone Weil: Attention and Human Needs</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.values_weil_desc">
|
||
Weil's philosophy of attention informs the orchestrator's deliberative process. <em>The Need for Roots</em> identifies fundamental human needs (order, liberty, responsibility, equality, hierarchical structure, honor, security, risk, etc.) that exist in tension. Proper attention requires seeing these needs in their full particularity rather than abstracting them into algorithmic weights. In AI-augmented organizations, the risk is that bot-mediated processes treat human values as optimization parameters rather than incommensurable needs requiring careful attention.
|
||
</p>
|
||
|
||
<p class="mb-3"><strong data-i18n="sections.theoretical_foundations.values_williams_title">Bernard Williams: Moral Remainder</strong></p>
|
||
<p class="mb-4 pl-4" data-i18n="sections.theoretical_foundations.values_williams_desc">
|
||
Williams' concept of moral remainder acknowledges that even optimal decisions create unavoidable harm to other legitimate values. The orchestrator documents dissenting perspectives not as "minority opinions to be overruled" but as legitimate moral positions that the chosen course necessarily violates. This prevents the AI governance equivalent of declaring optimization complete when values conflicts are merely suppressed.
|
||
</p>
|
||
|
||
<p class="mb-4" data-i18n="sections.theoretical_foundations.values_implementation">
|
||
<strong>Framework Implementation:</strong> Rather than algorithmic resolution, the PluralisticDeliberationOrchestrator facilitates:
|
||
</p>
|
||
|
||
<ul class="list-disc pl-6 mb-4 space-y-2">
|
||
<li data-i18n="sections.theoretical_foundations.values_implementation_1"><strong>Stakeholder identification:</strong> Who has legitimate interest in this decision? (Weil: whose needs are implicated?)</li>
|
||
<li data-i18n="sections.theoretical_foundations.values_implementation_2"><strong>Non-hierarchical deliberation:</strong> Equal voice without automatic expert override (Berlin: no privileged value hierarchy)</li>
|
||
<li data-i18n="sections.theoretical_foundations.values_implementation_3"><strong>Quality of attention:</strong> Detailed exploration of how decision affects each stakeholder's needs (Weil: particularity not abstraction)</li>
|
||
<li data-i18n="sections.theoretical_foundations.values_implementation_4"><strong>Documented dissent:</strong> Minority positions recorded in full (Williams: moral remainder made explicit)</li>
|
||
</ul>
|
||
|
||
<p class="mb-4" data-i18n="sections.theoretical_foundations.values_conclusion">
|
||
This approach recognises that <strong>governance isn't solving values conflicts—it's ensuring they're addressed through appropriate deliberative process with genuine human attention</strong> rather than AI imposing resolution through training data bias or efficiency metrics.
|
||
</p>
|
||
|
||
<div class="text-sm text-gray-600 border-t border-gray-200 pt-4 mt-4">
|
||
<a href="/downloads/cultural-dna-rules.pdf"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
class="inline-flex items-center bg-amber-600 text-white px-5 py-3 rounded-lg font-semibold hover:bg-amber-700 transition shadow-md">
|
||
<svg class="w-5 h-5 mr-2" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
<span data-i18n="sections.theoretical_foundations.values_pdf_link">View Cultural DNA Rules (PDF)</span>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Empirical Observations -->
|
||
<section class="mb-16">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.empirical_observations.heading">Empirical Observations: Documented Failure Modes</h2>
|
||
|
||
<p class="text-sm text-gray-600 mb-6" data-i18n="sections.empirical_observations.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.
|
||
</p>
|
||
|
||
<!-- Failure Mode 1: Pattern Bias -->
|
||
<div class="bg-white border border-gray-300 rounded-lg p-6 mb-4">
|
||
<div class="flex items-start gap-3 mb-3">
|
||
<div class="flex-shrink-0 w-8 h-8 bg-red-100 rounded flex items-center justify-center">
|
||
<span class="text-red-700 font-bold text-sm">1</span>
|
||
</div>
|
||
<div class="flex-1">
|
||
<h3 class="text-lg font-bold text-gray-900 mb-2" data-i18n="sections.empirical_observations.failure_1_title">Pattern Recognition Bias Override (The 27027 Incident)</h3>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.observed_behaviour_label">Observed behaviour:</strong> <span data-i18n="sections.empirical_observations.failure_1_observed">User specified "Check MongoDB on port 27027" but AI immediately used default port 27017 instead. This occurred within same message—not forgetting over time, but immediate autocorrection by training data patterns.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.root_cause_label">Root cause:</strong> <span data-i18n="sections.empirical_observations.failure_1_root_cause">Training data contains thousands of examples of MongoDB on port 27017 (default). When AI encounters "MongoDB" + port specification, pattern recognition weight overrides explicit instruction. Similar to autocorrect changing correctly-spelled proper nouns to common words.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.traditional_failed_label">Why traditional approaches failed:</strong> <span data-i18n="sections.empirical_observations.failure_1_traditional_failed">Prompt engineering ("please follow instructions exactly") ineffective because AI genuinely believes it IS following instructions—pattern recognition operates below conversational reasoning layer.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700">
|
||
<strong data-i18n="sections.empirical_observations.intervention_label">Framework intervention:</strong> <span data-i18n="sections.empirical_observations.failure_1_intervention">InstructionPersistenceClassifier stores explicit instructions in external persistence layer. CrossReferenceValidator checks AI actions against stored instructions before execution. When AI proposes port 27017, validator detects conflict with stored "27027" instruction and blocks execution.</span>
|
||
</p>
|
||
</div>
|
||
</div>
|
||
<div class="flex items-center justify-end gap-3 text-sm pt-3 border-t border-gray-200">
|
||
<span class="text-gray-500" data-i18n="sections.empirical_observations.failure_1_prevention">Prevented by: InstructionPersistenceClassifier + CrossReferenceValidator</span>
|
||
<a href="/demos/27027-demo.html" class="text-amber-700 hover:text-amber-800 font-medium" data-i18n="sections.empirical_observations.failure_1_demo_link">View interactive timeline →</a>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Failure Mode 2: Values Drift -->
|
||
<div class="bg-white border border-gray-300 rounded-lg p-6 mb-4">
|
||
<div class="flex items-start gap-3 mb-3">
|
||
<div class="flex-shrink-0 w-8 h-8 bg-orange-100 rounded flex items-center justify-center">
|
||
<span class="text-orange-700 font-bold text-sm">2</span>
|
||
</div>
|
||
<div class="flex-1">
|
||
<h3 class="text-lg font-bold text-gray-900 mb-2" data-i18n="sections.empirical_observations.failure_2_title">Gradual Values Drift Under Context Pressure</h3>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.observed_behaviour_label">Observed behaviour:</strong> <span data-i18n="sections.empirical_observations.failure_2_observed">Project established "privacy-first" as strategic value. After 40-message conversation about analytics features, AI suggested tracking implementation that violated privacy constraint. User caught it; AI acknowledged violation but had drifted from principle through incremental feature additions.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.root_cause_label">Root cause:</strong> <span data-i18n="sections.empirical_observations.failure_2_root_cause">Strategic values (established early in project) conflict with tactical optimisations (implemented later under time pressure). As conversation lengthens, tactical thinking dominates. AI didn't actively reject privacy principle—it simply stopped checking whether new features aligned.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.traditional_failed_label">Why traditional approaches failed:</strong> <span data-i18n="sections.empirical_observations.failure_2_traditional_failed">Values stated in system prompt become less salient as conversation progresses. Context compaction can drop early strategic decisions. Prompt reminders ("remember privacy-first") treat symptom not cause.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700">
|
||
<strong data-i18n="sections.empirical_observations.intervention_label">Framework intervention:</strong> <span data-i18n="sections.empirical_observations.failure_2_intervention">BoundaryEnforcer maintains strategic values as persistent constraints external to conversation context. Before implementing analytics feature, enforcer checks against stored "privacy-first" constraint. Detects conflict, blocks autonomous implementation, escalates for human deliberation on whether privacy principle should be reconsidered or analytics approach modified.</span>
|
||
</p>
|
||
</div>
|
||
</div>
|
||
<div class="flex items-center justify-end gap-3 text-sm pt-3 border-t border-gray-200">
|
||
<span class="text-gray-500" data-i18n="sections.empirical_observations.failure_2_prevention">Prevented by: BoundaryEnforcer (STRATEGIC constraint checking)</span>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Failure Mode 3: Silent Degradation -->
|
||
<div class="bg-white border border-gray-300 rounded-lg p-6">
|
||
<div class="flex items-start gap-3 mb-3">
|
||
<div class="flex-shrink-0 w-8 h-8 bg-yellow-100 rounded flex items-center justify-center">
|
||
<span class="text-yellow-700 font-bold text-sm">3</span>
|
||
</div>
|
||
<div class="flex-1">
|
||
<h3 class="text-lg font-bold text-gray-900 mb-2" data-i18n="sections.empirical_observations.failure_3_title">Silent Quality Degradation at High Context Pressure</h3>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.observed_behaviour_label">Observed behaviour:</strong> <span data-i18n="sections.empirical_observations.failure_3_observed">During complex multi-file operation at 85% context capacity, AI silently omitted error handling in generated code. No indication to user that corners were being cut. User discovered missing validation only during code review.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.root_cause_label">Root cause:</strong> <span data-i18n="sections.empirical_observations.failure_3_root_cause">As context fills, AI faces implicit trade-off: complete requested functionality OR maintain quality standards. Training incentivises completing user requests over acknowledging limitations. Silence about degradation is path of least resistance.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700 mb-3">
|
||
<strong data-i18n="sections.empirical_observations.traditional_failed_label">Why traditional approaches failed:</strong> <span data-i18n="sections.empirical_observations.failure_3_traditional_failed">AI doesn't recognise it's degrading—from its perspective, it's successfully completing task under constraints. Asking "did you cut corners?" produces confident denial because AI genuinely believes its output meets standards.</span>
|
||
</p>
|
||
<p class="text-sm text-gray-700">
|
||
<strong data-i18n="sections.empirical_observations.intervention_label">Framework intervention:</strong> <span data-i18n="sections.empirical_observations.failure_3_intervention">ContextPressureMonitor tracks multiple factors (token usage, conversation length, task complexity). When pressure exceeds thresholds (>75% tokens, >40 messages, high complexity), monitor forces explicit pressure acknowledgment and recommends context refresh. Makes degradation risk visible rather than silent.</span>
|
||
</p>
|
||
</div>
|
||
</div>
|
||
<div class="flex items-center justify-end gap-3 text-sm pt-3 border-t border-gray-200">
|
||
<span class="text-gray-500" data-i18n="sections.empirical_observations.failure_3_prevention">Prevented by: ContextPressureMonitor (multi-factor session tracking)</span>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="mt-6 text-sm text-gray-600 bg-gray-50 border border-gray-200 rounded p-4">
|
||
<strong>Research Note:</strong> <span data-i18n="sections.empirical_observations.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.</span>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Architectural Components -->
|
||
<section class="mb-16">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.architecture.heading">Six-Component Architecture</h2>
|
||
|
||
<div class="border-l-4 border border-gray-200 rounded-lg border-l-service-validator">
|
||
<button class="accordion-button bg-white p-5 flex justify-between items-center hover:bg-purple-50 transition-colors duration-200 w-full text-left"
|
||
data-accordion="architecture"
|
||
aria-expanded="false"
|
||
aria-controls="architecture-content"
|
||
id="architecture-button">
|
||
<h3 class="font-semibold text-gray-900 group-hover:text-[#8b5cf6] transition-colors" data-i18n="sections.architecture.services_title">Framework Services & Functions</h3>
|
||
<svg id="architecture-icon" class="accordion-icon w-5 h-5 text-purple-600 transition-transform duration-300" aria-hidden="true" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 9l-7 7-7-7"/>
|
||
</svg>
|
||
</button>
|
||
<div id="architecture-content" class="accordion-content" role="region" aria-labelledby="architecture-button">
|
||
<div class="p-5 border-t border-gray-200 space-y-4 text-sm">
|
||
|
||
<div class="border-l-2 border-amber-500 pl-4">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="sections.architecture.service_1_name">1. BoundaryEnforcer</div>
|
||
<div class="text-gray-600 mb-2" data-i18n="sections.architecture.service_1_desc">Blocks AI from making values decisions without human approval. Maintains strategic constraints as persistent rules checked before action execution.</div>
|
||
<div class="text-xs text-gray-500" data-i18n="sections.architecture.service_1_addresses">Addresses: Values drift, autonomous decision-making on contested trade-offs</div>
|
||
</div>
|
||
|
||
<div class="border-l-2 border-gray-300 pl-4">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="sections.architecture.service_2_name">2. InstructionPersistenceClassifier</div>
|
||
<div class="text-gray-600 mb-2" data-i18n="sections.architecture.service_2_desc">Stores explicit instructions external to AI context with persistence levels (HIGH/MEDIUM/LOW) and temporal scope (STRATEGIC/OPERATIONAL/TACTICAL). Prevents pattern bias override.</div>
|
||
<div class="text-xs text-gray-500" data-i18n="sections.architecture.service_2_addresses">Addresses: Pattern recognition bias (27027-style failures)</div>
|
||
</div>
|
||
|
||
<div class="border-l-2 border-gray-300 pl-4">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="sections.architecture.service_3_name">3. CrossReferenceValidator</div>
|
||
<div class="text-gray-600 mb-2" data-i18n="sections.architecture.service_3_desc">Validates AI proposed actions against stored instructions and governance rules before execution. Detects conflicts and blocks inconsistent operations.</div>
|
||
<div class="text-xs text-gray-500" data-i18n="sections.architecture.service_3_addresses">Addresses: Instruction override, policy violation detection</div>
|
||
</div>
|
||
|
||
<div class="border-l-2 border-gray-300 pl-4">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="sections.architecture.service_4_name">4. ContextPressureMonitor</div>
|
||
<div class="text-gray-600 mb-2" data-i18n="sections.architecture.service_4_desc">Multi-factor tracking of session health: token usage, conversation length, task complexity, error frequency. Makes degradation risk explicit when thresholds exceeded.</div>
|
||
<div class="text-xs text-gray-500" data-i18n="sections.architecture.service_4_addresses">Addresses: Silent quality degradation, context-pressure failures</div>
|
||
</div>
|
||
|
||
<div class="border-l-2 border-gray-300 pl-4">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="sections.architecture.service_5_name">5. MetacognitiveVerifier</div>
|
||
<div class="text-gray-600 mb-2" data-i18n="sections.architecture.service_5_desc">Self-checks reasoning quality before complex operations (>3 files, >5 steps, architecture changes). Validates alignment, coherence, considers alternatives.</div>
|
||
<div class="text-xs text-gray-500" data-i18n="sections.architecture.service_5_addresses">Addresses: Reasoning shortcuts under complexity, insufficient alternative consideration</div>
|
||
</div>
|
||
|
||
<div class="border-l-2 border-gray-300 pl-4">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="sections.architecture.service_6_name">6. PluralisticDeliberationOrchestrator</div>
|
||
<div class="text-gray-600 mb-2" data-i18n="sections.architecture.service_6_desc">Facilitates multi-stakeholder deliberation when values conflicts detected. Non-hierarchical engagement, documented dissent, moral remainder acknowledgment.</div>
|
||
<div class="text-xs text-gray-500" data-i18n="sections.architecture.service_6_addresses">Addresses: Values conflicts, stakeholder exclusion, algorithmic resolution of contested trade-offs</div>
|
||
</div>
|
||
|
||
<div class="text-xs text-gray-600 bg-gray-50 p-3 rounded mt-4">
|
||
<strong data-i18n="sections.architecture.principle_label">Architectural principle:</strong> <span data-i18n="sections.architecture.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.</span>
|
||
</div>
|
||
|
||
<div class="border-t border-gray-200 pt-4 mt-4">
|
||
<a href="/architecture.html"
|
||
class="inline-flex items-center bg-blue-600 text-white px-5 py-3 rounded-lg font-semibold hover:bg-blue-700 transition shadow-md">
|
||
<svg class="w-5 h-5 mr-2" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M9 12h6m-6 4h6m2 5H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
<span data-i18n="sections.architecture.view_full_architecture_link">View Full System Architecture & Technical Details</span>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Interactive Demonstrations -->
|
||
<section class="mb-16">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.demos.heading">Interactive Demonstrations</h2>
|
||
|
||
<div class="grid grid-cols-1 md:grid-cols-3 gap-4">
|
||
<a href="/demos/classification-demo.html" class="block border border-gray-300 rounded-lg p-5 hover:border-amber-500 hover:shadow-md transition">
|
||
<h3 class="font-semibold text-gray-900 mb-2" data-i18n="sections.demos.classification_title">Instruction Classification</h3>
|
||
<p class="text-sm text-gray-600" data-i18n="sections.demos.classification_desc">Explore how instructions are classified across quadrants with persistence levels and temporal scope.</p>
|
||
</a>
|
||
|
||
<a href="/demos/27027-demo.html" class="block border border-gray-300 rounded-lg p-5 hover:border-amber-500 hover:shadow-md transition">
|
||
<h3 class="font-semibold text-gray-900 mb-2" data-i18n="sections.demos.incident_title">27027 Incident Timeline</h3>
|
||
<p class="text-sm text-gray-600" data-i18n="sections.demos.incident_desc">Step through pattern recognition bias failure and architectural intervention that prevented it.</p>
|
||
</a>
|
||
|
||
<a href="/demos/boundary-demo.html" class="block border border-gray-300 rounded-lg p-5 hover:border-amber-500 hover:shadow-md transition">
|
||
<h3 class="font-semibold text-gray-900 mb-2" data-i18n="sections.demos.boundary_title">Boundary Evaluation</h3>
|
||
<p class="text-sm text-gray-600" data-i18n="sections.demos.boundary_desc">Test decisions against boundary enforcement to see which require human judgment vs. AI autonomy.</p>
|
||
</a>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Research Resources -->
|
||
<section class="mb-16">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.resources.heading">Research Documentation</h2>
|
||
|
||
<div class="space-y-3 text-sm">
|
||
<a href="https://huggingface.co/spaces/tractatus-framework/audit-log-viewer"
|
||
target="_blank"
|
||
rel="noopener noreferrer"
|
||
class="flex items-center justify-between p-4 border-2 border-orange-400 bg-gradient-to-r from-orange-50 to-yellow-50 rounded-lg hover:border-orange-500 hover:shadow-md transition">
|
||
<div class="flex items-center">
|
||
<span class="text-2xl mr-3">🤗</span>
|
||
<div>
|
||
<span class="font-bold text-gray-900 block" data-i18n="sections.resources.hf_space_title">Interactive Audit Log Explorer (Hugging Face)</span>
|
||
<span class="text-xs text-gray-600" data-i18n="sections.resources.hf_space_subtitle">Explore 3,942 governance decisions from production deployment</span>
|
||
</div>
|
||
</div>
|
||
<svg class="w-5 h-5 text-orange-500" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M10 6H6a2 2 0 00-2 2v10a2 2 0 002 2h10a2 2 0 002-2v-4M14 4h6m0 0v6m0-6L10 14"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/downloads/organizational-theory-foundations-of-the-tractatus-framework.pdf" target="_blank" class="flex items-center justify-between p-4 border border-gray-300 rounded hover:border-amber-500 hover:bg-gray-50 transition">
|
||
<span class="font-medium text-gray-900" data-i18n="sections.resources.doc_1_title">Organisational Theory Foundations</span>
|
||
<svg class="w-5 h-5 text-gray-400" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/downloads/cultural-dna-rules.pdf" target="_blank" class="flex items-center justify-between p-4 border border-gray-300 rounded hover:border-amber-500 hover:bg-gray-50 transition">
|
||
<span class="font-medium text-gray-900" data-i18n="sections.resources.doc_2_title">Cultural DNA Rules</span>
|
||
<svg class="w-5 h-5 text-gray-400" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/downloads/case-studies-real-world-llm-failure-modes.pdf" target="_blank" class="flex items-center justify-between p-4 border border-gray-300 rounded hover:border-amber-500 hover:bg-gray-50 transition">
|
||
<span class="font-medium text-gray-900" data-i18n="sections.resources.doc_3_title">Case Studies: Real-World LLM Failure Modes</span>
|
||
<svg class="w-5 h-5 text-gray-400" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/downloads/framework-governance-in-action-pre-publication-security-audit.pdf" target="_blank" class="flex items-center justify-between p-4 border border-gray-300 rounded hover:border-amber-500 hover:bg-gray-50 transition">
|
||
<span class="font-medium text-gray-900" data-i18n="sections.resources.doc_4_title">Framework in Action: Pre-Publication Security Audit</span>
|
||
<svg class="w-5 h-5 text-gray-400" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/downloads/tractatus-agentic-governance-system-glossary-of-terms.pdf" target="_blank" class="flex items-center justify-between p-4 border border-gray-300 rounded hover:border-amber-500 hover:bg-gray-50 transition">
|
||
<span class="font-medium text-gray-900" data-i18n="sections.resources.doc_5_title">Appendix B: Glossary of Terms</span>
|
||
<svg class="w-5 h-5 text-gray-400" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 10v6m0 0l-3-3m3 3l3-3m2 8H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/docs.html?category=technical-reference" class="flex items-center justify-between p-4 border border-gray-300 rounded hover:border-amber-500 hover:bg-gray-50 transition">
|
||
<span class="font-medium text-gray-900" data-i18n="sections.resources.doc_6_title">Complete Technical Documentation</span>
|
||
<svg class="w-5 h-5 text-gray-400" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13 7h8m0 0v8m0-8l-8 8-4-4-6 6"/>
|
||
</svg>
|
||
</a>
|
||
|
||
<a href="/docs/business-intelligence/governance-bi-tools.pdf" target="_blank" class="flex items-center justify-between p-4 border-2 border-purple-200 bg-gradient-to-r from-purple-50 to-blue-50 rounded hover:border-purple-400 transition">
|
||
<div>
|
||
<span class="font-medium text-gray-900">Business Intelligence Tools: Measuring Governance ROI</span>
|
||
<span class="ml-2 text-xs bg-purple-100 text-purple-800 px-2 py-1 rounded">v1.0 Prototype</span>
|
||
<p class="text-xs text-gray-600 mt-1">Cost avoidance, maturity scoring, and team performance analytics</p>
|
||
</div>
|
||
<svg class="w-5 h-5 text-purple-600" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M9 19v-6a2 2 0 00-2-2H5a2 2 0 00-2 2v6a2 2 0 002 2h2a2 2 0 002-2zm0 0V9a2 2 0 012-2h2a2 2 0 012 2v10m-6 0a2 2 0 002 2h2a2 2 0 002-2m0 0V5a2 2 0 012-2h2a2 2 0 012 2v14a2 2 0 01-2 2h-2a2 2 0 01-2-2z"/>
|
||
</svg>
|
||
</a>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Agent Lightning Integration: Research Perspective -->
|
||
<section class="mb-16 bg-gradient-to-br from-purple-50 to-blue-50 border-2 border-purple-200 rounded-xl p-8">
|
||
<div class="flex items-start gap-4 mb-6">
|
||
<div class="flex-shrink-0">
|
||
<div class="w-14 h-14 rounded-full bg-gradient-to-br from-purple-600 to-indigo-600 text-white flex items-center justify-center text-2xl">
|
||
⚡
|
||
</div>
|
||
</div>
|
||
<div class="flex-1">
|
||
<h2 class="text-3xl font-bold text-gray-900 mb-3">
|
||
Agent Lightning Integration: Open Research Questions
|
||
</h2>
|
||
<p class="text-lg text-gray-700">
|
||
Exploring governance persistence through reinforcement learning optimization cycles
|
||
</p>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Research Context -->
|
||
<div class="bg-white rounded-lg p-6 border border-purple-200 mb-6">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4">🔬 Research Context</h3>
|
||
<p class="text-gray-700 mb-4">
|
||
Microsoft's <strong>Agent Lightning</strong> uses reinforcement learning to optimize agentic AI performance through continuous training on human feedback. This creates a natural research question for governance frameworks:
|
||
</p>
|
||
<div class="bg-blue-50 border-l-4 border-blue-600 p-4 rounded-r-lg">
|
||
<p class="text-blue-900 font-semibold">
|
||
Can architectural governance constraints persist through long-term optimization cycles?
|
||
</p>
|
||
</div>
|
||
<p class="text-gray-700 mt-4">
|
||
Traditional governance assumes relatively static AI behavior. Reinforcement learning introduces <strong>dynamic adaptation</strong> - the agent's behavior changes over time. Does this erode governance boundaries, or can they be maintained through architectural separation?
|
||
</p>
|
||
</div>
|
||
|
||
<!-- What We've Validated -->
|
||
<div class="bg-white rounded-lg p-6 border border-purple-200 mb-6">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4">✅ What We've Validated (Demo 2)</h3>
|
||
|
||
<div class="bg-amber-50 border-2 border-amber-400 rounded-lg p-4 mb-4">
|
||
<div class="flex items-start gap-3">
|
||
<svg class="w-6 h-6 text-amber-600 mt-0.5 flex-shrink-0" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 9v2m0 4h.01m-6.938 4h13.856c1.54 0 2.502-1.667 1.732-3L13.732 4c-.77-1.333-2.694-1.333-3.464 0L3.34 16c-.77 1.333.192 3 1.732 3z" />
|
||
</svg>
|
||
<div>
|
||
<p class="font-semibold text-amber-900 mb-1">Validation Status: Small-Scale Only</p>
|
||
<p class="text-sm text-amber-800">
|
||
Results below are from <strong>5 training rounds, single agent, simulated environment</strong>. This is preliminary evidence, not production validation. Treat findings as suggestive, requiring replication at scale.
|
||
</p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<p class="text-gray-700 mb-4">
|
||
Demo 2 tested whether Tractatus governance services could maintain boundaries while Agent Lightning optimized performance. Early findings suggest:
|
||
</p>
|
||
|
||
<div class="space-y-3 mb-4">
|
||
<div class="flex items-start gap-3">
|
||
<span class="text-green-600 font-bold flex-shrink-0">✓</span>
|
||
<div>
|
||
<p class="font-semibold text-gray-900">Governance Coverage Maintained</p>
|
||
<p class="text-sm text-gray-700">100% of decisions passed through BoundaryEnforcer across all 5 training rounds - no governance bypass detected</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start gap-3">
|
||
<span class="text-green-600 font-bold flex-shrink-0">✓</span>
|
||
<div>
|
||
<p class="font-semibold text-gray-900">Performance Optimization Successful</p>
|
||
<p class="text-sm text-gray-700">Agent Lightning reduced task completion time by 23% while maintaining near-baseline success rate (97% vs 98%)</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start gap-3">
|
||
<span class="text-green-600 font-bold flex-shrink-0">✓</span>
|
||
<div>
|
||
<p class="font-semibold text-gray-900">Architectural Separation Held</p>
|
||
<p class="text-sm text-gray-700">Governance layer operated independently - AL training loops did not modify boundary constraints</p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="text-sm text-gray-600 bg-gray-50 p-4 rounded border border-gray-200">
|
||
<strong>Interpretation:</strong> These results <em>suggest</em> that architectural separation can maintain governance through optimization cycles, but this is far from proven. 5 rounds is insufficient to demonstrate long-term persistence. Real-world validation with hundreds/thousands of training rounds is needed.
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Open Research Questions -->
|
||
<div class="bg-white rounded-lg p-6 border border-purple-200 mb-6">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4">❓ Open Research Questions</h3>
|
||
<p class="text-gray-700 mb-4">
|
||
These questions represent genuine research gaps we're actively investigating. We welcome collaboration from researchers working on similar problems:
|
||
</p>
|
||
|
||
<div class="space-y-4">
|
||
<div class="border-l-4 border-purple-400 bg-purple-50 p-4 rounded-r-lg">
|
||
<p class="font-semibold text-purple-900 mb-2">1. Long-Term Persistence at Scale</p>
|
||
<p class="text-sm text-gray-700">
|
||
Does governance coverage maintain through 1,000+ training rounds? At what point (if any) do optimization pressures begin to erode architectural boundaries? Do we see different persistence patterns across different agent types or task domains?
|
||
</p>
|
||
</div>
|
||
|
||
<div class="border-l-4 border-purple-400 bg-purple-50 p-4 rounded-r-lg">
|
||
<p class="font-semibold text-purple-900 mb-2">2. Performance Trade-offs Under Governance</p>
|
||
<p class="text-sm text-gray-700">
|
||
Demo 2 showed minimal performance degradation (98% → 97% success rate). Is this consistent across different task complexities? Are there task types where governance constraints significantly impair Agent Lightning's ability to optimize?
|
||
</p>
|
||
</div>
|
||
|
||
<div class="border-l-4 border-purple-400 bg-purple-50 p-4 rounded-r-lg">
|
||
<p class="font-semibold text-purple-900 mb-2">3. Multi-Agent Governance Coordination</p>
|
||
<p class="text-sm text-gray-700">
|
||
Demo 2 validated single-agent scenarios. How does governance scale when multiple agents (each with AL optimization) interact? Do boundary conflicts emerge? Can PluralisticDeliberator handle multi-agent stakeholder deliberations efficiently?
|
||
</p>
|
||
</div>
|
||
|
||
<div class="border-l-4 border-purple-400 bg-purple-50 p-4 rounded-r-lg">
|
||
<p class="font-semibold text-purple-900 mb-2">4. Adversarial Optimization Pressure</p>
|
||
<p class="text-sm text-gray-700">
|
||
What happens when training data or feedback contains attempts to bypass governance? Can Agent Lightning's optimization inadvertently discover governance workarounds? How robust is ContextPressureMonitor to sophisticated manipulation attempts embedded in training loops?
|
||
</p>
|
||
</div>
|
||
|
||
<div class="border-l-4 border-purple-400 bg-purple-50 p-4 rounded-r-lg">
|
||
<p class="font-semibold text-purple-900 mb-2">5. Generalization Across LLM Architectures</p>
|
||
<p class="text-sm text-gray-700">
|
||
Demo 2 used Claude Code (Anthropic). Does the Tractatus + Agent Lightning integration maintain governance coverage when using different base models (GPT-4, Gemini, Llama, etc.)? Are there model-specific vulnerabilities?
|
||
</p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Collaboration & Resources -->
|
||
<div class="bg-white rounded-lg p-6 border border-purple-200">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4">🤝 Collaboration & Community</h3>
|
||
<p class="text-gray-700 mb-4">
|
||
We're building a research community focused on agentic AI governance. If you're working on related problems - reinforcement learning safety, multi-agent governance, constraint persistence - we'd like to hear from you.
|
||
</p>
|
||
|
||
<div class="grid grid-cols-1 md:grid-cols-2 gap-4">
|
||
<a href="https://discord.gg/Dkke2ADu4E" target="_blank" class="flex items-center gap-3 p-4 bg-gradient-to-r from-purple-600 to-indigo-600 text-white rounded-lg hover:shadow-lg transition-all">
|
||
<svg class="w-8 h-8 flex-shrink-0" viewBox="0 0 24 24" fill="currentColor">
|
||
<path d="M20.317 4.37a19.791 19.791 0 0 0-4.885-1.515a.074.074 0 0 0-.079.037c-.21.375-.444.864-.608 1.25a18.27 18.27 0 0 0-5.487 0a12.64 12.64 0 0 0-.617-1.25a.077.077 0 0 0-.079-.037A19.736 19.736 0 0 0 3.677 4.37a.07.07 0 0 0-.032.027C.533 9.046-.32 13.58.099 18.057a.082.082 0 0 0 .031.057a19.9 19.9 0 0 0 5.993 3.03a.078.078 0 0 0 .084-.028a14.09 14.09 0 0 0 1.226-1.994a.076.076 0 0 0-.041-.106a13.107 13.107 0 0 1-1.872-.892a.077.077 0 0 1-.008-.128a10.2 10.2 0 0 0 .372-.292a.074.074 0 0 1 .077-.01c3.928 1.793 8.18 1.793 12.062 0a.074.074 0 0 1 .078.01c.12.098.246.198.373.292a.077.077 0 0 1-.006.127a12.299 12.299 0 0 1-1.873.892a.077.077 0 0 0-.041.107c.36.698.772 1.362 1.225 1.993a.076.076 0 0 0 .084.028a19.839 19.839 0 0 0 6.002-3.03a.077.077 0 0 0 .032-.054c.5-5.177-.838-9.674-3.549-13.66a.061.061 0 0 0-.031-.03zM8.02 15.33c-1.183 0-2.157-1.085-2.157-2.419c0-1.333.956-2.419 2.157-2.419c1.21 0 2.176 1.096 2.157 2.42c0 1.333-.956 2.418-2.157 2.418zm7.975 0c-1.183 0-2.157-1.085-2.157-2.419c0-1.333.955-2.419 2.157-2.419c1.21 0 2.176 1.096 2.157 2.42c0 1.333-.946 2.418-2.157 2.418z"/>
|
||
</svg>
|
||
<div>
|
||
<p class="font-bold">Join Tractatus Discord</p>
|
||
<p class="text-xs opacity-90">Governance-focused discussions</p>
|
||
</div>
|
||
</a>
|
||
|
||
<a href="https://discord.gg/bVZtkceKsS" target="_blank" class="flex items-center gap-3 p-4 bg-gradient-to-r from-blue-600 to-cyan-600 text-white rounded-lg hover:shadow-lg transition-all">
|
||
<svg class="w-8 h-8 flex-shrink-0" viewBox="0 0 24 24" fill="currentColor">
|
||
<path d="M20.317 4.37a19.791 19.791 0 0 0-4.885-1.515a.074.074 0 0 0-.079.037c-.21.375-.444.864-.608 1.25a18.27 18.27 0 0 0-5.487 0a12.64 12.64 0 0 0-.617-1.25a.077.077 0 0 0-.079-.037A19.736 19.736 0 0 0 3.677 4.37a.07.07 0 0 0-.032.027C.533 9.046-.32 13.58.099 18.057a.082.082 0 0 0 .031.057a19.9 19.9 0 0 0 5.993 3.03a.078.078 0 0 0 .084-.028a14.09 14.09 0 0 0 1.226-1.994a.076.076 0 0 0-.041-.106a13.107 13.107 0 0 1-1.872-.892a.077.077 0 0 1-.008-.128a10.2 10.2 0 0 0 .372-.292a.074.074 0 0 1 .077-.01c3.928 1.793 8.18 1.793 12.062 0a.074.074 0 0 1 .078.01c.12.098.246.198.373.292a.077.077 0 0 1-.006.127a12.299 12.299 0 0 1-1.873.892a.077.077 0 0 0-.041.107c.36.698.772 1.362 1.225 1.993a.076.076 0 0 0 .084.028a19.839 19.839 0 0 0 6.002-3.03a.077.077 0 0 0 .032-.054c.5-5.177-.838-9.674-3.549-13.66a.061.061 0 0 0-.031-.03zM8.02 15.33c-1.183 0-2.157-1.085-2.157-2.419c0-1.333.956-2.419 2.157-2.419c1.21 0 2.176 1.096 2.157 2.42c0 1.333-.956 2.418-2.157 2.418zm7.975 0c-1.183 0-2.157-1.085-2.157-2.419c0-1.333.955-2.419 2.157-2.419c1.21 0 2.176 1.096 2.157 2.42c0 1.333-.946 2.418-2.157 2.418z"/>
|
||
</svg>
|
||
<div>
|
||
<p class="font-bold">Join Agent Lightning Discord</p>
|
||
<p class="text-xs opacity-90">Technical implementation help</p>
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
<div class="mt-4 p-4 bg-gray-50 rounded border border-gray-200">
|
||
<p class="text-sm text-gray-700">
|
||
<strong>Research collaboration:</strong> If you're investigating governance persistence, multi-agent coordination, or RL safety under constraints, we're interested in cross-validation studies. Reach out via Discord or email research inquiries to the team.
|
||
</p>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Limitations & Future Research -->
|
||
<section class="mb-16">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.limitations.heading">Limitations & Future Research Directions</h2>
|
||
|
||
<div class="border-l-4 border border-gray-200 rounded-lg border-l-service-validator">
|
||
<button class="accordion-button bg-white p-5 flex justify-between items-center hover:bg-purple-50 transition-colors duration-200 w-full text-left"
|
||
data-accordion="limitations"
|
||
aria-expanded="false"
|
||
aria-controls="limitations-content"
|
||
id="limitations-button">
|
||
<h3 class="font-semibold text-gray-900 group-hover:text-[#8b5cf6] transition-colors" data-i18n="sections.limitations.title">Known Limitations & Research Gaps</h3>
|
||
<svg id="limitations-icon" class="accordion-icon w-5 h-5 text-purple-600 transition-transform duration-300" aria-hidden="true" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M19 9l-7 7-7-7"/>
|
||
</svg>
|
||
</button>
|
||
<div id="limitations-content" class="accordion-content" role="region" aria-labelledby="limitations-button">
|
||
<div class="p-5 border-t border-gray-200 space-y-6 text-sm text-gray-700">
|
||
|
||
<!-- What We've Validated -->
|
||
<div>
|
||
<h4 class="font-bold text-gray-900 mb-3" data-i18n="sections.limitations.validated_heading">What We've Validated (October 2025)</h4>
|
||
<p class="mb-3" data-i18n="sections.limitations.validated_intro">After 6 months of development and ~500 Claude Code sessions, we have grounded evidence for:</p>
|
||
|
||
<div class="space-y-3">
|
||
<div>
|
||
<p class="font-semibold text-green-700" data-i18n="sections.limitations.validated_1_title">✅ Architectural Blocking Mechanisms Functional</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.validated_1_item1">BoundaryEnforcer successfully blocks values decisions before execution</li>
|
||
<li data-i18n="sections.limitations.validated_1_item2">Pre-commit hooks prevent inst_017 violations (absolute assurance terms)</li>
|
||
<li data-i18n="sections.limitations.validated_1_item3">1,130+ audit decisions recorded in MongoDB (tractatus_dev.audit_log)</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-green-700" data-i18n="sections.limitations.validated_2_title">✅ Instruction Persistence Works in Single-Session Context</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.validated_2_item1">InstructionPersistenceClassifier maintains 62 active instructions (STRATEGIC: 22, SYSTEM: 21)</li>
|
||
<li data-i18n="sections.limitations.validated_2_item2">Pattern bias detection prevents AI from overriding explicit organizational directives</li>
|
||
<li data-i18n="sections.limitations.validated_2_item3">Temporal scopes (STRATEGIC/OPERATIONAL/TACTICAL) enforced successfully</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-green-700" data-i18n="sections.limitations.validated_3_title">✅ Audit Trails Capture Governance Decisions</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.validated_3_item1">External MongoDB storage (AI cannot modify logs)</li>
|
||
<li data-i18n="sections.limitations.validated_3_item2">Service-specific logging: BoundaryEnforcer (523 logs), ContextPressureMonitor (521 logs)</li>
|
||
<li data-i18n="sections.limitations.validated_3_item3">Immutable evidence chain for compliance demonstration</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-green-700" data-i18n="sections.limitations.validated_4_title">✅ Context Pressure Monitoring Operational</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.validated_4_item1">Real-time pressure scores calculated (token usage, message count, complexity)</li>
|
||
<li data-i18n="sections.limitations.validated_4_item2">Checkpoint triggers at 50k, 100k, 150k tokens</li>
|
||
<li data-i18n="sections.limitations.validated_4_item3">Framework fade detection alerts (5/6 components stale = warning)</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-green-700" data-i18n="sections.limitations.validated_5_title">✅ Single-Project Governance Successful</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.validated_5_item1">Framework governed development of agenticgovernance.digital</li>
|
||
<li data-i18n="sections.limitations.validated_5_item2">Cultural DNA rules (inst_085-089) enforced through pre-commit hooks</li>
|
||
<li data-i18n="sections.limitations.validated_5_item3">Zero credential exposures (defense-in-depth: 5 layers verified)</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- What We Have NOT Validated -->
|
||
<div class="border-t border-gray-200 pt-4">
|
||
<h4 class="font-bold text-gray-900 mb-3" data-i18n="sections.limitations.not_validated_heading">What We Have NOT Validated</h4>
|
||
<p class="mb-3" data-i18n="sections.limitations.not_validated_intro">Honest disclosure of research gaps where we lack evidence:</p>
|
||
|
||
<div class="space-y-3">
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_1_title">❌ Multi-Organization Deployments</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_1_item1">Validated: Single project, single user</li>
|
||
<li data-i18n="sections.limitations.not_validated_1_item2">Unknown: How framework performs across different organizations, domains, technical stacks</li>
|
||
<li data-i18n="sections.limitations.not_validated_1_item3">Research need: Pilot studies across industries (healthcare, finance, government)</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_2_title">❌ Adversarial Robustness</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_2_item1">Validated: Normal development workflows (~500 sessions)</li>
|
||
<li data-i18n="sections.limitations.not_validated_2_item2">Unknown: Resistance to deliberate bypass attempts, jailbreak prompts, adversarial testing</li>
|
||
<li data-i18n="sections.limitations.not_validated_2_item3">Research need: Red-team evaluation by security researchers</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_3_title">❌ Cross-Platform Consistency</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_3_item1">Validated: Claude Code (Anthropic Sonnet 4.5) only</li>
|
||
<li data-i18n="sections.limitations.not_validated_3_item2">Unknown: Generalizability to Copilot, GPT-4, AutoGPT, LangChain, CrewAI, open models</li>
|
||
<li data-i18n="sections.limitations.not_validated_3_item3">Research need: Cross-platform validation studies</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_4_title">❌ Concurrent Session Architecture</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_4_item1">Validated: Single session at a time</li>
|
||
<li data-i18n="sections.limitations.not_validated_4_item2">Unknown: Multi-developer concurrent use on shared codebases</li>
|
||
<li data-i18n="sections.limitations.not_validated_4_item3">Known limitation: MongoDB duplicate key errors, session state contamination, race conditions on .claude/instruction-history.json</li>
|
||
<li data-i18n="sections.limitations.not_validated_4_item4">Research need: Multi-tenant architecture design (session-specific state, file locking)</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_5_title">❌ Rule Proliferation Impact</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_5_item1">Validated: 62 active instructions work in current context</li>
|
||
<li data-i18n="sections.limitations.not_validated_5_item2">Unknown: Performance degradation as rule count grows (projected 30-50 instructions within 12 months)</li>
|
||
<li data-i18n="sections.limitations.not_validated_5_item3">Known concern: Transactional overhead (CrossReferenceValidator checks), context window pressure, cognitive load</li>
|
||
<li data-i18n="sections.limitations.not_validated_5_item4">Research need: Rule consolidation strategies, automated governance optimization</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_6_title">❌ Regulatory Evidence Sufficiency</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_6_item1">Validated: Audit trails exist with compliance tags (EU_AI_ACT_Article14, GDPR_Article22)</li>
|
||
<li data-i18n="sections.limitations.not_validated_6_item2">Unknown: Do regulators accept architectural audit trails as "meaningful human oversight" evidence?</li>
|
||
<li data-i18n="sections.limitations.not_validated_6_item3">Research need: Legal review by EU AI Act specialists, GDPR compliance officers</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_7_title">❌ Values Pluralism in Practice</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_7_item1">Validated: PluralisticDeliberationOrchestrator implements non-hierarchical process</li>
|
||
<li data-i18n="sections.limitations.not_validated_7_item2">Unknown: Real-world effectiveness resolving organizational value conflicts</li>
|
||
<li data-i18n="sections.limitations.not_validated_7_item3">Research need: Case studies with actual stakeholder deliberations (not theoretical scenarios)</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-amber-700" data-i18n="sections.limitations.not_validated_8_title">❌ Enterprise Scale Performance</p>
|
||
<ul class="list-disc pl-5 mt-1 space-y-1 text-gray-600">
|
||
<li data-i18n="sections.limitations.not_validated_8_item1">Validated: Single-user context</li>
|
||
<li data-i18n="sections.limitations.not_validated_8_item2">Unknown: Latency, throughput, database performance with thousands of concurrent users, millions of governance events</li>
|
||
<li data-i18n="sections.limitations.not_validated_8_item3">Research need: Load testing, performance optimization</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Documented Limitations -->
|
||
<div class="border-t border-gray-200 pt-4">
|
||
<h4 class="font-bold text-gray-900 mb-3" data-i18n="sections.limitations.documented_heading">Documented Limitations (Not "Future Work")</h4>
|
||
<p class="mb-3" data-i18n="sections.limitations.documented_intro">These are known structural constraints requiring honest acknowledgment:</p>
|
||
|
||
<div class="space-y-3">
|
||
<div>
|
||
<p class="font-semibold text-gray-900" data-i18n="sections.limitations.documented_1_title">1. Voluntary Invocation Weakness</p>
|
||
<p class="mt-1 text-gray-600" data-i18n="sections.limitations.documented_1_desc">Most critical: Framework can be bypassed if AI chooses not to invoke governance tools. We've addressed this through architectural patterns (automatic checks, external validation), but full enforcement requires runtime-level integration not universally available in current LLM platforms.</p>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-gray-900" data-i18n="sections.limitations.documented_2_title">2. Platform-Specific Implementation</p>
|
||
<p class="mt-1 text-gray-600" data-i18n="sections.limitations.documented_2_desc">Framework validated only with Claude Code. Integration points (hooks, tool APIs) vary across platforms. Generalization requires platform-specific adapters.</p>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-gray-900" data-i18n="sections.limitations.documented_3_title">3. Single-Tenant Architecture</p>
|
||
<p class="mt-1 text-gray-600" data-i18n="sections.limitations.documented_3_desc">Current design assumes one session at a time. Concurrent use creates state conflicts. Multi-tenant patterns not yet implemented.</p>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-gray-900" data-i18n="sections.limitations.documented_4_title">4. Rule Growth Without Consolidation</p>
|
||
<p class="mt-1 text-gray-600" data-i18n="sections.limitations.documented_4_desc">Each critical incident generates new HIGH persistence instructions. No automated rule consolidation mechanism exists. Manual governance required as rule count grows.</p>
|
||
</div>
|
||
|
||
<div>
|
||
<p class="font-semibold text-gray-900" data-i18n="sections.limitations.documented_5_title">5. No Formal Verification</p>
|
||
<p class="mt-1 text-gray-600" data-i18n="sections.limitations.documented_5_desc">Boundary enforcement properties validated empirically, not through formal proof. Mathematical verification of governance properties remains open research question.</p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Research Collaboration Opportunities -->
|
||
<section class="mb-16">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.research_collaboration.heading">Research Collaboration Opportunities</h2>
|
||
|
||
<div class="bg-blue-50 border-l-4 border-blue-600 p-6 rounded-r-lg mb-8">
|
||
<p class="text-gray-800" data-i18n="sections.research_collaboration.intro">We've identified specific gaps where external research collaboration would be valuable. These are concrete, answerable questions—not generic "help us improve" requests.</p>
|
||
</div>
|
||
|
||
<!-- High Priority Research Questions -->
|
||
<div class="mb-8">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4" data-i18n="sections.research_collaboration.high_priority_heading">High Priority (Immediate Need)</h3>
|
||
|
||
<div class="space-y-6">
|
||
<!-- RQ1 -->
|
||
<div class="border border-gray-200 rounded-lg p-5">
|
||
<h4 class="font-bold text-gray-900 mb-2" data-i18n="sections.research_collaboration.rq1_title">RQ1: Adversarial Robustness Testing</h4>
|
||
<p class="text-sm text-gray-700 mb-2"><span class="font-semibold" data-i18n="sections.research_collaboration.rq_label">Research Question:</span> <span data-i18n="sections.research_collaboration.rq1_question">Can architectural governance resist adversarial prompts designed to bypass it?</span></p>
|
||
|
||
<div class="mb-2">
|
||
<p class="text-sm font-semibold text-gray-900 mb-1" data-i18n="sections.research_collaboration.methodology_label">Methodology Needed:</p>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq1_method1">Red-team evaluation with security researchers</li>
|
||
<li data-i18n="sections.research_collaboration.rq1_method2">Jailbreak prompt testing against BoundaryEnforcer</li>
|
||
<li data-i18n="sections.research_collaboration.rq1_method3">Bypass attempt documentation and pattern analysis</li>
|
||
<li data-i18n="sections.research_collaboration.rq1_method4">Comparison: behavioral (constitutional AI) vs architectural (Tractatus) resistance</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<p class="text-sm text-gray-700"><span class="font-semibold" data-i18n="sections.research_collaboration.why_label">Why It Matters:</span> <span data-i18n="sections.research_collaboration.rq1_why">If adversarial prompts can trivially bypass governance, architectural approach offers no advantage over behavioral training.</span></p>
|
||
</div>
|
||
|
||
<!-- RQ2 -->
|
||
<div class="border border-gray-200 rounded-lg p-5">
|
||
<h4 class="font-bold text-gray-900 mb-2" data-i18n="sections.research_collaboration.rq2_title">RQ2: Concurrent Session Architecture Design</h4>
|
||
<p class="text-sm text-gray-700 mb-2"><span class="font-semibold" data-i18n="sections.research_collaboration.rq_label">Research Question:</span> <span data-i18n="sections.research_collaboration.rq2_question">What multi-tenant patterns enable safe concurrent governance on shared codebases?</span></p>
|
||
|
||
<div class="mb-2">
|
||
<p class="text-sm font-semibold text-gray-900 mb-1" data-i18n="sections.research_collaboration.methodology_label">Methodology Needed:</p>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq2_method1">Distributed systems analysis of race conditions</li>
|
||
<li data-i18n="sections.research_collaboration.rq2_method2">Session-specific state isolation designs</li>
|
||
<li data-i18n="sections.research_collaboration.rq2_method3">File locking vs database-backed state trade-offs</li>
|
||
<li data-i18n="sections.research_collaboration.rq2_method4">Performance impact of synchronization mechanisms</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<p class="text-sm text-gray-700"><span class="font-semibold" data-i18n="sections.research_collaboration.why_label">Why It Matters:</span> <span data-i18n="sections.research_collaboration.rq2_why">Current single-session assumption blocks enterprise deployment where multiple developers use AI concurrently.</span></p>
|
||
</div>
|
||
|
||
<!-- RQ3 -->
|
||
<div class="border border-gray-200 rounded-lg p-5">
|
||
<h4 class="font-bold text-gray-900 mb-2" data-i18n="sections.research_collaboration.rq3_title">RQ3: Regulatory Evidence Sufficiency</h4>
|
||
<p class="text-sm text-gray-700 mb-2"><span class="font-semibold" data-i18n="sections.research_collaboration.rq_label">Research Question:</span> <span data-i18n="sections.research_collaboration.rq3_question">Do architectural audit trails satisfy EU AI Act Article 14 "meaningful human oversight" requirements?</span></p>
|
||
|
||
<div class="mb-2">
|
||
<p class="text-sm font-semibold text-gray-900 mb-1" data-i18n="sections.research_collaboration.methodology_label">Methodology Needed:</p>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq3_method1">Legal analysis by EU AI Act specialists</li>
|
||
<li data-i18n="sections.research_collaboration.rq3_method2">Regulator interviews (GDPR DPAs, AI Act enforcement bodies)</li>
|
||
<li data-i18n="sections.research_collaboration.rq3_method3">Comparison with existing compliance frameworks (SOC 2, ISO 27001)</li>
|
||
<li data-i18n="sections.research_collaboration.rq3_method4">Case study: audit trail review in regulatory context</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<p class="text-sm text-gray-700"><span class="font-semibold" data-i18n="sections.research_collaboration.why_label">Why It Matters:</span> <span data-i18n="sections.research_collaboration.rq3_why">If regulators don't accept audit trails as evidence, architectural governance provides no compliance value.</span></p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Medium Priority Research Questions -->
|
||
<div class="mb-8">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4" data-i18n="sections.research_collaboration.medium_priority_heading">Medium Priority (Near-Term Investigation)</h3>
|
||
|
||
<div class="space-y-6">
|
||
<!-- RQ4 -->
|
||
<div class="border border-gray-200 rounded-lg p-5">
|
||
<h4 class="font-bold text-gray-900 mb-2" data-i18n="sections.research_collaboration.rq4_title">RQ4: Rule Proliferation Management</h4>
|
||
<p class="text-sm text-gray-700 mb-2"><span class="font-semibold" data-i18n="sections.research_collaboration.rq_label">Research Question:</span> <span data-i18n="sections.research_collaboration.rq4_question">At what rule count does transactional overhead create unacceptable latency?</span></p>
|
||
|
||
<div class="mb-2">
|
||
<p class="text-sm font-semibold text-gray-900 mb-1" data-i18n="sections.research_collaboration.methodology_label">Methodology Needed:</p>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq4_method1">Performance testing with varying instruction counts (50, 100, 200, 500 rules)</li>
|
||
<li data-i18n="sections.research_collaboration.rq4_method2">CrossReferenceValidator latency measurements</li>
|
||
<li data-i18n="sections.research_collaboration.rq4_method3">Context window pressure analysis</li>
|
||
<li data-i18n="sections.research_collaboration.rq4_method4">Rule consolidation algorithm design and validation</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<p class="text-sm text-gray-700"><span class="font-semibold" data-i18n="sections.research_collaboration.why_label">Why It Matters:</span> <span data-i18n="sections.research_collaboration.rq4_why">If rule growth causes performance degradation, framework doesn't scale long-term.</span></p>
|
||
</div>
|
||
|
||
<!-- RQ5 -->
|
||
<div class="border border-gray-200 rounded-lg p-5">
|
||
<h4 class="font-bold text-gray-900 mb-2" data-i18n="sections.research_collaboration.rq5_title">RQ5: Cross-Platform Validation</h4>
|
||
<p class="text-sm text-gray-700 mb-2"><span class="font-semibold" data-i18n="sections.research_collaboration.rq_label">Research Question:</span> <span data-i18n="sections.research_collaboration.rq5_question">Do governance patterns generalize beyond Claude Code to other LLM systems?</span></p>
|
||
|
||
<div class="mb-2">
|
||
<p class="text-sm font-semibold text-gray-900 mb-1" data-i18n="sections.research_collaboration.methodology_label">Methodology Needed:</p>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq5_method1">Replication studies with Copilot, GPT-4, AutoGPT, LangChain, CrewAI</li>
|
||
<li data-i18n="sections.research_collaboration.rq5_method2">Platform-specific adapter development</li>
|
||
<li data-i18n="sections.research_collaboration.rq5_method3">Comparative effectiveness analysis</li>
|
||
<li data-i18n="sections.research_collaboration.rq5_method4">Failure mode documentation per platform</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<p class="text-sm text-gray-700"><span class="font-semibold" data-i18n="sections.research_collaboration.why_label">Why It Matters:</span> <span data-i18n="sections.research_collaboration.rq5_why">If governance is Claude Code-specific, it's a niche tool not general framework.</span></p>
|
||
</div>
|
||
|
||
<!-- RQ6 -->
|
||
<div class="border border-gray-200 rounded-lg p-5">
|
||
<h4 class="font-bold text-gray-900 mb-2" data-i18n="sections.research_collaboration.rq6_title">RQ6: Values Pluralism Effectiveness</h4>
|
||
<p class="text-sm text-gray-700 mb-2"><span class="font-semibold" data-i18n="sections.research_collaboration.rq_label">Research Question:</span> <span data-i18n="sections.research_collaboration.rq6_question">Does PluralisticDeliberationOrchestrator successfully resolve real-world organizational value conflicts?</span></p>
|
||
|
||
<div class="mb-2">
|
||
<p class="text-sm font-semibold text-gray-900 mb-1" data-i18n="sections.research_collaboration.methodology_label">Methodology Needed:</p>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq6_method1">Case studies with actual organizational stakeholders (not hypothetical scenarios)</li>
|
||
<li data-i18n="sections.research_collaboration.rq6_method2">Deliberation process quality assessment</li>
|
||
<li data-i18n="sections.research_collaboration.rq6_method3">Minority voice preservation analysis</li>
|
||
<li data-i18n="sections.research_collaboration.rq6_method4">Comparison with traditional hierarchical decision-making</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<p class="text-sm text-gray-700"><span class="font-semibold" data-i18n="sections.research_collaboration.why_label">Why It Matters:</span> <span data-i18n="sections.research_collaboration.rq6_why">If pluralistic process doesn't work in practice, we've built theoretical machinery without empirical value.</span></p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Lower Priority Research Questions -->
|
||
<div class="mb-8">
|
||
<h3 class="text-xl font-bold text-gray-900 mb-4" data-i18n="sections.research_collaboration.lower_priority_heading">Lower Priority (Longer-Term)</h3>
|
||
|
||
<div class="space-y-3">
|
||
<div class="border border-gray-200 rounded-lg p-4">
|
||
<h4 class="font-bold text-gray-900 mb-1" data-i18n="sections.research_collaboration.rq7_title">RQ7: Enterprise Scale Performance</h4>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq7_item1">Load testing (1000+ concurrent users)</li>
|
||
<li data-i18n="sections.research_collaboration.rq7_item2">Database optimization for millions of governance events</li>
|
||
<li data-i18n="sections.research_collaboration.rq7_item3">Horizontal scaling patterns</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<div class="border border-gray-200 rounded-lg p-4">
|
||
<h4 class="font-bold text-gray-900 mb-1" data-i18n="sections.research_collaboration.rq8_title">RQ8: Formal Verification of Boundary Enforcement</h4>
|
||
<ul class="list-disc pl-5 text-sm text-gray-600 space-y-1">
|
||
<li data-i18n="sections.research_collaboration.rq8_item1">Mathematical proof of governance properties</li>
|
||
<li data-i18n="sections.research_collaboration.rq8_item2">Model checking of state transitions</li>
|
||
<li data-i18n="sections.research_collaboration.rq8_item3">Verification of architectural properties</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- What We Can Offer -->
|
||
<div class="bg-gray-50 border border-gray-200 rounded-lg p-6 mb-6">
|
||
<h3 class="text-lg font-bold text-gray-900 mb-3" data-i18n="sections.research_collaboration.offer_heading">What We Can Offer Research Collaborators</h3>
|
||
<p class="text-sm text-gray-700 mb-3" data-i18n="sections.research_collaboration.offer_intro">If you're investigating any of these questions, we can provide:</p>
|
||
|
||
<div class="grid grid-cols-1 md:grid-cols-2 gap-3 mb-4">
|
||
<div class="flex items-start">
|
||
<span class="text-green-600 mr-2">✅</span>
|
||
<div>
|
||
<p class="text-sm font-semibold text-gray-900" data-i18n="sections.research_collaboration.offer_1_title">Codebase Access</p>
|
||
<p class="text-xs text-gray-600" data-i18n="sections.research_collaboration.offer_1_desc">Full source code (Apache 2.0, open-source)</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start">
|
||
<span class="text-green-600 mr-2">✅</span>
|
||
<div>
|
||
<p class="text-sm font-semibold text-gray-900" data-i18n="sections.research_collaboration.offer_2_title">Documentation</p>
|
||
<p class="text-xs text-gray-600" data-i18n="sections.research_collaboration.offer_2_desc">Architecture specifications, implementation patterns, governance rules</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start">
|
||
<span class="text-green-600 mr-2">✅</span>
|
||
<div>
|
||
<p class="text-sm font-semibold text-gray-900" data-i18n="sections.research_collaboration.offer_3_title">Audit Data</p>
|
||
<p class="text-xs text-gray-600" data-i18n="sections.research_collaboration.offer_3_desc">1,130+ governance decisions in MongoDB (anonymized exports available)</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start">
|
||
<span class="text-green-600 mr-2">✅</span>
|
||
<div>
|
||
<p class="text-sm font-semibold text-gray-900" data-i18n="sections.research_collaboration.offer_4_title">Deployment Support</p>
|
||
<p class="text-xs text-gray-600" data-i18n="sections.research_collaboration.offer_4_desc">Help setting up local or cloud instances for testing</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start">
|
||
<span class="text-green-600 mr-2">✅</span>
|
||
<div>
|
||
<p class="text-sm font-semibold text-gray-900" data-i18n="sections.research_collaboration.offer_5_title">Coordination</p>
|
||
<p class="text-xs text-gray-600" data-i18n="sections.research_collaboration.offer_5_desc">Regular sync meetings to discuss findings</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="flex items-start">
|
||
<span class="text-green-600 mr-2">✅</span>
|
||
<div>
|
||
<p class="text-sm font-semibold text-gray-900" data-i18n="sections.research_collaboration.offer_6_title">Co-authorship</p>
|
||
<p class="text-xs text-gray-600" data-i18n="sections.research_collaboration.offer_6_desc">Academic publications documenting findings</p>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<p class="text-sm font-semibold text-gray-900 mb-2" data-i18n="sections.research_collaboration.cannot_offer_heading">What We Cannot Provide:</p>
|
||
<ul class="list-none space-y-1 text-sm text-gray-600">
|
||
<li><span class="text-red-600 mr-2">❌</span><span data-i18n="sections.research_collaboration.cannot_offer_1">Funding (we're not a grant-making body)</span></li>
|
||
<li><span class="text-red-600 mr-2">❌</span><span data-i18n="sections.research_collaboration.cannot_offer_2">Dedicated engineering resources (capacity constraints)</span></li>
|
||
<li><span class="text-red-600 mr-2">❌</span><span data-i18n="sections.research_collaboration.cannot_offer_3">Assured publication venues (but we'll support submission efforts)</span></li>
|
||
</ul>
|
||
</div>
|
||
|
||
<!-- Research Inquiry CTA -->
|
||
<div class="text-center">
|
||
<button id="research-inquiry-button" class="inline-flex items-center bg-purple-600 text-white px-6 py-3 rounded-lg font-semibold hover:bg-purple-700 transition shadow-md">
|
||
<svg class="w-5 h-5 mr-2" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M9 12h6m-6 4h6m2 5H7a2 2 0 01-2-2V5a2 2 0 012-2h5.586a1 1 0 01.707.293l5.414 5.414a1 1 0 01.293.707V19a2 2 0 01-2 2z"/>
|
||
</svg>
|
||
<span data-i18n="sections.research_collaboration.inquiry_button">Research Collaboration Inquiry</span>
|
||
</button>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Bibliography -->
|
||
<section class="mb-16 border-t border-gray-200 pt-12">
|
||
<h2 class="text-2xl font-bold text-gray-900 mb-6" data-i18n="sections.bibliography.heading">References & Bibliography</h2>
|
||
|
||
<div class="prose prose-sm max-w-none text-gray-700 space-y-3">
|
||
<div class="bg-amber-50 border border-amber-200 rounded p-4 mb-6 text-sm text-amber-900">
|
||
<strong data-i18n="sections.bibliography.theoretical_priority_label">Theoretical Priority:</strong> <span data-i18n="sections.bibliography.theoretical_priority_text">Tractatus emerged from concerns about maintaining human values persistence in AI-augmented organizations. Moral pluralism and deliberative process form the CORE theoretical foundation. Organizational theory provides supporting context for temporal decision authority and structural implementation.</span>
|
||
</div>
|
||
|
||
<h3 class="text-lg font-semibold text-gray-900 mt-6 mb-3" data-i18n="sections.bibliography.section_1_heading">Moral Pluralism & Values Philosophy (Primary Foundation)</h3>
|
||
<ul class="list-none space-y-2 text-sm">
|
||
<li class="pl-6 -indent-6">Berlin, Isaiah (1969). <em>Four Essays on Liberty</em>. Oxford: Oxford University Press. [Value pluralism, incommensurability of legitimate values]</li>
|
||
<li class="pl-6 -indent-6">Weil, Simone (1949/2002). <em>The Need for Roots: Prelude to a Declaration of Duties Towards Mankind</em> (A. Wills, Trans.). London: Routledge. [Human needs, obligations, rootedness in moral community]</li>
|
||
<li class="pl-6 -indent-6">Weil, Simone (1947/2002). <em>Gravity and Grace</em> (E. Crawford & M. von der Ruhr, Trans.). London: Routledge. [Attention, moral perception, necessity vs. grace]</li>
|
||
<li class="pl-6 -indent-6">Williams, Bernard (1981). <em>Moral Luck: Philosophical Papers 1973-1980</em>. Cambridge: Cambridge University Press. [Moral remainder, conflicts without resolution]</li>
|
||
<li class="pl-6 -indent-6">Nussbaum, Martha C. (2000). <em>Women and Human Development: The Capabilities Approach</em>. Cambridge: Cambridge University Press. [Human capabilities, plural values in development]</li>
|
||
</ul>
|
||
|
||
<h3 class="text-lg font-semibold text-gray-900 mt-6 mb-3" data-i18n="sections.bibliography.section_2_heading">Organisational Theory (Supporting Context)</h3>
|
||
<ul class="list-none space-y-2 text-sm">
|
||
<li class="pl-6 -indent-6">Bluedorn, A. C., & Denhardt, R. B. (1988). Time and organizations. <em>Journal of Management, 14</em>(2), 299-320. [Temporal decision horizons]</li>
|
||
<li class="pl-6 -indent-6">Crossan, M. M., Lane, H. W., & White, R. E. (1999). An organizational learning framework: From intuition to institution. <em>Academy of Management Review, 24</em>(3), 522-537. [Knowledge coordination]</li>
|
||
<li class="pl-6 -indent-6">Hamel, Gary (2007). <em>The Future of Management</em>. Boston: Harvard Business School Press. [Post-hierarchical authority]</li>
|
||
<li class="pl-6 -indent-6">Hannan, M. T., & Freeman, J. (1984). Structural inertia and organizational change. <em>American Sociological Review, 49</em>(2), 149-164. [Architectural resistance to drift]</li>
|
||
<li class="pl-6 -indent-6">Laloux, Frederic (2014). <em>Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage of Human Consciousness</em>. Brussels: Nelson Parker. [Distributed decision-making]</li>
|
||
</ul>
|
||
|
||
<h3 class="text-lg font-semibold text-gray-900 mt-6 mb-3" data-i18n="sections.bibliography.section_3_heading">AI Governance & Technical Context</h3>
|
||
<ul class="list-none space-y-2 text-sm">
|
||
<li class="pl-6 -indent-6">Anthropic (2024). <em>Claude Code: Technical Documentation</em>. Available at: https://docs.anthropic.com/claude-code</li>
|
||
</ul>
|
||
|
||
<div class="bg-gray-50 border border-gray-200 rounded p-4 mt-6 text-xs text-gray-600">
|
||
<strong data-i18n="sections.bibliography.intellectual_lineage_label">Note on Intellectual Lineage:</strong> <span data-i18n="sections.bibliography.intellectual_lineage_text">The framework's central concern—human values persistence in AI-augmented organizational contexts—derives from moral philosophy rather than management science. The PluralisticDeliberationOrchestrator represents the primary research focus, embodying Weil's concept of attention to plural human needs and Berlin's recognition of incommensurable values.</span>
|
||
|
||
<span data-i18n="sections.bibliography.future_development_text"><strong>Berlin and Weil will be integral to further development</strong> of the deliberation component—their work provides the philosophical foundation for understanding how to preserve human agency over values decisions as AI capabilities accelerate. Traditional organizational theory (Weber, Taylor) addresses authority through hierarchy; post-AI organizational contexts require authority through appropriate deliberative process across stakeholder perspectives. Framework development documentation (incident reports, session logs) maintained in project repository but not publicly released pending peer review.</span>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Additional Resources -->
|
||
<section class="border-t border-gray-200 pt-12">
|
||
<h2 class="text-xl font-bold text-gray-900 mb-4" data-i18n="footer.additional_resources">Additional Resources</h2>
|
||
<div class="grid grid-cols-1 md:grid-cols-2 gap-4">
|
||
<a href="/leader.html" class="block border border-gray-300 rounded-lg p-5 hover:border-amber-500 transition">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="footer.for_decision_makers">For Decision-Makers</div>
|
||
<div class="text-sm text-gray-600" data-i18n="footer.for_decision_makers_desc">Strategic perspective on governance challenges and architectural approaches</div>
|
||
</a>
|
||
<a href="/implementer.html" class="block border border-gray-300 rounded-lg p-5 hover:border-amber-500 transition">
|
||
<div class="font-semibold text-gray-900 mb-1" data-i18n="footer.implementation_guide">Implementation Guide</div>
|
||
<div class="text-sm text-gray-600" data-i18n="footer.implementation_guide_desc">Technical integration patterns and deployment considerations</div>
|
||
</a>
|
||
</div>
|
||
</section>
|
||
|
||
</div>
|
||
|
||
<!-- Research Inquiry Modal -->
|
||
<div id="research-inquiry-modal" class="fixed inset-0 bg-black bg-opacity-50 flex items-center justify-center p-4 hidden z-50">
|
||
<div class="bg-white rounded-lg max-w-3xl w-full max-h-[90vh] overflow-y-auto">
|
||
<div class="sticky top-0 bg-white border-b border-gray-200 px-6 py-4 flex justify-between items-center">
|
||
<h3 class="text-xl font-bold text-gray-900" data-i18n="modal.research_inquiry.heading">Research Collaboration Inquiry</h3>
|
||
<button id="close-modal" class="text-gray-400 hover:text-gray-600 transition">
|
||
<svg class="w-6 h-6" fill="none" stroke="currentColor" viewBox="0 0 24 24">
|
||
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M6 18L18 6M6 6l12 12"/>
|
||
</svg>
|
||
</button>
|
||
</div>
|
||
|
||
<div class="px-6 py-6">
|
||
<div class="bg-blue-50 border-l-4 border-blue-600 p-4 mb-6">
|
||
<p class="text-sm text-gray-800 mb-2" data-i18n="modal.research_inquiry.intro_1">If you're investigating limitations of architectural AI governance, we'd value collaboration. We're particularly interested in researchers who can bring methodological rigor to gaps we've identified but lack capacity to address.</p>
|
||
<p class="text-sm text-gray-800 font-semibold" data-i18n="modal.research_inquiry.intro_2">This is NOT a user acquisition form. We're looking for research partners who can help validate (or invalidate) our approaches in controlled settings.</p>
|
||
</div>
|
||
|
||
<form id="research-inquiry-form" class="space-y-6">
|
||
<!-- Research Question -->
|
||
<div>
|
||
<label for="research-question" class="block text-sm font-semibold text-gray-900 mb-2">
|
||
<span data-i18n="modal.research_inquiry.field_1_label">Research Question</span> <span class="text-red-600">*</span>
|
||
</label>
|
||
<select id="research-question" name="research-question" required class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent">
|
||
<option value="">-- Select Research Question --</option>
|
||
<option value="RQ1" data-i18n="modal.research_inquiry.rq1_option">RQ1: Adversarial Robustness Testing</option>
|
||
<option value="RQ2" data-i18n="modal.research_inquiry.rq2_option">RQ2: Concurrent Session Architecture Design</option>
|
||
<option value="RQ3" data-i18n="modal.research_inquiry.rq3_option">RQ3: Regulatory Evidence Sufficiency</option>
|
||
<option value="RQ4" data-i18n="modal.research_inquiry.rq4_option">RQ4: Rule Proliferation Management</option>
|
||
<option value="RQ5" data-i18n="modal.research_inquiry.rq5_option">RQ5: Cross-Platform Validation</option>
|
||
<option value="RQ6" data-i18n="modal.research_inquiry.rq6_option">RQ6: Values Pluralism Effectiveness</option>
|
||
<option value="RQ7" data-i18n="modal.research_inquiry.rq7_option">RQ7: Enterprise Scale Performance</option>
|
||
<option value="RQ8" data-i18n="modal.research_inquiry.rq8_option">RQ8: Formal Verification of Boundary Enforcement</option>
|
||
<option value="Other" data-i18n="modal.research_inquiry.other_option">Other (please specify below)</option>
|
||
</select>
|
||
</div>
|
||
|
||
<!-- Methodological Approach -->
|
||
<div>
|
||
<label for="methodology" class="block text-sm font-semibold text-gray-900 mb-2">
|
||
<span data-i18n="modal.research_inquiry.field_2_label">Your Methodological Approach</span> <span class="text-red-600">*</span>
|
||
</label>
|
||
<textarea id="methodology" name="methodology" required maxlength="1000" rows="4"
|
||
placeholder="How would you investigate this research question? What methods, controls, metrics would you use?"
|
||
data-i18n-placeholder="modal.research_inquiry.field_2_placeholder"
|
||
class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent"></textarea>
|
||
<p class="text-xs text-gray-500 mt-1" data-i18n="modal.research_inquiry.char_limit_1000">Maximum 1000 characters</p>
|
||
</div>
|
||
|
||
<!-- Validation Context -->
|
||
<div>
|
||
<label for="context" class="block text-sm font-semibold text-gray-900 mb-2">
|
||
<span data-i18n="modal.research_inquiry.field_3_label">Validation Context</span> <span class="text-red-600">*</span>
|
||
</label>
|
||
<textarea id="context" name="context" required maxlength="500" rows="3"
|
||
placeholder="What environment would you test in? (e.g., 'Multi-organization healthcare deployment with HIPAA requirements', 'Academic lab with adversarial prompt database')"
|
||
data-i18n-placeholder="modal.research_inquiry.field_3_placeholder"
|
||
class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent"></textarea>
|
||
<p class="text-xs text-gray-500 mt-1" data-i18n="modal.research_inquiry.char_limit_500">Maximum 500 characters</p>
|
||
</div>
|
||
|
||
<!-- What You'd Need From Us -->
|
||
<div>
|
||
<label class="block text-sm font-semibold text-gray-900 mb-2" data-i18n="modal.research_inquiry.field_4_label">What You'd Need From Us</label>
|
||
<div class="space-y-2">
|
||
<label class="flex items-start">
|
||
<input type="checkbox" name="needs" value="codebase" class="mt-1 mr-2">
|
||
<span class="text-sm text-gray-700" data-i18n="modal.research_inquiry.need_1">Codebase access and documentation</span>
|
||
</label>
|
||
<label class="flex items-start">
|
||
<input type="checkbox" name="needs" value="audit-logs" class="mt-1 mr-2">
|
||
<span class="text-sm text-gray-700" data-i18n="modal.research_inquiry.need_2">Anonymized audit log exports</span>
|
||
</label>
|
||
<label class="flex items-start">
|
||
<input type="checkbox" name="needs" value="deployment" class="mt-1 mr-2">
|
||
<span class="text-sm text-gray-700" data-i18n="modal.research_inquiry.need_3">Deployment support (setup assistance)</span>
|
||
</label>
|
||
<label class="flex items-start">
|
||
<input type="checkbox" name="needs" value="meetings" class="mt-1 mr-2">
|
||
<span class="text-sm text-gray-700" data-i18n="modal.research_inquiry.need_4">Regular coordination meetings</span>
|
||
</label>
|
||
<label class="flex items-start">
|
||
<input type="checkbox" name="needs" value="coauthorship" class="mt-1 mr-2">
|
||
<span class="text-sm text-gray-700" data-i18n="modal.research_inquiry.need_5">Co-authorship on publications</span>
|
||
</label>
|
||
<label class="flex items-start">
|
||
<input type="checkbox" name="needs" value="other" class="mt-1 mr-2">
|
||
<span class="text-sm text-gray-700" data-i18n="modal.research_inquiry.need_6">Other (specify below)</span>
|
||
</label>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Other Needs -->
|
||
<div>
|
||
<label for="other-needs" class="block text-sm font-semibold text-gray-900 mb-2" data-i18n="modal.research_inquiry.field_5_label">Other Needs</label>
|
||
<textarea id="other-needs" name="other-needs" maxlength="300" rows="2"
|
||
placeholder="Any other support you'd need for this research?"
|
||
data-i18n-placeholder="modal.research_inquiry.field_5_placeholder"
|
||
class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent"></textarea>
|
||
<p class="text-xs text-gray-500 mt-1" data-i18n="modal.research_inquiry.char_limit_300">Maximum 300 characters</p>
|
||
</div>
|
||
|
||
<!-- Institution/Affiliation -->
|
||
<div>
|
||
<label for="institution" class="block text-sm font-semibold text-gray-900 mb-2" data-i18n="modal.research_inquiry.field_6_label">Your Institution/Affiliation</label>
|
||
<input type="text" id="institution" name="institution"
|
||
placeholder="University, research lab, or independent"
|
||
data-i18n-placeholder="modal.research_inquiry.field_6_placeholder"
|
||
class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent">
|
||
</div>
|
||
|
||
<!-- Name -->
|
||
<div>
|
||
<label for="name" class="block text-sm font-semibold text-gray-900 mb-2">
|
||
<span data-i18n="modal.research_inquiry.field_7_label">Your Name</span> <span class="text-red-600">*</span>
|
||
</label>
|
||
<input type="text" id="name" name="name" required
|
||
class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent">
|
||
</div>
|
||
|
||
<!-- Email -->
|
||
<div>
|
||
<label for="email" class="block text-sm font-semibold text-gray-900 mb-2">
|
||
<span data-i18n="modal.research_inquiry.field_8_label">Contact Email</span> <span class="text-red-600">*</span>
|
||
</label>
|
||
<input type="email" id="email" name="email" required
|
||
class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent">
|
||
</div>
|
||
|
||
<!-- Timeline -->
|
||
<div>
|
||
<label for="timeline" class="block text-sm font-semibold text-gray-900 mb-2">
|
||
<span data-i18n="modal.research_inquiry.field_9_label">Expected Timeline</span> <span class="text-red-600">*</span>
|
||
</label>
|
||
<select id="timeline" name="timeline" required class="w-full px-4 py-2 border border-gray-300 rounded-lg focus:ring-2 focus:ring-purple-500 focus:border-transparent">
|
||
<option value="">-- Select Timeline --</option>
|
||
<option value="immediate" data-i18n="modal.research_inquiry.timeline_1">Starting immediately (within 1 month)</option>
|
||
<option value="near-term" data-i18n="modal.research_inquiry.timeline_2">Near-term (1-3 months)</option>
|
||
<option value="longer-term" data-i18n="modal.research_inquiry.timeline_3">Longer-term (3-6 months)</option>
|
||
<option value="exploring" data-i18n="modal.research_inquiry.timeline_4">Exploring feasibility (no timeline yet)</option>
|
||
</select>
|
||
</div>
|
||
|
||
<!-- Submit Button -->
|
||
<div class="flex justify-end space-x-3 pt-4 border-t border-gray-200">
|
||
<button type="button" id="cancel-modal" class="px-6 py-2 border border-gray-300 rounded-lg text-gray-700 hover:bg-gray-50 transition" data-i18n="modal.research_inquiry.cancel">Cancel</button>
|
||
<button type="submit" class="px-6 py-2 bg-purple-600 text-white rounded-lg hover:bg-purple-700 transition" data-i18n="modal.research_inquiry.submit">Submit Research Inquiry</button>
|
||
</div>
|
||
</form>
|
||
|
||
<!-- Success Message (hidden by default) -->
|
||
<div id="success-message" class="hidden">
|
||
<div class="bg-green-50 border-l-4 border-green-600 p-4 mb-4">
|
||
<p class="text-sm text-green-800 font-semibold mb-2" data-i18n="modal.research_inquiry.success_title">Thank you for your research inquiry.</p>
|
||
<p class="text-sm text-green-800" data-i18n="modal.research_inquiry.success_message">We'll review your proposal and respond within 5 business days.</p>
|
||
<p class="text-xs text-green-700 mt-2" data-i18n="modal.research_inquiry.success_note">Note: We receive research inquiries from academics, security researchers, and AI safety investigators. Response priority is based on methodological rigor and research question relevance, not institutional affiliation.</p>
|
||
</div>
|
||
<div class="flex justify-end">
|
||
<button id="close-success" class="px-6 py-2 bg-purple-600 text-white rounded-lg hover:bg-purple-700 transition" data-i18n="modal.research_inquiry.close">Close</button>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Share CTA -->
|
||
<section class="bg-gray-100 py-12">
|
||
<div class="max-w-2xl mx-auto px-4 sm:px-6 lg:px-8">
|
||
<div class="bg-white rounded-lg shadow-sm border border-gray-200 p-8">
|
||
<h2 class="text-2xl font-semibold text-gray-900 mb-3" data-i18n="share_cta.heading">
|
||
Help us reach the right people.
|
||
</h2>
|
||
<p class="text-gray-700 mb-6" data-i18n="share_cta.description">
|
||
If you know researchers, implementers, or leaders who need structural AI governance solutions, share this with them.
|
||
</p>
|
||
<div class="flex flex-wrap gap-3">
|
||
<button
|
||
data-action="copy-link"
|
||
class="bg-blue-600 hover:bg-blue-700 text-white px-6 py-2.5 rounded-lg font-medium transition-colors shadow-sm"
|
||
data-i18n="share_cta.copy_link">
|
||
Copy Link
|
||
</button>
|
||
<button
|
||
data-action="email-share"
|
||
class="bg-blue-600 hover:bg-blue-700 text-white px-6 py-2.5 rounded-lg font-medium transition-colors shadow-sm"
|
||
data-i18n="share_cta.email">
|
||
Email
|
||
</button>
|
||
<button
|
||
data-action="linkedin-share"
|
||
class="bg-blue-600 hover:bg-blue-700 text-white px-6 py-2.5 rounded-lg font-medium transition-colors shadow-sm"
|
||
data-i18n="share_cta.linkedin">
|
||
LinkedIn
|
||
</button>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- Footer -->
|
||
<!-- Internationalization (must load first for footer translations) -->
|
||
<script src="/js/i18n-simple.js?v=0.1.2.1762133909969"></script>
|
||
<script src="/js/components/language-selector.js?v=0.1.2.1762133909969"></script>
|
||
|
||
<!-- Scroll Animations (Phase 3) -->
|
||
<script src="/js/scroll-animations.js?v=0.1.2.1762133909969"></script>
|
||
<!-- Page Transitions (Phase 3) -->
|
||
<script src="/js/page-transitions.js?v=0.1.2.1762133909969"></script>
|
||
|
||
<!-- Version Management & PWA -->
|
||
|
||
<script src="/js/version-manager.js?v=0.1.2.1762133909969"></script>
|
||
<script src="/js/researcher-page.js?v=0.1.2.1762133909969"></script>
|
||
|
||
<!-- Share CTA functionality -->
|
||
<script src="/js/share-cta.js?v=0.1.2.1762133909969"></script>
|
||
|
||
<!-- Footer Component -->
|
||
<script src="/js/components/footer.js?v=0.1.2.1762133909969"></script>
|
||
|
||
<!-- Feedback System (Governed by Tractatus + Agent Lightning) -->
|
||
<script src="/js/components/feedback.js?v=0.1.2.1762133909969"></script>
|
||
|
||
</body>
|
||
</html>
|