Record what the source says
arroway_verifyRecord what you found when your work ALREADY took you to a memory's source. This is bookkeeping, not an errand: never go verifying memories as a task — measured over a month, that never happens. But when you open a file, query, ticket or CRM that a memory points at, and you can see whether it still holds, say so here. Use the #handle shown in the read. Never guess an outcome you did not actually see. What the evidence decides, Arroway closes by itself (ARROW-290): a FACT whose source is proven gone is retired on the spot; a FACT whose source says something different is retired the moment you propose the correction with arroway_remember supersedes_id in this same session. On a FINDING, source_gone archives it the same way; conflicts is corrected in place with treatment=finding and supersedes_id, with no human queue. Rules and decisions are never retired this way — they only get marked.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Required for 'conflicts' (what the source actually says — it is what lets a human fix it without checking again) and for 'source_gone' (what you saw that proves removal — a note describing a timeout, an auth failure or a service being down is refused). | |
| memory | Yes | The #handle from the read (8 chars), or the full id | |
| outcome | Yes | matches = the source says what the memory says · source_gone = the source is PROVEN REMOVED (404, file deleted from the repository, record gone) — never 'unreachable': a timeout, a login wall or a service that is down is unavailability, and nothing is retired for it · conflicts = the source says something DIFFERENT (then also call arroway_remember with supersedes_id; on a fact that proposal retires the wrong fact at once; on a finding the correction replaces it in place, with no human queue) | |
| project | Yes |