Aionis v0.3.10 Evidence Authority and Runtime Convergence Candidate

Aionis v0.3.10 Evidence Authority and Runtime Convergence Candidate

Aionis Runtime v0.3.10 is a release candidate for the self-hosted,
single-process Public Beta. This document does not claim that the Runtime tag,
Docker image, or GitHub Release exists. The tag is pushed only after the final
candidate commit reaches main and its pre-tag gates pass. That push triggers
the exact-tag workflow. A successful workflow publishes the candidate image;
an independent digest-pinned smoke then approves that image before the GitHub
Release is created.

Candidate Scope

• Feedback attribution and measure persistence are atomic SQLite authority
  operations with exact operation receipts and replay protection.
• Commit mutations include their authoritative state in the canonical digest;
  scoped heads use monotonic revisions and compare-and-swap parent binding.
• Episode-ledger learning control supports the two-arm evidence gate, fixed
  gate-policy authority, durable work, and verified exposure-to-outcome
  attribution. The shipped global admission-candidate policy defaults to off;
  explicit selected-profile operation remains an operator-controlled evidence
  posture.
• External evidence ingestion has lifecycle, provenance, and attestation
  authority instead of being treated as an unverified learning signal.
• Deployment-slot recovery, authority-writer extraction, filesystem hardening,
  awaited shutdown, and Linux CI convergence close the main Runtime integrity
  and operability gaps found during the v0.3.10 convergence sprint. The
  deployment-authority tooling has real SIGKILL replay evidence, but the
  production isolated one-shot worker remains deferred and the current
  authority is not signing-eligible.
• Runtime and Docker CI resolve the frozen SDK and Manifest coordinates, verify
  their exact source/package identities, and exercise the real integrations.

Product and Compatibility Boundary

• The governed /v1 product surface remains 21 routes and 177 environment
  fields. Research protocols, evaluation drivers, and
  deployment-authority tooling are not new public Runtime routes.
• The authoritative SQLite schema is v6. Complete v4 and v5 databases upgrade
  transactionally on startup. Downgrade is unsupported; back up the database
  before upgrading and restore that backup if rollback is required.
• This candidate is a single-process, self-hosted Public Beta. It does not
  claim high availability, a managed control plane, or general autonomous
  learning readiness.
• Formal learning-gate calibration is still pending. Global candidate serving
  and autonomous promotion remain off by default.
• Package coordinates are frozen and are not republished for this Runtime
  candidate. The default installer remains on Runtime v0.3.6.
• The candidate Docker coordinate is linux/amd64 only. It is not valid until
  the tag workflow publishes it, and it must not move the latest tag.

Frozen Coordinates

Artifact	Version or ref
Runtime source	v0.3.10
Docker image (linux/amd64)	ghcr.io/ostinatocc/aionis:v0.3.10
Default installer Runtime	v0.3.6
aionis	0.3.8
@aionis/create	0.3.8
@aionis/sdk	0.3.19
@aionis/manifest	0.1.1
@aionis/mcp	0.3.7
@aionis/aifs	0.3.4
@aionis/claude-code	0.3.5
@aionis/substrate	0.1.11

The package rows identify already-frozen immutable artifacts. No npm publish is
part of the v0.3.10 Runtime candidate promotion.

Pre-Tag Evidence

The last pre-promotion source snapshot, commit 2467af8, passed the complete
GitHub CI run
29684934464.
Its recorded convergence evidence includes:

• 99/99 static checks;
• 339 src source modules and 171,316 src source lines;
• a daemon startup closure of 285 modules and 140,346 lines;
• a 13-module, 11,319-line authority package;
• zero detected production import cycles;
• fresh-install and external no-embedding contract smoke coverage.

This evidence is a floor, not the final release claim. The exact candidate
commit must independently pass local release gates and exact-commit GitHub CI.
An external-package smoke using DashScope qwen3.7-text-embedding must also prove
the available-embedding path, semantic/ANN provenance, feedback attribution,
persisted measure authority, and exact replay before tagging.

Completion Conditions

The candidate becomes a published v0.3.10 release only when all of the
following are true:

1. The final candidate commit is merged to origin/main without changing its
   tree and exact-commit CI is green.
2. The available-embedding external-package smoke passes against that exact
   source and the frozen package coordinates.
3. Annotated tag v0.3.10 points to that main commit and the tag workflow
   publishes the immutable linux/amd64 image.
4. Digest-pinned post-publish smoke passes before the GitHub Release is treated
   as complete.

Historical v0.3.9 evidence is retained verbatim in
v0.3.9.md.