Commit graph

117 commits

Author SHA1 Message Date
TheFlow
649eda71e1 chore: bump cache version to 0.1.1 for JS changes 2025-10-25 08:47:54 +13:00
TheFlow
65784f02f8 feat(blog): integrate Tractatus framework governance into blog publishing
Implements architectural enforcement of governance rules (inst_016/017/018/079)
for all external communications. Publication blocked at API level if violations
detected.

New Features:
- Framework content checker script with pattern matching for prohibited terms
- Admin UI displays framework violations with severity indicators
- Manual "Check Framework" button for pre-publication validation
- API endpoint /api/blog/check-framework for real-time content analysis

Governance Rules Added:
- inst_078: "ff" trigger for manual framework invocation in conversations
- inst_079: Dark patterns prohibition (sovereignty principle)
- inst_080: Open source commitment enforcement (community principle)
- inst_081: Pluralism principle with indigenous framework recognition

Session Management:
- Fix session-init.js infinite loop (removed early return after tests)
- Add session-closedown.js for comprehensive session handoff
- Refactor check-csp-violations.js to prevent parent process exit

Framework Services:
- Enhanced PluralisticDeliberationOrchestrator with audit logging
- Updated all 6 services with consistent initialization patterns
- Added framework invocation scripts for blog content validation

Files: blog.controller.js:1211-1305, blog.routes.js:77-82,
blog-curation.html:61-72, blog-curation.js:320-446

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-25 08:47:31 +13:00
TheFlow
c0bc35f2de fix(newsletter): convert ObjectId to string in DELETE button data attributes
Root cause: MongoDB ObjectId objects were being inserted into data-id
attributes as '[object Object]' instead of their string representation.

Fix: Explicitly call String() on sub._id when creating data attributes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 20:24:54 +13:00
TheFlow
d8006f62d7 fix(architecture): interactive diagram SVG click handler timing issues
Fixed non-responsive service node clicks on architecture.html interactive diagram.

Root cause: SVG loaded via <object> tag had contentDocument timing issues -
event listeners attached before SVG fully accessible.

Solution:
- Added retry mechanism for contentDocument access (100ms intervals)
- Implemented multiple loading strategies (immediate, load event, timeout)
- Enabled event capturing phase (addEventListener 3rd param: true)
- Enhanced logging for debugging click event flow
- Auto-display overview panel on initialization
- CSP-compliant cursor styling via JavaScript

Deployed to production: https://agenticgovernance.digital/architecture.html

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 18:22:15 +13:00
TheFlow
edb1540631 feat(crm): complete Phase 3 multi-project CRM + critical bug fixes
Phase 3 Multi-Project CRM Implementation:
- Add UnifiedContact model for cross-project contact linking
- Add Organization model with domain-based auto-detection
- Add ActivityTimeline model for comprehensive interaction tracking
- Add SLATracking model for 24-hour response commitment
- Add ResponseTemplate model with variable substitution
- Add CRM controller with 8 API endpoints
- Add Inbox controller for unified communications
- Add CRM dashboard frontend with tabs (Contacts, Orgs, SLA, Templates)
- Add Contact Management interface (Phase 1)
- Add Unified Inbox interface (Phase 2)
- Integrate CRM routes into main API

Critical Bug Fixes:
- Fix newsletter DELETE button (event handler context issue)
- Fix case submission invisible button (invalid CSS class)
- Fix Chart.js CSP violation (add cdn.jsdelivr.net to policy)
- Fix Chart.js SRI integrity hash mismatch

Technical Details:
- Email-based contact deduplication across projects
- Automatic organization linking via email domain
- Cross-project activity timeline aggregation
- SLA breach detection and alerting system
- Template rendering with {placeholder} substitution

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 18:10:14 +13:00
TheFlow
fe3035913e feat(crm): implement unified contact form system
Complete CRM foundation with contact modal in footer

Backend:
- Contact.model.js: Full CRUD model with statistics tracking
- contact.controller.js: Submit, list, assign, respond, update, delete
- contact.routes.js: Public submission + admin management endpoints
- routes/index.js: Mount contact routes at /api/contact

Frontend:
- footer.js: Replace mailto link with Contact Us modal button
- Contact modal: Form with type, name, email, org, subject, message
- CSRF protection: Extracts token from cookie (like newsletter)
- Rate limiting: formRateLimiter (5/min)
- Validation: Input sanitization + required fields
- UX: Success/error messages, auto-close on success

Admin UI:
- navbar-admin.js: New 'CRM & Communications' section
- Links: Contact Management, Case Submissions, Media Inquiries

Foundation for multi-project CRM across tractatus, family-history, sydigital

Next: Build /admin/contact-management.html page
2025-10-24 16:56:21 +13:00
TheFlow
49a5c07248 feat(admin): reorganize navbar with CRM section and add missing tools
- Add new 'CRM & Communications' section for contact/inquiry management
- Add Editorial Guidelines to Content Management
- Add Credential Vault to System & Framework
- Reorganize for future unified CRM across all projects
2025-10-24 16:51:04 +13:00
TheFlow
cfc4347e9b fix(csrf): enable newsletter subscription from mobile
CRITICAL FIX: Newsletter subscription was returning "Forbidden" error
because the CSRF protection was incorrectly configured.

Root cause:
- CSRF cookie was set with httpOnly: true
- JavaScript cannot read httpOnly cookies
- Frontend couldn't extract token to send in X-CSRF-Token header
- Double-submit CSRF pattern requires client to read the cookie

Changes:
- csrf-protection.middleware.js: Set httpOnly: false (required for double-submit pattern)
- blog.js: Extract CSRF token from cookie and include in X-CSRF-Token header

Security Note: This is the correct implementation per OWASP guidelines
for double-submit cookie CSRF protection. The cookie is still protected
by SameSite: strict and domain restrictions.

Fixes: #newsletter-subscription-forbidden-mobile
2025-10-24 16:42:56 +13:00
TheFlow
b036c14d84 fix(submissions): extract data from API response wrappers
CRITICAL FIX: Economist submission package was showing no data because
the frontend was storing the entire API response wrapper instead of
extracting the actual post and submission data.

Changes:
- submission-modal-enhanced.js: Extract .post from blog API response
- submission-modal-enhanced.js: Extract .data from submissions API response
- publications.routes.js: Restore original routes and add /targets endpoint
- Cache version bumped to force browser updates

Fixes: #economist-submission-data-missing
2025-10-24 16:35:10 +13:00
TheFlow
0305dc1f48 feat(admin): add Editorial Guidelines Manager page
Created comprehensive Editorial Guidelines Manager to display all 22
publication targets with detailed submission requirements:

**New Page:** `/admin/editorial-guidelines.html`
- Display all publication targets in filterable grid
- Filter by tier, type, language, region
- Show submission requirements (word counts, language, exclusivity)
- Display editorial guidelines (tone, focus areas, things to avoid)
- Contact information (email addresses, response times)
- Target audience information

**Backend:**
- Added GET /api/publications/targets endpoint
- Serves publication targets from config file
- Returns 22 publications with all metadata

**Frontend:**
- Stats overview (total, premier, high-value, strategic)
- Publication cards with color-coded tiers
- Detailed requirements and guidelines display
- Responsive grid layout

This provides centralized access to submission guidelines for all
target publications including The Economist, Le Monde, The Guardian,
Financial Times, etc. Previously this data was only in the config
file and not accessible through the admin interface.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 13:05:47 +13:00
TheFlow
f8758fd95b fix(blog): add missing auth headers to submission modal API calls
Fixed 401 Unauthorized errors in blog validation/submission modal:
- Added Authorization Bearer token to /api/blog/admin/:id fetch (line 153)
- Added Authorization Bearer token to /api/submissions/by-blog-post/:id fetch (line 162)
- Added Authorization Bearer token to /api/submissions/:id/export fetch (line 818)

All admin API endpoints require authentication. The submission modal
was making unauthenticated requests, causing 401 errors when trying
to load article data or export submission packages.

The 404 error on by-blog-post is expected when no submission exists
for that blog post ID yet.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 13:00:11 +13:00
TheFlow
8c1eeb3a7a fix(calendar): Add cache-busting and better error handling
- Added cache: 'no-store' to prevent cached 500 errors
- Enhanced error messages with status codes
- Display detailed error messages to user
- Log API response text for debugging
- Helps diagnose mobile loading issues
2025-10-24 12:13:21 +13:00
TheFlow
8528fd079b feat(translation): complete DeepL translation workflow
Frontend:
- Add translate button click handler in submission-modal-enhanced.js
- Display loading state during translation ( Translating...)
- Update French textarea with translated content
- Auto-update word counts after translation
- Show success message with DeepL attribution

Backend:
- Add POST /api/submissions/:id/translate endpoint
- Integrate Translation.service (DeepL)
- Save translations to SubmissionTracking.documents
- Mark translations as 'translatedBy: deepl', 'approved: false'
- Return translated text with caching metadata

Complete Translation Flow:
1. User clicks 'Translate EN → FR' button
2. Frontend sends English text to /api/submissions/:id/translate
3. Backend calls DeepL API via Translation.service
4. Translation cached for 24 hours
5. Result saved to submission.documents[docType].versions[]
6. French textarea populated with translation
7. User can review/edit before saving submission

Next: Configure DEEPL_API_KEY in .env to enable translations
2025-10-24 11:22:50 +13:00
TheFlow
f5b8f1a85c feat(admin): add multilingual document editor with DeepL translation
- Display English and French versions side-by-side for all documents
- Add 'Translate EN → FR' button using DeepL
- Show word counts for each language version
- Display translation metadata (translatedBy, approved status)
- Mark primary language for each document
- Support readonly mode for blog-linked content

Documents tab now shows:
- Main Article (EN/FR)
- Cover Letter (EN/FR)
- Author Bio (EN/FR)
- Pitch Email (EN/FR)

Next: Add translation button click handler and API endpoint
2025-10-24 11:17:12 +13:00
TheFlow
d34ce5fa1e feat(translation): implement DeepL translation service (SOVEREIGN)
**GOVERNANCE RULE**: Tractatus uses DeepL API ONLY for all translations.
NEVER use LibreTranslate or any other translation service.

Changes:
- Created Translation.service.js using proven family-history DeepL implementation
- Added DEEPL_API_KEY to .env configuration
- Installed node-cache dependency for translation caching
- Supports all SubmissionTracking schema languages (en, fr, de, es, pt, zh, ja, ar, mi)
- Default formality: 'more' (formal style for publication submissions)
- 24-hour translation caching to reduce API calls
- Batch translation support (up to 50 texts per request)

Framework Note: Previous attempt to use LibreTranslate was a violation of
explicit user instruction. This has been corrected.

Signed-off-by: Claude <noreply@anthropic.com>
2025-10-24 11:16:33 +13:00
TheFlow
a800283583 feat(admin): add standalone submission package modal support
- Add data-is-standalone flag to manage-submission buttons
- Create openStandaloneSubmissionModal function for packages without blog posts
- Update renderOverviewTab to handle null article (standalone submissions)
- Display standalone submission notice with purple badge
- Load submission data directly via /api/submissions/{id}
- Differentiate UI labels (Submitted vs Published dates)
- Files modified: blog-validation.js, submission-modal-enhanced.js
2025-10-24 11:06:22 +13:00
TheFlow
f7d0b68d39 fix(admin): force fresh API requests to prevent cached 500 errors
- Add cache: 'no-store' to all apiCall functions in admin JS files
- Prevents browser fetch cache from serving stale error responses
- Addresses submissions endpoint 500 errors that weren't appearing in server logs
- Killed duplicate server process (PID 1583625)
- Added debug logging to submissions controller
- Files modified: blog-validation.js, blog-curation.js, blog-curation-enhanced.js
2025-10-24 11:02:43 +13:00
TheFlow
7f865fbe70 fix(blog-curation-enhanced): add null check for publication dropdown
- Fixed TypeError when page loads in Pre-Submission section
- publication-target element only exists in Generate section
- Cache version updated
2025-10-24 10:02:31 +13:00
TheFlow
eb666a2504 debug: add console logging to track Le Monde loading
- Added detailed console logs to track submission loading
- Check if API response is ok
- Log all submissions found
- Log filtering logic for standalone submissions
- Cache version updated
2025-10-24 09:53:14 +13:00
TheFlow
d3074f87a3 fix(blog-validation): show Le Monde standalone submission package
- Modified loadValidationArticles() to load standalone submissions (no blogPostId)
- Updated rendering to handle both blog posts and standalone packages
- Fixed API endpoint from /api/blog/posts/:id to /api/blog/admin/:id
- Standalone packages show with purple 'STANDALONE PACKAGE' badge
- Button text changes to 'View Package' for standalone submissions
- Cache version bumped to 0.1.1
2025-10-24 09:50:42 +13:00
TheFlow
971690bb64 feat(cache): enforce mandatory cache version updates for JS changes
- Enhanced update-cache-version.js to update service worker and version.json
- Added inst_075 governance instruction (HIGH persistence)
- Integrated cache check into deployment script (Step 1/5)
- Created CACHE_MANAGEMENT_ENFORCEMENT.md documentation
- Bumped version to 0.1.1
- Updated all HTML cache parameters

BREAKING: Deployment now blocks if JS changed without cache update
2025-10-24 09:43:20 +13:00
TheFlow
2298d36bed fix(submissions): restructure Economist package and fix article display
- Create Economist SubmissionTracking package correctly:
  * mainArticle = full blog post content
  * coverLetter = 216-word SIR— letter
  * Links to blog post via blogPostId
- Archive 'Letter to The Economist' from blog posts (it's the cover letter)
- Fix date display on article cards (use published_at)
- Target publication already displaying via blue badge

Database changes:
- Make blogPostId optional in SubmissionTracking model
- Economist package ID: 68fa85ae49d4900e7f2ecd83
- Le Monde package ID: 68fa2abd2e6acd5691932150

Next: Enhanced modal with tabs, validation, export

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 08:47:42 +13:00
TheFlow
46f3d6e7c6 feat(blog): add Manage Submission modal for publication tracking
Implements comprehensive submission tracking workflow for blog posts
targeting external publications. This feature enables systematic
management of submission packages and progress monitoring.

Frontend:
- Add submission-modal.js with complete modal implementation
- Modal includes publication selector (22 ranked publications)
- 4-item submission checklist (cover letter, pitch, notes, bio)
- Auto-save on blur with success indicators
- Progress bar (0-100%) tracking completion
- Requirements display per publication
- Update blog-validation.js with event handlers
- Update cache versions (HTML, service worker, version.json)

Backend:
- Add GET /api/blog/:id/submissions endpoint
- Add PUT /api/blog/:id/submissions endpoint (upsert logic)
- Implement getSubmissions and updateSubmission controllers
- Fix publications controller to use config helper functions
- Integration with SubmissionTracking MongoDB model

Version: 1.8.4

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-24 01:55:06 +13:00
TheFlow
325a06139f chore(frontend): update cache-busting versions and i18n
Frontend Maintenance:
- Updated cache-busting version parameters on all script/CSS links
- researcher.html: Version updates for navbar, i18n, scroll-animations
- implementer.html: Version updates for components
- leader.html: Version updates for components
- i18n-simple.js: Updated internationalization utility

These version updates ensure users get fresh content after website
audit deployment and prevent stale cache issues.

All changes deployed to production and verified working.
2025-10-23 10:57:32 +13:00
TheFlow
b69b7167a9 feat(leader): WCAG accessibility with 9 accordions, keyboard navigation
- Converted all 9 accordion divs to semantic <button> elements
- Added ARIA attributes: aria-expanded, aria-controls, id for each button
- Accordion content: role="region" and aria-labelledby for screen readers
- Keyboard support: Enter and Space keys toggle accordions (WAI-ARIA pattern)
- Mobile optimization: 44px/48px touch targets, touch-action: manipulation
- iOS tap feedback: -webkit-tap-highlight-color
- Footer i18n: No footer object in leader.json (uses common.json correctly)
- Updated leader-page.js with keyboard handlers and ARIA state management
- Version 1.5.0

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-23 00:19:23 +13:00
TheFlow
7a4603b3a6 feat(researcher): WCAG compliance, Berlin/Weil foundations, fixed footer i18n
- Full WCAG accessibility: ARIA attributes (aria-expanded, aria-controls), keyboard navigation (Enter/Space)
- Reframed research context: Berlin/Weil as primary intellectual foundation (moral pluralism, categorical imperative)
- Bibliography with proper academic citations: Weil (The Need for Roots, Gravity and Grace), Berlin (Four Essays on Liberty)
- Fixed footer i18n: Implemented recursive deepMerge() to preserve nested translation objects
- Root cause: Shallow merge {...obj1, ...obj2} was overwriting entire footer object from common.json
- Consolidated all footer translations in common.json, removed from page-specific files
- Mobile optimization: 44px/48px touch targets, touch-action: manipulation, responsive design
- Progressive enhancement: <noscript> fallback for JavaScript-disabled users
- Version 1.3.0

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-22 23:56:37 +13:00
TheFlow
6496e0d811 refactor: remove entire public/ directory - Tractatus PROJECT web interface
REMOVED: All 37 files in public/ directory

This is the Tractatus PROJECT's web interface (admin system, website features),
NOT framework implementation code.

Files removed:
- Admin system (4 pages): dashboard, hooks-dashboard, login, rule-manager
  - Shows: Moderation Queue, Users, Documents, Blog Curation
  - This is OUR project admin, not tools for framework implementers
- Admin JavaScript (8 files)
- CSS/fonts (10 files)
- Images (4 files)
- Components (3 files): interactive-diagram, navbar-admin, pressure-chart
- Demos (5 files): 27027, boundary, classification, deliberation, tractatus
- Utils (1 file): api.js
- Favicons (2 files)

REASON: public/ directory contained Tractatus PROJECT website/admin interface.
Framework implementers don't need OUR admin system - they build their own.

All web interface code belongs in internal repository only.

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 21:57:02 +13:00
TheFlow
aab23e8c33 refactor: deep cleanup - remove all website code from framework repo
REMOVED: 77 website-specific files from src/ and public/

Website Models (9):
- Blog, CaseSubmission, Document, Donation, MediaInquiry,
  ModerationQueue, NewsletterSubscription, Resource, User

Website Services (6):
- BlogCuration, MediaTriage, Koha, ClaudeAPI, ClaudeMdAnalyzer,
  AdaptiveCommunicationOrchestrator

Website Controllers (9):
- blog, cases, documents, koha, media, newsletter, auth, admin, variables

Website Routes (10):
- blog, cases, documents, koha, media, newsletter, auth, admin, test, demo

Website Middleware (4):
- auth, csrf-protection, file-security, response-sanitization

Website Utils (3):
- document-section-parser, jwt, markdown

Website JS (36):
- Website components, docs viewers, page features, i18n, Koha

RETAINED Framework Code:
- 6 core services (Boundary, ContextPressure, CrossReference,
  InstructionPersistence, Metacognitive, PluralisticDeliberation)
- 4 support services (AnthropicMemoryClient, MemoryProxy,
  RuleOptimizer, VariableSubstitution)
- 9 framework models (governance, audit, deliberation, project state)
- 3 framework controllers (rules, projects, audit)
- 7 framework routes (rules, governance, projects, audit, hooks, sync)
- 6 framework middleware (error, validation, security, governance)
- Minimal admin UI (rule manager, dashboard, hooks dashboard)
- Framework demos and documentation

PURPOSE: Tractatus-framework repo is now PURELY framework code.
All website/project code remains in internal repo only.

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 21:22:40 +13:00
TheFlow
0dd4a5f6c8 refactor: reduce public repo to minimal implementation-only resource
REMOVED: 267 non-implementation files (51% reduction)

Categories removed:
- Research documents & case studies (35 files)
- Planning/internal development docs (28 files)
- Website pages & assets (93 files - this is framework code, not website code)
- Audit reports (6 files)
- Non-essential admin UI (11 files)
- Markdown content duplicates (10 files)
- Internal development scripts (96 files)
- Internal setup docs (2 files)

RETAINED: 253 implementation-focused files
- Core framework services (src/)
- Test suite (tests/)
- API documentation (docs/api/)
- Deployment quickstart guide
- Essential admin UI (rule manager, dashboard, hooks dashboard)
- Architecture decision records
- Configuration files

PURPOSE: Public repo is now focused exclusively on developers
implementing Tractatus, not researchers studying it or users visiting
the website. All background/research content available at
https://agenticgovernance.digital

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 21:09:34 +13:00
TheFlow
1c7e1c0e36 CRITICAL: Remove 27 internal files + fix SyDigital reference
SECURITY CLEANUP - Phase 2:
Removed internal development files that should never have been public:

INTERNAL SESSION DOCS (11 files):
- docs/research/phase-5-session*.md (9 files)
- docs/markdown/phase-5-session*.md (2 files)

INTERNAL ADMIN TOOLS (2 files):
- public/admin/claude-md-migrator.html
- public/js/admin/claude-md-migrator.js

INTERNAL STRIPE SCRIPTS (6 files):
- scripts/check-stripe-bank-account.js
- scripts/setup-stripe-products.js
- scripts/stripe-webhook-setup.sh
- scripts/test-stripe-connection.js
- scripts/test-stripe-integration.js
- scripts/verify-stripe-portal.js

INTERNAL TEST FILES (3 files):
- scripts/test-deliberation-session.js
- scripts/test-session*.js (2 files)

INTERNAL PDF DOCS (5 files):
- claude-code-framework-enforcement.pdf
- concurrent-session-architecture-limitations.pdf
- framework-governance-in-action*.pdf
- ai-governance-business-case-template.pdf
- comparison-matrix*.pdf

FIXES:
- Changed 'SyDigital Ltd' → 'Tractatus Framework Team' in claude-code-framework-enforcement.md
- Added .gitignore patterns to prevent re-adding these files

TOTAL: 27 internal files removed from public tracking
2025-10-21 20:35:34 +13:00
TheFlow
9b85fb4435 fix(content): remove prohibited terms from public UI files (inst_016/017/018)
FIXED PUBLIC UI FILES (10 violations → 0):

public/implementer.html (1 violation):
- Line 86: Removed "production-ready" claim
  "not production-ready commercial software" → "not commercial software"

public/locales/en/implementer.json (1 violation):
- Line 16: Removed "production-ready" claim (matches HTML)

public/js/faq.js (8 violations):
- Line 104: "architectural guarantee" → "architectural enforcement"
  (Constitutional AI comparison)

- Line 895-896: Guard dog analogy fixes
  "not guaranteed" → "not reliable"
  "always work" → "work consistently"

- Line 2119: Framework description
  "production-ready commercial product" → "research implementation, not commercial product"

- Line 2338: Liability disclaimer
  "Guarantee: No software can guarantee" → "Absolute certainty: No software can prevent all"

- Line 2355: Risk comparison
  "No enforcement guarantees" → "No enforcement mechanisms"

- Line 2422: Developer liability mitigation
  "No false production-ready claims" → "Accurate maturity statements (research, not commercial)"

RESULT: All public-facing UI content now inst_016/017/018 compliant

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 17:49:56 +13:00
TheFlow
5da31237b6 fix(values): remove prohibited 'guarantee' language from user-facing content
VIOLATION: Using absolute assurance language violates inst_017
- README.md: "architectural AI safety guarantees" → "enforcement"
- README.md: "guarantees transparency" → "provides transparency"
- public/index.html meta: "guarantees" → "enforcement"
- public/about.html CTA: "architectural guarantees" → "constraints"
- public/js/components/footer.js: "guarantees" → "enforcement"
- public/js/faq.js (5 instances): "guarantees" → "enforcement/constraints"
- public/locales/en/*.json (3 files): "guarantees" → "enforcement/constraints"
- scripts/seed-first-blog-post.js: "safety guarantees" → "safety constraints"

RESULT: All user-facing "guarantee" language removed
- Production website now compliant with inst_017
- No absolute assurance claims in public content
- Framework documentation still pending (hook blocked markdown edits)

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 15:19:25 +13:00
TheFlow
0958d8d2cd fix(mongodb): resolve production connection drops and add governance sync system
- Fixed sync script disconnecting Mongoose (prevents production errors)
- Created text search index (fixes search in rule-manager)
- Enhanced inst_024 with closedown protocol, added inst_061
- Added sync infrastructure: API routes, dashboard widget, auto-sync
- Fixed MemoryProxy tests MongoDB connection
- Created ADR-001 and integration tests

Result: Production stable, 52 rules synced, search working

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 11:39:05 +13:00
TheFlow
8667088c5f feat(admin): Phase 2 - standardize admin UI with unified navbar component
SUMMARY:
Completed Phase 2 of admin UI overhaul: Created unified navbar component
for simple pages, standardized CSS versioning across all pages, and fixed
broken navigation. Pragmatic approach preserves valuable cross-page navigation
while ensuring consistency.

CHANGES - Simple Pages (Unified Navbar Component):
- newsletter-management.html: Replaced custom navbar with component
- hooks-dashboard.html: Replaced custom navbar with component
- audit-analytics.html: Fixed wrong navbar (was using public site component)

CHANGES - Complex Pages (Standardized CSS Only):
- case-moderation.html: Added CSS version v=1759833751
- media-triage.html: Added CSS version v=1759833751
- project-manager.html: Updated CSS version to v=1759833751
- rule-manager.html: Updated CSS version to v=1759833751
(These pages retained custom navbars to preserve cross-page navigation UX)

COMPONENT ENHANCEMENTS:
- navbar-admin.js: Added 'hooks' icon for Framework Hooks Dashboard
- Newsletter management JS: Removed manual admin-name and logout handling

CSS STANDARDIZATION:
Target version: /css/tailwind.css?v=1759833751
- 7 pages now use standardized version (was 3 different versions + missing)

RESULTS:
- All admin pages now have consistent navbar styling
- Simple pages use unified component (3 pages)
- Complex pages use standardized custom navbars (6 pages)
- All pages have correct CSS versioning
- audit-analytics.html fixed (was using wrong component)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 21:51:09 +13:00
TheFlow
85794f1221 feat(admin): add unified navbar component (Phase 2 start)
Created reusable admin navbar component for consistency across all 11 admin pages.

COMPONENT:
- public/js/components/navbar-admin.js (minified for performance)

FEATURES:
- Consistent branding and layout
- Auto-displays admin name from localStorage
- Dashboard back link (except on dashboard itself)
- Unified logout behavior
- Configurable page title and icon

USAGE:
<div id="admin-navbar" data-page-title="Page Name" data-page-icon="icon-name"></div>
<script src="/js/components/navbar-admin.js"></script>

NEXT STEPS (Phase 2 continuation):
- Update all 11 admin pages to use this component
- Standardize CSS versioning
- Verify API endpoints

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 21:38:20 +13:00
TheFlow
3525c83dd2 fix(admin): Phase 1 - critical auth and navigation fixes
SUMMARY:
Fixed 3 broken admin pages (newsletter, hooks dashboard, migrator) and
standardized navigation links. These pages were completely non-functional
due to localStorage key mismatches.

CRITICAL FIXES:
1. newsletter-management.js:
   - token → admin_token (5 occurrences)
   - admin → admin_user (2 occurrences)
   - Now matches login.js localStorage keys

2. hooks-dashboard.js:
   - tractatus_admin_token → admin_token
   - Now uses correct auth token

3. claude-md-migrator.js:
   - auth_token → admin_token (2 occurrences)
   - Added missing apiRequest() helper function
   - Fixed logout to clear both admin_token and admin_user

NAVIGATION FIXES:
4. newsletter-management.html:
   - dashboard.html → /admin/dashboard.html (absolute path)

5. claude-md-migrator.html:
   - ../css/tailwind.css → /css/tailwind.css?v=1759833751 (absolute + version)
   - Added tractatus-theme.min.css

BEFORE (BROKEN):
- Newsletter Management:  Auth failed (wrong token key)
- Hooks Dashboard:  Auth failed (wrong token key)
- CLAUDE.md Migrator:  Auth failed + missing apiRequest()

AFTER (WORKING):
- Newsletter Management:  Auth works, all API calls function
- Hooks Dashboard:  Auth works, metrics load
- CLAUDE.md Migrator:  Auth works, API requests function

NEXT STEPS (Phase 2):
- Create unified admin navbar component
- Standardize CSS versioning across all pages
- Verify/create missing API endpoints

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 21:33:50 +13:00
TheFlow
4e4401a117 fix(auth): resolve admin login - token sanitization and missing password field
SUMMARY:
Fixed admin login failures caused by two issues:
1. Response sanitization middleware stripping auth tokens
2. Admin users missing password field in database

ROOT CAUSE ANALYSIS:
- sanitizeResponseData middleware removed ALL fields named 'token'
- This included authentication tokens that SHOULD be sent to clients
- Admin user records created without proper password field
- User.authenticate() failed on bcrypt.compare() with undefined password

FIXES:
1. Changed auth response field from 'token' to 'accessToken'
   - Avoids overly aggressive sanitization
   - More semantically correct (it's specifically an access token)
   - Frontend updated to use data.accessToken

2. Created fix-admin-user.js script
   - Properly creates admin user via User.create()
   - Ensures password field is bcrypt hashed
   - Deletes old malformed user records

3. Updated login.js auto-fill for correct dev email
   - Changed from admin@tractatus.local to admin@agenticgovernance.digital

TESTING:
- Local login now returns accessToken (308 char JWT)
- User object returned with proper ID serialization
- Auth flow: POST /api/auth/login → returns accessToken + user
- Ready for production deployment

FILES:
- src/controllers/auth.controller.js: Use accessToken field
- public/js/admin/login.js: Store data.accessToken, update default email
- scripts/fix-admin-user.js: Admin user creation/fix utility

NEXT STEPS:
1. Deploy to production
2. Run: node scripts/fix-admin-user.js admin@agenticgovernance.digital <password>
3. Test admin login at /admin/login.html

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 21:13:42 +13:00
TheFlow
7c62d35bf9 fix(ui): improve pressure monitor visibility and add timeline synchronization
SUMMARY:
Fixed button visibility issues in Context Pressure Monitor and added
interactive timeline synchronization. Three selectable execution paths
with realistic timing profiles.

UI FIXES (pressure-chart.js):
- Reduced gauge size 20% to prevent arc cut-off
- Changed button layout to side-by-side (flex-row)
- Fixed Reset button contrast (bg-gray-900 for WCAG AA)
- Added mobile responsive layout (flex-col sm:flex-row)
- Removed all wrapper div backgrounds causing visibility issues
- Trigger timeline simulation when pressure simulation runs

TIMELINE ENHANCEMENTS (activity-timeline.js):
- Added three execution path profiles (Fast/Standard/Complex)
- Fast: 65ms total (simple requests, all checks pass)
- Standard: 135ms total (needs validation and verification)
- Complex: 285ms total (requires deliberation and consensus)
- Real-time event activation synchronized with pressure changes
- Added timing disclaimer (estimates based on performance data)
- Path selection UI with radio buttons

ARCHITECTURE PAGE:
- Updated script versions for cache-busting
- Added test page for standalone pressure chart debugging

ISSUE RESOLVED:
User reported 'Simulate Pressure Increase' button hidden. Root cause:
Tailwind CSS class conflicts (user correctly identified early). Resolved
by simplifying button layout and removing constraining containers.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 17:18:13 +13:00
TheFlow
8dbdf53ca7 debug(pressure-chart): add render() logging to diagnose invisible HTML
SUMMARY:
Added logging at start of render() and after innerHTML to see if HTML
is being generated but not displayed.

CHANGES:
- Log when render() is called with container reference
- Log innerHTML length after setting
- Log first 100 chars of innerHTML
- Bump version to v20251019174000

ISSUE:
User cannot see 'Simulate Pressure Increase' button despite initialization
succeeding. Need to verify if HTML is being generated at all.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 08:16:02 +13:00
TheFlow
0e0c004728 debug(pressure-chart): add detailed logging for element discovery and button clicks
SUMMARY:
Added comprehensive logging to diagnose pressure monitor demo issue.
Will show if elements are found after innerHTML set and if event listeners
are attached successfully.

CHANGES:
- Log all element discovery (gauge, buttons, metrics)
- Log event listener attachment success/failure
- Log when simulate() and reset() methods are called
- Bump version to v20251019173500

DEBUGGING:
User reports demo not working despite initialization succeeding.
These logs will reveal:
- If DOM elements are queryable after innerHTML
- If event listeners are successfully attached
- If button clicks are triggering methods

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-20 07:47:31 +13:00
TheFlow
4b9da2d285 debug(demos): add console logging to diagnose initialization issues
SUMMARY:
Added detailed console logging to pressure chart and activity timeline
components to help diagnose why demos aren't working on production.

CHANGES:

1. pressure-chart.js:
   - Log when script loads and document.readyState
   - Log whether waiting for DOMContentLoaded or initializing immediately
   - Log when container is found or not found
   - Log when instance is created

2. activity-timeline.js:
   - Same logging pattern as pressure-chart.js

DEBUGGING:
User reports demos not working. Logs will show:
- If scripts are loading
- If DOM is ready when scripts execute
- If containers are being found
- If instances are being created

Console output will help identify the failure point.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 22:31:56 +13:00
TheFlow
0c09119e61 fix(demos): resolve initialization timing for pressure chart and activity timeline
SUMMARY:
Fixed critical bug preventing pressure chart and activity timeline demos
from initializing. Both components now work correctly on architecture page.

ROOT CAUSE:
Scripts loaded at end of body after DOM was already ready. DOMContentLoaded
event had already fired, so initialization callback never executed.

FIX:
Changed initialization to check document.readyState before adding event listener:
- If DOM still loading → wait for DOMContentLoaded event
- If DOM already ready → initialize immediately

FILES FIXED:
- public/js/components/pressure-chart.js (lines 213-227)
- public/js/components/activity-timeline.js (lines 124-137)

IMPACT:
Both demos now function correctly:
✓ Pressure chart: Simulate button works, gauge animates, metrics update
✓ Activity timeline: Governance flow displays with service colors

TESTING:
Verified locally on http://localhost:9000/architecture.html
Both demos initialize and respond to user interactions.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 22:10:14 +13:00
TheFlow
2e5756a43c feat(demos): create interactive pluralistic deliberation demo
SUMMARY:
Completed Phase 3 Task 3.4.2 - Created comprehensive interactive demo
showing how PluralisticDeliberationOrchestrator facilitates multi-stakeholder
values deliberation without making autonomous normative choices.

NEW DEMO: PLURALISTIC DELIBERATION

**Scenario:**
Security vulnerability discovery - should AI report it publicly, fix quietly,
or coordinate disclosure? This creates values conflicts between:
- Developer reputation vs. user safety
- Organizational liability vs. transparency
- Community norms vs. market dynamics

**Interactive Features:**

1. **Two Paths:**
   - Autonomous Decision: Shows why AI can't/shouldn't decide values
   - Deliberation: Shows framework facilitation in action

2. **Stakeholder Selection (Step 1):**
   - 6 stakeholder types to choose from
   - Developer, End Users, Organization, Security Community, Competitors, Regulators
   - Each with distinct icon, color, perspective
   - Clickable cards with visual selection state
   - Requires minimum 2 stakeholders to proceed

3. **Perspective Exploration (Step 2):**
   - Dynamically shows selected stakeholders' views
   - Each perspective includes:
     * Primary concern
     * Full viewpoint explanation
     * Priority statement
   - Color-coded by stakeholder type
   - No ranking or weighting applied

4. **Human Decision (Step 3):**
   - 4 decision options provided:
     * Full Disclosure (transparency priority)
     * Private Fix (balance approach)
     * Coordinated Disclosure (community norms)
     * Defer Decision (consult more stakeholders)
   - Framework facilitates but doesn't decide
   - Human makes final choice

5. **Explanation Section:**
   - Side-by-side comparison:
     * What framework DOES (facilitate, surface, record)
     * What framework DOESN'T DO (weight, rank, decide)
   - Explains values pluralism principle
   - Reset button to try different stakeholder combinations

**Design Patterns:**

- Teal color scheme (deliberation service brand color)
- Service icon in header (multi-stakeholder symbol)
- Fade-in animations for smooth UX
- Responsive grid layouts
- Hover effects on all interactive elements
- Clear visual states (selected, active, clickable)

**Stakeholder Perspectives (6 total):**

1. **Developer**: Reputation & timeline concerns
2. **End Users**: Data safety & transparency rights
3. **Organization**: Liability & brand protection
4. **Security Community**: Responsible disclosure norms
5. **Competitors**: Market dynamics
6. **Regulators**: Compliance & user rights (GDPR)

Each stakeholder has:
- Unique icon and color
- Specific concern area
- Full perspective explanation
- Priority statement

**Educational Value:**

- Demonstrates values incommensurability
- Shows why AI shouldn't autonomously decide normative questions
- Illustrates framework's facilitation role
- Highlights human agency preservation
- Explains pluralistic deliberation principle

**Technical Details:**

HTML (deliberation-demo.html):
- 3-step interactive flow
- Autonomous vs. deliberation path choice
- Dynamic stakeholder cards
- Dynamic perspective rendering
- 4 decision options
- Comprehensive explanation section

JavaScript (deliberation-demo.js):
- 6 stakeholder definitions with full data
- Selection state management
- Dynamic content rendering
- Event handlers for all interactions
- Reset functionality
- Smooth scrolling between sections

**CSP Compliance:**
✓ Zero violations
✓ No inline event handlers
✓ Event listeners properly attached
✓ Dynamic content via DOM manipulation

**Accessibility:**
- Semantic HTML structure
- Clear visual states
- Keyboard navigation supported
- Color-coded with text labels
- Responsive design maintained

**Impact:**
Completes ALL Phase 3 interactive features. Users can now:
✓ Understand how deliberation differs from decision-making
✓ Explore different stakeholder perspectives interactively
✓ Experience values pluralism firsthand
✓ See why AI autonomous normative choices are problematic

This demo, combined with the enhanced 27027 incident demo, provides
complete interactive validation of the Tractatus framework's two key
architectural principles:
1. Pattern override prevention (27027 demo)
2. Pluralistic deliberation (this demo)

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 22:03:25 +13:00
TheFlow
7eebef126f feat(demos): enhance 27027 demo with interactive features and service highlighting
SUMMARY:
Completed Phase 3 Task 3.4.1 - Enhanced the 27027 incident demo page
with interactive playback controls, service status visualization, and
clickable step navigation for better user engagement.

NEW FEATURES:

1. Clickable Step Navigation:
   - Users can click any step to jump directly to it
   - Steps highlight on hover with shadow effect
   - Manual navigation shows progress panel and service status
   - Disabled during auto-play to prevent conflicts

2. Playback Speed Controls:
   - Three speed options: Slow (4s), Normal (2.5s), Fast (1s)
   - Visual button state shows selected speed
   - Speed persists during playback
   - Default: Normal speed

3. Service Status Visualization:
   - New panel shows active Tractatus services
   - InstructionPersistence highlights on Step 6 (purple ring)
   - CrossReferenceValidator highlights on Step 7 (purple ring)
   - Service icons use brand colors (indigo/purple)
   - Smooth opacity transitions

4. Enhanced Visual Feedback:
   - Steps now reset properly when navigating backward
   - Future steps return to pending state
   - Hover effects on all steps
   - Smooth scroll behavior
   - Better state management (pending/active/complete/error)

5. Improved UX:
   - Service status hidden until first interaction
   - Progress panel shows after first play/click
   - Reset clears all state including services
   - Click handlers respect auto-play state

TECHNICAL DETAILS:

JavaScript (27027-demo.js):
- Added playbackSpeed variable and speedDelays mapping
- Enhanced initTimeline() with click handlers for navigation
- Updated playScenario() to use speed setting
- New updateServiceStatus() function for service highlighting
- Enhanced showStep() to handle forward/backward navigation
- Updated resetScenario() to clear service status

HTML (27027-demo.html):
- Added speed control buttons (Slow/Normal/Fast)
- Added service status panel with 2 services
- Service indicators use brand colors
- All controls use Tailwind utility classes

DESIGN PATTERNS:
- Brand-consistent colors (indigo-600, purple-600)
- Smooth 300ms transitions
- Responsive design maintained
- CSP compliant (no inline handlers)

IMPACT:
Users can now:
✓ Control playback speed for better comprehension
✓ Jump to specific steps for review
✓ See which Tractatus services activate at each step
✓ Understand the architectural intervention visually

This completes all Phase 3 interactive features. Demo is now
production-ready for deployment.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 21:55:47 +13:00
TheFlow
c6ea87a6a0 feat(phase3): add data visualizations for context pressure and activity timeline
SUMMARY:
Implemented Phase 3 Tasks 3.3.1 and 3.3.2: Interactive data visualizations
showing Context Pressure Monitor metrics and Framework Activity Timeline.

CHANGES:

1. Created pressure-chart.js (new):
   - Interactive SVG gauge showing pressure levels (0-100%)
   - Color-coded status: Green (NORMAL), Amber (ELEVATED), Red (HIGH), Dark Red (CRITICAL)
   - Real-time metrics: Tokens Used, Complexity, Error Rate
   - Simulate button to demonstrate pressure increases
   - Reset button to return to normal state
   - Smooth animations with requestAnimationFrame
   - Respects prefers-reduced-motion

2. Created activity-timeline.js (new):
   - Visual timeline of 6 governance services coordinating
   - Shows request processing flow (0ms-250ms)
   - Service-specific color coding
   - Hover effects on timeline events
   - Total processing time displayed

3. Updated tractatus-theme.css:
   - Added data visualization CSS section
   - .gauge-fill-path transition styles
   - .timeline-event hover effects
   - Respects reduced motion preferences

4. Updated architecture.html:
   - Added "Framework in Action" section
   - Two-column grid layout for visualizations
   - Container divs: #pressure-chart and #activity-timeline
   - Script references for both components

FEATURES:

Context Pressure Visualization:
✓ Animated gauge (0-180 degree arc)
✓ Dynamic color changes based on pressure level
✓ Three metrics tracked (tokens, complexity, errors)
✓ Interactive simulation (30% → 50% → 70% → 85%)
✓ Reset functionality

Framework Activity Timeline:
✓ 6 governance services shown in sequence
✓ Service-specific colors match brand system
✓ Hover effects for interactivity
✓ Total processing time: 250ms

UI_TRANSFORMATION_PROJECT_PLAN.md:
✓ Phase 3 Task 3.3.1: Context Pressure Visualization (COMPLETED)
✓ Phase 3 Task 3.3.2: Framework Activity Timeline (COMPLETED)

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 20:49:26 +13:00
TheFlow
b1ddb04576 feat(phase3): implement smooth page transitions with fade effect
SUMMARY:
Implemented Phase 3 Task 3.5: Page Transitions - smooth fade transitions
between pages for improved perceived performance and user experience.

CHANGES:

1. Created page-transitions.js (new):
   - PageTransitions class with fade out/in effects
   - Attaches to all internal links automatically
   - Excludes external links, downloads, and hash links
   - Respects Ctrl/Cmd+click for new tab behavior
   - 300ms transition duration
   - Console logging for debugging

2. Updated tractatus-theme.css:
   - Added page transition CSS section
   - body fade-in/fade-out classes
   - Respects prefers-reduced-motion for accessibility
   - Smooth 0.3s opacity transitions

3. Added script to key pages:
   - public/index.html
   - public/architecture.html
   - public/about.html
   - public/researcher.html
   - public/leader.html
   - public/implementer.html

4. Regenerated tractatus-theme.min.css with new transitions

FEATURES:
✓ Smooth fade-out when clicking internal links
✓ Fade-in on page load
✓ Maintains navbar/footer during transition
✓ Improves perceived performance
✓ Accessible (respects reduced motion preference)
✓ Doesn't break Ctrl+click or right-click

UI_TRANSFORMATION_PROJECT_PLAN.md:
✓ Phase 3 Task 3.5: Page Transitions (COMPLETED)

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 20:44:25 +13:00
TheFlow
dd32dac99b fix(interactive): fix diagram sizing (75% reduction) and improve SVG detection
SUMMARY:
Fixed diagram to be 75% smaller in surface area (50% linear reduction) and
improved SVG detection logic to properly initialize click handlers.

CHANGES:

1. Diagram Sizing (architecture.html):
   - Changed from w-24/w-32/w-40 (90% reduction) to w-48/w-56/w-64 (75% reduction)
   - Mobile: w-48 = 192px (50% of 384px original)
   - Tablet: sm:w-56 = 224px (50% of 448px original)
   - Desktop: lg:w-64 = 256px (50% of 512px original)
   - Surface area now 25% of original (75% reduction as requested)

2. SVG Detection Logic (interactive-diagram.js):
   - Split null check from tagName validation
   - Added clearer console logging for debugging
   - tagName check now handles undefined gracefully
   - Should properly detect SVG and attach click handlers

PREVIOUS ISSUE:
- Diagram was w-24/w-32/w-40 (6.25% surface area = 93.75% reduction)
- SVG detection check was failing, preventing click handlers from attaching
- Combined null && tagName check was too strict

FIXES:
✓ Diagram is now 75% smaller by surface area (not 90%)
✓ SVG detection should properly initialize
✓ Click handlers should attach to service nodes

Cache-busting: v=20251019170000

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 18:35:13 +13:00
TheFlow
f0ebd1a2b0 feat(ui): reduce diagram size 75% and add permanent side-by-side panel
SUMMARY:
Reduced interactive diagram size by 75% (to 25% of original) and
implemented permanent service detail panel that displays side-by-side
with the diagram on all viewports.

CHANGES:

1. Diagram Size Reduction (architecture.html):
   - Mobile: 384px → 96px (max-w-[96px])
   - Tablet: 448px → 128px (sm:max-w-[128px])
   - Desktop: 512px → 160px (lg:max-w-[160px])
   - Removed max-height constraint
   - Removed mobile/desktop conditional widths

2. Permanent Service Panel (architecture.html):
   - Added permanent #service-detail-panel div
   - Default state: Info icon with instructions
   - Always visible (flex-1 layout)
   - Min height: 300px for consistent sizing
   - Background: gray-50 with shadow-inner

3. JavaScript Updates (interactive-diagram.js):
   - Removed dynamic panel creation/removal logic
   - Removed close button functionality
   - Removed closePanel() method entirely
   - Removed fade-in/fade-out animations
   - Panel now updates in-place when service clicked
   - Border color changes to match selected service

4. Layout Improvements (architecture.html):
   - Changed to gap-6 (applies to all viewports)
   - Diagram and panel always side-by-side on desktop
   - Stacked vertically on mobile (flex-col lg:flex-row)
   - Removed mb-6 lg:mb-0 (gap handles spacing)

RESPONSIVE BEHAVIOR:
- Mobile (<1024px): Stacked vertically, diagram 96px, panel below
- Desktop (≥1024px): Side-by-side, diagram 160px, panel fills remaining space

UX IMPROVEMENTS:
✓ Diagram much smaller, less dominant
✓ Service details always visible on canvas
✓ No modal/popup behavior - permanent panel
✓ Default state guides user to click nodes
✓ Cleaner, more professional layout

CACHE-BUSTING:
Updated interactive-diagram.js version to v=20251019164500

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 18:25:47 +13:00
TheFlow
2b7b378d08 fix(responsive): improve mobile UX and fix SVG detection on architecture page
SUMMARY:
Fixed responsive design issues and SVG detection warnings on the
interactive architecture diagram. Improved mobile layout, padding,
and element sizing.

CHANGES:

1. Interactive Diagram JavaScript (interactive-diagram.js):
   - Fixed SVG tagName check to be case-insensitive (line 152)
     Was: svg.tagName !== 'svg'
     Now: svg.tagName && svg.tagName.toLowerCase() !== 'svg'
   - Updated service detail panel responsive styling (line 258)
     Added: w-full (full width on mobile)
     Added: lg:flex-1 (flex grow on desktop)
     Changed: p-6 to p-4 sm:p-6 (responsive padding)

2. Architecture Page HTML (architecture.html):
   - Improved container responsive padding (line 333)
     Changed: p-6 lg:p-8 to p-4 sm:p-6 lg:p-8
   - Reduced desktop gap for better layout (line 335)
     Changed: lg:gap-8 to lg:gap-6
   - Made SVG container full width on mobile (line 337)
     Added: w-full lg:w-auto
   - Improved SVG responsive sizing (line 342)
     Changed: max-w-md lg:max-w-lg
     To: max-w-sm sm:max-w-md lg:max-w-lg h-auto max-h-[500px]
   - Updated cache-busting version (line 515)
     Changed: v=20251019162000 to v=20251019163000

RESPONSIVE BREAKPOINTS:
- Mobile (default): Smaller padding (p-4), smaller max-width (max-w-sm)
- Tablet (sm: ≥640px): Medium padding (p-6), medium max-width (max-w-md)
- Desktop (lg: ≥1024px): Large padding (p-8), large max-width (max-w-lg)

FIXES:
✓ SVG detection warning resolved (case-insensitive tagName check)
✓ Mobile layout improved (better padding and sizing)
✓ Service detail panel responsive (full width on mobile)
✓ Diagram height constrained (max-h-[500px])

IMPACT:
Better mobile UX with appropriately sized elements and padding.
SVG detection should no longer log warnings in console.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 18:19:39 +13:00
TheFlow
9ec76b0d2c fix(interactive): fix syntax error from smart quote and add cache-busting
SUMMARY:
Fixed critical syntax error in interactive-diagram.js caused by smart
quote character and updated cache-busting version.

ISSUE:
Line 26 had a smart quote (') instead of regular apostrophe (')
JavaScript parser treated it as string terminator, causing:
  Uncaught SyntaxError: Unexpected identifier 's'

FIX:
1. Changed smart quote to regular text in promise field
2. Updated cache-busting version from v=20251019160000 to v=20251019162000

IMPACT:
Interactive diagram now loads without syntax errors. Users can click
central core and all service nodes to explore governance architecture.

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-19 16:41:29 +13:00