Frameworks become maintenance debt the moment they stop updating. CRAFT keeps the framework and your work in separate folders and ships signed, versioned releases — so staying current is a deliberate folder swap you make, confirmed by a built-in check, that never touches your work. You update by choice; nothing is pushed to you.
This page has been rewritten for accuracy. An earlier version said the framework “keeps itself current” and “pulls updates to you,” and explained the process using an older, internal update mechanism. That wasn’t correct: CRAFT does not update itself, and nothing is pushed to your machine. Updating is a deliberate step you take — you download a new release and replace the framework folder, and your own work is never touched. We’d rather correct the record than leave a claim standing that the product doesn’t actually do. The accurate explanation follows.
Last week we covered CRAFT’s branding framework — how brand identity becomes something the AI checks against rather than something it tries to remember. This week, the closer: how CRAFT stays current, and how you bring those updates into your projects.
The Stale Framework Problem
Every framework you adopt has the same lifecycle. You install a version. You learn it. You build on it. Months later, a newer version exists with patterns that have settled — different folder names, new recipes, deprecated approaches. Your project is on the old one.
You have three options. Freeze on what you started with and accumulate a gap between your project and the world. Do a manual sync that risks breaking what works. Or skip the update and revisit “next quarter.”
None of these scale. The “next quarter” version of you is busy. Manual merges are where projects go to stall. And freezing means you’ve turned the framework into a fixed artifact instead of living infrastructure.
CRAFT’s answer is to make updating cheap and safe enough that you actually do it — by keeping the framework and your work in two separate folders, so an update can replace one without ever touching the other.
Two Folders: the Framework and Your Work
A CRAFT project is laid out in two top-level folders:
That separation is the whole trick. Because the framework lives in its own folder and your work lives in another, a new version can drop in by replacing one folder — with zero risk to anything you’ve made.
How Versions Are Named
Each release carries a version string in a consistent shape — for example, the current user release:
v.b0001.p202606.01c
Build · Channel + date (p = public, June 2026) · Increment
The version is recorded honestly inside the release (in VERSION.txt), so there’s never a question of which version you’re running — you read it, you don’t guess. The website always names the current version on the What’s New and Changelog pages, and the newest release is always at the top of the releases page.
How a Release Is Made and Shipped
A new version is built deterministically — the same source produces the same package, byte for byte — and then published as a GitHub Release. Each release carries three things: the framework .zip, a SHA256SUMS checksum file, and a detached GPG signature (SHA256SUMS.asc) so you can confirm the download is intact and untampered before you trust it.
Publishing a public release is a deliberate, signed, human step — not something that happens automatically — and every release is immutable once posted. That’s what lets the releases page act as a single, trustworthy source of truth.
How Updates Reach Your Project
CRAFT does not silently update itself, and nothing is pushed to your machine — you decide when to upgrade, and you do it. The good news is that, thanks to the two-folder layout, it’s a single, safe step:
CRAFT Core Files/ folder with the new one — your operating system does the swap. Your CRAFT Project Files/ folder is left exactly as it was.Keep the old CRAFT Core Files/ folder and you can roll back at any time by restoring it. After upgrading, start a fresh session so Claude loads the new version. No rebuilding your project, no hand-merging files.
You don’t merge the framework into your project. You replace one folder and leave the other alone. The cost of staying current drops from a risky weekend to a quick, verifiable swap.
8 Weeks in 8 Sentences
The capability spotlight at a glance:
Each one builds on the previous. Memory needs files; files need a layout; the layout needs a brand layer; the brand layer needs to stay current as new CRAFT versions ship. The whole stack is a stack because each piece holds up the next.
Why This Matters
Frameworks are infrastructure. Like all infrastructure, they either stay maintainable or they become maintenance debt. The frameworks that survive are the ones where staying current costs less than diverging.
CRAFT keeps that cost low by design: the framework and your work live in separate folders, upgrades are a verifiable folder swap, and every release is signed and immutable. Staying current isn’t a side project — it’s built into how CRAFT is laid out.
