Repository navigation
Description
Decision (owner, 2026-11-12)
Slice 3 of 3 of the formal-verification plugin. The whole design, the directory layout, the decided names and the design rules are on slice 1: Add the formal-verification plugin's chart skill, setup and consumer contract, proven on the loop-lane claim protocol.
Source: her maintain-formal-verification-skill (cursor/plugins pstack/skills/, MIT), text kept as far as possible. The dangerous case she names is a pass on a stale description, "because it looks like a proof".
Depends on
- Add the formal-verification plugin's chart skill, setup and consumer contract, proven on the loop-lane claim protocol #15648: the consumer contract and the first
formal-<area>skill this slice's dogfood changes. - Add the formal-verification specify skill's propose, create and check forms #15773:
specifyand thecheckscript this slice extends.
This item
/formal-verification:specify refresh: bring a project's formal verification back in line with the code after the code changes, and say whether each failure is drift in the verification or a bug in the code.
Every step of hers is kept:
- Find the checks by what they do, not by name. Collect the property, covered code, bounds, command and sync commit; with no sync commit recorded, use the last commit that changed the verification files and say so.
- Run each check unchanged first.
- Read every change to covered code since the sync commit, including moved or renamed code and new code touching guarded state. Classify each: no effect; the verification no longer describes the code; the promise changed on purpose (with cited evidence); the promise may be broken.
- "Update from the code, not from the result." Change a property only for an intended promise change, recording the old wording, the new wording and the evidence; report any reduced bound. A property change needs a person's yes even with cited evidence. Attended: propose old wording, new wording and evidence, change on yes. Unattended: report the proposal and leave the check
blocked, sync commit not moved. - Rerun and judge. On a pass, break the new code and confirm the check catches it. On a failure, replay the counterexample against the real code step by step: an impossible step means the verification is wrong; otherwise it is a bug, with the introducing commit named.
- Update the consumer's
formal-<area>skill and move the sync commit forward, never for a blocked check. "Then follow the verify skill once as the next agent would, so that you know its steps still run."
Each check ends in sync, updated, bug or blocked; a check can be both updated and a bug. Edits stay inside the consumer's formal-<area> folder; verification updates go in their own change, separate from any product fix.
- Report: her five per-check bullets as prose, each check opening with a fixed outcome line (a check can be both
updatedandbug). No machine-readable summary until a routine exists to read one. - Bugs: a
bugis filed, through/bugs:writethen/work-items:track addwith noneeds-humanlabel, only when its counterexample was replayed step by step against the real code: attended on the person's yes, unattended automatically. An unreplayed counterexample stays in the report. - Unattended: refresh runs every step but writes only for checks that end
in syncorupdatedwith a seeded break caught, and reruns checks only when the toolchain is already installed. It makes no verification edit for a property change, abugor ablockedoutcome; those go in the report. - Branch rule, as
/app-control:map refresh: on a ticket branch, a commit there; otherwise its own upkeep branch and one pull request; never in the same commit as a product fix. Only theformal-<area>folder, the paths listed insync.yamland a named conversion path are staged. A pass on a detached HEAD that is not the default branch's tip commits nothing. - A verification skill outside the contract: attended refresh lists it and converts it only when the person names it; unattended refresh runs her pass on it report-only, files nothing and converts nothing.
- CI: a pull request that touches a path listed in any
sync.yamlgets an advisory line from thecheckscript in CI, naming the stale check andrefresh; advisory by default, following the per-checkon_stalesetting. - Scheduling: the
autonomyplugin's routines catalog gains aformal-verification-upkeeprow: output a report, a work item and one pull request confined to theformal-<area>folder and listed paths; join: proven recurring manual pattern; stated as distinct fromformal-logic-modeling. No routine file in this slice.
Before build
The interview ran and the owner confirmed it on 2026-11-14 ("Go with recommendations, whatever the research says, and whatever is the best fit in our repo", "Go with recommendations.", then "Confirmed."). The unattended behavior, the routine and the report's shape are stated above.
Left to planning: the exact form of the outcome line and what the refresh pull request body is built from; the argument that names a conversion path.
Dogfood
A deliberate change to code covered by this repository's first formal-<area> skill, classified and refreshed by the skill. It counts as one manual run and schedules nothing.
Owner step
If the dogfood's classification proposes a property change, it waits for a person's yes before the property is changed.
Done when
-
/formal-verification:specify refreshfinds checks by what they do, not by name, and collects each one's property, covered code, bounds, command and sync commit. - With no sync commit recorded,
/formal-verification:specify refreshuses the last commit that changed the verification files and says so in its report. -
/formal-verification:specify refreshruns each check unchanged before any edit. -
/formal-verification:specify refreshclassifies each change to covered code since the sync commit, moved, renamed and new code touching guarded state included, into her four classes. -
/formal-verification:specify refreshchanges a property only for an intended promise change and records the old wording, the new wording and the evidence. -
/formal-verification:specify refreshreports any reduced bound. - Attended,
/formal-verification:specify refreshproposes a property change with old wording, new wording and evidence, and changes it only on a person's yes. - Unattended,
/formal-verification:specify refreshreports a proposed property change, leaves that checkblocked, and does not move its sync commit. - On a pass,
/formal-verification:specify refreshbreaks the new code and confirms the check catches it. - On a failure,
/formal-verification:specify refreshreplays the counterexample step by step against the real code, calls an impossible step a verification error, and otherwise reports abugnaming the introducing commit. -
/formal-verification:specify refreshupdates the consumer'sformal-<area>skill and moves its sync commit forward, never for ablockedcheck. - After updating,
/formal-verification:specify refreshfollows theformal-<area>skill once as the next agent would. - Each check
/formal-verification:specify refreshhandles endsin sync,updated,bugorblocked, and one check can be bothupdatedandbug. - The
/formal-verification:specify refreshreport gives her five per-check bullets as prose, each check opening with a fixed outcome line, with no machine-readable summary. - Unattended,
/formal-verification:specify refreshwrites only for checks that endin syncorupdatedwith a seeded break caught. - Unattended,
/formal-verification:specify refreshreruns checks only when the toolchain is already installed. - Unattended,
/formal-verification:specify refreshmakes no verification edit for a property change, abugor ablockedoutcome, and reports each one. - Started on a ticket branch,
/formal-verification:specify refreshcommits there; otherwise it commits on its own upkeep branch and opens one pull request. -
/formal-verification:specify refreshnever puts a verification update in the same commit as a product fix. -
/formal-verification:specify refreshstages only theformal-<area>folder, the paths listed insync.yamland a named conversion path. - A
/formal-verification:specify refreshpass on a detached HEAD that is not the default branch's tip commits nothing. -
/formal-verification:specify refreshhands abugto/bugs:writethen/work-items:track add, with noneeds-humanlabel, only when its counterexample was replayed step by step. - Attended,
/formal-verification:specify refreshhands a replayedbugon only after the person's yes; unattended, it does so without asking. -
/formal-verification:specify refreshkeeps an unreplayed counterexample in the report and hands it to no tracker. - Attended,
/formal-verification:specify refreshlists a verification skill outside the contract and converts it only when the person names it. - Unattended,
/formal-verification:specify refreshruns her pass on a verification skill outside the contract report-only, and hands nothing to a tracker and converts nothing. - The formal-verification
checkscript prints an advisory line in CI for a pull request touching a path listed in anysync.yaml, naming the stale check andrefresh, following the per-checkon_stalesetting. - The
autonomyplugin's routines catalog has aformal-verification-upkeeprow: output a report, a work item and one confined pull request; join: proven recurring manual pattern; distinct fromformal-logic-modeling. - No routine file schedules
/formal-verification:specify refresh. - The formal-verification dogfood makes a deliberate change to code the first
formal-<area>skill covers, and/formal-verification:specify refreshclassifies and refreshes it.
Out of scope
- A scheduled refresh routine: none until refresh has been run by hand repeatedly.
- A machine-readable refresh summary: added when a routine exists to read it.
- A spec-side mutation check.
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Priority
Activity
github-actions commentedon Nov 13, 2026
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: intent
Blocked by: #15648
I understood this as slice 3 of the formal-verification plugin: a
/formal-verification:specify refreshaction that re-syncs a project's verification with changed code and ends each check as in sync, updated, bug or blocked. It depends on the design and consumer contract in #15648. #15648 is still open. Related sibling: the propose/create/check slice (not a duplicate).The issue says three things must be locked before build: the unattended behavior, whether an
autonomyroutine schedules it, and the report's shape. They are open.autonomyroutine schedule refresh? RECOMMENDED: no routine in this slice; run it on demand and mirror/app-control:map refreshfor unattended runs. That keeps the slice to the action itself.To answer, post a comment that starts with this line:
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 13, 2026
The triage verdict left this issue at
needs-owner-decision:Reason:
intentkyle-sexton commentedon Nov 14, 2026
Decision recorded. Interview complete, owner-confirmed 2026-11-14 ("Go with recommendations, whatever the research says, and whatever is the best fit in our repo", "Go with recommendations.", then "Confirmed."). The shared decisions are on issue #15648 and the
checkscript's are on #15773. Decisions for this slice:in syncorupdatedwith a seeded break caught, and reruns checks only when the toolchain is already installed. It makes no verification edit for a property change, abugor ablockedoutcome; those go in the report.blocked, sync commit not moved./app-control:map refresh: on a ticket branch, a commit there; otherwise its own upkeep branch and one pull request; never in the same commit as a product fix. Only theformal-<area>folder, the paths listed insync.yamland a named conversion path are staged. A pass on a detached HEAD that is not the default branch's tip commits nothing.updatedandbug). No machine-readable summary until a routine exists to read one.bugis filed, through/bugs:writethen/work-items:track addwith noneeds-humanlabel, only when its counterexample was replayed step by step against the real code: attended on the person's yes, unattended automatically. An unreplayed counterexample stays in the report.plugins/autonomy/reference/routines.mdgains aformal-verification-upkeeprow: output a report, a work item and one pull request confined to theformal-<area>folder and listed paths; join: proven recurring manual pattern; stated as distinct fromformal-logic-modeling. No routine file in this slice; the dogfood counts as one manual run and schedules nothing.sync.yamlgets an advisory line from thecheckscript in CI, naming the stale check andrefresh; advisory by default, following the per-checkon_stalesetting.Left to planning: the exact form of the outcome line and what the refresh pull request body is built from; the argument that names a conversion path.