Conversation
This was referenced Sep 26, 2026
This branch has not been deployed
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.
Purpose
Define the first stronger semantic obligation family on top of Assurance IR.
Each source-grounded semantic path ending in a protected effect is compiled into a standard OVK
VerificationObligationwith explicit:Core property
Performed(principal, effect, resource) -> Authorized(principal, effect, resource)This PR defines the obligation structure only. It does not yet wire a backend that can establish every facet.
Binding semantics
Identity bindings are represented explicitly. Non-identical references can be connected through an explicit Assurance IR binding constraint. Missing bindings remain unresolved instead of being treated as equal.
Trust boundary
This PR does not claim:
Those are intentionally left for backend/source-profile work.
Stack
This PR is stacked on #30 and targets
feat/assurance-ir-v1; it should not be merged independently intomain.The current OVK v1.3.0-rc.1 release process remains isolated from both feature branches.