Fictional structural fixture · no real notices, identifiers, records, or editorial actions
A source change starts verification. It does not settle the record.
This demonstration follows one imaginary status alert from detection and identifier matching through human verification, affected-record review, and an editorial disposition.
The maintenance path
Five steps preserve the difference between a signal and a decision.
- 01
Detect
A fictional source-status change enters a bounded maintenance queue.
- 02
Match
A canonical fixture identifier points toward one source record.
- 03
Verify
A human checks source identity, notice status, dates, and applicability.
- 04
Review impact
Connected articles, claims, studies, trials, and topics are examined separately.
- 05
Dispose
Publish an update, hold, dismiss, or take no action—with the reason retained.
Fixture alert
One alert, described without a verdict.
Each field answers a different maintenance question. None is an evidence, truth, credibility, or person score.
Fictional source-status change
status-alert:fixture-correction
- Canonical identifier
- FIXTURE-STATUS-001
- Previous status
- Unknown
- Observed status
- Corrected
- Match confidence
- Exact identifier · not verification
- Source role
- Primary support
- Triage
- Needs verification
- Verification
- Needs verification
- Record correction state
- None · pending verification
- Disposition
- Hold
- Stale after
- August 6 fixture deadline
Affected-record traversal
Connected records are reviewed independently.
Needs verification
The fictional article cites the changed source. Its wording and source use require review.
Not assessed
The fictional claim mapping is connected, but the alert alone does not change its assessment.
Unavailable
The fictional study record cannot yet be checked independently, so no update is published.
Three separate judgments
Matching, verification, and disposition answer different questions.
Identifier match
Does the alert point toward the same canonical fixture record?
Here: exact match, still unverified.Source verification
Did a human confirm the source status, date, identity, and applicability?
Here: not yet.Editorial disposition
Should an affected record be updated, held, dismissed, or left unchanged?
Here: hold pending review.Append-only history
The alert trail keeps uncertainty visible.
- Detected
A fictional corrected status entered the queue.
- Matched
The fixture identifier resolved to one source record.
- Verification requested
A human check was required before any record change.
- Affected records reviewed
Three connected fixture records received independent states.
- Held
No automated publication or record mutation occurred.
Honest states
Every unresolved condition stays explicit.
Detected
A possible change entered the queue.
Matched
An identifier points to a record, not a conclusion.
Needs verification
A human check is required.
Verified
Source status and applicability were confirmed.
Dismissed
The alert did not require an update.
Unavailable
The source cannot currently be checked.
Unknown
A value has not been established.
Corrected
A dated correction changed the current record.
Superseded
A newer status replaced the current state.
Retracted
The source is marked retracted; affected use still needs review.
Stale
The verification deadline passed without a current check.
Interpretation boundary
Record status is not a judgment about people or fields.
A correction, expression of concern, retraction, registry change, or regulator update applies to a specific record and its current use. It is not a credibility score for an author, researcher, organization, intervention, or scientific field.
Continue