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
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
7552715b20
docs: add comprehensive security implementation roadmap
...
Created detailed 6-phase implementation plan for security framework (inst_041-046).
**Overview:**
- 8-14 week timeline across 6 phases
- Exclusive use of sovereign tools (ClamAV, YARA, SpamAssassin, fail2ban, Redis)
- Proton suite for secure email
- Signal for text/video communication
- Defense-in-depth architecture
**Phases:**
**Phase 1: Foundation (1-2 weeks)**
- Install all sovereign tools (ClamAV, YARA, fail2ban, Redis)
- Set up logging infrastructure
- Configure ProtonMail and Signal communication channels
- Create security documentation structure
**Phase 2: File & Email Security (2-3 weeks)**
- Implement file upload validation middleware (inst_041)
- Configure email security stack (postfix, SpamAssassin, amavisd-new)
- Set up quarantine management for suspicious files/emails
- DKIM/SPF/DMARC validation
**Phase 3: Application Security (1-2 weeks)**
- Deploy form input sanitization (inst_043)
- Implement HTTP security headers (inst_044)
- Add CSRF protection
- Configure CSP violation reporting
**Phase 4: API Protection (1-2 weeks)**
- Tiered rate limiting (public/authenticated/admin)
- JWT authentication (15min access, 7day refresh)
- IP blocking after repeated violations
- Request validation and response sanitization
**Phase 5: Monitoring & Alerting (2-3 weeks)**
- Build security monitoring dashboard
- Integrate fail2ban with security logs
- Configure ProtonMail alert system
- Set up Signal notifications for critical events
- Automate weekly security reports
**Phase 6: Integration & Hardening (1-2 weeks)**
- Comprehensive integration testing
- Penetration testing
- Performance optimization
- Complete security documentation
- Team training and incident response drills
**Key Features:**
- Complete code examples for all middleware
- Detailed tool configuration files
- Testing procedures for each phase
- Success criteria and rollback plans
- Resource requirements (personnel, infrastructure)
- Risk mitigation strategies
- Post-implementation maintenance schedule
- Incident response playbook
- Communication protocols (ProtonMail + Signal)
**Documentation Includes:**
- Tool installation procedures
- Configuration examples
- Integration code
- Testing procedures
- Alert threshold definitions
- Incident classification levels
- Team training modules
- Timeline and resource estimates
Total effort: 240-330 person-hours across 8-14 weeks.
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-14 14:50:33 +13:00
