KERI.host is a non-profit, reference-grade “ecosystem foundry” for KERI-native economies. It is not a SaaS provider, wallet company, or workflow engine. It is an open, forkable reference implementation — a pattern library for building economies, communities, and governance structures on cryptographic accountability instead of centralized control.
The primary audience is community organizers and entrepreneurs (economy builders). Developers are the supporting cast. The initial phase is narrative-first, no code — building shared understanding before shared infrastructure.
“You are not selling technology. You are teaching people how to organize. KERI simply becomes the inevitable tool once they try.”
These constraints govern every artifact produced:
| # | Constraint | Meaning |
|---|---|---|
| 1 | Reference > Platform | Forkable, self-hostable, documented as patterns. If KERI.host disappears, nothing breaks. |
| 2 | Optional Hosting, Never Required | Every demo must be runnable without KERI.host infrastructure. |
| 3 | Simulated but Real | Demos are flight simulators — legally plausible, structurally identical to production, swappable for real endpoints. |
| 4 | Subjective, Plural Reputation | No universal score. Reputation is contextual, community-defined, algorithmically diverse. |
| 5 | Regulator-Friendly Framing | Show audit trails, evidence, accountability, reduced compliance cost — without surveillance. |
| 6 | Cooperation, Not Competition | Non-profit, cost-covering, no ecosystem wars, no official endorsements. |
Type: Essay (1–2 pages) Working Title: “Building Communities Without Gatekeepers” Purpose: The north star document. Sets tone, philosophy, and intent for everything that follows.
Contents:
Voice: Human-first, anti-hype, grounded, quietly radical. No crypto vocabulary. No jargon unless it earns its keep.
Type: Single page / reference document Purpose: Prevent confusion and build trust fast by explicitly stating what KERI.host is not.
Contents:
Type: Reference document Purpose: Identify and design against the failure modes that would corrupt the mission.
Sections:
Type: Glossary / concept reference Purpose: Define the recurring patterns in plain language so all subsequent artifacts use consistent terminology.
Key Patterns to Define:
These five sections form the narrative backbone of KERI.host’s public content. Every subsequent artifact slots into one of these sections.
Type: Essay series (3–4 pieces) Purpose: Describe problems the audience already feels — before mentioning KERI at all.
Candidate Essays:
Rule: No KERI mentioned yet. These should feel uncomfortably familiar to the reader.
Type: Essay series (3–4 pieces) Purpose: Introduce patterns, not technology. Social architecture concepts.
Concepts to Introduce:
Rule: Still no deep KERI terms. This is about how humans can organize differently.
Type: Narrative walkthroughs (9 total, start with 3 flagship) Purpose: The heart of the content. Each story follows a consistent template so readers see themselves in the narrative.
Story Template:
Only after the story lands: “This pattern is enabled by KERI.”
Priority Flagship Stories (Write First):
| # | Story | Proves |
|---|---|---|
| 7a | Homeschool network run by parents | Personal / small community |
| 7b | Small trades cooperative (concrete, welding) | Economic / blue collar |
| 7c | City permit office | Civic / institutional |
Remaining Ecosystem Stories (Write Later):
| # | Vertical | Key Themes |
|---|---|---|
| 7d | Universities | Credentials, delegated authority, cross-institution verification, revocation |
| 7e | Municipalities (full) | Permits, licenses, procurement, contractor reputation, anti-bribery |
| 7f | Auto Loans / Lending | Borrower AID, vehicle AID, loan-as-ACDC, AI payment agent, delegated repossession |
| 7g | KERI Commerce | Merchant AIDs, inventory credentials, proof-of-delivery, dispute resolution |
| 7h | Service Orgs (Red Cross, United Way) | Volunteer credentials, donation traceability, delegated field authority |
| 7i | Female-Led Community Orgs | Child safety credentials, event permissions, selective disclosure by default |
| 7j | Male-Led Orgs (Sports → National) | Team rosters, referee authority, anti-cheating, cross-league interop |
| 7k | Reputation & Credit | Legacy credit ingestion, native reputation graphs, bring-your-own-score |
Type: Essay / guide Purpose: Developers enter as enablers, not heroes. Position developers as “infrastructure gardeners, not platform owners.”
Framing:
Type: Positioning page Purpose: Very explicit, very humble description of what KERI.host provides.
Contents:
Type: Speculative narrative essays Purpose: Imagination scaffolding — not technical docs.
Candidate Essays:
Type: Explainer essay Working Title: “What if nobody owned the process?” Purpose: Make the strongest technical differentiator accessible to community builders.
Contents:
Type: Soft persuasion piece Working Title: “How Accountability Can Be Stronger Without Surveillance” Purpose: Quietly reassure cities, NGOs, auditors, and risk-averse partners.
Key Narrative: “Here’s how a municipal auditor could reconstruct an entire procurement process without asking permission, without special access, and without anyone knowing they looked.”
Type: Technical reference / architecture overview Purpose: Document the three-layer infrastructure that everything hangs on.
Layer 1 — KERI Primitives:
Layer 2 — Interaction Primitives:
Layer 3 — Meaning:
Key Insight: This quietly replaces OAuth, SAML, IDPs, workflow engines, and most integration platforms.
Type: Architecture pattern document Purpose: Deep dive into the “no central workflow engine” pattern with concrete flow diagrams.
Demonstrates:
Type: Design specification Purpose: Define how AI agents operate as delegated KERI participants.
Contents:
Type: Case study collection Purpose: Show where KERI becomes unavoidable — corruption detection.
Corruption Scenarios:
KERI-Native Detection Mechanisms:
For each scenario, show: How corruption becomes detectable, how honest actors are protected, how blame is precise (not collective).
Type: Detailed specification per demo vertical Purpose: Structurally identical to production — flight simulators, not PowerPoints.
| Demo | Focus |
|---|---|
| Municipality | Permits + procurement |
| Trades / Blue Collar | Certs + jobs |
| University | Credentials |
| Service Org | Volunteers |
| KERI Commerce | Merchant flows |
Each demo spec includes:
Type: Design document Purpose: Specify how subjective, plural reputation works in practice.
Contents:
Type: Framework specification Purpose: Define patterns for AI agents with delegated AIDs operating across ecosystems.
Contents:
Type: Comprehensive guide Purpose: Enable others to replicate without permission.
Contents:
Type: Information architecture / wireframe document Purpose: Design the public face of KERI.host as a narrative hub.
Suggested Structure:
| Priority | Artifact | Phase | Type |
|---|---|---|---|
| 🔴 1 | Manifesto | 0 | Essay |
| 🔴 2 | “What We Don’t Do” Page | 0 | Reference |
| 🔴 3 | 3 Flagship Ecosystem Stories | 0 | Narratives |
| 🔴 4 | “No Central Workflow” Explainer | 0 | Essay |
| 🟡 5 | Regulator Narrative | 0 | Essay |
| 🟡 6 | Threat Model Document | 0 | Reference |
| 🟡 7 | Pattern Vocabulary | 0 | Glossary |
| 🟡 8 | Section A Problem Essays | 0 | Essay series |
| 🟡 9 | Section B Pattern Essays | 0 | Essay series |
| 🟡 10 | “What If KERI Wins?” Series | 0 | Essays |
| 🟢 11 | Architecture Document | 1 | Technical |
| 🟢 12 | Cross-Org Workflow Pattern | 1 | Technical |
| 🟢 13 | AI Actor Specification | 1 | Technical |
| 🟢 14 | Anti-Corruption Case Studies | 1 | Case studies |
| 🔵 15 | 5 Deep Demo Specs | 2 | Specifications |
| 🔵 16 | Remaining 8 Ecosystem Stories | 2 | Narratives |
| 🟣 17 | Reputation Marketplace Design | 3 | Design doc |
| 🟣 18 | AI Delegation Framework | 3 | Framework |
| ⚪ 19 | “Start Your Own” Guide | 4 | Guide |
| ⚪ 20 | Homepage Structure | 0–1 | IA / Wireframe |
| ⚪ 21 | Builder Narrative (Section D) | 1 | Essay |
| ⚪ 22 | Positioning Page (Section E) | 0–1 | Reference |
Legend: 🔴 Write First (30–60 days) · 🟡 Write Next (60–90 days) · 🟢 Phase 1 · 🔵 Phase 2 · 🟣 Phase 3 · ⚪ Ongoing/Flexible
Phase 0–1: Option A — Operate informally as a personal project with a public mission. Publish a manifesto, transparency statement, and “future non-profit intent” note. Cost: $0.
Phase 2: Option B — Incorporate as a 501(c)(3) non-profit. State filing ($50–200) + IRS Form 1023-EZ (~$275). Total: ~$300–1,200. Done 100% online in 2–6 weeks.