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> --brief.

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:e2212fbecdb2f07a16821c87e6819adfbf920ea4d068cd6ede1294a6598d09a4

Root authority hash

sha256:8168cae0c29218f2bf847d96f45e9d9fd85ba6eee1e5c01ef6ff175b438e3d23

Signature hash

sha256:fab28124dae5e8c5a931b0a919bb3473749d5aff0eeac9e40fcb68e7091702a0

Statement id

organchor-statement-pq-2026-001

Issued at

2026-10-18T17:08:42.282Z

Generated at

2026-10-18T17:09:28.611Z

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:e70f18fe930553ed5ae3f7379480b0cd1564c146f1030aad23ba289fc0e25f61

Report Markdown

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

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:9d987e6135017531f6261dc7c345794c38fcd7f722f12b07eaa3b35b0a3b1d34

Root signatures

2 of 2

Human summary: 49 receipt(s) across 7 provider(s). The table shows only the latest receipt for each provider; the complete signed history remains in the lockfile for tools and AI agents.

Verifiable History Over Time

This page represents a signed organization state. When successive states are preserved with signed receipt history, external time anchors, correction or supersession links, and migration records, they can form a verifiable longitudinal record.

This does not make older records automatically true or make a newer organization less trustworthy. It gives reviewers another inspectable dimension: what was published at different verifiable moments, which authority signed it, what changed, and whether the visible history contains unexplained gaps or contradictions.

A date declared inside a signed file is not independent proof that the file existed on that date. Check the signed lockfile, carrier receipts, external timestamp proofs, preserved snapshots, and migration files before making a cross-time inference.

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

organchor-root-authority-hybrid-2026-001
sha256:8168cae0c29218f2bf847d96f45e9d9fd85ba6eee1e5c01ef6ff175b438e3d23

Current threshold

2 of 3

Migration status

1 migration statement(s) verified as a chain to the current root authority.

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.

Previous Root Authorities

Official Endpoints

Root Authority

Authority id

organchor-root-authority-hybrid-2026-001

Threshold

2 of 3

Signatures

Migration History

These migration statements link an older root authority to the current root authority shown on this page.

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:40803e71fab0df2cab80a77e4288ab8ebdf0d40746ea6bb833c37adeb5d4ac63
  claims/product-claims.json.sig
  sha256:8990e415582b9b18a4b2671e09149d43ab4dcbdf601f95f37e8b19615d1c9f85
• Evidence Manifest
  sha256:23f5d92da44618fbab761de321e3c06a4e7a625a9650958ba03f8af64e01bbc1
  evidence/evidence-manifest.json.sig
  sha256:74524eb6a16ef9195f6a278452e3cf336f20f4f6c199d7ffd017da5cab6ea47d

Migration Files

• migrations/migration-pq-2026-001.json
  sha256:b1c17b8013079f1392778ec26d4a3d1468d33d7f6f07b91e2a8fc6f064106224
  migrations/migration-pq-2026-001.json.sig
  sha256:3bb68ebbd1ef94ebe3d8558f1940448e24a501d070f97483076cd5f4487e9b09
  New authority acceptance
  sha256:b781aa6b690ec4beb9d678c78f156406286c5249a19392f122ba27d2c8a01af2

CLI Verification

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

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