[FLO-13.2c] Complete artifact adversaries, compositions, and provider-kit evidence - #60
Merged
Merged
Conversation
7 tasks
7 tasks
11 tasks done
This was referenced Sep 24, 2026
szmyty
marked this pull request as ready for review
September 24, 2026 15:39
Pull Request Summary by devActivityMetricsAchievements
|
This was referenced Sep 26, 2026
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
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.
Closes #56
Closes #57
Closes #58
Closes #59
Parent: #46
Parent kit: #29
Next after merge and green default-branch CI: #30
Outcome
Completes all four sequential #46 checkpoints in one maintainer-directed draft PR. Invalid physical/evidence outcomes stop at their exact Flow-owned boundary, fixed single-provider and two-provider compositions preserve exact accepted-artifact handoffs, and the hermetic provider kit now has its complete package workflow, behavior catalog, parent #29 evidence matrix, and #30 handoff.
Changes
Checkpoint #56 — physical outcomes
Checkpoint #57 — evidence integrity and freshness
ValidatedExecutionand protocol-valid event/result contradictions during artifact acceptance.ObservedArtifactSetto its canonical root and exact binding snapshot.Checkpoint #58 — deterministic compositions
inspect → transformsingle-provider and two-provider fixtures.AcceptedArtifactSet, preserving artifact ID, port, media type, kind, locator, and digest.Checkpoint #59 — package and evidence closeout
trusted-unconfined, scheduler, and unknown-mode-test limits explicitly.Explicit limits
The supported redistributable artifact is the MIT source bundle plus locked build instructions. A locally built binary is conformance input, not a turnkey binary distribution; target-specific dependency licenses and notices remain the binary redistributor's responsibility. The fixed test sequencer is not a scenario-manifest executor, production scheduler, durable plan/run engine, retry, checkpoint, or resume implementation. The synthetic providers are not real Aniflow, Optiflow, or Renderflow adapters. Final re-observation detects net evidence drift but is not an atomic filesystem snapshot or operating-system sandbox.
Validation
Passed locally for the #59 head:
python3 tools/validate_contracts.pypython3 tools/generate_scenario_sources.py --checkpython3 .agents/specs/validate-specs.pypython3 .agents/skills/validate-skills.pypython3 .agents/agents/validate-agents.pygit diff --checkHead
d3f6e49fbf8526ad8a109cfdf2e3aa9f926044afpassed fresh PR CI run #46: repository validators plus Rust 1.85 and stable rustfmt, clippy with warnings denied, all-target tests, Rustdoc, examples, and package verification.