# Deployment Readiness

Date: 2026-07-20

## Verdict

For the current public-release decision, see `release-status.md`. This document preserves the deeper deployment evidence and remaining production blockers.

The core chain thesis works: a controller can register a constitution commitment, preserve one `agentId` while changing runtimes, verify lineage, commit receipts, and suspend the agent.

Encrypted cross-device browser continuity is live. A user can create a vault, edit the brain, disconnect, and recover the same ciphertext-backed state with a 24-word phrase or an enrolled passkey on another browser session. Markdown adapters are round-trip tested against installed Hermes and OpenClaw runtimes and current upstream NanoClaw and OpenHands repositories.

The open-source decentralized storage path is live: an official Kubo v0.40.0 node on `sxna-apps-01` receives authenticated encrypted uploads through `pin.aeonora.net` and serves public immutable reads through `ipfs.aeonora.net`. The administrative Kubo RPC remains private. Vercel production has the pin endpoint and token configured. A real encrypted two-file brain returned a pinned CID, exposed no plaintext, and restored the exact Markdown. A disposable EVM stored and resolved that CID with its ciphertext commitment.

The full on-chain thesis is not production-ready. Aeonora has not deployed its registry to a persistent public chain or completed an independent security audit. Controller rotation and delayed guardian recovery are implemented and verified on a disposable local EVM.

## Real Local EVM Proof

A disposable Ganache chain (`chainId 31337`) exercised the compiled `AeonoraRegistry`:

- deployment transaction: `0xd255bdc32c042b0758c23d14e87f16e004a84a95f2aaea58248847c4af0b0ddd`
- local contract: `0xe78a0f7e598cc8b0bb87894b0f60dd2a88d6a8ab`
- registration transaction: `0x43d451cdb6c67b88a12c3edb6384943e3814376f9e1a2cd0f7cb4c8c4fe96e62`
- agent ID: `0x07ff2126775e05bb168de494798e25e01416e3e80f07810f4461a4a017b000d2`
- initial constitution: `0xec756e129c15f2705c7dcbdfebe7ee5b6b4d05db2b304da479bf2b8e12fc871f`
- migrated constitution: `0xc81d1cba1a898f2c6b0bfd08011b71192aee52cffd75429bb7135cf0f4f41ed9`
- version after Hermes-to-OpenClaw runtime change: `2`
- previous commitment preserved: yes
- independent anchor verification: valid
- unauthorized controller write: rejected
- suspend/reactivate: passed
- action receipt commit: passed
- voluntary controller transfer: passed
- guardian recovery with two-day delay: passed
- controller cancellation during recovery delay: passed
- identity and constitution lineage preserved across controller changes: passed
- encrypted IPFS upload, recursive pin, retrieval, and exact restore: passed
- controller-gated IPFS CID and ciphertext commitment: passed

These addresses and receipts exist only on the disposable local chain. They are not public deployment claims.

## What Is Actually Useful Today

1. Create a hosted encrypted Markdown brain from the web app.
2. Recover the same brain on another device with the 24-word phrase.
3. Use a passkey with WebAuthn PRF as device-local convenience where supported.
4. Capture/install supported Markdown context surfaces for four named harnesses.
5. Define, sign, validate, and locally migrate a stable agent constitution.
6. Deploy the registry to a developer EVM and independently compare local commitment with chain state.

## Deployment Blockers

| Blocker | Why it matters | Required proof |
|---|---|---|
| Live harness semantic proof | File-level portability is proven; behavioral equivalence through model execution is not | Same fixed question answered from restored context through installed Hermes and OpenClaw |
| CLI cross-runtime remote key handoff | Browser recovery works; CLI remote envelopes remain bound to their owning runtime key | Owner-authorized rewrap, restore, and post-revocation denial |
| Public testnet deployment | Local chain proves mechanics only | Verified source, address, transaction receipts, and explorer links |
| Production IPFS replication | One local node proves integration, not durable availability | Two independent healthy pins plus retrieval monitoring and Filecoin renewal policy |
| Contract/security review | Controller and lineage semantics are security-critical | Tests, invariant/fuzz suite, and independent review |
| Edge abuse controls | Per-request limits do not prevent many valid-token writes | Cloudflare write-rate rule plus storage quota/alert proof |
| PQC implementation | Current X25519 wrapping is not post-quantum | Hybrid ML-KEM implementation, vectors, interop, migration |
| ERC-8004 adapter | Standards positioning is still aspirational | Registration document and registry compatibility test |

## Minimum Credible Pilot

Use one real SXNA agent and one real GBrain:

1. Export and encrypt its brain snapshot.
2. Derive the manifest brain commitment from encrypted bytes.
3. Register on a public EVM testnet.
4. Run and query it through Hermes.
5. Stop Hermes; reconnect the same encrypted brain through OpenClaw.
6. Prove same `agentId`, same brain root, new runtime commitment, and preserved history.
7. Revoke the old runtime grant and prove it can no longer decrypt.

Until this passes, market Aeonora as a live encrypted continuity vault plus experimental on-chain identity framework, not deployed immortal agents.

## User-wallet deployment path

The live vault now contains an optional Base Sepolia flow. It asks an injected wallet to switch networks, deploys the compiled `AeonoraRegistry`, registers the current encrypted-brain commitment, decodes `AgentRegistered`, and links the transaction on Basescan. No private key reaches Aeonora.

This path passed browser E2E against a chain with ID `84532`: wallet connect, contract deployment, successful registration receipt, decoded agent ID, and test-vault cleanup. That proves the interface and contract flow. It is not a public deployment claim until a user signs the transactions on Base Sepolia and the explorer receipts are recorded here.