USEBRICK / LOCAL CANDIDATE
The repository remembers what your agents forget.
Verified Repository Memory. Repository-owned, agent-independent, and evidence-backed. UseBrick keeps architecture, implementation, agent context, and policy aligned as AI writes more of the software.
- Repository Memory
- Scan
- Context
- Guard
- Repair
- Record
- Runtime Labs
Local candidate, not a public UseBrick release. Task-scoped Context and bounded cold-start task listing, Scan, Guard, and one bounded Repair are locally qualified. Repository Memory and the one bounded handoff Record now have locally qualified, fixed-policy admission for new v1 writes and preview-first sequential handoff continuity. It is a checked mail slot, not arbitrary data-loss prevention: older records are not certified, independent heads remain conflicts, and cross-agent usefulness is not yet proven. One bounded local Runtime Labs build-to-render smoke is qualified; broader Runtime Labs remains planned. The standalone site is live at usebrick.dev; usebrick 0.1.0 remains unpublished.