About
Repositories should retain the lessons hidden in code review.
Project Spine is a solo-maintainer beta project for teams building with coding agents. It turns a reviewed failure into explicit evidence, a narrow repository rule, and a historical replay that shows whether the rule would have caught the recorded break.
The problem
Valuable repository knowledge often appears once, in a pull-request correction: do not call this helper in a background job; this file must always register that handler; this path has a tenant boundary. The review closes, the lesson disappears into history, and the next coding agent starts with the same blind spot.
The approach
Project Spine keeps that correction as a source-linked case. It can express deterministic require-text and forbid-text rules, replay them against recorded broken and corrected commits, and enforce verified rules in CI. Relevant rules can reach any coding agent through local context and MCP. The existing compile and drift tools remain available.
The maintainer
I'm Petri Lahdelma. Background in design systems and developer tooling. Project Spine is a one-person project right now; I use it on my own client work and iterate based on what I find. The code is open on GitHub and the thinking is in PRD.md.
If you try it and it breaks, or you disagree with a decision I made, email support@projectspine.dev. I read every message. For security issues, please use security@projectspine.dev per SECURITY.md.
What you won't find
- A corporate “we”.There is no team page pretending to be a team. One maintainer, honestly labelled.
- Fake testimonials or logos.When real users show up and consent to be quoted, they'll be here. Until then, the research citations on the homepage are what we have.
- Tracking.Google Analytics is loaded for aggregate site measurement. The CLI learning, replay, guard, compile, and drift paths stay local, and repo contents are not uploaded by the public workflow. Check the site's CSP; it's documented.