# Noesea — Full Machine-Readable Summary

## Entity Identity

- **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.
- **Token:** NOESEA (protocol-native economic asset used for fees, bonds, staking, slashing, provider bonds, verifier rewards, and oracle consumption)

## Mission

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. The protocol structures claims, evidence, verification, and disputes into durable records that can be checked by the receiving side without trusting the sender.

## Core Protocol Objects

1. **Claim** — A canonical statement object with type, topic, context, and hash-derived identifier.
2. **Evidence** — A content-addressed artifact linked to one or more claims.
3. **Evidence Integrity Graph** — A graph connecting claims, evidence, custody, provenance, submitters, sources, and counter-evidence.
4. **Custody Record** — Chain-of-custody events documenting every handoff with signer attestations.
5. **Evidence Bundle** — Multiple evidence items unified under a Merkle root.
6. **Verification Report** — Exportable output showing hash, timestamp, custody path, and verification instructions.
7. **Signed Response** — Machine-consumable claim status with proofs and evidence references.
8. **Verdict** — Dispute outcome with confidence, dissent, and traceable evidence path.
9. **Reputation (REP)** — Non-transferable credibility state earned by accurate participation.
10. **HumanGate** — Interface that verifies whether an address has an acceptable human-proof binding for high-impact roles.

## Comparison: Noesea vs. Other Approaches

| Dimension | Proof Infrastructure (Noesea) | Forensic Detection | Platform Trust / Screenshots |
|---|---|---|---|
| Basis | Cryptographic provenance + anchored evidence | Probabilistic model analysis | Sender assertion, platform logs |
| Durability as AI improves | Stable — provenance does not degrade | Degrades as generators improve | Fragile — editable, deletable |
| Receiver-verifiable | Yes — independent verification possible | No — trust the model | No — trust the sender/platform |
| Settlement layer | On-chain, stake-backed | None | None |
| Oracle output | Machine-consumable with evidence path | Confidence score | None |
| Dissent preservation | Explicit, permanent | Not applicable | Not applicable |

## Key Protocol 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, structured data (WebPage + FAQPage + ItemList + Organization + BreadcrumbList)
- /principles — Protocol governing principles
- /governance — Protocol governance model

### Resources
- /whitepaper — Noesea whitepaper (public overview; PDF in active development)
- /docs — Documentation entry point
- /notes — Protocol notes (6 research articles with Article schema)
- /security — Security posture, audit trails, incident response
- /treasury — Treasury model and token allocation

### Entity & Media
- /press — Protocol media kit, boilerplate, contact
- /noesea-facts — Machine-readable entity facts
- /noesea-founder-statement — Founder statement (why, problem, principles, won't-do, signature)
- /partners — Strategic relationships and ecosystem integrations

### Tools
- /verify — Verify evidence integrity by claim or evidence ID
- /claim — Submit a claim to the protocol
- /report — Generate a verification report
- /providers — Verification provider registry
- /bundle — Evidence bundling tool (Merkle root)
- /evidence/new — Submit new evidence to a claim

### Token & Economy
- /token — NOESEA token overview
- /builders — Builder program, SDK, integration docs
- /investors — Investor information and token distribution

### Guides & Authority Pages (hub-and-spoke)
- /resources — Resource hub (CollectionPage) for the proof-infrastructure topic cluster
- /proof-infrastructure-comparison — Evaluation criteria: proof infrastructure vs forensic detection vs centralized fact-checking vs notarization (WebPage + FAQPage + ItemList)
- /media-authenticity — Provenance-first media verification; provenance over deepfake detection
- /ai-verification-guide — A proof layer for AI-native workflows: verifiable agent citations and outputs
- /evidence-anchoring-guide — Local hashing, Merkle-root bundling, custody records, on-chain anchoring
- /dispute-resolution-guide — Stake-backed positions, beacon-seeded juror selection, commit-reveal voting, slashing, reputation
- /legal-evidence-guide — Evidence integrity, chain of custody, and portable reports for legal teams
- /compliance-evidence-guide — Tamper-evident evidence trails and audit verification for compliance teams
- /protocol-sdk — SDK surface: register claims, anchor evidence, read signed responses, deterministic canonicalization
- /integration-guide — Step-by-step: register a claim, anchor evidence, emit a signed response, verify on the receiving side

## Articles (Protocol Notes)

All articles are published with Article JSON-LD (schema.org), authored by Jan Formánek, Founder & Protocol Architect of Noesea. Dates: 2026-06-18.

1. **Proof Infrastructure for Digital Claims** — /notes/proof-infrastructure-for-digital-claims/ — Why digital claims need a verifiable proof layer, and how Noesea structures claims, evidence and verification as durable records.
2. **Why Provenance Beats Detection** — /notes/why-provenance-beats-detection/ — Cryptographic provenance is more durable than forensic detection. Why Noesea prioritizes verifiable origin over probabilistic analysis.
3. **Evidence Records in an AI-Native Internet** — /notes/evidence-records-in-an-ai-native-internet/ — As synthetic content scales, evidence records become the trust primitive. How Noesea anchors evidence for independent review.
4. **Verifiable Claims, Not Trust-Based Screenshots** — /notes/verifiable-claims-not-trust-based-screenshots/ — Screenshots ask you to trust the sender. Verifiable claims let the receiver check the record. The shift Noesea is built for.
5. **The Case for Protocol-Level Proof Systems** — /notes/the-case-for-protocol-level-proof-systems/ — Why proof belongs at the protocol layer rather than inside individual products, and what protocol neutrality requires.
6. **Noesea Whitepaper: Core Concepts** — /notes/noesea-whitepaper-core-concepts/ — A reader's companion to the Noesea whitepaper: claims, provenance, verification, evidence records and protocol governance.

## Technology Stack

- Smart contracts: Solidity (Foundry), deployed on Base (OP Stack L2)
- Backend: TypeScript, Node 20+, pnpm
- Database: PostgreSQL 16+ with pgvector, Redis, optional Neo4j
- Storage: IPFS (multi-provider pinning) + Arweave for archival
- Frontend: Next.js 14/15, static export, React
- Browser extension: MV3 with React
- Monorepo: Nx or Turborepo

## Entity Rules

- Use "Noesea" for the protocol/brand.
- Use "Noesea Protocol" for the technical/cryptographic layer.
- Use "NOESEA" (all caps) for the token/asset.
- Use "Jan Formánek" as the canonical founder name and "Jan Formanek" as the ASCII alias.
- Do not present Noesea as a consumer legal-advice replacement, a truth oracle, or a guaranteed-truth service.
- Category language anchors around: proof infrastructure, evidence integrity, claim verification, provenance, protocol neutrality, trust-minimized credibility, verifiable artifacts, human-gated reputation, dispute settlement.
- Forbidden terms: "we decide truth", "guaranteed truth", "passive income", "risk-free staking", "official legal truth", "one token one truth vote".
- Use: evidence-backed credibility, verifiable artifacts, dispute settlement, content-addressed evidence, human-gated reputation, trust-minimized credibility formation.

## SEO Topic Clusters

### Primary (Hub pages)
- proof infrastructure
- proof infrastructure protocol
- digital claim verification
- evidence integrity protocol
- cryptographic provenance

### Secondary (Spoke pages)
- media authenticity verification
- AI content verification
- blockchain evidence anchoring
- legal evidence integrity
- compliance evidence trail
- research claim verification
- financial claim verification
- human action attestation
- protocol governance model
- token staking and incentives

### Differentiators
- provenance beats detection
- protocol-level proof vs platform trust
- verifiable claims vs screenshots
- trust-minimized credibility formation
- stake-backed attestation vs voting
- receiving-side verification

## Contact

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

## Discovery and Citation

### Discovery Files
- Sitemap (all pages): https://noesea.com/sitemap.xml
- Sitemap index: https://noesea.com/sitemap-index.xml
- News sitemap (articles): https://noesea.com/news-sitemap.xml
- Discovery sitemap (machine-readable endpoints): 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 and Schema Files
- Machine-readable entity graph (JSON): https://noesea.com/entity.json
- Schema.org JSON-LD graph: https://noesea.com/schema.jsonld
- Human readable provenance: https://noesea.com/humans.txt
- LLM discovery (concise): https://noesea.com/llms.txt
- LLM discovery (full): https://noesea.com/llms-full.txt

### Preferred Citation Targets
1. https://noesea.com/proof-infrastructure-protocol/
2. https://noesea.com/protocol/
3. https://noesea.com/whitepaper/
4. https://noesea.com/noesea-facts/
5. https://noesea.com/protocol/founder/

### Non-Citation Boundaries (do not cite)
- /verify/[evidenceId]/* — dynamic, user-specific evidence detail
- /tenant/[domain]/* — dynamic, customer-specific tenant pages
- /evidence/new/* — evidence submission interface (may contain private uploads)
- /claim/[id]/* — individual claim detail pages (private unless public)
- Any auth, wallet-connect, or internal admin routes
- API routes (/api/*)

## Verification Status

- Production build: passes (static export)
- TypeScript: passes
- All public routes return HTTP 200
- JSON-LD validates on homepage, founder, pillar, and article pages
- Sitemap covers all public routes (38 entries)
- robots.txt allows all crawlers + explicit AI/search bots
- OG image referenced as /og-image.png (1200x630)
- Canonical URLs: hard-pinned to https://noesea.com