Skip to content

AOI v0.5 unpublished internal adoption

The public v0.5.0a1 route and completion boundary in the canonical v0.5 implementation and release plan remain unchanged. One bounded local exception may precede public publication for maintainer-owned internal adoption. It is not a release, promotion, public readback, Company OS READY result, or evidence that the v0.5 completion boundary passed. It may not create or move a tag, publish to GitHub or PyPI, upload a release artifact, or substitute local evidence for any public or provider-live gate.

The exception is fail-closed and ordered:

  1. This policy change itself must receive independent exact-byte review, normal non-admin Git delivery, and fresh successful test.yml plus docs.yml readback on the same exact merged main commit.
  2. A clean external worktree at that commit must create exactly one reviewed reviewed_local_install_bundle with proof_scope=exact_local_wheel_install_only. The bundle, wheel, sdist, source manifest, inventory, rehearsal, review, and seal remain local and content-addressed. Caller-supplied test context is not source-to-wheel derivation proof.
  3. The exact wheel must be installed offline in a new side-by-side AOI-only environment while frozen N-1 and rollback assets remain available. Package, installed-metadata, synthetic Company OS, Supervisor, IC-Pack, IC-RAG, hook-receipt rotation, and archive canaries must pass on disposable state. The synthetic Company OS canary is not provider-live Company OS READY.
  4. Internal rehearsal and distribution readback may verify only those local content-addressed artifacts. They grant no public release or promotion status.
  5. Before touching an existing project, every old writer must be proven quiescent; a complete repo-external backup and non-live rollback rehearsal must verify; and a digest-bound migration preview must retain the exact candidate proof, preimages, old environment, and rollback assets. The side-by-side migration may apply once only while those identities remain exact, followed by hooks, doctor, task, Chief, handoff, and Dashboard readback. Unknown effect, drift, failed rollback, or non-quiescence stops the route without retry or relaunch.
  6. Only after that internal migration and readback may a separate AOI-managed ARISE read-only dogfood task begin. It may use existing evidence and produce a repo-external architecture decision package, but may not modify ARISE source, RTL, docs, AOI project files, or Git, and may not launch VCS, EDA, or GPU work. It is internal dogfood evidence only and cannot be promoted into v0.5.0a1 release evidence.

This exception does not satisfy any public acceptance target. Public ARISE adoption still follows public readback, and public v0.5 completion still requires every item in the canonical completion boundary.