HOW CLAIM AUTOPSY WORKS
The X capture, factual proposition, burden of proof, documents, contrary context, date scope, and transparent revision history stay together.
Phase 06 operating boundary
Each record belongs to one Phase 05 source statement and one permanent politician identity. When an article references other officials, that does not make them the original speaker.
Our seven possible classifications describe specific propositions, not an official’s overall honesty or suitability for office. The initial Phase 06 evidence dossiers publish source-limited reasoning without applying categorical political labels. No system-generated judgment is final.
| Classification | Scope and requirement |
|---|---|
| Supported | The evidence presented would support the narrowly worded factual proposition, with cited scope. |
| Accurate but incomplete | The narrow statement may be accurate while relevant, material context is omitted. |
| Misleading | A review documents that presentation or framing conveys an implication not supported by identified facts. |
| Contradicted | Reliable records directly conflict with a specific, testable proposition. |
| Unsupported | The cited material cannot substantiate the requested proposition. |
| Unresolved | Evidence is missing, inaccessible, or credibly conflicting. |
| Opinion / rhetoric | The proposition is primarily advocacy, an opinion, or a request, not a falsifiable factual assertion. |
Evidence versus inference
Official source pages can establish dates, text, votes and individual statements. They do not necessarily establish intentions, causation, private negotiations, illegality or whether a reader-supplied X screenshot matches an independently retrieved post.
All public claims disclose when the underlying X content was not directly recovered. Alternative accounts are attributed, and procedural votes are distinguished from substantive enactment.
Manual publishing procedure
A research bot prepares offline draft JSON, collects a dated source-check ledger and preserves original material in the private development archive. Approved records receive a stable file ID and a public page; the publisher deploys a complete static ZIP. No D1, R2, public editor, sign-in form or writing endpoint is required.