Interaction plane
HOM presents sessions, workspaces, memory, tools, settings, and operator control.
ApplicationPublic architecture
One operating system. Distinct planes of authority.
HOM coordinates the human-facing workspace. AIMOS owns durable memory and cognition. A cryptographic trust plane makes consequential state transitions inspectable.
System topology
Separate responsibilities. One remembered state.
The public diagram intentionally communicates architectural boundaries without disclosing internal service topology or security-sensitive implementation details.
Execution plane
Providers and tools are selected explicitly and act within permission boundaries.
ReplaceableMemory plane
AIMOS composes sessions, persists evidence, resolves recall, and calibrates cognition.
DurableTrust plane
Identity, authorization, provenance, mutation, and audit records support verification.
CryptographicCanonical memory path
From interaction to verifiable recall.
A simplified lifecycle showing what the system promises publicly—not an exposure of internal routing.
Session
Scoped interaction retains temporal and participant boundaries.
Composition
The session owner produces durable memory at the correct lifecycle point.
Signed save
Identity, authority, and provenance accompany canonical persistence.
Recall
Native retrieval resolves relevant, temporal, and related evidence.
Calibration
Evidence is ranked and returned with confidence and traceability.
Mutation proof
Cognitive change produces an auditable transition rather than silent rewrite.
Architectural commitments
The constraints are part of the product.
HOM's differentiators are not decorative features. They constrain how memory, authority, and evidence move through the system.
No silent decay or deletion.
Memory remains addressable. Supersession and lower relevance do not erase the evidence that came before.
No environment-owned identity.
Credentials, permissions, configuration, and agent identity are designed around system custody and ledgered authority.
No wrapper pretending to be architecture.
Core behavior belongs in native system paths with explicit callers, callees, and proof—not placeholders around inherited behavior.
No publication claim without artifacts.
Benchmark identity, inputs, models, receipts, hashes, failures, timing, and denominators belong beside the result.
Σ
Cognitive mutation
Change the assessment. Preserve the chain.
A memory can become more or less useful as the system encounters new evidence. AIMOS treats that change as a traceable state transition—not permission to hide the original record.
Architecture before spectacle
The public repository will carry the reproducible detail.
This website establishes the system boundary. Source, installation ceremony, benchmark reproduction, and cryptographic evidence will belong to the release.