TheFlow
|
86d7042f42
|
feat(governance): implement comprehensive enforcement architecture
Completes enforcement implementation from ENFORCEMENT_AUDIT.md analysis:
✅ Implemented (6 enforcement mechanisms):
1. Token checkpoint monitoring (inst_075)
- .claude/hooks/check-token-checkpoint.js
- PostToolUse hook integration
2. Trigger word detection (inst_078, inst_082)
- .claude/hooks/trigger-word-checker.js (already completed)
- "ff" and "ffs" triggers architecturally enforced
3. Framework activity verification (inst_064)
- Enhanced scripts/session-init.js with fade detection
- Alerts when components stale >20 messages
4. Test requirement enforcement (inst_068)
- Enhanced .git/hooks/pre-commit
- Runs tests if test files exist for modified code
- Blocks commits on test failures
5. Background process tracking (inst_023)
- scripts/track-background-process.js
- Integrated into session-init.js and session-closedown.js
- Tracks persistent vs temporary processes
6. Security logging verification (inst_046)
- scripts/verify-security-logging.js
- Can be integrated into deployment workflow
7. Meta-enforcement monitoring system
- scripts/audit-enforcement.js
- Scans HIGH persistence instructions for imperatives
- Reports enforcement gaps (currently 28/39 gaps)
🔒 Protection Added:
- inst_027: Hard block on instruction-history.json edits
- Conventional commit format enforcement (inst_066)
- CSP + test validation in pre-commit hook
📊 Current Enforcement Status:
- Baseline: 11/39 imperative instructions enforced (28%)
- Framework fade detection operational
- Token checkpoints architecturally monitored
🎯 Philosophy:
"If it's MANDATORY, it must be ENFORCED architecturally, not documented."
This addresses the root cause of voluntary compliance failures identified
when Claude missed "ffs" trigger and token checkpoints despite active
HIGH persistence instructions.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
|
2025-10-25 13:15:06 +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 |
|