Short answer first, since that’s the actual question: a Sacred Spine is an enforced sequence of record types, in Craft11, Client → Inquiry → Offer → Project → Invoice, where each stage can only exist if its predecessor exists. Not “should.” Can’t. The database itself won’t let an Offer be created without a parent Inquiry attached to it.
That’s the whole mechanism. The interesting part is why it matters more than it sounds like it should.
The problem it’s actually solving
Most business software treats workflow as a suggestion. There’s a pipeline view, sure, with columns for “lead,” “negotiating,” “won.” But nothing stops you from creating an invoice with no project behind it, or a project that never had a real offer, because someone needed to start billing before the paperwork caught up. Every business does this eventually. It’s not negligence. It’s just what happens when the tool doesn’t care about order and a deadline is closer than the admin work.
The cost shows up later, quietly. Someone asks “what did we actually agree to on this one?” and the answer lives in an email thread, not the system. A new hire opens a project record and finds three notes and no history of how the client relationship started. The system technically has the data, but not the connections between it, and connections are where the actual institutional knowledge lives.
What “enforced” really means here
This isn’t a UI nudge. It’s structural. The completeness gates sit underneath the interface, at the point where a record actually gets written. If the relationship isn’t there, the write doesn’t happen. A Project literally cannot be created floating free of an Offer, the same way a building inspector won’t sign off on a wall with no foundation under it, regardless of how good the wall looks.
The practical effect: open any Project six months from now, and the entire chain that led to it is still attached: the original raw inquiry note, the priced offer, every status change along the way. Not because someone remembered to link things. Because there was never a path to create it any other way.
What it doesn’t do
It doesn’t lock you into rigid process within a stage. You can edit freely, attach files, add both raw notes and structured updates, reassign work to whoever’s covering it this week. The constraint is on the order, not the content. And it doesn’t apply to everything in Craft11. Finance and Calendar are separate modules a company can turn off if they don’t need them. Reports can be toggled off too. The spine itself is the one piece that isn’t configurable. That’s intentional. A spine that bends defeats the purpose of having one.
It also isn’t rigid about timing. Need to send an offer before the inquiry paperwork is fully logged? Start the Offer anyway. Stark notices the gap, offers to backfill the basic parameters and a description itself, clearly marked as AI-generated, and asks before filling anything in. Need to revise pricing mid-project? Create a new Offer straight from the Project; it saves as a new version and the Project updates automatically to match. The sequence holds together. It was never about refusing to let anyone move fast.
Why the connections matter beyond record-keeping
There’s a reason this isn’t just tidier bookkeeping. Stark’s answers get sharper the more connected, structured history he has to match a new question against. An Offer that’s actually linked to its Inquiry, sitting inside a Project linked to its Invoice, is a pattern the system can find and reuse the next time something similar comes up. A pile of disconnected records, however well each one is written individually, doesn’t give the AI anything to match against. The enforcement isn’t there to make the AI’s job easier at your expense. It’s there because the same structure that keeps a person from losing context six months later is what lets the AI actually find patterns instead of guessing.