← Back to Evidence

How to Verify This Evidence

This page explains how to independently verify every claim made in the AOS Evidence Repository. We designed this repository to be trustless — you don't need to trust us, you can verify everything yourself.

Quick Start: 5 Minutes

  1. Clone the repo: git clone https://github.com/genesalvatore/aos-evidence.com
  2. Check timestamps: git log --format="%H %ai %s" -20
  3. Verify commit integrity: git fsck --full
  4. Read the evidence: Browse the documents in your local copy

What You Can Verify

1. Timeline Claims

What we claim: Key innovations were documented before industry announcements.

How to verify:

# See all commits with timestamps
git log --format="%H %ai %s"

# Verify a specific commit date
git show --format="%H%nAuthor Date: %ai%nCommit Date: %ci" <commit-hash>

# Check for any rebase or force-push (these would be visible)
git reflog

2. Document Integrity

What we claim: Documents have not been modified after initial publication.

How to verify:

# Show when a file was first committed
git log --follow --diff-filter=A -- <filename>

# Show all changes to a file
git log --follow -p -- <filename>

# Verify file hasn't changed since initial commit
git diff <first-commit>..<latest-commit> -- <filename>

3. Cross-Reference External Sources

What to check:

  • Industry announcements — Compare our commit dates to public announcements
  • Patent filings — Verify our provisional patent dates (filed January 10, 2026)
  • GitHub API — Use GitHub's API to independently verify push timestamps
  • Web archives — Check Wayback Machine for our public pages

4. Git Integrity Verification

Git provides built-in integrity checks:

# Full integrity check
git fsck --full --strict

# Verify object hashes
git verify-pack -v .git/objects/pack/*.idx

# Check for unsigned commits (we sign with GPG)
git log --show-signature

What We Cannot Fake

  1. Git commit timestamps — While author dates can be set manually, GitHub's push timestamps are server-side and cannot be manipulated
  2. GitHub push events — The GitHub Events API records when pushes happen, independently of commit dates
  3. Commit hash chains — Each commit hash includes the parent hash, creating a tamper-evident chain
  4. External references — Industry announcements, news articles, and third-party timestamps cannot be retroactively modified

Key Evidence Anchors

Canonical Anchor

Tag: evidence-2026-02-06

Commit: 9f4b0d9

This is the first complete evidence package. All documents present at this commit represent the baseline public record.

ChatGPT Audit Evidence

Initial: 8c685ee

Correction: aaffd3c

Path: EVIDENCE/chatgpt_security_audit_feb_5_2026/

12 documents, 9,323 insertions — the complete record of the world's first AI-to-AI security audit of constitutional governance.

Reporting Issues

If you find inconsistencies, please report:

Email: contact@aos-evidence.com
GitHub Issues: Open an issue
Public disclosure: Encouraged

We commit to:

  1. Acknowledge all valid critiques
  2. Correct errors publicly
  3. Update documents with corrections noted
  4. Never delete evidence (only append corrections)

Verification Checklist

  • Clone repository locally
  • Check Git commit timestamps
  • Verify timeline consistency across docs
  • Cross-reference industry announcements
  • Review technical claim plausibility
  • Check for Git history manipulation
  • Test reproducibility (when code available)
  • Search for external confirmations/denials
  • Compare claimed dates to public records
  • Archive for future reference

Time required: 1–2 hours for thorough verification

Remember: We designed this repository to BE verifiable.
If you can't verify our claims, we failed our mission.