Skip to content

deliberate skill: amendments are first-class specs (same review budget as originals) #510

Description

@aarontrowbridge

Problem — Two same-day incidents (2026-08-22): amendments to approved specs drafted as post-conversation summaries contradicted the frozen contracts they amended (6 and 9 blockings respectively, caught only by post-hoc review). The skill's review loop covers original specs but says nothing about amendments — the cheap-talk draft is the documented gap.

Fix — Add a subsection to the deliberate skill: amendments to approved specs are first-class specs — same three-lens adversarial review, same round budget, before landing. Drafting discipline: re-read the parent spec's invariants, D-decisions, Measurement Protocol, and all prior amendments line-by-line before writing; edits to enumerated lists, tier memberships, invariants, criterion preconditions, or cross-spec pointers are checked against the exact text they edit and every sibling amendment.

Evidence: the vault distillation spec's same-day review notes (Amendments 2 and 3, spec-20260821-090401); the memory card feedback_amendment_review_budget in the personal vault.

Metadata

Metadata

Assignees

No one assigned

    Labels

    hitlHuman-in-the-loop — needs human review/decision

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions