memai-confidencelisted
Install: claude install-skill Filipe-Soares-de-Almeida/MemAI
# 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](#5-review_after--closing-the-decay-loop)).
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 co