AetherMind evolves · one central core
Let the work remember.
AetherMind carries the judgment a transcript leaves behind: why a decision held, what changed it, what remains uncertain, and what must be checked next.
One continuity core. Project-owned records. Multiple ways to connect.
The next chapter
A shared engine.
Continuity beside the work.
AetherMind is evolving around a central core. The new aethermind-engine repository brings the continuity implementation together: one library, a CLI, and an optional MCP server.
The code has a central home. Each project keeps its own append-only layers, corrections, and texture. Writers run on the host that owns those files.
Start with the engine.aethermind/Layers · texture · events · evidence pointers
Repository roles in the evolving architecture. Check each source for its current integration status.
Choose your way in
Start with the question you actually have.
Understand what crosses a handoff.
What continuity carries, what it does not replace, and how it directs the next safe action.
Choose the right surface.
Start with the central engine, then explore the coordinator, primitive, harness adapter, and research repositories.
Inspect the claim with its boundary intact.
An unsubmitted thesis, early exploratory work, and a benchmark design that is honest about what remains unproven.