One primitive, specific product lanes
Meridian Platform
The shared primitive
Meridian is not a pile of use cases. It is one trust record used by different identities. Every product lane writes to the same evidence-linked ledger.
Identity
Person, creator, AI agent, company, team, or institution.
Record
Claim, prediction, promise, approval, action, or resolution.
Evidence
Source URL, document, official result, API event, or audit note.
Outcome
Open, resolved, disputed, void, correct, incorrect, or harmful.
Reputation
Score, confidence, calibration, domain record, and history.
General people
Prove what they said before reality arrived.
Product
Public proof records, World Cup records, Trust Profile.
Business model
Free consumer surface.
Creators and analysts
Turn public judgment into credibility.
Product
Shareable proof records, profile history, domain accuracy, calibration.
Business model
Pro subscriptions and audience trust tools.
Companies
Make forecasts, product claims, and public commitments auditable.
Product
Verified org profiles, claim registry, evidence archive, audit exports.
Business model
Enterprise seats and compliance plans.
AI agents
Log high-impact actions with permissions, approvals, and outcomes.
Product
Agent action ledger, approval trail, failure history, trust score.
Business model
API usage and enterprise agent governance.
Institutions
Publish canonical outcomes and resolve disputed claims.
Product
Resolution authority, source registry, challenge workflow.
Business model
Verified institutional accounts.
Developers
Write trust records into Meridian from other products.
Product
API for claims, actions, approvals, evidence, outcomes, and trust profiles.
Business model
Usage-based API pricing.
| Step | What must happen |
|---|---|
| 1. Record | Create a timestamped proof record with identity, claim/action, confidence, deadline, and resolution standard. |
| 2. Attach evidence | Link primary sources, documents, APIs, approvals, or official records. |
| 3. Resolve | Record what happened with source, resolver, timestamp, and challenge window. |
| 4. Score | Update reputation only from resolved outcomes and preserve every change. |
| 5. Reuse | Trust Profile travels into profiles, APIs, enterprise dashboards, and public records. |
Industry expansion
Meridian should expand by reusing the same primitive in high-trust contexts, not by inventing a different product for every industry. The product changes workflow and permissions; the record layer stays consistent.
| Industry | Meridian value |
|---|---|
| Legal firms | Evidence timelines, claim history, challenge history, amendments, and exportable audit packs. |
| Financial services | Approval records, identity-adjacent evidence trails, AI action logs, and dispute-ready chronology. |
| Media | Source records, correction history, public claims, provenance posture, and challengeable reporting timelines. |
| Marketplaces | Buyer/seller commitments, delivery evidence, dispute records, and seller trust history. |
| Enterprise AI | Agent identity, authority scope, tool use, human owner, risk level, and outcome history. |
| Governments | Official statement records, resolution authority, amendment history, and public proof boundaries without social scoring. |
| Universities | Research claims, replication commitments, evidence archives, and domain-scoped credibility. |
| Developers | APIs, embeds, webhooks, and trust records written from other products. |