Safety And Portability

The runtime enforces several invariants independently of the mineable ABI. They remain fixed while candidates compete on memory quality and efficiency.

• Canonical event writes remain under runtime control.
• Every derived artifact cites its source events and is schema-validated.
• Retracted, deleted, expired, superseded, or out-of-scope evidence is excluded before serving.
• M5 may rank only material admitted by M4, and M6 may select only material surviving M5.
• Unknown, duplicate, fabricated, or malformed references fail closed.
• The runtime constructs the final context and rechecks its rendered budget.
• Retrieved memory is fenced from automatic reinjection as new source evidence.
• Tenant, user, agent, profile, and optional session scopes are enforced at the adapter boundary.
• Hooks run with bounded compute and derived-storage allowances. Their sandbox disables network access.

Portability is a property of the runtime and ABI. Miners focus on improving the memory pipeline while candidate modules pass the published compatibility preflight. The same accepted release must execute under the supported Python, operating-system, and CPU architecture matrix. The launch runtime has been exercised on native x86-64 and native ARM64.