Skip to content

Accept frozen campaign requests from JSON files - #581

Open
CaelmBleidd wants to merge 1 commit into
caelmbleidd/pbt-completed-state-evidencefrom
caelmbleidd/pbt-public-experiment
Open

CaelmBleidd wants to merge 1 commit into
caelmbleidd/pbt-completed-state-evidencefrom
caelmbleidd/pbt-public-experiment

Conversation

@CaelmBleidd

@CaelmBleidd CaelmBleidd commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Frozen experiment cases currently need a compiled service-loaded registry before they can use the public campaign runner. Add the campaign-file <request.json> <artifact.json> entry point, which decodes one property and its explicit controls, invokes PropertyCampaignRunner, and writes its actual artifact once. The concrete seed also initializes the symbolic machine seed.

This is a small experiment input adapter: it adds no runner, retained session, generation loop or selector policy. Relative source roots resolve against the request file. It is stacked on #579 at b7b2a010dcfba3ed5cf72dc16d4acc106e2472b4; only this PR's commit belongs in the follow-up after dependencies are merged. Own diff: 3 files, +148/-1.

Validation: two real-backend CLI regressions passed for registry-free symbolic/native capture and invalid controls; main/test Detekt reports zero findings. Installed distribution built successfully. Experiment corpus and comparative measurements remain separate follow-up work for #356/#357/#405.

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