OrgAnchor

How to Read This Page

This page has two audiences: people who need a visible review path, and machines that need stable artifacts to verify. Use this order before relying on the organization.

1. 1. Check identity first

   If identity checks fail, stop. Evidence and carrier mirrors are not meaningful until the signed statement verifies against the expected root authority.

2. 2. Review evidence state

   Value and evidence status show what support is present, what is missing, and what still needs external review.

3. 3. Apply external policy

   OrgAnchor does not certify quality, safety, legality, or suitability. The requesting person, organization, directory, or agent applies its own policy.

4. 4. Re-check with tools

   Machines should start from /.well-known/organchor.json or organchor.json, then run organchor verify url <origin> --compact.

Reliance Guardrails

These guardrails prevent a visible page from being mistaken for endorsement. They are intentionally shown before the detailed proof trail.

Visible Proof Trail

These checks were performed when this static verification package was generated. They are recorded here so humans can see what happened, and in organchor.json so machines can inspect the same evidence.

Agent Verification View

This is the human-readable version of the same machine-readable verification package. It shows what an AI agent can cheaply learn first, before making any external policy or transaction decision.

Key Terms

Short explanations for human review. The machine-readable protocol still uses stable JSON keys, status codes, and policy route codes.

Root authority

The organization's authority record for OrgAnchor verification. It lists the root member keys and signature threshold used to verify current statements.

Statement

The signed official endpoint declaration. It says which website, verify page, security contact, and related public entry points currently belong to the organization.

Signature threshold

How many authorized root-member signatures are required before a statement is accepted as valid.

Agent Verification View

A human-readable version of the same first-pass state that AI agents read from organchor.json.

Overall status

A summary of identity, evidence, and conformance checks. It is not an endorsement of the organization.

Identity status

Whether the signed statement, hashes, signatures, and root authority checks passed.

Value status

Whether the signed claims and evidence package is present and whether obvious evidence gaps were found.

Conformance

How completely this package matches the OrgAnchor verification contract expected by tools and AI agents.

Trust decision

The final reliance decision. OrgAnchor does not assign it; the requesting person, organization, directory, or AI agent applies its own policy.

External Policy Route

A machine-readable hint telling external agents whether to stop, review warnings, request more evidence, or continue with their own policy.

S1 First-party

Evidence submitted by the organization itself. Useful for scope and integrity, but not independent by itself.

S2 Third-party

Third-party-looking material such as certification or lab reports, preferably with a recheck route and clear scope.

S3 Sampling

Evidence from random purchase, random sampling, or real market/customer-site sample checks, designed to reduce hand-picked sample risk.

S4 Observation

Real-world use, delivery, support, uptime, repair, or supply-continuity observation over time. In Fireseed Alpha this is design preview.

S5 Challenge

Public challenge, negative evidence, correction, dispute lifecycle, and historical accountability. In Fireseed Alpha this is design preview.

Carrier receipts

Records showing where artifacts were mirrored, archived, pinned, or timestamped. Carriers help durability, but they are not the identity root.

Lockfile

A publication ledger for carrier receipts and artifact hashes. When signed by the root authority, it becomes a tamper-evident snapshot of publication history.

Identity Artifacts

Statement hash

sha256:5811e45488c093e8820b35edf144a8dbae0c20a79063a44993043bfdf26a0a36

Root authority hash

sha256:7d720aa028e4b3b94d47b8e8789b0d7f5c8bb0564e80fac7f0ad7b275718e1b9

Signature hash

sha256:ad353bd72e7b1fa4137ec609a85d06bfaa0ce7564ef1e3fd4581defba9c4a532

Statement id

organchor-statement-2026-001

Issued at

2026-05-12T02:50:03.094Z

Generated at

2026-07-06T03:10:26.918Z

Value Continuity

This section summarizes the organization's signed claims and evidence trail. It does not prove the organization is good or that every claim is true; it helps people and AI agents see how much support the claims currently have.

Report JSON

reports/value-continuity-report.json
sha256:ea8a9921342a88ff43c2fac262c96cb97852e0067afed46cce706dd163d8c764

Report Markdown

reports/value-continuity-report.md
sha256:c84a066996d90cee2f42a2d2737de3371cc772510963d1be3d52d1fc93d0e7c2

Carrier Receipts

These receipts summarize where this verification package or related proof artifacts were mirrored, archived, pinned, or timestamped. Carriers help discovery and durability; they are not the identity root.

Lockfile Integrity

The lockfile is the publication receipt ledger. A signed lockfile snapshot makes receipt history tamper-evident: changing a receipt, timestamp, CID, TX id, or artifact hash changes the lockfile hash and breaks the signature check.

SIGNED

Lockfile

organchor.lock.json
sha256:f67473676a29ccd17008a22a46e94047d6b8b66a85f8c4fe35309e8aab92b471

Lockfile signature

organchor.lock.json.sig
sha256:5731f5d96076c3f2c0d145f3eeb1900056514173957a51534b094f5e5b64f75b

Root signatures

2 of 2

Root Continuity

The current root authority is the root that verifies new statements in this package. Older statements remain historical records and must be checked against the root authority that signed them.

Current root authority

root-authority-2026
sha256:7d720aa028e4b3b94d47b8e8789b0d7f5c8bb0564e80fac7f0ad7b275718e1b9

Current threshold

2 of 3

Migration status

No migration chain is included. Current statements use the current root authority directly.

Historical statements

Historical statements use the root authority that signed them.

Future statements

New statements should be verified against the current root authority unless a later valid migration supersedes it.

Official Endpoints

Root Authority

Authority id

root-authority-2026

Threshold

2 of 3

Signatures

Machine-Readable Files

• organchor.json
• root-authority.json
• official-endpoints.json
• official-endpoints.json.sig
• organchor.lock.json
• organchor.lock.json.sig

Claims And Evidence

• Product Claims Manifest
  sha256:9d27f1b5f19debde55b6550bbc1d9fc8fcaa3a71e4feb33010eaaf742168d771
  claims/product-claims.json.sig
  sha256:3838f37e7c5fd38a65f31324763890b12462440783a2ec2eb5d15dc308e03005
• Evidence Manifest
  sha256:98e09592668e63f03ce3f262f613242988b458fc2abd82bf573492a21971768b
  evidence/evidence-manifest.json.sig
  sha256:abefc12b3ff21a94c1af274df385895f87273d11fa76fa493665f2c23164d3cc

CLI Verification

organchor statement verify \
  --authority root-authority.json \
  --expected-authority-hash sha256:7d720aa028e4b3b94d47b8e8789b0d7f5c8bb0564e80fac7f0ad7b275718e1b9 \
  --in official-endpoints.json \
  --sig official-endpoints.json.sig

organchor lockfile verify \
  --authority root-authority.json \
  --expected-authority-hash sha256:7d720aa028e4b3b94d47b8e8789b0d7f5c8bb0564e80fac7f0ad7b275718e1b9 \
  --in organchor.lock.json \
  --sig organchor.lock.json.sig