Review, correct and supersede
Keep decisions and replacement assertions traceable
Review records a human decision about an assertion. 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 assertion |
| 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.
Semantic retirement preserves the original claim as Superseded and closes its validity through the governed retirement trigger. Direct edits to the claim's value or validity remain blocked; use the correction workflow to replace a claim.
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 correct it rather than changing its content in place.
- Choose Correct assertion 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. Saving it is your review: the replacement is recorded as a separate, approved assertion, and the original becomes Corrected with its validity closed where the replacement takes effect. Inspect both.
- 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 assertion 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 an assertion that changed after review. Generic public workspace-key assertion decision endpoints and MCP assertion-review mutation tools are not currently exposed; assertion_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.
Provenance when replacing an assertion
The correction form prefills the original source artifact, record, field, citation
and recorded artifact revision. The service also inherits omitted source context
for the same source. Explicit null clears a source reference. Choosing a different
source artifact does not carry an unrelated old record/field into that artifact.
Supporting evidence is not automatically copied as if it proved the replacement; the original evidence remains accessible through the correction chain. Legacy links without an original revision stay unresolved rather than pinning today's bytes as historical evidence. Existing query bindings keep their chosen read mode. The source-provenance section lists query binding matches for review; it does not rewrite queries or change earlier releases/forecast evidence.