Skip to content

Log every draft command and replay it - #55

Merged
peterbjohnson merged 5 commits into
devfrom
wb/t23
Sep 20, 2026
Merged

peterbjohnson merged 5 commits into
devfrom
wb/t23

Conversation

@peterbjohnson

Copy link
Copy Markdown
Member

A draft is built up by commands, some chosen by a model. If the commands are logged the draft can be rebuilt from the source and the log with no model in the loop, which is what makes a run reproducible and a saved run a test.

Every command that changes a draft appends itself to a command log in draft.json, and every field the draft holds carries its provenance: which layer wrote it (1 spec, 2 predicate, 3 range, 4 literal), the source ranges it was copied from, whether it was edited, and by whom. in2lambda draft replay rebuilds the draft from the source and the log and must produce the same draft.json byte for byte.

Done when a draft built by a sequence of commands in a test replays identically, and a replay against a source whose hash has changed is refused.


Workbench ticket t23.

@peterbjohnson
peterbjohnson merged commit d63030d into dev Sep 20, 2026
3 of 6 checks passed
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