Create an optional hook system for externally-managed verification
This commit is contained in:
parent
bb7422f4c0
commit
51ff9e2572
5 changed files with 99 additions and 9 deletions
|
|
@ -113,7 +113,11 @@ Parse the TLC output to determine:
|
|||
|
||||
### All properties pass
|
||||
|
||||
Update all statuses in `spec/formal/traceability.md` from `formalized` to `checked`. Report success with a summary of what was verified: number of properties checked, state space explored, time taken. Suggest proceeding with `/formspec.plan.4` to create an implementation plan.
|
||||
If `spec/hooks/run-checks` exists and is executable, delegate TLC verification to it instead of running TLC locally (see `/formspec.init` for the hook interface). Present the returned results to the developer, including any dashboard URLs.
|
||||
|
||||
If the hook does not exist or fails, run TLC locally as described in Phase 4.
|
||||
|
||||
In either case, update all statuses in `spec/formal/traceability.md` from `formalized` to `checked`. Report success with a summary of what was verified: number of properties checked, state space explored, time taken. Suggest proceeding with `/formspec.plan.4` to create an implementation plan.
|
||||
|
||||
### Meaning drift detected (Phase 2 issue)
|
||||
|
||||
|
|
@ -133,6 +137,8 @@ If TLC finds a property violation and the TLA+ faithfully represents the design:
|
|||
|
||||
**IMMEDIATELY STOP ALL WORK.**
|
||||
|
||||
Update `spec/formal/traceability.md` to set the violated property's status to `violated`.
|
||||
|
||||
Present to the developer:
|
||||
|
||||
1. **Which property was violated**: Name and human-readable description
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue