Skip to content

Releases

keel 0.6.0 — the plan contract grows teeth, and the voyage learns to resume

Choose a tag to compare

@policyon policyon released this 07 Sep 16:17

0.6.0 — the plan contract grows teeth, and the voyage learns to resume

The planning layer's enforcement half, the resume command, and the first
exercised relaxation: what 0.5.0 promised as vocabulary, this release makes
mechanism.

  • skills/castoff/: the resume counterpart to /keel:moor — a read-only
    session boot from the newest mooring record plus a survey, reporting the
    open threads, what is actionable in this session's state, and one
    recommended track. Writes nothing; the plan still goes through the gate.
  • hooks/keel_gate.py: the plan contract is now asserted at write time —
    a session-ledger write missing a task identifier, a Route:, an
    Accept:, or carrying placeholder vocabulary is refused with the
    findings named, on every instrument: the write tools, edits checked from
    their payload, and mutating shell commands (which cannot be
    contract-checked and are therefore denied toward the checkable path).
    Refit drafts and other non-ledger files keep the plain carve-out.
  • scripts/keel_attest.py: attest reads contract-shaped ledgers (task ids
    and Route: sub-bullets), and the fix-round ladder lands as R44 —
    resume ceiling, fresh-context floor, and a hard cap of five rounds as
    constants the check reads; a task past the cap, or an id-shaped token
    that will not parse, is a discrepancy that turns the report non-clean.
  • agents/: every agent definition pins its model class per the routing
    table (researcher fast, executors standard/deep, reviewers standard),
    and keel_checks --agents fails on drift between the pins and the map.
  • .keel/keel-policy.md (this repository's own arming file, by ratified
    refit): relax: release-version-bump — the version bump that produced
    this very release demotes from deny to a question. Survey wording and
    the template's kill-switch row now state the accepted override values.
  • skills/moor/: a second same-day mooring takes a numbered suffix
    instead of overwriting another session's record; and the closure check
    reads every skill's references pages, not just its SKILL.md.