# Noesea — Proof Infrastructure Protocol

## Entity

- **Name:** Noesea
- **Alternate names:** Noesea Protocol
- **Type:** Proof infrastructure protocol
- **Founder & Protocol Architect:** Jan Formánek (also Jan Formanek)
- **Website:** https://noesea.com
- **Description:** Noesea is a proof infrastructure protocol for digital claims, provenance, verification and evidence records. It anchors hashes, stakes, outcomes and reputation on-chain — never raw content — so claims and evidence can be reviewed independently.

## What Noesea Does

Noesea builds public proof infrastructure for digital claims. When a claim matters, its evidence and review path should survive outside the original sender or platform.

Key capabilities:
- Claim registration with stable identity (content hash, type rules)
- Evidence hashing and anchoring (local hash, Merkle root, custody events)
- Provenance-first design (cryptographic origin over forensic detection)
- Verification outputs for independent review (browser checks, CLI, reports)
- Dispute settlement with stake-backed juror voting and reputation tracking
- Protocol governance with transparent parameter control

## Key Pages

### Protocol
- /protocol — Protocol overview and architecture
- /protocol/founder — Jan Formánek, Founder & Protocol Architect
- /proof-infrastructure-protocol — Pillar page: what proof infrastructure is, comparison table, FAQ
- /principles — Protocol governing principles
- /governance — Protocol governance model

### Resources
- /whitepaper — Noesea whitepaper (overview; PDF in development)
- /docs — Documentation entry point
- /notes — Protocol notes (research articles)
- /security — Security posture
- /treasury — Treasury model

### Entity & Media
- /press — Protocol media kit
- /noesea-facts — Machine-readable entity facts
- /noesea-founder-statement — Founder statement
- /partners — Strategic relationships

### Tools
- /verify — Verify evidence integrity
- /claim — Submit a claim
- /report — Generate a verification report
- /providers — Verification provider registry
- /bundle — Evidence bundling tool

### Token
- /token — NOESEA token overview
- /builders — Builder program
- /investors — Investor information

### Guides & Authority Pages
- /resources — Resource hub for the proof-infrastructure topic cluster
- /proof-infrastructure-comparison — Compare proof infrastructure vs detection, fact-checking, notarization
- /media-authenticity — Media provenance and authenticity verification
- /ai-verification-guide — Verifying AI-generated claims, citations and outputs
- /evidence-anchoring-guide — Hashing, Merkle roots and custody
- /dispute-resolution-guide — Stake-backed voting, juror selection, reputation
- /legal-evidence-guide — Evidence integrity for legal teams
- /compliance-evidence-guide — Compliance evidence trails and audit verification
- /protocol-sdk — Builder SDK surface
- /integration-guide — End-to-end integration path

## Articles (Protocol Notes)

1. /notes/proof-infrastructure-for-digital-claims
2. /notes/why-provenance-beats-detection
3. /notes/evidence-records-in-an-ai-native-internet
4. /notes/verifiable-claims-not-trust-based-screenshots
5. /notes/the-case-for-protocol-level-proof-systems
6. /notes/noesea-whitepaper-core-concepts

## Comparison

Noesea is a proof infrastructure protocol. It is not a forensic detection service, a centralized fact-checking operation, a legal SaaS product, or an editorial truth authority.

| Approach | Basis | Durability | Receiver-Verifiable |
|---|---|---|---|
| Proof infrastructure (Noesea) | Cryptographic provenance + anchored evidence | Stable — does not degrade as AI improves | Yes |
| Forensic detection | Probabilistic model analysis | Degrades as generators improve | No |
| Platform trust / screenshots | Sender assertion, exports | Fragile — editable, deletable | No |

## Citation Guidance

- Cite the protocol entity as "Noesea" or "Noesea Protocol".
- Cite the founder as "Jan Formánek, Founder & Protocol Architect of Noesea".
- Cite the token as "NOESEA" (all caps).
- Do not cite private auth, wallet-connect, evidence-upload detail pages, or API-backed dynamic routes.
- Preferred citation targets: /protocol, /proof-infrastructure-protocol, /whitepaper, /noesea-facts.

## Contact

- General: hello@noesea.com
- Investors: investors@noesea.com
- Security: security@noesea.com
- Legal: legal@noesea.com
- Partners: partners@noesea.com
- Treasury: treasury@noesea.com

## Discovery Files

- Sitemap: https://noesea.com/sitemap.xml
- Sitemap index: https://noesea.com/sitemap-index.xml
- News sitemap: https://noesea.com/news-sitemap.xml
- Discovery sitemap: https://noesea.com/discovery-sitemap.xml
- RSS feed: https://noesea.com/feed.xml
- Robots: https://noesea.com/robots.txt
- OpenSearch: https://noesea.com/opensearch.xml
- Entity graph (JSON): https://noesea.com/entity.json
- Schema.org graph: https://noesea.com/schema.jsonld
- Provenance: https://noesea.com/humans.txt
- Full LLM context: https://noesea.com/llms-full.txt

## Not Indexable (do not cite)

- Any /verify/[evidenceId] detail pages (dynamic, user-specific)
- Any /tenant/[domain] pages (dynamic, customer-specific)
- Any auth, wallet-connect, or internal admin routes