Shipped and released
Now
Page 12 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 12
- Work-loop now supplies reusable lessons through project-knowledge without having to assemble its storage and safety details.
- Reviewers now test the evidence behind a finding before they emit it. They retain uncertain concerns, clearly marking an untraced consequence instead of silently dropping it.
- Architecture work reuses before it creates.
architect-designlooks for an adequate prior design or existing capability first and creates no new artifact when no real choice remains. A Stage-0 concept is a valid final answer, not a waypoint to a full design. - Architecture reviews challenge unnecessary surface.
architect-reviewgained a design-doc reduction pass covering unnecessary components, services, dependencies, boundaries and custom mechanisms; ignored standard, native or provider capabilities; speculative scale and configurability; and complexity no named quality attribute supports.
- Architecture work reuses before it creates.
- An RFC that should not exist no longer costs you an identifier and a file.
new-rfcnow decides what artifact the work actually needs before it resolves an ordinal or writes anything. When the answer is "skip", "an existing decision already covers this", or "an ADR, a spec, a PR, an issue, an architecture design, or a reversible trial fits better", it names the route and stops, leaving nothing behind. - RFCs get a review mode built for prose. The adversarial reviewer now has an RFC mode that needs no code diff, and treats the draft under review as untrusted data that cannot change its scope, severity, verdict, or routing.
- An RFC that should not exist no longer costs you an identifier and a file.
- Planning-only sessions can now prove TDD acceptance criteria without leaving failing tests in the repository. The approved plan carries the executable stub, and implementation sessions materialize it only when code work begins.
- Spec review now separates original defects from faults introduced by a prior repair before another edit begins. Every completed report is independently adjudicated, and a green gate is used only for the behavior it actually proves.
- The authoring workflow now offers a `knowledge-provider` mode, and the corpus behind it will not answer a question it has no evidence for. Four topics were admitted out of seventeen candidates, because admission requires two observations at distinct skill paths in distinct packs and measured retrieval that selects the topic alone. The other thirteen are recorded as absent with the reason and what would admit them, so a reader can tell an unevidenced subject from an overlooked one.
- You can install a skill straight from a repository, without a catalogue. Point
agentbundle installat a skill folder, askills/collection, or a single pack — locally or on GitHub — and it admits the source against explicit size and shape limits, pins it to the commit its bytes came from, and shows you exactly what the publisher declared before anything is written. A collection never installs everything by default: name the skills you want, or ask for all of them. - An upgrade that widens what a skill can do now stops and tells you what changed. Added tools, changed boundaries, new payload files, or a different credentialed status each need explicit acceptance, tied to the exact list you were shown.
- You can install a skill straight from a repository, without a catalogue. Point
- Authors can independently check an intent, delivery brief, or draft spec before construction starts. Core's shaping reviewer tests whether the contract is bounded and observable without replacing later adversarial, security, or quality code review.
- A read-only agent's declared boundaries are now checked where they are written, and never shipped into a projection that cannot use them. Adopters get the least-privilege posture their source declares on every supported adapter.
- `work-loop` can now correct a sealed spec or plan before the first wave runs. Review that finds a defect in the window between sealing the baseline and executing wave 1 previously had no legal move:
contract-amendmentrefused until at least one task had completed, so the only way out was resetting the run and losing its identity and amendment history.
- `work-loop` can now correct a sealed spec or plan before the first wave runs. Review that finds a defect in the window between sealing the baseline and executing wave 1 previously had no legal move:
- An acceptance criterion that hides two contracts is now caught while it is being written, not three review rounds later.
new-specnames the test — parts with separate failure modes and separate remedies are separate criteria — and fixes its boundary with five worked examples rather than an adjective an author can self-certify past.
- An acceptance criterion that hides two contracts is now caught while it is being written, not three review rounds later.
- Spec authors can keep the contract and the plan independently sharp. An acceptance criterion now states one checkable obligation, and a plan's tests name the verification mechanism an implementer cannot infer instead of repeating the criterion.
- A plan now tests its riskiest assumption before anyone reviews it. One cheap throwaway check can reshape the approach before reviewers spend rounds arguing about work nobody has started.
- Catalogue checks now admit the portable rule lookups shipped by the core pack while rejecting undeclared seed paths. Adopters can receive the new bounded rule router and scoped docs guidance through the normal seed flow.
- Agents now make chat, documentation, and skill-led work easier to scan without dropping checks, warnings, evidence, or depth. Repository rules, generated artifacts, and independent skills share the same outcome-first behavior without requiring a new host primitive.
- Compiled OKF skills now carry the same outcome-first output contract as hand-authored ones. A generated router or procedure skill reads the same way as the rest of the catalogue without a separate rule file.
- Architecture, design, and product artifacts now lead with the decision and keep long work easy to resume. The output stays plain and scan-friendly while preserving requested depth, evidence, constraints, and exact terms.
- Engineering artifacts and handoffs now stay quiet during routine tool work while keeping exact code, errors, and verification. Results lead with the current outcome and name a next action only when one remains.
- Connected-service and research workflows now ask for less at once and return the current result without routine tool narration. Safety issues, blockers, needed choices, and host requirements still interrupt silence.
- Work-loop tools now reject execution state outside the current repository and finish safely when local Git stops responding.