Admission Surfaces
Aionis compiles memory into four Agent-facing surfaces.
use_now | inspect_before_use | do_not_use | rehydrateThese surfaces are used for native Aionis memory and for external candidates from Mem0, Zep, vector DBs, markdown, or custom stores.
The Four Surfaces
| Surface | Meaning | Agent instruction |
|---|---|---|
use_now | Directly usable current memory. | You may use this to guide the next action. |
inspect_before_use | Relevant but not trusted enough for direct action. | Check it against current evidence before acting. |
do_not_use | Failed, stale, contested, suppressed, or blocked as guidance. | Do not use it as a route or instruction. |
rehydrate | Pointer to colder payload or raw evidence. | Request expansion before exact use. |
Why inspect And use Are Separate
Inspect means “allowed to read as evidence.” Direct use means “allowed to follow as direction.” This distinction matters when an old file, old procedure, or old branch is still useful reference material while the current route lives elsewhere.
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 as a warning. Aionis separates:
| Concept | Meaning |
|---|---|
prompt_included | Some bounded representation reached the Agent. |
admission_action | Whether the memory can steer action. |
actionable | Whether 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 contextAionis governs external candidates before deciding how they may influence the current prompt. Explicit observe/write paths remain available when the host wants those candidates stored in Runtime memory.