Run shared behavioral laws against both runtimes through one harness - #240
Merged
Conversation
Add a backend-neutral behavioral conformance harness (conformance/behavior) with normalized observations and a Backend contract, and run the same 18 shared control-law bodies against kernel.Runtime (integer fixture) and the production engine.Engine Resolve/Apply path (in-memory software fixture). Record the one semantic mismatch: kernel.Runtime cannot express explicit-only transitions. Add a program-drift suspension/reconciliation strengthening test at the supervisor boundary.
…falsifiable The software adapter now withholds the trusted minimum by compiling advance to an effect whose kernel-owned floor demands publication.publish, a capability repository-class authority cannot grant, so the production capability projection itself denies. The explicit-only law isolates the explicit transition as the only admissible candidate before asserting it is never implicit progress. ConcurrentApply forces both racing applies onto one observed base revision so the engine's in-lock revalidation is load-bearing. Each law now fails deterministically under mutation of its production guard.
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
1 participant
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.
Summary
boatstack/conformance/behavior: normalized decision/observation/event types, a minimalBackendcontract, andRunSharedLawsimplementing 18 shared supervisory control-law bodies exactly once.kernel.Runtimeover the existing deterministic integer fixture, and the productioninternal/softwaredelivery/engine.EngineResolve/Applyboundary over a minimal in-memory software fixture (no network/GitHub effects).kernel.Runtimecannot express explicit-only transitions (kernel.Transitiondeclares no selection class andRuntime.resolvemarks every admissible candidate selectable); the law is a recorded skip on the kernel backend and passes on the software engine.Policy.ReconcilesProgram) remains resolvable.conformance/tree in the flow/standard ownership-completeness contract; add a release note.No production code changes; software delivery's stronger journal, recovery, authority, and idempotency semantics are untouched.
Test plan
GOWORK=off go test -count=1over kernel, kernel/conformance, engine, delivery, flow/standard, controlprogram, effects, surfaces, and conformance/behavior — all okgo build ./...andgo vet ./...cleanBOATSTACK_REQUIRE_FLOW_FRONTEND=1frontend conformance: 15 pass, 0 skips