Start here
Threadbaire is a simple method for keeping your context and decisions in one place when working with AI. Two markdown files. Works with any model. No installation required.
What you get
Four files in the GitHub repository:
README.md
The guide. Explains what this is, why it helps, and how to use it.
Core_Template.md
Holds stable information about your project: what it is, who it's for, voice, constraints, guardrails.
Addendum_Template.md
A running log of decisions and progress. Each entry has a receipt: who, why, source, date, model.
Extensions.md
Optional extras for specific project types: dev logs, content metrics, pipeline tracking.
How it works
Copy the templates
Download Core_Template.md and Addendum_Template.md. Rename them for your project.
Fill in the Core
Add your project's identity: what it is, who it's for, voice, constraints. Keep it short—this travels with every conversation.
Log as you go
When you make a decision or learn something durable, add an entry to the Addendum with a receipt.
Paste into new sessions
When you start a new AI conversation, paste the Core. Add Addendum entries when relevant. Context travels with you.
Receipts
Every Addendum entry includes a receipt—a short note recording where the decision came from:
who: [you or collaborator]
why: [reason for the decision]
source: [link, document, or conversation]
date: [when it happened]
model: [which AI, which version]
Receipts make your work traceable. You can prove where answers came from, replay the same setup on different models, and avoid re-explaining decisions.
Questions
Do I need to install anything?
No. These are markdown files. Copy them, edit them in any text editor, and paste them into your AI conversations.
Does it work with ChatGPT? Claude? Other models?
Yes. The method is model-agnostic. Use it with any AI that accepts text input. The receipts help you track which model produced which output.
Can I modify the format?
Absolutely. Adapt it to what you need. Skip sections that don't apply. Add sections that help. The templates are starting points, not rules.
What's the difference between Core and Addendum?
Core holds stable information (project identity, rules, constraints). Addendum is a running log (decisions, progress, lessons learned). Core changes rarely; Addendum grows over time.
When should I add Extensions?
Only when you need them. Dev projects might add a Technical Core and Dev Log. Content projects might add metrics tracking. Start simple; extend when there's a reason.
Why markdown?
It's portable, readable, and works everywhere. No vendor lock-in. Your context lives in files you control, not in someone else's platform.