john/tractatus
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
913 commits 1 branch 0 tags 125 MiB
Commit graph

4 commits

Author SHA1 Message Date
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
9cbc26b91b refactor: remove all non-implementation documentation 
REMOVED: 11 background/internal documentation files from docs/

Internal Project Documentation (3):
- ADR-001-dual-governance-architecture.md - Internal decision about file vs DB storage
- IMPLEMENTATION_PLAN_2025-10-21.md - Internal planning (session effectiveness 4/10)
- USER_GUIDE_PROJECTS.md, USER_GUIDE_RULE_MANAGER.md - Admin UI guides for Tractatus website

Background/Educational Content (5):
- GLOSSARY.md (both versions) - "Non-technical stakeholders" glossary
- introduction.md - Wittgenstein philosophy background
- core-concepts.md - Conceptual explanations
- technical-architecture.md - Internal architecture overview

Diagrams (2):
- architecture-diagram.mmd, architecture-diagram-generic.mmd - Show website features

RETAINED Implementation Docs:
- API documentation (docs/api/) - RULES_API, PROJECTS_API, OpenAPI spec, examples
- Architecture diagrams (docs/diagrams/*.svg) - Visual reference
- Deployment quickstart

REASON: Public GitHub is for developers IMPLEMENTING the framework,
not for understanding what Tractatus is philosophically or how the
Tractatus project internally works.

All background content belongs on https://agenticgovernance.digital

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-21 21:28:57 +13:00
TheFlow
c984ebfd7d feat: add runtime-agnostic architecture page with honest early-stage positioning 
Created new /architecture.html page with generic architecture diagram that emphasizes Tractatus works with any agent runtime (not just Claude Code). Revised tone to reflect early-stage research status, including limitations section and call for industry collaboration, per user feedback on avoiding overconfident claims.

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

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-13 21:51:58 +13:00
TheFlow
e086066b99 feat: technical architecture diagram with comprehensive documentation (Task 8) 
Complete system architecture visualization showing Claude Code + Tractatus
integration across 4 layers: API/Web, Governance, Persistence, and Runtime.

**Diagram Files:**

1. architecture-diagram.svg (15KB)
   - Scalable vector format for web and documentation
   - 4-layer visualization with color-coded components
   - Data flow arrows showing integration points
   - Professional design suitable for research papers

2. architecture-diagram.png (581KB)
   - High-resolution 2400x2000 raster format
   - Generated via Inkscape from SVG
   - Suitable for presentations and print materials

3. architecture-diagram.mmd
   - Mermaid diagram for markdown embedding
   - Supports dynamic rendering in documentation
   - Version control friendly text format

**Documentation:**

4. docs/markdown/technical-architecture.md (18KB)
   - Comprehensive technical architecture guide
   - Layer-by-layer component descriptions
   - Integration points and data flows
   - Performance characteristics (<10ms overhead)
   - Deployment architecture (Docker/systemd)
   - Complementarity with Claude Code explanation

5. public/downloads/technical-architecture-diagram.pdf
   - Generated from markdown with embedded diagram
   - Complete documentation in portable format
   - Suitable for offline reading and distribution

**Implementer Page Integration:**

6. public/implementer.html
   - Added "System Architecture" section after Deployment Quickstart
   - Full-width diagram display with shadow effects
   - Three download buttons: SVG, PNG (High-Res), PDF
   - 4-card layer breakdown (API → Governance → Persistence → Runtime)
   - 3-point integration explanation with numbered badges
   - Professional color scheme matching brand (purple/green/yellow/blue)

**Architecture Layers:**

Layer 4 - API & Web Interface:
  - Demo endpoints (/api/demo/*)
  - Admin dashboard
  - Documentation system
  - Blog with AI curation

Layer 3 - Tractatus Governance:
  - BoundaryEnforcer (values decisions)
  - InstructionPersistenceClassifier (classification)
  - CrossReferenceValidator (pattern bias prevention)
  - ContextPressureMonitor (degradation detection)
  - MetacognitiveVerifier (complex operation verification)

Layer 2 - MongoDB Persistence:
  - governance_rules collection (rule storage with indexes)
  - audit_logs collection (compliance trail)
  - session_state collection (pressure tracking)
  - instruction_history collection (cross-reference validation)

Layer 1 - Claude Code Runtime:
  - Base LLM environment (200k context window)
  - Session management (persistent state)
  - Tool access (Bash, Read, Write, Edit)
  - File system operations (.claude/ directory)

**Key Integration Points:**

1. Pre-Action Checks:
   - All actions validated against governance rules
   - BLOCK or ALLOW with explanation
   - Audit log entry created

2. Instruction Persistence:
   - User instructions classified (quadrant, persistence, scope)
   - Stored in .claude/instruction-history.json + MongoDB
   - Cross-referenced before conflicting actions

3. Context Pressure Monitoring:
   - Real-time pressure calculation (tokens, messages, errors)
   - Mandatory checkpoint reporting (50k, 100k, 150k)
   - Early warning system for degradation

**The 27027 Incident Prevention Flow:**

User: "Use MongoDB port 27027"
  → Classifier: SYSTEM/HIGH/session
  → Stored in instruction_history
[107k tokens later, pressure builds]
AI attempts: port 27017 (pattern recognition)
  → CrossReferenceValidator: CONFLICT DETECTED
  → Action BLOCKED, user notified
  → AI corrects to 27027
  → Audit log created

**Deployment:**

✅ Deployed to production:
  - SVG/PNG diagrams to /public/images/
  - PDF to /public/downloads/
  - Markdown docs to /docs/markdown/
  - Updated implementer.html with diagram section

**Roadmap Progress:**

Phase 2, Week 3, Task 8: Technical Architecture Diagram - COMPLETED
Priority: High | Effort: 4-6 hours | Status: ✅ Done

**Success Criteria Met:**

✓ Clear, professional diagram explaining complementarity with Claude Code
✓ High-resolution exports (SVG, PNG, PDF)
✓ Comprehensive technical documentation
✓ Integrated into implementer page
✓ Multiple format downloads available
✓ Layer-by-layer component breakdown
✓ Data flow visualization
✓ Performance metrics documented

Next: Task 9 - Video Walkthrough (Week 3, 2-3 days)

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

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-10-12 07:37:10 +13:00