tractatus/CLAUDE.md
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

4.1 KiB

Tractatus - Active Session Governance (Claude Code)

Project: Tractatus Website | Database: tractatus_dev (port 27017) | App Port: 9000 Status: Phase 1 Development | Separate from: family-history, sydigital


⚠️ MANDATORY SESSION START

node scripts/session-init.js

⚠️ CRITICAL: Also run this IMMEDIATELY after continuing from a compacted conversation!

This script enforces:

  • Local development server running on port 9000 (BLOCKS if not running)
  • Framework components initialized and operational
  • Token checkpoints configured (50k, 100k, 150k)
  • Session state tracking active
  • Instruction history loaded

If blocked: Follow on-screen instructions to start local server, then re-run.


⚠️ SESSION CLOSEDOWN

node scripts/session-closedown.js

Run when user requests: "wrap up", "end session", "create handoff", "process session closedown"

This script executes:

  • Background process cleanup
  • Instruction database sync verification
  • Framework performance analysis (all 6 services)
  • Audit log analysis with rule suggestions
  • Git status documentation
  • Comprehensive handoff document creation
  • Compaction marker for next session detection

STOP ALL WORK after script completes. Script output includes next session startup instructions.


🔍 FRAMEWORK TRIGGER: "ff"

When user prefixes prompt with ff, invoke full framework audit:

node scripts/framework-audit-response.js \
  --prompt "user's actual question" \
  --type "boundary_question"

Purpose: Manually trigger ALL 6 framework services for conversational responses (BoundaryEnforcer, PluralisticDeliberationOrchestrator, MetacognitiveVerifier, CrossReferenceValidator, ContextPressureMonitor, InstructionPersistenceClassifier).

When: User asks questions about VALUES, trade-offs, architectural decisions, or boundary-crossing topics.

Output: Include audit IDs in response (e.g., "🔍 Framework Audit: audit_67abc123")

See: inst_078 in instruction-history.json


🎯 QUICK REFERENCE

Database: tractatus_dev (MongoDB port 27017) App: Node.js/Express on port 9000 (systemd, NOT pm2) Stack: Vanilla JS, Tailwind CSS, MongoDB Separate from: family-history, sydigital (no shared code) Approval required: Architectural changes, DB schema, security, values Quality: World-class, no shortcuts, no fake data

Common Commands:

# Session management
node scripts/session-init.js                  # Initialize session (MANDATORY)
node scripts/session-closedown.js             # End session (user request only)
node scripts/check-session-pressure.js        # Check context pressure

# Local development
npm start                                     # Start local server (port 9000)

# Production deployment
./scripts/deploy-full-project-SAFE.sh         # Deploy to production (safe)
ssh -i ~/.ssh/tractatus_deploy ubuntu@vps-93a693da.vps.ovh.net "sudo systemctl status tractatus"
ssh -i ~/.ssh/tractatus_deploy ubuntu@vps-93a693da.vps.ovh.net "sudo systemctl restart tractatus"

# Document workflow
npm run migrate:docs -- --source docs/markdown --force
node scripts/generate-single-pdf.js <input.md> <output.pdf>

🚨 FRAMEWORK ENFORCEMENT

Governance is ENFORCED architecturally, not documented:

  1. session-init.js - Blocks without local server on port 9000
  2. Framework components - Initialize automatically, run continuously
  3. Token checkpoints - Report pressure at 50k, 100k, 150k
  4. Pre-action checks - node scripts/pre-action-check.js <type> [path] "<desc>"

Framework fade = enforcement gap → fix architecturally, not in docs.


📚 REFERENCE DOCUMENTS

  • CLAUDE_Tractatus_Maintenance_Guide.md - Full governance framework
  • docs/SESSION_MANAGEMENT_ARCHITECTURE.md - Session lifecycle design
  • .claude/instruction-history.json - Persistent instruction database (auto-accessed)

Last Updated: 2025-10-24 (Added session closedown script; session management now fully automated) Philosophy: If it can be enforced in code, it should not be documented here.