crbro-memory

Overview Schema Source Related Servers Discussions Admin

Revise a neuron

crbro_revise

Idempotent

Retire, reactivate, or verify stored facts and entries without deleting them, and edit neuron metadata or split entries into another neuron.

Instructions

Write: change what a neuron says without deleting anything. Stage 2 of the lifecycle: something stopped being true, or was never true, and nothing replaces it → crbro_revise (kept in the file, gone from recall, reversible with status active). If a replacement exists, crbro_learn with supersedes does both; for what must not exist on disk use crbro_forget. facts retires facts by id or exact text; entries retires decisions, patterns, errors and debts by exact text; status active reactivates either (local only on a shared neuron: the next sync re-applies the retirement, shared_warning says so); status verified records that a fact, decision or pattern was checked against its source and still holds. summary, domain, tags and name edit metadata in the same call (tags replaces the whole list; the id never changes). move_to splits: the listed entries go to another neuron with their dates. Anything in unmatched is STILL LIVE — fix and re-run.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Rename the neuron. Its id, file, synapses and shared state stay the same.
`note`	No	Why. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder. Ignored with status verified.
`tags`	No	Replace the WHOLE tag list (trimmed, deduplicated). On protocol neurons re-send the priority: and source: tags or they are gone.
`facts`	No	Facts to move to `status`: their ids (from crbro_recall) or exact text (trimmed, case-insensitive). For superseded/retracted only active facts match; for active only retired ones do.
`domain`	No	Replace the neuron domain unconditionally, e.g. "proyectos-web".
`neuron`	Yes	Neuron id or name holding what to revise, e.g. "project_octochat".
`status`	No	superseded = a newer truth exists (default); retracted = it was never true; active = reactivate a retired fact or entry (local only on a shared neuron: the next sync re-applies the retirement; shared_warning says so). verified = you checked these active facts, or live decisions or patterns, against their source and they still hold: their last verification becomes now and they leave possibly_stale. A retired target is not verifiable: it comes back in unmatched and retired_targets.
`entries`	No	Exact texts of decisions, patterns, errors or debts to move to `status`. Retired entries stay in the file (entry_status) but leave recall like a superseded fact. With status verified: decisions or patterns, by exact text or entry id.
`move_to`	No	Split: move the entries listed in facts/entries (ids from crbro_inspect, or exact text; any kind) to this neuron — id or name, created if missing with the same type and domain. They keep their dates, keys and retirement; the source is quarantined first and the two neurons are linked. status and note are ignored. Refused while `neuron` is shared.
`summary`	No	Replace the neuron summary. Credentials are redacted and listed in redacted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.9.1Oct 7, 2026

changedInput schema / properties / entries / description

Previous value: -"Exact texts of decisions, patterns, errors or debts to move to `status`. Retired entries stay in the file (entry_status) but leave recall like a superseded fact."New value: +"Exact texts of decisions, patterns, errors or debts to move to `status`. Retired entries stay in the file (entry_status) but leave recall like a superseded fact. With status verified: decisions or patterns, by exact text or entry id."

changedInput schema / properties / note / description

Previous value: -"Why. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder."New value: +"Why. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder. Ignored with status verified."

changedInput schema / properties / status / description

Previous value: -"superseded = a newer truth exists (default); retracted = it was never true; active = reactivate a retired fact or entry. Reactivation is local: on a shared neuron the next sync re-applies the retirement (the response carries shared_warning)."New value: +"superseded = a newer truth exists (default); retracted = it was never true; active = reactivate a retired fact or entry (local only on a shared neuron: the next sync re-applies the retirement; shared_warning says so). verified = you checked these active facts, or live decisions or patterns, against their source and they still hold: their last verification becomes now and they leave possibly_stale. A retired target is not verifiable: it comes back in unmatched and retired_targets."

changedInput schema / properties / status / enum

Previous value: -[
-  "superseded",
-  "retracted",
-  "active"
-]New value: +[
+  "superseded",
+  "retracted",
+  "active",
+  "verified"
+]

Changed1 schema field changedv2.5.1Sep 20, 2026

addedInput schema / properties / move_to

Added value: +{
+  "description": "Split: move the entries listed in facts/entries (ids from crbro_inspect, or exact text; any kind) to this neuron — id or name, created if missing with the same type and domain. They keep their dates, keys and retirement; the source is quarantined first and the two neurons are linked. status and note are ignored. Refused while `neuron` is shared.",
+  "type": "string"
+}

Changed1 schema field changedv2.4.0Sep 13, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed11 schema fields changedv2.0.0Sep 3, 2026

addedInput schema / properties / domain

Added value: +{
+  "description": "Replace the neuron domain unconditionally, e.g. \"proyectos-web\".",
+  "type": "string"
+}

addedInput schema / properties / entries

Added value: +{
+  "description": "Exact texts of decisions, patterns, errors or debts to move to `status`. Retired entries stay in the file (entry_status) but leave recall like a superseded fact.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / facts / description

Previous value: -"Facts to retire: their ids (from crbro_recall) or exact text (trimmed, case-insensitive). Already-retired facts never match."New value: +"Facts to move to `status`: their ids (from crbro_recall) or exact text (trimmed, case-insensitive). For superseded/retracted only active facts match; for active only retired ones do."

addedInput schema / properties / name

Added value: +{
+  "description": "Rename the neuron. Its id, file, synapses and shared state stay the same.",
+  "type": "string"
+}

changedInput schema / properties / neuron / description

Previous value: -"Neuron id or name holding the facts, e.g. \"project_octochat\"."New value: +"Neuron id or name holding what to revise, e.g. \"project_octochat\"."

changedInput schema / properties / note / description

Previous value: -"Why it stopped being true. The next reader will wonder."New value: +"Why. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder."

changedInput schema / properties / status / description

Previous value: -"superseded = there is a newer truth (default); retracted = it was never true."New value: +"superseded = a newer truth exists (default); retracted = it was never true; active = reactivate a retired fact or entry. Reactivation is local: on a shared neuron the next sync re-applies the retirement (the response carries shared_warning)."

changedInput schema / properties / status / enum

Previous value: -[
-  "superseded",
-  "retracted"
-]New value: +[
+  "superseded",
+  "retracted",
+  "active"
+]

addedInput schema / properties / summary

Added value: +{
+  "description": "Replace the neuron summary. Credentials are redacted and listed in redacted.",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Replace the WHOLE tag list (trimmed, deduplicated). On protocol neurons re-send the priority: and source: tags or they are gone.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "neuron",
-  "facts"
-]New value: +[
+  "neuron"
+]

Addedv1.14.0Sep 3, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds behavioral traits beyond the annotations: retired items stay in the file but leave recall, reactivation is reversible, reactivation is local-only on a shared neuron and the next sync re-applies the retirement, move_to quarantines the source first, and the id never changes. It does not contradict idempotentHint/destructiveHint=false. Slightly dense but genuinely informative; not a full 5 because permission/auth requirements are left implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the destructive/non-destructive distinction, then the alternatives. It is long and clause-heavy with semicolon packing, but nearly every clause carries a distinct routing or behavior rule, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with no output schema, the description covers the practical return semantics (unmatched, retired_targets, shared_warning, redacted) and the full lifecycle rules. An agent has what it needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds real cross-parameter semantics the schema lacks: which facts match for each status, tags replacing the whole list, note being ignored with status verified, status/note ignored on move_to, and the unmatched/retired_targets outcome when a target is ineligible.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'Write: change what a neuron says without deleting anything.' It immediately frames the tool as the non-destructive retirement/verification path and distinguishes itself from both siblings by name (crbro_learn with supersedes, crbro_forget). An agent can tell what this does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use routing: nothing replaces it / stopped being true → crbro_revise; a replacement exists → crbro_learn with supersedes; must not exist on disk → crbro_forget. It also names what each status value is for and the shared-neuron caveat, leaving virtually nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Revise a neuron

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools