System requirements and Genesis.
Supported platforms, dependency inspection, database creation, identity custody, housekeeper enrollment, guide ingestion, readiness proof, and crash-safe recovery.
Release documentation
Document the ceremony. Make the system reproducible.
Release documentation contract for HOM and AIMOS: installation, security, benchmark reproduction, and cryptographic evidence — published in the release repository.
Documentation set
From first install to verified recall.
Every public instruction must be reproducible on a fresh supported machine and must not assume the creator's private configuration.
Save, recall, and memory lifecycle.
Session composition, signed persistence, evidence-backed recall, cognitive mutation, diagnostics, and the exceptional whole-brain purge ceremony.
Identity, authority, and threat model.
Key custody, agent identity, signed envelopes, permissions, canaries, provenance, security ladder behavior, and incident boundaries.
Benchmarks and publication evidence.
Dataset acquisition, run identity, model roles, scratch isolation, complete denominators, evidence verification, and signed cleanup.
First-run contract
The system should not wake up blank.
A fresh installation is designed to create its own database, establish cryptographic identity, enroll its housekeeper, ingest its verified operating guide, and prove readiness before serving memory.
Inspect
Verify platform and dependency state.
Genesis
Create ledgers and system identity.
Ingest
Housekeeper saves the verified guide.
Prove
Signed save and recall confirm readiness.
⌁
Documentation status
No stale command becomes public guidance.
Installation commands, ports, package versions, and benchmark reproduction steps are published in the release repository, verified against a clean environment.
Release updates
Documentation follows verified behavior.
Contact us if you want to review the installation or reproduction experience when the release candidate opens.