Memory Governance

Memory governance endpoints decide how memory is allowed to influence an Agent. They are useful for Aionis-native memory and for external backends such as Mem0, Zep, vector databases, search indexes, logs, or markdown stores.

Endpoint	Call it when
POST /v1/memory/govern	You already have candidate memory and want Aionis admission before prompt use.
POST /v1/rehydrate	A guide returned a compact pointer and the Agent needs more evidence.
POST /v1/forget	A host or operator needs to suppress, restore, or lifecycle-control memory.

Admission actions

Action	Meaning
`use_now`	Memory can directly guide the next Agent action.
`inspect_before_use`	Memory is relevant but should be verified before direct action.
`do_not_use`	Memory must not guide action, but may appear as a warning or audit note.
`rehydrate`	The compact context points to evidence that should be expanded on demand.

Common flow


external candidates -> govern -> compact context -> feedback -> future admission

Use POST /v1/memory/govern when Aionis is fronting another memory backend. Use POST /v1/guide when Aionis should recall from its own Runtime memory first.