EXPERIMENT 05 · FEEDBACK AND REPEATED WORK
After the review,
what next?
A review can change what work is needed. Keep valid evidence, repeat what has become stale, and test whether a response policy can reach the goal across every modeled outcome.
Computed in your browser · Explicit finite horizon · Fictional refuge
KEEP THE EVIDENCE THAT STILL HOLDS
A drawing correction need not restart the analysis.
EXPERIMENT 04 · RETAINED
One mechanism.
Many ways through.
Choose a project state and generate the bounded family of ways to complete the refuge. Keep work branches, joint resource starts, token-supply histories and schedules visible.
Generate ways to complete the refuge →Open the Process Contract Lab ↗
Earlier methods, retained.
The Process Contract Lab keeps the earlier ancestry-family and typed-composition questions available.
Keep the “either”
Compare the alternative sequential orders supported by a selected execution’s histories. Test whether a single dependency graph preserves them, or exhibits a false permission or restriction.
Open this experiment →Explore every compatible ancestry
Enumerate producer-count token histories for the selected trace. Discover whether all, some or none admit an exact task tree. A cutoff keeps the answer explicitly unresolved.
Open this experiment →Build with actual wires
Compose refuge activities through matching typed ports. Keep identity wires, resource ownership and selective handoffs visible, then generate the resulting executions.
Open this experiment →EXPERIMENT 02 · RETAINED
Inspect one
causal witness.
The Causal Plan Lab follows one chosen token ancestry into a dependency graph and schedule. It checks exactly when an elementary sequence/parallel task tree preserves that witness, and exposes an N obstruction when it cannot.
Open the Causal Plan LabINHERITED BASELINE · BROADER GIMMER COLLECTION
Two processes.
One chosen plan.
This earlier human-steered, AI-assisted comparison supplied the starting point. It is not a higher-autonomy experiment. The comparison is presented in broader Gimmer. Its forward scheduler remains in the core collection, using the same maintained application.
What the certificate means
Each certificate names its domain: a bounded observed-state response policy, a whole-family state/step construction, one witness, a selected trace’s ancestry family, or a typed port construction. A retrospective branch schedule does not certify an online concurrent policy. An exact language of sequential orders does not establish concurrent-step or timed equivalence. Search bounds and the distinction between proved and unresolved results remain visible.
This is the Petri/WBS route, FORAY-WBS-PATHS, within FORAY-PROCESSES-TO-PLANS. The broader hill/travel scenario remains outside this public slice. The new feedback experiment has explicit completed-event checkpoints; continuous operation and uncertain engineering calibration remain outside its claim. Construction methods and durations are illustrative.