Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Revise a neuron

crbro_revise
Idempotent

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…

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

NameRequiredDescriptionDefault
nameNoRename the neuron. Its id, file, synapses and shared state stay the same.
noteNoWhy. Stored as revision_note on facts and entry_status.note on entries. The next reader will wonder. Ignored with status verified.
tagsNoReplace the WHOLE tag list (trimmed, deduplicated). On protocol neurons re-send the priority: and source: tags or they are gone.
factsNoFacts 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.
domainNoReplace the neuron domain unconditionally, e.g. "proyectos-web".
neuronYesNeuron id or name holding what to revise, e.g. "project_octochat".
statusNosuperseded = 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.
entriesNoExact 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_toNoSplit: 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.
summaryNoReplace the neuron summary. Credentials are redacted and listed in redacted.
evidenceNoWith verified: source means the caller actually checked the reference (required); user means the user confirmed it. Omitted remains an unspecified explicit check for older clients. Never inferred from repeating a fact.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.10.0
    • addedInput schema / properties / evidence
      Added value: +{
+  "description": "With verified: source means the caller actually checked the reference (required); user means the user confirmed it. Omitted remains an unspecified explicit check for older clients. Never inferred from repeating a fact.",
+  "properties": {
+    "method": {
+      "enum": [
+        "source",
+        "user"
+      ],
+      "type": "string"
+    },
+    "reference": {
+      "properties": {
+        "field": {
+          "maxLength": 256,
+          "type": "string"
+        },
+        "kind": {
+          "enum": [
+            "file",
+            "url",
+            "person"
+          ],
+          "type": "string"
+        },
+        "project": {
+          "maxLength": 256,
+          "type": "string"
+        },
+        "value": {
+          "maxLength": 2048,
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "value"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "method"
+  ],
+  "type": "object"
+}
  2. Changed4 schema fields changedv2.9.1
    • 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"
+]
  3. Changed1 schema field changedv2.5.1
    • 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"
+}
  4. Changed1 schema field changedv2.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  5. Changed11 schema fields changedv2.0.0
    • 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"
+]
  6. Addedv1.14.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description reinforces rather than contradicts them by stressing the content is 'kept in the file, gone from recall, reversible with status active'. It adds real behavioral context the annotations cannot carry: shared-neuron sync re-application, tags replacing the whole list, move_to quarantining the source, and the fact that unmatched items remain live. It stops short of describing return shape or error behavior beyond the unmatched/shared_warning mentions.

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: the first two sentences deliver the purpose and lifecycle position before any parameter detail. The middle section is a dense run of parenthetical clauses (shared sync caveat, tags replacement, id immutability) that is information-dense but harder to scan than the opening.

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

Completeness4/5

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

For an 11-parameter mutation tool with a nested evidence object and no output schema, the definition covers lifecycle positioning, the verified/evidence semantics, move_to splitting, and shared-state caveats. Return keys (unmatched, shared_warning, redacted, retired_targets) are referenced without full description, which is the main remaining gap given no output schema exists to carry them.

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 coverage is 100%, so the baseline is 3; the description earns a step above by explaining the facts-vs-entries routing (facts retire facts by id or exact text; entries retire decisions/patterns/errors/debts) and the cross-parameter interactions the schema documents only piecemeal. It also surfaces the operational contract that anything in unmatched is 'STILL LIVE — fix and re-run', which is not fully spelled out in any single schema field.

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 and resource ('Write: change what a neuron says without deleting anything') and immediately frames it as 'Stage 2 of the lifecycle', which positions it against crbro_learn and crbro_forget by name. An agent can distinguish this from all 14 siblings without opening a 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?

Gives an explicit selection rule: 'something stopped being true... and nothing replaces it → crbro_revise', plus routing to crbro_learn with supersedes when a replacement exists and crbro_forget when it must not exist on disk. It also states the reactivation caveat (local-only on a shared neuron, next sync re-applies) and the unmatched re-run requirement, which are genuine when/when-not conditions.

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

Deploy Server

Other Tools