Intro

Aionis is a state-adjudicated memory Runtime for Agents that need to keep working across sessions, roles, failures, and compaction boundaries.

Most memory systems retrieve related text. Aionis decides whether that memory is current, stale, contested, failed, reusable, or worth rehydrating, then compiles the governed state into the next Agent context.


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

What Aionis Is

Aionis is	Aionis is not
A memory Runtime for Agent loops.	An autonomous Agent runner.
A context compiler with admission gates.	A raw vector database.
A way to preserve execution state.	A prompt-only summary layer.
A feedback-attributed governance surface.	A replacement for your tool sandbox or host auth.

Aionis sits between an Agent and its history. Your Agent host still plans, executes tools, validates work, and owns permissions. Aionis records evidence, governs what memory can influence the next turn, and explains the decision.

The Core Difference

Recall memory answers:


What memories are related to this query?

Aionis answers:


Which memories are allowed to affect this action right now?

That difference matters when old failed branches, stale assumptions, contested facts, or large raw traces remain semantically relevant. Aionis separates use_now, inspect_before_use, do_not_use, and rehydrate so related history does not automatically become instruction.

Product Surfaces

Surface	Use
Execution Memory	Continue long-running work across sessions, agents, handoffs, failed branches, and accepted routes.
Memory Firewall	Govern memory candidates from Mem0, Zep, vector DBs, markdown, or custom backends before prompt use.
Agent Flight Recorder	Replay what an Agent could see, what was blocked, and why.
Loop Engineering	Give plan/change/observe/revise loops memory, feedback attribution, and measurement.
Controlled Forgetting	Suppress, archive, unsuppress, or delete memory with traceable lifecycle state.
Admission Dataset Export	Export admission, usage, outcome, and feedback records for analysis and future learned policy.

Execution Memory is the primary Runtime capability. Memory Firewall is the fastest adoption path when you already have another memory backend.

How It Works

Your host calls observe when the Agent attempts work, sees tool output, gets verifier feedback, or finishes a handoff.
Your host calls guide before the next Agent turn.
Aionis compiles governed context: current path, inspect-only evidence, blocked branches, procedures, and rehydrate pointers.
The Agent acts in your host.
Your host sends feedback tied to the guide trace.
Aionis can measure effect and expose a snapshot for replay.

Start Here

Goal	Next page
Run Aionis locally	Quickstart
Understand the setup path	Get Started
Learn the product surfaces	Products
Understand the mental model	Core Concepts
Wire the loop into your host	Using Aionis
Pick SDK, HTTP, MCP, or external memory	Integrations