1
Open the change queue
Visit
http://localhost:3000/changes and select Propose memory. The workspace provider fills the current namespace ID for you.2
Propose a policy candidate
Set the memory class to policy, the trust class to observed, and enter:Use a valid source URL and source content that describes the policy. Submit the proposal. Stash returns a generated candidate ID and stores the content and source digests.
3
Screen the candidate
Open the candidate and select Screen candidate. A safe candidate advances to
evaluating. A deterministic poisoning or provenance failure is quarantined and cannot be approved.4
Run behavioral evaluation
Select Run evaluation. Wait for the status to report Evaluation Passed. The evaluation is asynchronous: the API first queues evidence work, then the outbox worker records the terminal receipt.
5
Approve the exact evidence binding
Enter a review reason and approve the candidate. The review binds the candidate digest to the evaluation run, baseline namespace revision, and policy version. Changing any bound input makes the review stale.
6
Promote the memory
Enter a stable key such as
refund-human-review and a promotion reason. Promote the candidate. Stash creates a new memory version and advances the namespace revision in one transaction.7
Confirm agent-visible retrieval
Open Memory and locate the promoted text. The active version shows its lineage, version, namespace revision, source, and release history. Semantic search reads only active, tenant-scoped memory.
8
Roll back without erasing history
Open the memory lineage, choose an earlier version, provide a rollback reason, and confirm. Stash writes a new forward revision using the earlier payload; the prior release and its audit events remain intact.