Skip to content

architect Phase D: write accepted deviations back into the design before a unit closes #47

Description

@zeitlinb

What happened

An architect run produced a design contract with a Build sequence of five units. The first unit landed with six accepted deviations from the contract (names, placements, and one behaviour change: a throw became a refused outcome). Phase D says to surface deviations, which the lane did in its report, but nothing says to write them back. The design file was untouched, so the second unit opened against a contract the code no longer matched, and the contract's own sentence "a unit deviating from the contract re-opens the design" had no mechanism behind it.

Proposal

Add a step to Phase D: before a unit closes, each accepted deviation is diffed against the sketch (types, signatures, module map) and either patched into the design file or recorded there as "unchanged, deviation is local to the unit". A unit is not done while the design and the code disagree silently.

Why upstream

The write-back belongs to the phase that owns the design file. This project does not fork pstack and keeps its own rules outside the plugin.

Context: open-pstack 1.2.1 on Claude Code, macOS. Happy to send a PR if you prefer.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions