Correct and erase claims
Fix a claim that is wrong, add one Hyperstruck could not have read, merge duplicate entities, and remove claims for good.
In short
People and API keys can correct or add claims at any time, and people can merge or split entities. Every change is recorded with who made it and when. Erasing removes claims for good and gives you a receipt.
Correct or add a claim
If a claim is wrong, or your agent needs a detail no document states, send it with POST /statements. A correction replaces the claim you name; a new claim starts or joins a line of its own. Either way it is recorded as yours, and the line says so: "corrected by Mei Tanaka on 28 October 2026". Nobody mistakes it for something a document said.
The same route closes an obligation or moves its due date.
Decisions that need a person
Most claims need no one's attention. These are the decisions that do:
| Decision | Who can make it | How |
|---|---|---|
| Which of two conflicting claims stands, or that both do | People and API keys | Settle a conflict |
| Correct a claim, add one, or close an obligation | People and API keys | Correct or add a claim |
| Two entities are really one, one is really two, or an entity has another name | People | Fix who is who |
| Two attribute names mean the same thing | People | Fold one attribute into another |
| An attribute holds readings, or is protected | People; an API key may only mark it protected | Set an attribute's nature |
Every decision is recorded with who made it and when, and the line shows it. Each one needs curate access on the agent (access control).
To find what is waiting, list what is left to decide: every conflicting line and every pair of entities that may be the same one, each with a sentence saying why.
Erase claims
| To remove | What goes |
|---|---|
| An entity | Every claim about it, with a receipt counting what was removed. Add dry_run=true to see the receipt first, with nothing erased. See Erase an entity |
| A document | The claims that only that document supported. Claims another source also supports stay |
| An agent's whole store | Every claim the agent holds |
Who can see claims
Claims belong to the agent that recorded them. A request only ever sees claims in the spaces it is allowed to read, and an entity it cannot see answers 404, exactly like one that does not exist. Sharing and visibility explains spaces.