Core Concepts

Aionis is not recall memory. It is state-adjudicated memory.

The practical difference:


retrieval asks: what text is related?
Aionis asks: can this memory safely shape the next Agent action now?

The Core Difference

Recall memory	Aionis
Retrieves related text	Governs whether memory can influence action
Treats history as context	Treats history as state with lifecycle
Optimizes semantic similarity	Optimizes current, safe, attributable Agent context
Usually lacks outcome attribution	Records guide decisions and feedback attribution
Often stores summaries as truth	Keeps raw evidence, lifecycle state, and rehydrate pointers separate

Product Loop

Aionis is built around a closed loop:


observe -> guide -> agent action -> feedback -> measure -> snapshot

Step	Runtime role
`observe`	Record ordinary memory, execution events, validator outcomes, and handoffs.
`guide`	Compile governed Agent context with admission decisions.
Agent action	Your host runs tools, browser, shell, verifier, or model calls.
`feedback`	Attribute outcome to memory that was actually exposed and used.
`measure`	Report what memory changed without overclaiming.
`snapshot`	Produce operator-facing replay and state surfaces.

Memory Lifecycle

Aionis asks a narrower question than “is this relevant?”:


Can this memory safely shape the Agent's next action now?

That answer becomes one of four admission surfaces:

use_now: current, actionable memory for direct context use.
inspect_before_use: useful but requires verification before action.
do_not_use: stale, failed, suppressed, blocked, or unsafe as guidance.
rehydrate: compact pointer that should be expanded only on demand.

Two Kinds Of Memory

Type	Examples	Aionis treatment
Ordinary memory	Preferences, facts, project notes	Scoped recall, lifecycle gating, feedback attribution.
Execution memory	Attempts, validator results, handoffs, failed branches, procedures	Branch isolation, active path preservation, failed route suppression, workflow projection.

Execution memory is Aionis’s strongest product wedge. It lets an Agent continue work without turning old mistakes into new instructions.

Product Boundary

Aionis owns memory governance, not tool execution. Your host still owns plans, shell commands, browser automation, validation, retries, and final task control.

This boundary is deliberate. Aionis should be easy to put next to Claude Code, Cursor, OpenHands, custom loops, or multi-agent systems without becoming another Agent runner.