Repository navigation
fix: enforce integrity contracts and ship Yeoul 0.3.0 - #12
Merged
Merged
Conversation
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.
Summary
Harden the supervised Yeoul workflow without making preregistration mandatory for discussion arcs.
Verification
Compatibility and honest scope
v0.3.0 intentionally requires a supervisor baseline for protected standalone verification; --current-only is an explicit weaker diagnostic. Existing ledgers/archives are not rewritten. Local hashes do not establish identity, external time, content truth or independent reproduction. Agents with permission to rewrite every artifact remain outside this workflow-level boundary. Token limits are between-round controls, not hard provider spending caps.