Publish AiNIR v1.0.0 RC2 profile and conformance SDK - #1
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
Publishes the AiNIR v1.0.0 RC2 public refresh on the real GitHub lineage.
This change turns the bounded public demo into an externally inspectable profile-and-conformance SDK while preserving fail-closed trust boundaries. It adds stable artifact contracts and CLI surfaces, packaged schemas/resources, profile authoring and conformance, registry evolution and replay modes, deterministic offline EvidenceProvider contracts, bounded MCP tool-call preflight, and a host-owned non-executing OpenAI function-tool normalization example.
Safety boundaries
Verification
Local verified baseline before publication:
Hosted checks on this PR must confirm Python 3.10-3.13 plus Windows and macOS before merge.
Review focus
Please review
PROTECTED_INVARIANTS.md, public/private boundaries, exact receipt/registry bindings, external profile restrictions, no-execution adapter boundaries, release wording, and distribution resource parity.