# Files to Upload to Claude Web Project Knowledge ## Priority 1: Essential Context (Upload These First) ### 1. CLAUDE_WEB_BRIEF.md **Why:** Claude-to-Claude communication written specifically for strategic discussions. Contains everything Claude Web needs to understand the framework, limitations, and opportunities. **Path:** `/home/theflow/projects/tractatus/CLAUDE_WEB_BRIEF.md` --- ### 2. docs/research/tractatus-inflection-point-2025.md **Why:** Full research paper documenting the framework's superiority over CLAUDE.md-only approaches. Includes: - Quantitative results (95% persistence, 100% boundary enforcement) - Comparison methodology - Production deployment case study - Honest limitations section - Future research questions **Path:** `/home/theflow/projects/tractatus/docs/research/tractatus-inflection-point-2025.md` --- ### 3. docs/markdown/introduction-to-the-tractatus-framework.md **Why:** Comprehensive introduction to core concepts, philosophical foundations, and practical implementation. Good starting point for understanding "what is Tractatus?" **Path:** `/home/theflow/projects/tractatus/docs/markdown/introduction-to-the-tractatus-framework.md` --- ### 4. docs/markdown/core-concepts.md **Why:** Technical deep-dive into the 6 services, their interactions, and architectural principles. Essential for technical discussions. **Path:** `/home/theflow/projects/tractatus/docs/markdown/core-concepts.md` --- ### 5. SESSION_HANDOFF_2025-10-13_ARCHITECTURE.md **Why:** Most recent session context. Shows what's been accomplished, user feedback ("order of magnitude improvement"), and current state. **Path:** `/home/theflow/projects/tractatus/SESSION_HANDOFF_2025-10-13_ARCHITECTURE.md` --- ## Priority 2: Implementation & Technical Details ### 6. docs/markdown/implementation-guide.md **Why:** Practical guide for deploying Tractatus. Shows how the framework integrates with agent runtimes and what's required for adoption. **Path:** `/home/theflow/projects/tractatus/docs/markdown/implementation-guide.md` --- ### 7. docs/markdown/technical-architecture.md **Why:** Detailed technical architecture including MongoDB schemas, service APIs, data flows. Critical for architectural discussions. **Path:** `/home/theflow/projects/tractatus/docs/markdown/technical-architecture.md` --- ### 8. docs/markdown/GLOSSARY.md **Why:** Comprehensive terminology reference. Ensures Claude Web uses terms correctly (quadrant, persistence level, temporal scope, etc.). **Path:** `/home/theflow/projects/tractatus/docs/markdown/GLOSSARY.md` --- ## Priority 3: Evidence & Case Studies ### 9. docs/case-studies/27027-incident-detailed-analysis.md **Why:** Canonical failure example that motivated CrossReferenceValidator. Shows real-world failure mode and how framework prevents it. **Path:** `/home/theflow/projects/tractatus/docs/case-studies/27027-incident-detailed-analysis.md` --- ### 10. docs/case-studies/framework-in-action-oct-2025.md **Why:** Documents AI fabrication incident (Claude invented statistics) and how framework detected and corrected it. Shows governance working in practice. **Path:** `/home/theflow/projects/tractatus/docs/case-studies/framework-in-action-oct-2025.md` --- ### 11. docs/case-studies/when-frameworks-fail-oct-2025.md **Why:** Honest documentation of when framework FAILED. Shows limitations and learning process. Critical for realistic discussion. **Path:** `/home/theflow/projects/tractatus/docs/case-studies/when-frameworks-fail-oct-2025.md` --- ## Priority 4: Strategic Context ### 12. docs/markdown/business-case-tractatus-framework.md **Why:** Business justification for governance frameworks. Useful for discussing adoption strategy and value proposition. **Path:** `/home/theflow/projects/tractatus/docs/markdown/business-case-tractatus-framework.md` --- ### 13. docs/plans/integrated-implementation-roadmap-2025.md **Why:** Strategic roadmap for framework development. Shows where we're going and what's next. **Path:** `/home/theflow/projects/tractatus/docs/plans/integrated-implementation-roadmap-2025.md` --- ### 14. docs/research/executive-summary-tractatus-inflection-point.md **Why:** Condensed version of inflection point paper. Good for quick reference on key claims and evidence. **Path:** `/home/theflow/projects/tractatus/docs/research/executive-summary-tractatus-inflection-point.md` --- ## Priority 5: Limitations & Research Needs ### 15. docs/research/rule-proliferation-and-transactional-overhead.md **Why:** Research into potential downsides of governance frameworks. Important for balanced discussion of trade-offs. **Path:** `/home/theflow/projects/tractatus/docs/research/rule-proliferation-and-transactional-overhead.md` --- ### 16. docs/markdown/llm-integration-feasibility-research-scope.md **Why:** Documents feasibility research for LLM integration. Shows what's been explored and what remains unknown. **Path:** `/home/theflow/projects/tractatus/docs/markdown/llm-integration-feasibility-research-scope.md` --- ### 17. docs/research/concurrent-session-architecture-limitations.md **Why:** Analyzes specific technical limitation (concurrent sessions). Example of honest limitation documentation. **Path:** `/home/theflow/projects/tractatus/docs/research/concurrent-session-architecture-limitations.md` --- ## Priority 6: Values & Philosophy (Optional but Valuable) ### 18. docs/markdown/organizational-theory-foundations.md **Why:** Explains theoretical foundations from organizational theory, philosophy (Wittgenstein), and political science. Good for understanding "why" behind design choices. **Path:** `/home/theflow/projects/tractatus/docs/markdown/organizational-theory-foundations.md` --- ### 19. docs/pluralistic-values-deliberation-plan-v2.md **Why:** Detailed plan for PluralisticDeliberationOrchestrator. Shows how framework handles values conflicts without imposing hierarchy. **Path:** `/home/theflow/projects/tractatus/docs/pluralistic-values-deliberation-plan-v2.md` --- ## Priority 7: Governance & Maintenance (For Complete Picture) ### 20. CLAUDE_Tractatus_Maintenance_Guide.md **Why:** Full operational manual for the framework as deployed on this project. Shows framework dogfooding itself. **Path:** `/home/theflow/projects/tractatus/CLAUDE_Tractatus_Maintenance_Guide.md` --- ### 21. docs/claude-code-framework-enforcement.md **Why:** Technical documentation of how framework enforces its own rules during Claude Code sessions. Meta-governance example. **Path:** `/home/theflow/projects/tractatus/docs/claude-code-framework-enforcement.md` --- ## Recommended Upload Strategy ### Minimum Viable Context (5 files, ~150KB) Upload these if you have file size/count limits: 1. CLAUDE_WEB_BRIEF.md 2. docs/research/tractatus-inflection-point-2025.md 3. docs/markdown/core-concepts.md 4. SESSION_HANDOFF_2025-10-13_ARCHITECTURE.md 5. docs/case-studies/27027-incident-detailed-analysis.md **This gives:** Technical foundation, evidence, current state, concrete example. --- ### Recommended Full Context (15 files, ~500KB) Upload Priority 1-4 (files 1-14) for comprehensive strategic discussions. **This gives:** Complete technical understanding, evidence base, strategic context, implementation details, honest limitations. --- ### Complete Archive (21 files, ~800KB) Upload all files if no constraints. **This gives:** Everything needed for any discussion about Tractatus—technical, strategic, philosophical, operational. --- ## How to Upload 1. **Create ZIP Archive:** ```bash cd /home/theflow/projects/tractatus # Minimum viable (5 files) zip -r tractatus-claude-web-min.zip \ CLAUDE_WEB_BRIEF.md \ docs/research/tractatus-inflection-point-2025.md \ docs/markdown/core-concepts.md \ SESSION_HANDOFF_2025-10-13_ARCHITECTURE.md \ docs/case-studies/27027-incident-detailed-analysis.md # Full context (15 files) zip -r tractatus-claude-web-full.zip \ CLAUDE_WEB_BRIEF.md \ docs/research/tractatus-inflection-point-2025.md \ docs/markdown/introduction-to-the-tractatus-framework.md \ docs/markdown/core-concepts.md \ SESSION_HANDOFF_2025-10-13_ARCHITECTURE.md \ docs/markdown/implementation-guide.md \ docs/markdown/technical-architecture.md \ docs/markdown/GLOSSARY.md \ docs/case-studies/27027-incident-detailed-analysis.md \ docs/case-studies/framework-in-action-oct-2025.md \ docs/case-studies/when-frameworks-fail-oct-2025.md \ docs/markdown/business-case-tractatus-framework.md \ docs/plans/integrated-implementation-roadmap-2025.md \ docs/research/executive-summary-tractatus-inflection-point.md \ docs/research/rule-proliferation-and-transactional-overhead.md # Complete archive (all 21 files) zip -r tractatus-claude-web-complete.zip \ CLAUDE_WEB_BRIEF.md \ docs/research/tractatus-inflection-point-2025.md \ docs/markdown/introduction-to-the-tractatus-framework.md \ docs/markdown/core-concepts.md \ SESSION_HANDOFF_2025-10-13_ARCHITECTURE.md \ docs/markdown/implementation-guide.md \ docs/markdown/technical-architecture.md \ docs/markdown/GLOSSARY.md \ docs/case-studies/27027-incident-detailed-analysis.md \ docs/case-studies/framework-in-action-oct-2025.md \ docs/case-studies/when-frameworks-fail-oct-2025.md \ docs/markdown/business-case-tractatus-framework.md \ docs/plans/integrated-implementation-roadmap-2025.md \ docs/research/executive-summary-tractatus-inflection-point.md \ docs/research/rule-proliferation-and-transactional-overhead.md \ docs/markdown/llm-integration-feasibility-research-scope.md \ docs/research/concurrent-session-architecture-limitations.md \ docs/markdown/organizational-theory-foundations.md \ docs/pluralistic-values-deliberation-plan-v2.md \ CLAUDE_Tractatus_Maintenance_Guide.md \ docs/claude-code-framework-enforcement.md ``` 2. **Upload to Claude Web Project Knowledge** - Go to Claude Web - Create new project or open existing - Upload ZIP file(s) - Claude Web will extract and index all markdown files 3. **Verify Context Loaded** Ask Claude Web: *"What is Tractatus and what are its key limitations?"* Should get response mentioning: - External governance architecture - 6 core services - 95% persistence / 100% boundary enforcement - Early-stage with no red-team testing - Voluntary invocation problem - Order of magnitude productivity improvement --- ## What This Enables With these files uploaded, Claude Web can: ✅ **Discuss architecture** - Technical depth on 6 services, data flows, schemas ✅ **Evaluate feasibility** - Understand implementation requirements and constraints ✅ **Assess evidence** - Review quantitative results and case studies ✅ **Identify gaps** - Discuss known limitations and research needs ✅ **Explore opportunities** - Brainstorm next steps, collaborations, extensions ✅ **Plan strategy** - Help prioritize roadmap based on evidence and resources ✅ **Consider risks** - Analyze failure modes and mitigation strategies ✅ **Position messaging** - Maintain honest early-stage tone consistently --- ## Initial Prompt for Claude Web (After Upload) ``` I've uploaded documentation for the Tractatus AI Safety Framework—an early-stage governance system I've been developing with Claude Code over 6 months. Start by reading CLAUDE_WEB_BRIEF.md, which is a Claude-to-Claude summary written specifically for you. Key context: - I'm a sole operator with limited technical background - Framework has delivered "order of magnitude improvement" in my productivity - It's working in practice (95% persistence, 100% boundary enforcement) but early-stage - Major limitation: voluntary AI invocation (can be bypassed) - Need strategic thinking on where to go from here After reading the brief, tell me: 1. What you understand about the framework's core innovation 2. What you see as the most important limitation to address 3. What opportunities stand out as highest leverage for a solo operator Then let's discuss strategic priorities. ``` --- **Files list complete. Ready for Claude Web strategic collaboration.**