Persistent memory and AHCE are Praxa product capabilities. Use @praxa/sdk/memory for read-only provider federation; AHCE is not a public ingestion endpoint.
Provided capabilities
Example outcomes
- Correct a durable memory. Open Memory settings, change or delete an owner-visible memory, and verify future recall respects the correction.
- Capture a goal. State a concrete goal in cloud text chat and review the proposed goal record before accepting it.
- Review adaptive context. Open Adaptive Context, inspect the learned rhythm, and submit a correction or abstention.
- Federate an existing store. Use the memory federation tutorial to query an existing provider without migrating it.
Verify the surface
- Confirm the capability status and listed surface in the Capability Atlas.
- Sign in to the intended Praxa product surface and select the correct personal or organization workspace.
- Exercise the example with the smallest safe scope and inspect the visible result or approval card.
- Test one unavailable, denied, or disconnected state so the surface fails honestly.
- Use a developer tutorial only when this guide links to a supported public developer contract.
Integrate existing memory
Use read-only federation when your backend already owns a supported memory provider. This does not write into AHCE or Praxa personal memory.