memai-confidence

memai-confidence — verifying facts, setting confidence

confidence is only worth setting when the claim was checked live. This skill reads a memory's anchors against today's source and sets the field — and it is where a memory the store handed back as due gets its recheck (§5).

The pass proposes: everything below is staged through optimize_stage and applied by a human in the dashboard.

---

1. The three values

Value	When
confirmed	A note/reasoning/anti_pattern/diagram whose structural anchors were checked live: the file and line exist, the symbol is there, the table/column exists, the domain resolves, the URL answers.
contradicted	The claim is false today — the fact no longer holds. Requires a non-empty verified; normally staged next to a reword or an archive.
unverified	Nothing to check it against: ephemeral or point-in-time (a count, a value, "open this month"), external, or a checkpoint still bearing live work.

A checkpoint stays unverified. Its content is where the work stood, not a verifiable fact, so there is nothing for a live check to agree with. A checkpoint for an effort that has closed is not a confidence question either — it is retirement, in [[memai-checkpoints]].

Do not let an ephemeral tail contaminate a durable core. A note carrying a durable mechanism plus one dated example (the counts from one run, one queue's depth) is confirmed on the mechanism. The dated example neither blocks the confirmation nor earns a demotion.

---

2. How a check is made

• Start from the anchors the scan already extracted. Per memory, optimize_scan pulls the verifiable references out of the full body — URLs, file paths, table/field-style identifiers, SNAKE_CASE constants — and returns them space-joined. That is the work list, without re-reading every body. It is capped at the top 5: when the verdict needs more than those, open the record with get_memory(uid).
• A check is read-only, against the live source the claim points at. Code and config: read the file, grep the symbol. Schema: describe the table. A URL: fetch it. Which tool is allowed to read a database, and which agent a fan-out may be delegated to, are the host project's rules — read them and use what they approve. This skill names no server and no model tier; it only requires that the check touches the real thing and changes nothing.
• Fan the checks out into separate agents, one per cluster (§4). Verifying an anchor costs the reading it takes — files opened, tables described, dead ends — and that reading belongs in an agent's context, not in the pass's own. Each agent returns a verdict per claim plus the evidence for it; the pass keeps the verdicts.
• Ask for a verdict, not a repair. The agent reports what it found (file:line, the column, the resolved domain). Fixing the code is not this pass.
• Hand over exact paths. Resolve them (Glob) before dispatching, or every agent spends its first turns finding what the pass already knew.