Governance

Understand what your agent knows. And why.

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

The record includes what changed.

Customer preferencerecord / 184
  1. SEP 02 · 09:41

    Preference reported

    “Please send deliveries to my office.”

    Source: customer conversation
  2. SEP 08 · 14:12

    Customer correction

    Office address Home address

    Source: customer follow-up
  3. SEP 12 · 11:06

    Removal requested

    Reason: customer request

    Audit reference: example-request-184

Record the request. Review its scope.

A removal request has an audit reference. Your retention process must also account for backups, exports, and downstream copies.

Choose a chapter to explore

Illustrative audit history. A removal request is not confirmation that every retained copy has been erased.

From source to decision

Follow the information through its life.

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.

01

Trace a claim to its source

Record whether information was observed, reported, or inferred, and follow how later claims were derived from it.

02

Review before accepting

Hold new knowledge separately while configured checks look for conflicts, anomalies, and suspicious input.

03

Keep a record of removal

Keep the reason, returned deletion count, and audit identifier for a removal request. Review any records the tool reports as skipped.

04

Keep source quality visible

Carry source-quality information into derived claims, so a weak source does not disappear behind a confident explanation.

05

Carry uncertainty forward

Account for uncertainty when one conclusion depends on another. A chain of claims should retain its limitations.

06

Compare confidence with outcomes

Use calibration measures to see whether high-confidence predictions are supported by observed results.

Managing a deletion

Remove a reviewed record. Keep the details.

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.

See an example record history
Illustrated workflowGovernance folio
One record. Its full account.

From source to audit reference.

FOLIO
001
Source recordSample 01
Reported
“Q3 revenue dipped after the channel mix shifted.”
Source
finance-review
Memory
mem_sample_01
Tags
q3 · revenue

The claim keeps its attribution.
Origin is part of the record.

Deletion request02
Forget selected memory

Reasonstale quarterly note

mem_sample_01
Audit referenceSample
audit_idaudit_sample_01

Illustrative identifier. This preview makes no live deletion request.

01 / 03

Keep the source with the claim.

Inspect where a fact came from before relying on what it says.

Request removal and keep the audit identifiertypescript
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);
Technical details

Evidence your team can review.

Governance features support your review and retention processes. They do not, on their own, establish regulatory compliance or certify how your application uses data.

At a glance
Source history
Origins and derivation relationships
New knowledge
Configurable verification and promotion
Deletion requests
Audit identifier, deletion count, and skipped records
Deletion modes
Soft deletion by default; hard deletion on request
Review scope
Application policy, deployed configuration, and retained copies

Make your agent’s knowledge reviewable.

Connect the source, the changes, and the decision in a record your team can follow.