Shipped and released
Now
Page 10 of 14. Every release ever published is still here — across these pages, in theAtom feed, and at its own permanent link. Nothing is dropped as it ages.
Released highlights, page 10
- Checking where the work stands costs a fraction of what it did. The orientation payload now carries the decisions you act on rather than the full working set behind them, and the saving grows with the size of your workspace. Ask for the long form when you want it.
- The spec and traceability checks report what they found instead of listing it. A passing run prints its summary lines and says how many items it withheld, so nothing goes quietly missing. Anything that fails still prints in full.
- The directory your intents land in is now described in the conventions you install with them.
CONVENTIONS.mdreads an intent on two axes: the altitude it sits at, and how far it has travelled from a framed bet to a ratified outcome. Only a feature-level intent becomes a spec directly. - Admitting an intent that was already shaped upstream adds to it instead of overwriting it. The outcome, altitude and assumptions you framed survive the handoff into repository work.
- The directory your intents land in is now described in the conventions you install with them.
- The defects a spec review keeps finding are now named where the spec is written, not only where it is reviewed.
new-specships a spec-authoring rubric: six failure classes worked in order before criterion shape, starting with the one no criterion craft repairs — an obligation authored where an owner already exists.
- The defects a spec review keeps finding are now named where the spec is written, not only where it is reviewed.
- A new catalogue now gives Claude Code the same pack and profile guidance every other agent already got.
agentbundle catalogue initwrites aCLAUDE.mdbeside eachAGENTS.mdit scaffolds, so a Claude session picks up your scoped instructions instead of missing them.
- A new catalogue now gives Claude Code the same pack and profile guidance every other agent already got.
- A skill author deciding whether to hand work to an isolated worker, or whether to ship a set of components as one package, now gets those concepts from the corpus instead of being routed to a runtime profile that does not exist.
- A cooled delivery's parent link is now declared on its workspace entry, so reconciliation stops guessing. When a cooled spec's
source.parentis missing or names no registered brief,workspace-statusreportscooled_child_scope_unknownagainst that entry and holds every dependency on a brief until someone answers — instead of silently reading the missing value as "this delivery has no parent" and releasing the work. - Declaring `none` is a real answer. A delivery with no parent brief is declared as such once and dispatches normally, so the new refusal is something a maintainer clears rather than waits out.
- A cooled delivery's parent link is now declared on its workspace entry, so reconciliation stops guessing. When a cooled spec's
- `workspace-status` now distinguishes unavailable cooling support from a malformed lifecycle record. It directs maintainers to install or repair the cooling capability instead of repairing a valid record.
- Installed direct skills can now move to later repository revisions.
agentbundle upgrade --skill <name>re-runs admission, shows the capability consent surface, previews changes, and removes files dropped upstream before it records the new revision.
- Installed direct skills can now move to later repository revisions.
- `work-loop` now rejects unsafe or ambiguous reference providers before it calls them. Provider guidance is visibly enclosed as untrusted evidence, so it cannot quietly expand the planning workflow's authority.
- `architect-design` now rejects unsafe or ambiguous reference providers before it calls them. Provider guidance is visibly enclosed as untrusted evidence, so it cannot quietly expand the design workflow's authority.
- Closeout now keeps unrelated work visible when it shares a path with a cooled legacy entry. A second entry at the same path still blocks closeout, so maintainers are not told to invoke
close-workwhile that work remains unresolved.
- Closeout now keeps unrelated work visible when it shares a path with a cooled legacy entry. A second entry at the same path still blocks closeout, so maintainers are not told to invoke
- A durable owner accepting an artifact now survives the session that recorded it. The lifecycle record carries
Reclassified, so "this left delivery and someone else owns it now" persists as readable state instead of being lost at closeout. A reclassified artifact keeps its file where its record says it is, drops out of ordinary orientation, is never due for a retention review, and is not counted among the obligations someone still owes delivery work against. - It is reached deliberately and only once. Reclassification is available only from a record already retained under an exception, only when the durable owner's acceptance is supplied and validated at the transition, and never again afterwards — nothing transitions out of it, and no deletion route admits a lifecycle record. It is not gated on a date, because a durable owner accepting an artifact is not a day-30 event.
- A durable owner accepting an artifact now survives the session that recorded it. The lifecycle record carries
- Light-mode review now runs until it is clean instead of stopping after a fixed number of rounds. A loop that is converging finishes. At the third round and every second round after, the loop asks whether findings are getting fewer and smaller, and keeps going while they are. A loop that is no longer converging asks whether the reviewed construct should exist at all and puts that choice to the person who asked for the work, rather than sending a small change through the heavier mode.
- When a
work-looptask is about a skill, a skill script or evaluation, an agent loop, a hook, or a plugin, planning now reaches the installed agent-skill-engineering reference for compiled guidance and cites the topics and provenance it used, instead of answering from model memory. - Without that pack installed,
work-looprecordsknowledge provider unavailableand completes the same planning work it did before.
- When a
- When an
architect-designtask turns on how to package agent behaviour — a subagent, a hook, a skill, or a plugin — the design procedure now reaches the installed agent-skill-engineering reference for compiled guidance and cites what it used. - Without that pack installed, the procedure records
knowledge provider unavailableand produces the same design work it did before.
- When an
- The shipped knowledge provider contract now states every diagnostic the seam can return, so a consuming pack can quote a receipt an adopter actually receives rather than one that existed only in a test fixture.
- A work-loop phase now decides which behavioural rules an authoring agent is taught. A registry inside the
work-loopskill declares the policy families each phase carries, and a selector turns one phase into the ordered families it selects, each with its enforcement tier and a fingerprint of the file that teaches it.
- A work-loop phase now decides which behavioural rules an authoring agent is taught. A registry inside the
- A lesson that a rule or a control has since absorbed can be retired where it lives. Distillation now carries the lifecycle and the retirement record, so a topic settles as
canonicalized,enforced,obsolete,merged, orinvalidated, naming the successor that took the lesson over. A retired topic stays in place for history and stops being offered as current guidance. - A topic keeps every occurrence that produced it. Reconciling a second observation into an existing topic appends to its provenance instead of replacing it, so the record of what was seen, and when, survives revision.
- A lesson that a rule or a control has since absorbed can be retired where it lives. Distillation now carries the lifecycle and the retirement record, so a topic settles as
- Shaping skills now suggest a workspace entry that can actually be picked up.
frame-situationanddiverge-solutionsprinted a short legacy form that is never dispatchable, so an entry added exactly as instructed never surfaced as ready work. Both now print the canonical five-field entry and route registration throughwork-intake. - A reference to a command that no longer exists is gone. The skills pointed at a retired skill name, so following the instruction did nothing.
- Shaping skills now suggest a workspace entry that can actually be picked up.
- The OKR cascade now writes a workspace entry that can be picked up.
run-okr-cascaderecords each gap it finds, and it was writing a legacy form that is never dispatchable — so every gap it recorded was invisible to the shaping room it was recording into. It now writes the canonical five-field entry.
- The OKR cascade now writes a workspace entry that can be picked up.