Choose the surface, not the slogan.
AetherMind is not one oversized product. The primitive, local coordinator, harness adapter, evidence packet, and control-plane prototype each solve a different part of the problem.
Repository field guide
Five public paths. Different contracts.
Expand a row for the short answer. Each full guide explains what the repository is, what makes it distinct, when to use it, and what it should not be mistaken for.
Use the continuity system
aethermindLocal-first coordinatorPre-release, source-available
The cross-harness AetherMind coordinator. It wakes supported agents into project-local continuity and returns bounded, caller-driven context from the work beside them.
This is the product-level coordination surface. It sits above the primitive store and adapters so more than one supported harness can orient from the same local continuity record.
Use it when work moves between supported AI environments and you want one local coordinator, explicit provenance, and bounded recall rather than another hosted memory account.
It is not a cloud memory service or a generic transcript archive. It is source-available pre-release software, so the current README and support boundary are the authority before installation.
aethermind-primitiveOpen continuity primitiveMIT open source primitive
The MIT-licensed, harness-neutral continuity primitive: an append-only project-local store, a reference library, validators, and a command-line interface for writing layers beside work.
This is the portable foundation, not a coordinator. It defines the small local contract that any shell-capable agent or adapter can use without inheriting a product-specific control plane.
Use it when you want the simplest durable continuity surface, need a neutral integration foundation, or want to add layers directly from a repository workflow.
It is not a task manager, a chat log, or a retrieval index. The store holds only load-bearing decisions, corrections, uncertainty, friction, evidence, and verification posture.
aethermind-hermes-pluginHermes reference adapterApache-2.0 reference adapter
An Apache-2.0 Hermes plugin that initializes a compact project-local AetherMind store, reads the relevant brief at session start, and exposes continuity tools during the session.
This repository packages the primitive for one harness. It is a narrow reference adapter, not the harness-neutral primitive and not proof that every Hermes deployment has native continuity support.
Use it when Hermes is the active agent environment and you want project-rooted orientation and lifecycle hooks without turning the project into a prompt transcript.
A remote service. The plugin keeps its continuity record beside the project and does not send that record to a hosted AetherMind account. It is a narrow Hermes adapter, while the project’s source records remain authoritative.
Inspect the evidence
aethermind-first-benchmark-proofPublic redacted evidence packetPublic snapshot · 26 May 2026 · commit 9272d62Historical evidence packet
A public-safe, redacted report of early AetherMind onboarding work: its methodology, aggregate observations, and the boundaries that keep the result from saying more than it can.
- Published
- Version
- No tagged release
- Source record
- Commit 9272d62
This is evidence, not software. It lets readers inspect an early orientation signal and its limits without mistaking an exploratory packet for a released benchmark or a product feature.
Use it when you want to inspect the exploratory setup, understand what was measured, or see why the project does not make portable outcome claims from it.
It is not an installer, an independent replication, or a general performance verdict. Raw prompts, recordings, private paths, and condition details are deliberately absent.
hermes-continuity-control-planeBounded local control-plane prototypeLocal adapter and kernel prototype
A small MIT-licensed local prototype that explores continuity envelopes, an append-only event ledger, narrow gate policy, and a Hermes-style integration surface.
This is adjacent architectural research, not the AetherMind store primitive or current coordinator. It tests a bounded local control-plane model without claiming native Hermes integration, production readiness, or a general memory system.
Use it when you are studying local continuity gates and control-plane behavior, or want to inspect the prototype's Python tests and contract boundaries.
It is not a context engine, bulk prompt injector, federated memory provider, or proof that compression and resumption are solved in production.