Review, correct and supersede
Keep decisions and replacement claims traceable
Review records a human decision about a claim. Approval, rejection and correction are separate from creating it, assigning confidence, materializing facts or declaring model terms.
Review state
| State | Meaning |
|---|---|
| Proposed | Created and awaiting a review decision |
| Approved | Approved by a reviewer; still subject to validity and evidence limitations |
| Corrected | A correction decision is recorded; inspect the replacement claim |
| Rejected | Not accepted; reason/history are retained |
| Superseded | Replaced/retired by a newer record under a supported lifecycle path |
Status alone does not prove current validity, independence of evidence or complete downstream recomputation.
A correction walkthrough
You need a Semogram account, project access and the supported reviewer permissions. Start with a real assertion for https://example.com/orders/1 and predicate https://example.com/operations#delivered claiming true.
- Open its project Assertions detail. Inspect subject, value, validity, confidence, actual evidence links and history. Compare the receipt with the order ID.
- If it is correct, use the supported Approve action. If the statement is unsupported or wrong, reject it or propose a correction rather than changing its content in place.
- Choose Propose correction when the statement needs replacement. The form keeps the original identity context; enter the correct replacement value and review what it says.
- Save the correction. Inspect the original's correction state and the new replacement assertion. A newly created replacement is a separate claim and needs its own review; creating it is not automatic approval.
- Inspect derived-output impact and rerun the relevant query under its configured statuses, validity and conflict rules.
For example, a receipt that proves attempted delivery rather than completed delivery does not support true. Record the narrower supported statement or leave completion unknown; do not convert missing evidence into false without justification.
Supported actions and limits
The current project UI supports approval, rejection and correction through its claim workflow. Generic content updates are refused; use correction for changing statement content. Some displayed lifecycle choices may be restricted by the server; inspect the response and saved state rather than treating a button click as a recorded decision.
The governed decision contract includes operation key, expected revision, action, reason, decision time and replacement for corrections. Revision protection prevents a decision against a claim that changed after review. Generic public workspace-key assertion decision endpoints and MCP claim-review mutation tools are not currently exposed; claim_get is inspection, not approval.
Time and propagation
Business validity describes when a statement applies; recorded/review times describe when Semogram knew or acted on it. These are different. An asserted binding's validAt filters business validity against current review state; it is not a complete historical reconstruction of every past decision.
Corrections and retractions can mark dependent outputs stale or requiring review. They do not undo completed external writes or automatically republish queries. Inspect replacement links, derivations, affected outputs and current query results.