The visible record behind every story
Swivver is designed so accuracy can improve over time through sources, labels, monitoring, and correction history you can inspect.
Swivver does not just publish stories. It publishes story state.
Read our standardsTrust stack
Inspectable accountability at story level
Provenance and source bundle
Stories can attach URLs, documents, and official statements with source type and trust tier metadata.
Verification state visibility
Verified, Developing, and Disputed labels make uncertainty explicit at the point of consumption.
Correction-native timeline
Changes are versioned with timestamp, owner, and reason, including contested, superseded, and retracted states.
Continuous monitoring
Key claims can be re-checked on schedule or after new developments, then labels update transparently.
Moderation and appeals log
Moderators can label, limit, correct, remove, or suspend content with case records and appeal workflow.
Sample Swivve ledger view
First publish time, source set, verification updates, change owner, change reason, and moderation state stay attached to one story.
First publish
07:42 UTC - Story published with 3 attached sources
Verification change
08:13 UTC - State changed to Developing while conflicting claims were reviewed
Correction event
08:39 UTC - Correction added with rationale and source amendment
Moderation case
09:05 UTC - User report closed with visible case outcome and appeal window
Current state
Status: Verified - Last checked 17 min ago