Northstar Motion Components
Fictional manufacturer used only for the OrgAnchor evidence-interpretation evaluation.
This is an adopting organization OrgAnchor verification page. The page helps people and machines find signed verification artifacts.
This page display does not by itself prove identity. Trust comes from verifying the signed statement against the expected root authority.
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. 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. Review evidence state
Value and evidence status show what support is present, what is missing, and what still needs external review.
-
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. 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.
Identity checks passed when this package was generated. Re-run verification from the current origin before relying.
The claims/evidence package is present and no structural evidence-link gaps were found by the local value audit. This does not establish evidence sufficiency or claim truth.
OrgAnchor does not certify that this organization is good, safe, lawful, effective, or the best choice. It exposes verifiable materials for external judgment.
S4 real-use observation and S5 public challenge, correction, and historical accountability are not finished Fireseed acceptance gates. Do not treat them as mature governance systems yet.
IPFS, Arweave, OpenTimestamps, websites, and other carriers can improve durability and discovery, but they are not the identity root.
A lockfile snapshot is missing or unsigned. Treat carrier receipts as helpful metadata until a signed snapshot is published.
Use organchor.json for machine inspection and run organchor verify url <origin> --compact against the current public origin.
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.
| Check | Status | Detail |
|---|---|---|
| Official endpoint statement | PASS | Canonical hash recorded as sha256:bcf05755fadac013f5b032d10505703b986e9255bcbaef0966c921941ab43c5a. |
| Root authority binding | PASS | Statement root authority hash matches sha256:5f9cc31cd32f4c3727c45a5e2552fe0f3615eeb4bbc1606e0f587591e468741a. |
| Signature threshold | PASS | 1 valid signature(s) found; 1 required. |
| Signature file | PASS | Detached signature hash recorded as sha256:5486ec8aa272759ec51b57cbf931ccb56efae4dcfc1a480e1cfefb71d0d0f550. |
| Claims manifest | PASS | Signed claims manifest was included and verified against this root authority. |
| Evidence manifest | PASS | Signed evidence manifest was included and verified against this root authority. |
| Value continuity report | PRESENT | Value audit report included with 1 claim(s), 1 evidence-linked claim(s), and 0 unsupported claim(s). |
| Migration history | NOT_INCLUDED | No migration history is included in this verify package yet. |
| Carrier receipts | NOT_INCLUDED | No IPFS, Arweave, OpenTimestamps, or other carrier receipts were included. |
| Lockfile integrity | NOT_INCLUDED | No signed publication receipt ledger was included. |
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.
Evidence Classes
Organization-submitted evidence. Useful for scope and integrity, but not independent by itself.
Organization-submitted third-party material with mechanical route and gap checks.
Random purchase or sampling records. Current tooling checks declared gates; network slot ledgers are future work.
Real-use or delivery observation. Alpha support is partial and should be treated as a design-preview signal.
Public challenge, correction, negative evidence, and historical accountability governance is documented but not implemented as a finished acceptance gate.
External Policy Route
EXTERNAL_POLICY_REVIEW
Verification passed, but external policy still needs to decide whether the evidence is sufficient for the intended purpose.
Reasons: manual_checks_present
Next Checks
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:bcf05755fadac013f5b032d10505703b986e9255bcbaef0966c921941ab43c5a- Root authority hash
sha256:5f9cc31cd32f4c3727c45a5e2552fe0f3615eeb4bbc1606e0f587591e468741a- Signature hash
sha256:5486ec8aa272759ec51b57cbf931ccb56efae4dcfc1a480e1cfefb71d0d0f550- Statement id
- northstar-official-presence-2026-001
- Issued at
- 2026-07-16T17:48:56.056Z
- Generated at
- 2026-07-16T17:48:58.806Z
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:e5996fcb89a62545808b478a53e1ccf90c63a1fd9bd047de3bbe2dd104e36c39 - Report Markdown
- reports/value-continuity-report.md
sha256:ed60b1043e86e7d612c5f81323c6ed2ec76612c57f601e64f09547d8e4dabbf6
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.
NOT_INCLUDED
No lockfile snapshot was included in this verification package.
No carrier receipts were included in this verification package.
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
- northstar-root-authority-2026
sha256:5f9cc31cd32f4c3727c45a5e2552fe0f3615eeb4bbc1606e0f587591e468741a - Current threshold
- 1 of 1
- 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
| website | https://northstar-motion.example |
|---|---|
| verify | https://northstar-motion.example/verify |
| security | mailto:security@northstar-motion.example |
| documentation | https://northstar-motion.example/docs |
Root Authority
- Authority id
- northstar-root-authority-2026
- Threshold
- 1 of 1
| Key id | Algorithm |
|---|---|
| northstar-root-2026 | ed25519 |
Signatures
| Key id | Algorithm | Signed at |
|---|---|---|
| northstar-root-2026 | ed25519 | 2026-07-16T17:48:56.273Z |
Machine-Readable Files
Claims And Evidence
-
Product Claims Manifest
sha256:98a023ea4502937d257c802b6db9877226a4e6fe091f0862b1986bb8eb540145
claims/product-claims.json.sigsha256:bb319fb3db16cd4be5f35386268fc1fe856bd2d7119a36e28ecb0c5d8dc17e74 -
Evidence Manifest
sha256:53a578a8eba28cba0d38a8cd9765f2e741c356affbb9a27bbbb11c66cd25205e
evidence/evidence-manifest.json.sigsha256:33d931e4d9293fb4b9a20d864ab6a8bbc4064325ea3dcad5d38e8ec332f041de
CLI Verification
organchor statement verify \
--authority root-authority.json \
--expected-authority-hash sha256:5f9cc31cd32f4c3727c45a5e2552fe0f3615eeb4bbc1606e0f587591e468741a \
--in official-endpoints.json \
--sig official-endpoints.json.sig