What people use a spine for
A Project Spine helps you gather the context around a real problem, work with AI inside that context, produce useful output, and carry the results forward.
Browse a few examples. The goal isn't to find your exact kind of project — it's to see the pattern and imagine what a spine could do for your own work.
You may have more projects than you think. Anything you keep coming back to can count.
- Start with a real problem.
- Gather the context into a spine.
- Work with AI inside that context.
- Produce useful output.
- Fold the results back in — you review what gets saved.
Manufacturing
Work a real shop-floor problem
A machine keeps going down, a quality issue keeps returning, or an improvement project has notes, measurements, meetings, and prior attempts scattered everywhere.
Works alongside your quality systems, ERP, and document control — it doesn't replace them.
See what goes in the spine
In the spine: Machine history, manuals, measurements, operator notes, meeting notes, prior attempts, constraints, decisions, test plans, results.
The AI helps produce: Troubleshooting plans, pilot-test checklists, meeting summaries, gap lists, next-action plans, follow-up questions.
You review and add back: What was tried, what worked, what failed, updated decisions, real-world observations, next steps.
Research + purchasing
Keep a research or purchasing decision on the record
A serious evaluation — a proposal, an equipment purchase, a research question — collects specs, quotes, papers, vendor claims, comparisons, and half-settled decisions over weeks or months.
Months later, "why did we choose this one?" has an answer you can point to.
See what goes in the spine
In the spine: Requirements, specs, quotes, vendor claims, papers and references, comparison notes, constraints, what's settled, what's still open.
The AI helps produce: Comparison tables, requirement checklists, questions to send vendors, proposal drafts, summaries of where the decision stands, next steps.
You review and add back: New quotes, vendor answers, test results, changed requirements, the decision and the reasons for it.
Small business
Keep a small operation's know-how in one place
Procedures, vendor choices, customer notes, pricing decisions, and staff handoffs live in texts, emails, and someone's head.
A new helper can be handed the picture instead of shadowing someone for a month.
See what goes in the spine
In the spine: Procedures, price lists, vendor details, customer preferences, staffing notes, seasonal patterns, past decisions.
The AI helps produce: Checklists, training notes, customer follow-ups, vendor questions, schedules, drafts of the documents you keep rewriting.
You review and add back: What changed, what worked, new vendor terms, updated procedures, lessons from the season.
Education
Keep a course graded the same way in week twelve as in week one
A course accumulates a lab guide, a rubric, worked examples, and dozens of small rulings you make while grading — this counts as showing work, that unit error costs one point and not three. Each ruling comes from a specific paper. By the end of the term most of them live only in your head, and the last stack gets graded differently from the first.
The spine holds the guide, the rubric and your rulings — never student work. Your LMS stays the system of record, and you read and enter every grade yourself.
See what goes in the spine
In the spine: The lab guide or assignment as issued, the rubric as approved, grading rulings with the reasoning that produced them, worked examples, common misconceptions, feedback phrasings you reuse.
The AI helps produce: Draft comments against the rubric, consistency checks across a stack, a summary of where a class is losing points, questions to ask before you deduct.
You review and add back: Every comment before a student sees it, new rulings and what prompted them, what the rubric missed, what to change next term.
Software
Keep AI-assisted development on one thread
Code projects pile up issues, design decisions, AI sessions, test results, and handoffs. Without a spine, each new session can lose the thread.
A continuity layer around your repo, issue tracker, and code review — not a replacement for them.
See what goes in the spine
In the spine: Project goals, architecture notes, open issues, implementation decisions, session notes, repo constraints, test results, handoff instructions.
The AI helps produce: Implementation plans, bug-investigation steps, issue summaries, test checklists, review notes, release notes.
You review and add back: What changed, what was accepted, what failed tests, what still needs review, what the next session should do.
Restaurants
Change the menu and keep the operation on the same page
Menus change fast, ingredients run out, and kitchen, floor, buying, and service notes drift out of sync.
After you update the spine, an AI session can help draft a revised menu, a kitchen note, and a server briefing — so you can hand the same updated picture to the people who need it.
See what goes in the spine
In the spine: Recipes, menu style, vendor availability, ingredient costs, prep constraints, staffing notes, allergen details, customer feedback, past specials.
The AI helps produce: Printable menus, kitchen prep sheets, buying notes, server briefings, allergen notes, social posts for tonight's specials.
You review and add back: What sold, what ran out, what customers liked, what prep took too long, what should change tomorrow.
Personal
Carry a big personal project across months
A renovation, a long restoration, a big move, or a document-heavy family project piles up quotes, photos, measurements, manuals, and decisions — with long gaps between work sessions.
Pick the project back up after three busy weeks without re-reading everything.
See what goes in the spine
In the spine: Photos, measurements, quotes, contractor and vendor notes, manuals, receipts, timelines, decisions, open questions.
The AI helps produce: Plans, comparison notes, questions to ask before you commit, checklists, summaries of where things stand, next steps.
You review and add back: What was done, what it cost, what changed, what you'd decide differently, what's next.
Writing
Carry a thesis, book, or long report across drafts
A thesis, book, grant application, or long report accumulates sources, notes, outlines, drafts, feedback, and revision decisions over months — often with long gaps between writing sessions.
Come back after two weeks away and the next session can catch up to draft four — because you're carrying the context, not reconstructing it.
See what goes in the spine
In the spine: Sources and references, notes, outlines, draft history, advisor or editor feedback, style decisions, what's settled, what's still open.
The AI helps produce: Outline options, source-note summaries, consistency checks, revision plans, questions your argument still has to answer, notes for the next writing session.
You review and add back: Revised drafts, feedback, changed structure, settled arguments, what to tackle next.
A spine isn't tied to one kind of project. It's a repeatable way to turn scattered project knowledge into useful AI-assisted work.
The more examples you see, the easier it is to imagine your own.
Have a messy project? Build the spine around the problem, not around the tool.
SpineVault is in private alpha, with logins going to a small group now. To ask for one, email testers@spinevault.app.