Trace a claim to its source
Record whether information was observed, reported, or inferred, and follow how later claims were derived from it.
When an agent uses a fact, you need to know where it came from and how it changed. Minds brings source history, checks on new knowledge, and deletion records together, so your team can investigate an answer and manage the information behind it.
Governance
“Please send deliveries to my office.”
Source: customer conversationOffice address Home address
Reason: customer request
Audit reference: example-request-184A removal request has an audit reference. Your retention process must also account for backups, exports, and downstream copies.
Illustrative audit history. A removal request is not confirmation that every retained copy has been erased.
A customer corrects an account detail. You need to inspect the original source, review the correction, and track what is removed. These controls help your team manage each step.
Record whether information was observed, reported, or inferred, and follow how later claims were derived from it.
Hold new knowledge separately while configured checks look for conflicts, anomalies, and suspicious input.
Keep the reason, returned deletion count, and audit identifier for a removal request. Review any records the tool reports as skipped.
Carry source-quality information into derived claims, so a weak source does not disappear behind a confident explanation.
Account for uncertainty when one conclusion depends on another. A chain of claims should retain its limitations.
Use calibration measures to see whether high-confidence predictions are supported by observed results.
Confirm the exact record before requesting removal. This HTTP example uses soft deletion and keeps the returned audit details. Set AKASHA_URL, AKASHA_TOKEN, and a signed AKASHA_CAPABILITY credential with deletion permission; set AKASHA_MEMORY_ID to the reviewed record ID. Your retention process also needs to cover backups, exports, and downstream systems.
const memoryId = process.env.AKASHA_MEMORY_ID;
if (!memoryId) throw new Error("Set the reviewed memory ID first");
const response = await fetch(
new URL("/v1/mcp/tools/call", process.env.AKASHA_URL),
{
method: "POST",
headers: {
Authorization: "Bearer " + process.env.AKASHA_TOKEN,
"X-Akasha-Capability": process.env.AKASHA_CAPABILITY!,
"Content-Type": "application/json",
},
body: JSON.stringify({
name: "forget",
arguments: {
memory_ids: [memoryId],
reason: "Customer deletion request",
mode: "soft",
},
}),
},
);
if (!response.ok) throw new Error("Removal request failed: " + response.status);
const output = await response.json();
if (output.is_error) throw new Error("Memory tool failed");
console.log(output.result.audit_id, output.result.deleted_count, output.result.skipped);Governance features support your review and retention processes. They do not, on their own, establish regulatory compliance or certify how your application uses data.
Connect the source, the changes, and the decision in a record your team can follow.