Repository navigation
test: prove ores-legal #28 AI-policy peer-authority parity - #17
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.
Cross-org promotion evidence for
ores-legal/ores-legal-interfaces#28at source headcea162a3ebb04439adb5893a126450ac697fa58b.This public test lane has demonstrated working runners today. It mirrors the exact AI-policy TypeSpec and independently authored JSON Schema authorities and runs the pinned
typespec-json-schema-validatoraction.The workflow requires a passed report, zero unexplained findings, no authority precedence, zero differential divergence/refusal, and records Git blob plus source-head binding.