Skip to content

v0.16.0 — the hand-over is gated, the mapping is citable

Choose a tag to compare

View all tags
@stranxik stranxik released this 16 Jul 02:02
v0.16.0
634783c

The whitespace phase: the three grounds the audit named as ours to own, shipped as product.

  • Hand-over becomes a gated conformance phase (ADR-0026). "The hand-over is proven by a real task redone without you" was Definition-of-Done prose no gate verified. Now runward/handover.md is a gated deliverable — the kit index, the redone-task proof record, the named succession, the provider-swap drill — verified by four new handover rules (handover-redone-task-proof CRITICAL, handover-runbook-executable, handover-agents-charter-final, handover-succession-named). Rules 60 → 64; a fifth phase skill surfaces the craft at the point of succession. The reference mission ships a filled note and its finalized AGENTS.md (init --example lays down the leave-behind charter, not the scaffold). The repo's own mission records the honest state: no succession has occurred, the redone-task row is a reasoned n/a with the mechanical half (pristine CI reproducing build, tests and the strict gate) pointed at, and the flip condition named.
  • The OSCAL mapping is a published, citable mini-spec (ADR-0025). docs/spec/runward-oscal-mapping.md v1.0, implementation-independent: the decision → ADR → manifest → OSCAL chain, the status-derivation rules (paper coverage never upgrades the status), the deterministic UUID seed grammar, the regime-lens stamp, byte-identity conditions, the evidence-lock v1 format, and conformance criteria for independent implementations. The golden fixture is the normative example; CITATION.cff makes citing mechanical.
  • Kiro joins the adapter family (ADR-0018 amended). --tools kiro mirrors the phase skills as steering files (.kiro/steering/, inclusion: auto — the same relevance semantics as the SKILL.md trigger; AGENTS.md is read natively), and templates/adapters/kiro-hooks.json ships the turn-end gate (Stop trigger, the same inert one line as the Claude Code hook; adapters 5 → 6). Traced decisions inform in-session enforcement in one more harness — a complement riding the harness's own seams, never a runtime of ours.

Full detail: CHANGELOG · ADR-0025/0026 in docs/adr/

Assets 2
Loading