Signed continuity
A root authority signs official endpoint statements, claims, evidence manifests, lockfiles, and future migration records.
Fireseed Alpha.5 is open for external validation
Verifiable organization continuity for people and AI agents.
OrgAnchor helps organizations publish signed identity, official-presence, claims, evidence, and migration records so others can discover, verify, understand, and compare them at lower transaction cost.
Why this exists
Organizations usually present themselves through domains, websites, platform accounts, cloud services, certificates, reports, product pages, media, and public claims. Those carriers are useful, but they are scattered and can change over time.
Without a shared verifiable structure, people and AI agents must repeatedly answer basic questions: is this the same organization, where is its current official presence, what does it claim, what evidence supports it, what changed, what is missing, and what should be checked next?
OrgAnchor turns those questions into signed, inspectable, migratable public artifacts. The goal is lower discovery, verification, understanding, comparison, and next-action cost.
A convincing present is cheap. A verifiable past is harder to fabricate.
AI can quickly assemble a polished current website, report, or organization profile. It is much harder to backfill a long history that was already published at multiple real moments, signed by the relevant authority, externally time-anchored, and kept consistent with evidence, corrections, migrations, and surviving outside observations.
1
Publish a signed state
Identity, official presence, claims, evidence, and current limits are bound to an authority.
2
Anchor the moment
Receipts, archives, and external timestamp proofs distinguish witnessed publication from a date declared later.
3
Append change
Updates, corrections, withdrawals, and migrations point back instead of silently replacing the only visible copy.
4
Inspect across time
People and AI agents can review what changed, what stayed consistent, and where gaps or contradictions remain.
Boundary: history length is not a trust score. Older records are not automatically true, and newer organizations are not presumed untrustworthy. Time becomes one more inspectable evidence dimension.
The core model
Public verification package
The verify package exposes human-readable status and stable machine-readable artifacts under predictable URLs.
External judgment
OrgAnchor verifies structure, signatures, hashes, declared relationships, and gaps. It does not decide whether a claim is true enough for your purpose.
How an AI agent should use it
1
Find the signal
Read /.well-known/organchor.json from a candidate organization.
2
Verify the package
Check signatures, hashes, root authority, and statement continuity.
3
Inspect evidence
Read claims, evidence, manual checks, risk gaps, and next actions.
4
Apply policy
Use external purpose-specific policy to decide whether to proceed.
npm install organchor@alpha organchor doctor https://organchor.org organchor verify url https://organchor.org --compact
Alpha boundary
OrgAnchor Alpha.5 is ready for external validation, not production trust delegation. Its current minimum evidence baseline covers S1-S3. S4 is partial, and S5 remains later-stage design work.
Do not treat an OrgAnchor PASS result as evidence sufficiency, claim truth, certification, endorsement, ranking, or a final trust decision. Treat it as a verified input for your own policy.
Start as small as you need
You do not need to adopt OrgAnchor publicly. Use the guided first-look page to understand the model, then begin with a short verification check, continue into a local-only sandbox if it is useful, and publish a real pilot only after your organization approves it.
15-minute public check
Verify the current OrgAnchor package and report one failed command, confusing status, hidden gap, or unnecessary step.
Local-only assisted trial
Use fictional or real organization material in a private workspace. There is no obligation to publish, and the organization retains control of its keys and evidence.
Public pilot by consent
Publish a real verify package only after the organization approves its wording, custody plan, evidence, and public artifacts.
Never send private keys, recovery codes, provider tokens, wallet files, customer-private data, or confidential evidence. Participation is not certification, endorsement, ranking, or a final trust decision.
Review paths
For implementers
Install the CLI, run verification against this site, and inspect the public artifacts.
For AI agent builders
Start from the Beacon, consume the compact result, then decide what additional policy checks your agent needs.
For public reviewers
Use the visible verify page to check what is signed, what is present, and what gaps remain.