1
3-8 minutes · understand only
Read the fuller explanation
Use the public explainer if you want the design, boundaries, human and Agent views, and current Alpha capability in one document.
Open the public explainerA guided first look at Fireseed Alpha.5
Understand OrgAnchor before you try it.
OrgAnchor gives an organization a signed, recheckable way to connect who it is, where its official presence is now, what it claims, what evidence it exposes, and how those records change over time.
About three minutes
No installation
No public adoption
The problem is not a lack of information. It is a lack of a shared verification path.
Organizations already publish websites, product pages, reports, certificates, repositories, platform accounts, and public statements. These materials are often scattered across different carriers, change over time, and do not automatically explain how one record relates to another.
When a person or AI agent evaluates an organization, the same foundational questions must therefore be reconstructed repeatedly:
- Is this still the same organization?
- Where is its current official presence?
- Which claims are actually being made?
- What evidence supports each claim?
- What changed, expired, or remains disputed?
- What should be checked next?
OrgAnchor supplies a common signed structure for those questions. Its goal is to reduce repeated discovery, verification, interpretation, and comparison work. It does not replace websites, platforms, certification bodies, or the evaluator's own judgment.
One concrete working example
OrgAnchor uses itself as its first public test subject. The chain below is live now; it is not a mock-up.
1
Known website
A reviewer begins at organchor.org.
2
Standard signal
The website exposes /.well-known/organchor.json.
3
Signed package
The signal leads to identity, official-presence, claim, evidence, and receipt records.
4
Mechanical checks
Tools check signatures, hashes, root authority, relationships, freshness signals, and gaps.
5
External decision
The reviewer decides whether the verified material is sufficient for a particular purpose.
What this example can and cannot tell you
It can establish
- which root authority signed the current records;
- which official locations the organization declared;
- whether signed files, hashes, and declared links verify;
- which claims and evidence summaries are present;
- which gaps, stale signals, limits, and next checks are visible.
It cannot establish by itself
- that the organization is good, safe, lawful, or suitable;
- that every product or service claim is true;
- that the available evidence is sufficient for your purpose;
- that this candidate is the best commercial choice;
- that a valid package should be treated as a trust badge.
Continue only as far as useful
There is no single required adoption path. Choose the smallest step that answers your question, and stop whenever the next step is not worth the cost.
2
5-10 minutes · inspect facts
Examine the live self-pilot
See what is signed, what evidence is present, what is missing, and which checks still depend on external policy.
Open the public verify page3
About 15 minutes · reproduce
Run the public verification
Use three commands without checking out the source, then report one failure, confusing result, hidden gap, or unnecessary step.
Open the 15-minute check4
By agreement · private first
Request an assisted local-only trial
Use fictional, public, or approved organization material in a private workspace. Nothing is published without explicit approval.
Ask about a non-public pilotWhat a non-public trial means
A trial is an evaluation of the workflow, not a commitment to adopt OrgAnchor and not a request for confidential material by email.
You choose the material
Use fictional information, already-public records, or real material explicitly approved for the trial.
We prepare the local package
OrgAnchor assists with the workspace, custody plan, generated preview, verification, and friction record.
You control publication
The organization may stop locally. Public release happens only after it approves the wording, evidence, keys, and 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.