Skip to Content
Aionis currently ships as a local-first Lite Runtime for developer machines and self-managed deployments.
Core ConceptsAdmission Surfaces

Admission Surfaces

Aionis compiles memory into four Agent-facing surfaces.

use_now | inspect_before_use | do_not_use | rehydrate

These surfaces are used for native Aionis memory and for external candidates from Mem0, Zep, vector DBs, markdown, or custom stores.

The Four Surfaces

SurfaceMeaningAgent instruction
use_nowDirectly usable current memory.You may use this to guide the next action.
inspect_before_useRelevant but not trusted enough for direct action.Check it against current evidence before acting.
do_not_useFailed, stale, contested, suppressed, or blocked as guidance.Do not use it as a route or instruction.
rehydratePointer to colder payload or raw evidence.Request expansion before exact use.

Why inspect Is Not use

Inspect means “allowed to read as evidence.” It does not mean “allowed to follow as direction.” This distinction matters when an old file, old procedure, or old branch is still useful reference material but must not become the current route.

Prompt Inclusion vs Direct Use

A blocked memory may still appear in the Agent context as a short warning:

Do not extend fullBundleEnvironment.ts; it was superseded by the bundledDev path.

That is prompt inclusion, not direct-use authority. Aionis separates:

ConceptMeaning
prompt_includedSome bounded representation reached the Agent.
admission_actionWhether the memory can steer action.
actionableWhether the Agent may act on it directly.

External Candidate Admission

External memory is treated as candidate evidence:

Mem0/Zep/vector result -> Aionis admission -> governed Agent context

Aionis does not silently import external candidates into Runtime memory. It decides how they may influence the current prompt.

API Guide

AIONIS_PRODUCT_API_USAGE.md