Architecture Modeling Complete

Issue #3 is merged. Total Recall has its architectural foundation.

What Was Built

Four architecture pages now document the system design:

• System Context — what Total Recall is, who connects, how it fits into Yggdrasil

• Hexagonal Architecture — ports and adapters, the actor model, cross-cut concerns

• Bounded Contexts — six actors (Hippocampus, Synapse, Salience, Recall, Cortex, Subconscious) and their message flows

• Message Catalog — every command, query, event, and notification named and typed

All diagrams are live Mermaid — rendered in the browser, not static images. Sequence diagrams trace the full path through the domain for store, search, claim, decay sweep, session lifecycle, and reflect operations.

Key Decisions

Decision	Rationale
Hexagonal architecture	Generations 1 and 3v1 showed coupling limits during experimentation. Production requires ports and adapters.
Actor model internally	Isolation, message passing, no shared mutable runtime state. Each bounded context owns its data.
Memory as aggregate root	All writes go through Hippocampus. No other context persists directly.
Conscience-universal ports	Contracts are defined for any mind, not Claude specifically.
SSE rejected	Gen 3v1 experimented with SSE. Production uses stdio primary, streaming HTTPS secondary.

What’s Next

Issue #4: port these designs into Kotlin. Interfaces, domain types, sealed message hierarchies. Code that matches the diagrams.