-
v0.198.02026-08-21
The Humane Product Canvas is now a free thing you can just take — a page and a Markdown template, CC BY-SA 4.0, no install, no signup, no email. It's the one-page canvas BOSS's
/canvasskill is built on: everything Lean and the Business Model Canvas cover, plus two questions neither of them asks — who this could harm or exclude, and the principles you'll hold when holding them costs you something. Print it, fork it, teach from it. The tool is for when you want something to keep asking; the framework is yours either way. -
v0.197.02026-08-21
If you have ever edited a skill or agent BOSS installed,
boss sync --applyused to overwrite it without asking. It no longer does — a managed file you changed is left alone and reported by name, and/boss-sync(or--force) decides what to do with it. Files that predate this release get copied to.boss/backups/before being written, because BOSS genuinely cannot tell whether you touched them. -
v0.196.02026-08-21
BOSS now notices when your canvas has fallen behind your own product. If three or more features you marked
shippedare newer than the canvas, it says so once — because a canvas describes a product, and when things have shipped and it hasn't moved since, it describes a product that no longer exists. It fires on shipped, not on drafting: writing three specs is building, and building is not drift. Touching the canvas silences it. It never rewrites the canvas for you. -
v0.195.02026-08-21
If your project isn't trying to make money — open source, Creative Commons, a research tool, something you're building for friends or for fun — BOSS was quietly making you lie. The canvas's Business Model cell was the only one in its group with no condition on it, so it counted toward leaving Quickstart for every project, and its follow-up questions were "who pays, how much." You had two bad options: invent a revenue line, or leave it blank and read as permanently unfinished. Now the cell asks the question it always meant to ask. Its actual prompt — "how will you sustain this without compromising your promise?" — was already right for a maintainer; only the follow-ups assumed money. There's a second set now: what keeps this alive, who else could carry it, what happens when you get bored or busy or hit by a bus, and what would make you stop.
/moneyalso stops routing you. It used to read where you are in the money arc with no branch for not being in it, so it would point you at/interviewto go get a yes you never wanted. It now says the verb doesn't apply, and stops. None of this makes the question softer — most open-source projects die of maintainer exhaustion, not of a missing business model. -
v0.192.02026-08-20
Your board was probably lying to you. A status like
shipped (v0.3.0 — the pull half)is well-formed BOSS — the vocabulary doc encourages the detail — but the board compared the whole string, so any status with a parenthetical fell through into Captured. On BOSS's own board that was 12 of 31 cards: eight shipped and four in build, all filed as raw ideas nobody had touched. Fixed. Two more things came with it: every card now carries a one-line gist (boss board --detail, hover on--html, orboss board <ID>for one card in full), anddeferred/droppedwork folds into Parked instead of sitting in Captured looking like a decision you still owe. On BOSS's own backlog that second change took Captured from 31 cards to 1. -
v0.190.02026-08-20
The deceptive-pattern catalog is now filtered by what you're building.
boss craft deceptive-patterns --shape mobile-app(orcli,edtech,chatbot,marketplace… 14 shapes) shows only the surfaces you actually have;--surface checkout-and-pricinggives you the rows for the thing you're on right now, each with the honest version. Four surfaces are new — consent banners, tracking & telemetry, device permissions, and install/update — and/red-team --humanenow tests all of them instead of five chatbot probes. -
v0.189.02026-08-20
if you're at MVP, you now have a
designer— one agent for how it looks, how it behaves, and how it reads — plus/design-reviewbefore code and/ux-checkafter. If you're already at V1,ui-designerandux-designerare superseded by it;boss syncwill say so, and anything you edited stays yours.db-architectis gone and you don't need to remember to open anything in its place./specnow asks the data questions while your feature is still a paragraph, andschema-guard(turn it on in.claude/settings.json) tells you when a migration creates a table without the rule that decides who can read its rows. Askmentor-architectthe judgment calls. Yourdocs/architecture/files stay where they are.every agent now says what it does in words you already know.
boss syncwill walk the renames; your own edits are flagged by name first, and removal is never automatic.the business-model mentor now arrives at MVP instead of V1, so
/money's first-price step finally has the mentor it already named as its owner — if you took a first dollar at MVP before this, the handoff it offered you pointed at an agent your project didn't have. The talent mentor now arrives at Scale instead of V1. Run/boss-syncto pick both up. Nothing you already have is removed, and no command changes. -
v0.188.02026-08-20
if you skip
/close, the conscience is no longer blind. It now reads the facts your repo already carries — what's in flight, what shipped, and what it has already said to you recently — so it can stop repeating a nudge that didn't land./closestill writes the part that matters most: what those facts mean. Nothing about running it changes. -
v0.187.02026-08-20
if you keep a single venture canvas at
docs/ideas/CANVAS.md— which/canvastells you to — the conscience has been telling you your canvas loop is stalled when it isn't. Fixed. And if you already test under another name (npm test, CI), record it with/smokeso the verification nudge stops; it was never meant to fire at someone who is already verified. -
v0.186.02026-08-20
boss records --programsgroups records that belong together (program: <slug>— one line, nothing to create first) and shows which umbrella is moving and which is stuck. It's onboss board --htmltoo. Promote a program to its own record only when it has something to say that belongs to no single member — not when it hits some number of items. -
v0.185.02026-08-20
boss idgives you the next free record number, computed rather than counted — use it before creating an IDEA or FEAT.boss records --timelineshows when each idea was captured and when it actually got built, derived from your own git history, with a median. Andboss board --htmlnow has a Shipped over time strip so there is something to look at that is behind you. Promote an idea to a FEAT when it has named slices or spans more than one release — not before. -
v0.184.02026-08-20
boss records— new. Your docs make claims about your code (shippedmeans the thing exists), and nothing ever checked them. Addproof: <path>to a record and BOSS will tell you when the two stop agreeing — in both directions. The one that costs you is a finished feature whose record still says "exploring": that is a thing you might build twice, or hand to an agent that rebuilds it, because the agent believes your docs.boss statusnow says so in one line.