Skip to content

Strengthen unit shaping and repeated-review escape hatch - #14

Merged
bermudi merged 18 commits into
v2from
litespec/strengthen-unit-review-loop
Aug 31, 2026
Merged

bermudi merged 18 commits into
v2from
litespec/strengthen-unit-review-loop

Conversation

@bermudi

@bermudi bermudi commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Summary

  • Units now shape around one external boundary or one failure policy, with identified outcome clauses mapped to named test scenarios
  • Filesystem/process/network units declare a closed Boundary: vocabulary and account for five standard risks
  • After two completed review-requested rebuild cycles against one digest, the next finding records a digest-bound re-plan marker instead of a third rebuild; only a plan-authored amendment resolves it
  • Cumulative review coverage is append-only, HEAD-keyed, and advisory-only; reviewers must draft an independent risk inventory before consulting prior coverage
  • validate success output now states structural-only scope and unverified implementation semantics across text, minimal, and JSON modes

Closes #13.

Test plan

  • go test ./...
  • go vet ./...
  • go build ./...
  • litespec validate --issue 13 --minimal -> structure-ok semantics-unverified 7 units
  • Fresh review returned PASS with HEAD-keyed coverage record appended

@bermudi
bermudi merged commit 563c542 into v2 Aug 31, 2026
1 check failed
@bermudi
bermudi deleted the litespec/strengthen-unit-review-loop branch August 31, 2026 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant