Problem
Governance drift happens gradually — code changes without ledger updates, new files without REQ coverage, CI modifications without tool registry alignment. Currently you have to manually run \specsmith audit\ to catch drift.
Proposed Solution
\specsmith watch --project-dir .\ runs a background daemon that:
- Watches for file changes via filesystem events
- Auto-validates governance consistency in real-time
- Alerts when LEDGER.md hasn't been updated after code changes
- Alerts when REQ↔TEST coverage drops below threshold
- Alerts when CI config diverges from tool registry
- Provides pre-commit hook integration (beyond just lint)
- WebSocket feed for the React dashboard
- Desktop notifications (optional)
Use Cases
- Developer makes code changes → daemon alerts 'LEDGER.md not updated'
- Someone edits CI manually → daemon alerts 'CI no longer matches tool registry'
- New test file added → daemon suggests 'add Covers: REQ-xxx reference'
Problem
Governance drift happens gradually — code changes without ledger updates, new files without REQ coverage, CI modifications without tool registry alignment. Currently you have to manually run \specsmith audit\ to catch drift.
Proposed Solution
\specsmith watch --project-dir .\ runs a background daemon that:
Use Cases