AiNIR has reached a v1.0 RC candidate packaging point, but it is not a v1.0 final release and not a production runtime.
This public repository demonstrates a bounded safety pipeline around AI-generated program semantics. It is still conservative by design: it is suitable for private GitHub trial, README/CI review, and external-style evaluation, not production deployment.
status: v1.0 RC candidate / pre-v1-to-v1 transition
public_release_type: demo / launch candidate
production_runtime_ready: false
human_external_review: pending
v1_final_ready: false
It is accurate to describe this repository as:
a v1.0 RC candidate public demo showing how unsafe AI-generated program-semantic drafts can be parsed, normalized, checked, refused, receipted, replayed, and only then lowered into an auditable host-enforcement skeleton.
Do not claim that this repository is:
- a v1.0 final release;
- a production compiler;
- a production payment/deletion/email runtime;
- a complete formal proof system;
- the full private AiNIR archive;
- externally human-reviewed final software.
The public candidate includes the following core surfaces:
- Safety Registry as single source of truth
- Strict Draft AST
- Evidence Ledger binding
- Operation Spec and workflow semantic profile binding
- Trusted Execution Context separation
- Lowering Eligibility Gate and host enforcement contract
- Negative conformance corpus and deterministic robustness harness
- Golden traces and replay harness
- Public/private split and documentation hardening
- Effect contracts and semantic role tightening
- Terminology conformance
- Transaction binding and semantic integrity
- Release candidate reassessment and review package
- Operation contract and launch runner stabilization
- Capability least-privilege and host enforcement contract
- Exact capability contracts
- Final defensive conformance review
- Trust Gate surface consolidation
- TrustReceipt persistence and replay
- TrustReceipt conformance integration
- Launch readiness with TrustReceipt replay
- Verified Intent export surface and external consumer profile slot
- VerifiedIntentPacket export contract hardening
- VerifiedIntentPacket semantic grounding and validator hardening
- VerifiedIntentPacket contract strictness and registry consistency
- Local private GitHub trial simulation
- README and boundary polish
- First-impression polish
- Private archive and external context profile split
- v1.0 RC scope freeze and candidate packaging
The v1.0 RC candidate freezes the public API surface for review. It does not freeze production deployment behavior, enterprise registry governance, or downstream consumer integrations.