Record, Not Rumor
Record,Not Rumorsource first Records Directory →
CANONICAL SYSTEM & GOVERNANCE RECORD

Source before conclusion.
Architecture before assertion.

Record, Not Rumor is a custom-built public evidence system. It preserves source provenance, separates evidence from allegation and inference, tests public claims against their strongest available record, exposes evidentiary limits, and makes material corrections visible.

This page defines what the system is, what it is not, how evidence may eventually enter the review process, how findings are classified, and how the public record remains inspectable without exposing private source code or security-sensitive operational details.
SYSTEM IDENTITY

What Record, Not Rumor is.

Record, Not Rumor is an independently built records-audit and claim-verification application. Its founding archive concerns the Clancy case, but the system is designed around a reusable evidence standard rather than a true-crime format.

Records audit

Claims are decomposed into testable propositions and compared with authenticated or otherwise properly classified source material.

Provenance system

Sources are identified by what they are, where they came from, what context surrounds them, and what they can and cannot establish.

Public evidence application

Published findings expose the source path, reasoning boundary, evidentiary limits, and correction path rather than asking readers to trust the creator.

Reusable governance model

Subjects may change. Source hierarchy, chronology controls, classification rules, correction standards, and public-access commitments do not.

BOUNDARIES

What it is not.

Record, Not Rumor is not a crowdsourcing platform. Future public submissions may provide leads or source material, but popularity, volume, voting, follower count, community consensus, or repeated submission never determines evidentiary weight or a published conclusion.

It is not a true-crime publication. A criminal case may be the subject of a bounded record; sensationalism is not the editorial model.

It is not a no-code or template publication. The current production application is custom-built and maintained as source-controlled software with automated verification and deployment controls.

It is not a paid truth layer. Published evidence audits, source methodology, record matrices, and material corrections are not placed behind a reader paywall.

No paywall
No voting
No crowd verdicts
No purchased truth
FUTURE SOURCE INTAKE

Where did you get this?

That question comes before: “What does it say?”

  1. Identify the submitted artifact. State whether it is a court record, transcript, exhibit, news article, screenshot, social post, video, audio recording, database entry, correspondence, or another source class.
  2. Identify the origin. Provide the original URL, publisher or issuing body, author or speaker when known, publication or filing date, and enough information to retrieve the source independently.
  3. Trace screenshots and excerpts backward. A screenshot of text is treated as a lead until the underlying article, filing, transcript, recording, or other origin can be located and its context checked.
  4. Evaluate the source itself. Determine whether it is primary, official, authenticated, contemporaneous, expert evidence, attributed reporting, argument, allegation, commentary, or an unresolved artifact.
  5. Follow its citations. When an article or secondary source cites a filing, study, transcript, exhibit, interview, dataset, or other record, the review continues to that underlying source whenever reasonably available.
  6. Preserve context. Read or watch enough surrounding material to prevent a cropped quotation, attorney question, headline, edit, or screenshot from silently becoming the meaning of the complete source.
  7. Cross-check independently. Test the proposition against chronology, other witnesses, records, physical or digital evidence, explicit source limitations, and material evidence that could disprove the working conclusion.
  8. Classify and expose the limit. Publish what is supported, what is contradicted, what is inference, what remains unknown, and what evidence would be required to change the finding.
Screenshot ruleA screenshot with no identifiable source may be preserved as an investigative lead. It does not alter a finding until its origin and context can be traced well enough to evaluate. If the origin cannot be established, that limitation remains visible.
Submission ruleSubmitting material does not make it evidence. The identity or number of submitters does not determine the result; the provenance and evidentiary quality of the source do.
CLASSIFICATION STANDARD

What is true? What is false? What is still unknown?

TRUE / SUPPORTED BY THE RECORD

The reviewed record establishes the proposition within the stated source boundary.

FALSE / CONTRADICTED BY THE RECORD

Reliable source material directly contradicts the proposition as circulated.

PARTLY TRUE / MIXED

Material components are supported while other components are false, unsupported, or unresolved. Each component is identified separately.

MISLEADING / OVERSTATED

The source supports a narrower statement than the public claim, or a real fact has been combined with an inference that the source cannot establish.

NO EVIDENCE FOUND IN THE REVIEWED RECORD

No authenticated or otherwise properly supported source reviewed within the stated boundary establishes the proposition. This is not a claim of omniscience.

UNRESOLVED

The available evidence cannot responsibly determine the proposition. Uncertainty is preserved rather than converted into a verdict.

Component ruleA single claim may contain a proven fact, a false attribution, an unsupported motive, and an unresolved detail at the same time. The system separates those components instead of forcing the entire claim into an artificial binary.
CORRECTION CONTROL

A better source can change the finding.

If authenticated or materially stronger evidence supports, contradicts, or narrows a published conclusion, Record, Not Rumor will revise the classification and explain what changed and why.

The creator is not the evidentiary source. The creator designs and applies the review standard. A finding must therefore be capable of surviving a challenge from a better source—and capable of changing when it does not.

Challenge standardA published finding may be challenged by supplying the exact source, enough provenance to authenticate or evaluate it, and the full context necessary to test the proposition.
PUBLIC TECHNICAL RECORD

Custom software. Reviewable controls.

The purpose of this disclosure is verifiability—not exposure of protected implementation details.

Application layerCustom React application with a Vite production build and purpose-built source, record, claim, chronology, and classification structures.
Machine-readable publicationCanonical URLs, route-level static metadata, structured data, sitemap discovery, and JavaScript-independent summaries support indexing and research access.
Durable source controlProduction development is checkpointed in an owner-controlled private Git source repository rather than relying on a temporary workspace as canonical storage.
Dependency controlDirect production dependencies are exactly pinned at verified checkpoints and subjected to automated dependency auditing.
Build verificationRepository automation performs clean dependency installation and production builds before changes are accepted.
Browser verificationAutomated Chromium interaction tests exercise critical mobile and desktop behaviors against the built application.
Preview before productionGit branches create isolated Vercel Preview deployments so changes can be reviewed without moving the production aliases.
Git-driven productionVerified main-branch merges trigger production deployment, with prior known-good deployments retained as rollback candidates where supported.
SECURITY BOUNDARY

Transparency is not an operator manual.

Public governance describes controls and guarantees without publishing credentials, environment variables, private repository locations, internal project identifiers, security tokens, unpublished source locations, or other operational details that would create unnecessary attack surface.

  • The public intake form remains disabled until private delivery, spam controls, retention boundaries, and abuse handling are verified.
  • Public evidence access does not require exposing protected source code.
  • Security controls are proportional to the current public/static attack surface and are revised when the architecture changes.
PUBLIC ACCESS COMMITMENT

Source truth is not a premium feature.

Record, Not Rumor does not charge readers for access to its published evidentiary audits, record matrices, source methodology, or material corrections. Evidence quality is not determined by purchasing power, membership, or subscriber status.

Future professional services associated with the creator are separate from this public evidence project and do not alter the evidentiary standard or public-access rule.