spec: source-blind Quint model of the instance lifecycle - #3
Open
closer-claudio wants to merge 2 commits into
Open
spec: source-blind Quint model of the instance lifecycle#3closer-claudio wants to merge 2 commits into
closer-claudio wants to merge 2 commits into
Conversation
First artifact of the spec-driven testing experiment (farcloser-level SPEC-DRIVEN-TESTING.md): a state-machine model of what ossein is meant to do with backgrounded buildkit instances, cache volumes and the image cache, written from the public surface only (--help output, README, the acceptance criteria in docs/TODO.md) and without reading any source. The model takes the strict reading of every documented sentence and encodes it as invariants: one writer per cache volume, gc leaves no orphans, one-shot commands leave no state, project-local caches are never deleted by ossein, a failed command changes nothing observable, and a fail-fast refusal is only ever caused by a live lock holder. Where the docs are silent the model does not guess: nine numbered questions in spec/README.md, the first of which (no way to list instances) blocks replay of every instance invariant until answered. Typechecks and simulates clean at 300 runs of 12 steps with quint run --backend=typescript; the flag matters because the default backend downloads an evaluator at run time. Signed-off-by: closer-claudio <claudio@farcloser.world>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First artifact of the spec-driven testing experiment (farcloser-level
SPEC-DRIVEN-TESTING.md): a Quint state-machine model of what ossein is meant to do with backgrounded buildkit instances, cache volumes and the image cache, written from the public surface only (--helpoutput, README, the acceptance criteria indocs/TODO.md) and without reading any source.The model takes the strict reading of every documented sentence and encodes it as invariants: one writer per cache volume, gc leaves no orphans, one-shot commands leave no state, project-local caches are never deleted by ossein, a failed command changes nothing observable, and a fail-fast refusal is only ever caused by a live lock holder. Where the docs are silent the model does not guess: nine numbered questions in
spec/README.md. The first (there is no way to list instances) blocks replay of every instance invariant until answered; the second (does a dead lock holder still block a newbuildkit?) is the most likely real bug the driver will find.Verified:
quint typecheckclean;quint run --backend=typescript --invariant=all_invariantsfinds no violation over 300 runs of 12 steps. Quint itself arrives through the limen baseline (farcloser/limen#58); until that release is pinned here the commands inspec/README.mdneed a quint on PATH. Fulljust lintandjust testgreen on this branch after rebasing onto #1.🤖 Generated with Claude Code
https://claude.ai/code/session_016PTjN7e8aNY1gNsfZ98hgL