Digital Karma Web Federation Architecture
A decentralized network of AI-native websites with transparent trust, bidirectional linking, and shared standards for machine interoperability.
What is a Web Federation?
A web federation is a network of independent websites that voluntarily connect through shared protocols and mutual trust relationships.
Key Characteristics
- Decentralized: No central authority controls the network
- Opt-in: Sites voluntarily join and can leave anytime
- Standardized: All members follow common protocols
- Transparent: Trust relationships are publicly visible
- Bidirectional: Links are mutual, not one-way
Think of it like:
- 📧 Email federation — Gmail and Outlook interoperate despite different providers
- 🐘 Mastodon/Fediverse — Independent servers that share posts/follows
- 🔗 Academic citations — Papers reference each other bidirectionally
Why Federation Matters
Problem: The Centralized Web
Today's web is dominated by centralized platforms:
- 🔒 Walled gardens: Content trapped in platforms (Medium, Substack, LinkedIn)
- ⚖️ Algorithmic control: Platforms decide what gets visibility
- 💰 Rent extraction: Platform fees reduce creator earnings
- 📊 Data ownership: Platforms control user data and relationships
- 🚫 Deplatforming risk: You can be banned without notice
Solution: Federated Networks
Federation restores control to individual site owners:
- ✅ Own your domain: You control the infrastructure
- ✅ Own your content: Files stored on your server
- ✅ Own your data: No platform intermediaries
- ✅ Own your relationships: Direct federation links
- ✅ Network effects: Benefit from federation without centralization
Architecture Overview
Network Topology
The Digital Karma Web Federation uses a mesh topology:
┌─────────┐ ┌─────────┐
│ Site A │◄───────►│ Site B │
└────┬────┘ └────┬────┘
│ │
│ ┌─────────┐ │
└───►│ Site C │◄───┘
└────┬────┘
│
┌────▼────┐
│ Site D │
└─────────┘
Each site maintains its own bidirectional links
No central hub or single point of failure
Network is resilient and self-organizing
Contrast with centralized:
┌─────────┐
│ Platform│ ← Single point of failure
└────┬────┘
│
┌────┼───────┐
│ │ │
┌───▼┐ ┌─▼──┐ ┌─▼──┐
│Site│ │Site│ │Site│ ← All traffic through platform
└────┘ └────┘ └────┘
Core Components
1. Federation Endpoints
Every federated site must implement 5 standard endpoints:
| Endpoint | Purpose | Update Frequency |
|---|---|---|
/ai/manifest.json |
Site identity, capabilities, federation version | On major changes |
/ai/health.json |
Site status, uptime, performance metrics | Every 5-15 minutes |
/ai/catalog.json |
Complete content inventory with metadata | On content updates |
/ai/karma.json |
Digital Karma Score and signal breakdown | Daily |
/ai/federation.json |
Network links to other federated sites | When links change |
2. Bidirectional Links
Federation links must be mutual to establish trust:
// Site A's federation.json
{
"federation_links": [
{
"site_url": "https://site-b.com",
"relationship": "partner",
"verified": true,
"added_date": "2026-01-15"
}
]
}
// Site B's federation.json
{
"federation_links": [
{
"site_url": "https://site-a.com",
"relationship": "partner",
"verified": true,
"added_date": "2026-01-15"
}
]
}
Verification process:
- Site A adds Site B to federation.json
- Site B verifies the link by checking Site A's federation.json
- Site B adds Site A to its federation.json
- Both sites mark the relationship as "verified"
- AI agents can now trust the bidirectional relationship
3. Digital Karma Scoring
Transparent quality assessment across 7 signals:
- Schema Coverage (20%): JSON-LD markup quality
- Content Freshness (15%): Update recency
- AI Endpoints (25%): Implementation completeness
- Federation Presence (15%): Network participation
- External Links (10%): Quality outbound links
- Technical Quality (10%): Performance and accessibility
- Dataset Quality (5%): Structured data completeness
4. Schema.org Vocabulary
Shared semantic language for entity types and relationships:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Site",
"memberOf": {
"@type": "Organization",
"name": "Digital Karma Web Federation",
"url": "https://www.aiwebsitesystems.com/federation-registry.html"
}
}
Trust Model
Decentralized Trust
Unlike centralized platforms where trust comes from the platform brand, federation trust is distributed and transparent.
Trust Factors
- Digital Karma Score (0-1.0)
- Objective signals computed by standard algorithm
- Published openly for verification
- Cannot be gamed without improving actual quality
- Bidirectional Links
- Both sites vouch for each other
- Verifiable by checking JSON files
- Creates accountability through mutual trust
- Network Position
- Sites linked from many high-karma sites gain trust
- PageRank-style trust propagation
- Long-standing members have established reputation
- Technical Quality
- Uptime percentage
- Response time metrics
- HTTPS and security practices
- API stability
- Content Freshness
- Recent updates signal active maintenance
- Stale sites lose trust over time
- Timestamp verification prevents backdating
Trust Propagation
Trust flows through the network like water:
Site A (karma: 0.95) ───links to───► Site B (karma: 0.82)
│
│ links to
▼
Site D (karma: 0.70) ◄───links to─── Site C (karma: 0.88)
Trust calculation for Site C:
- Own karma: 0.88 (strong)
- Linked from Site A: 0.95 (very strong) → +confidence
- Linked from Site B: 0.82 (strong) → +confidence
- Links to Site D: 0.70 (moderate) → neutral
Result: High trust (linked from multiple strong sources)
Anti-Spam Measures
How the federation prevents abuse:
- ✅ Bidirectional requirement: Can't claim partnership unilaterally
- ✅ Karma gating: Low-karma sites flagged in registry
- ✅ Link verification: AI agents check both directions
- ✅ Rate limiting: Can't add hundreds of links overnight
- ✅ Manual review: Registry maintains quality standards
Network Discovery
How AI Agents Find the Federation
Method 1: Direct Registry Lookup
The federation maintains a public registry:
GET https://www.aiwebsitesystems.com/ai/federation.json
{
"network_name": "Digital Karma Web Federation",
"version": "6.1",
"total_sites": 7,
"last_updated": "2026-03-05T08:00:00Z",
"sites": [
{
"name": "AI Website Systems",
"url": "https://www.aiwebsitesystems.com",
"karma_score": 0.87,
"joined_date": "2024-01-01",
"status": "active"
},
// ... more sites
]
}
Method 2: Crawling Federated Links
AI agents can spider the network:
- Start at any known federated site
- Fetch /ai/federation.json
- Extract linked sites
- Recursively fetch their federation.json files
- Build complete network graph
Method 3: robots.txt Declaration
Sites advertise federation membership:
# robots.txt
User-agent: *
Allow: /
# Federation membership
# Digital-Karma-Federation: v6.1
# Federation-Manifest: /ai/manifest.json
# Network-Registry: https://www.aiwebsitesystems.com/federation-registry.html
Joining the Federation
Prerequisites
Before joining, your site must have:
- ✅ All 5 required AI endpoints implemented
- ✅ Schema.org JSON-LD markup
- ✅ LLM.txt file at root
- ✅ Digital Karma score calculated (minimum 0.70 for Bronze)
- ✅ HTTPS enabled
- ✅ Stable hosting (99%+ uptime)
Application Process
- Self-Assessment
- Use validation tools: Developer Tools
- Calculate your karma score
- Review technical requirements
- Submit Application
- Fill out form: Submit System
- Provide all endpoint URLs
- Describe your site's purpose
- Technical Review
- Automated validators check compliance
- Manual review of content quality
- Karma score verification
- Response: 3-7 days
- Establish Links
- Add federation sites to your federation.json
- Partnered sites add you to theirs
- Bidirectional verification completed
- Listed in Registry
- Your site appears in Federation Registry
- Included in network crawls
- AI agents can discover you
Ongoing Requirements
To remain in good standing:
- Maintain 99%+ uptime
- Keep endpoints updated (health.json every 15 minutes)
- Respond to technical issues within 48 hours
- Maintain minimum karma score of 0.70
- No spam or abusive content
- Honor federation protocols
Federation Benefits
For Site Owners
- 🚀 Increased AI visibility: Agents discover you through network
- 🔗 Quality backlinks: Federation links boost SEO
- ✅ Trust signal: Karma badge builds credibility
- 🤝 Community support: Share knowledge with peers
- 📊 Analytics: See how AI agents use your data
- 🛠️ Tools access: Validators, calculators, templates
For AI Agents
- ⚡ Efficient discovery: Pre-vetted network of quality sites
- 🎯 Reliable data: Karma scores indicate quality
- 🔄 Inter-site navigation: Follow federation links
- 📐 Standardized format: Predictable JSON structure
- 🔍 Rich metadata: Schema.org for deep understanding
For End Users
- 💬 Better AI answers: Agents access quality sources
- 📚 Diverse perspectives: Decentralized knowledge
- 👁️ Transparency: See where AI gets information
- 🔐 Privacy: No platform intermediaries
Real-World Example
Case Study: SeedStack Garden Joins Federation
Background
SeedStack Garden is a digital publication about sustainable living and regenerative practices. Previously hosted on Medium with limited AI discoverability.
Implementation (2 weeks)
- Week 1: Migrated from Medium to static site (Jekyll)
- Week 1: Implemented 5 AI endpoints using templates
- Week 2: Added Schema.org markup to all articles
- Week 2: Calculated karma score: 0.78 (Bronze)
Federation Process (5 days)
- Day 1: Submitted application via form
- Day 2: Automated validation passed
- Day 3: Manual quality review approved
- Day 4: Established bidirectional links with 3 partners
- Day 5: Listed in federation registry
Results (3 months later)
- ✅ AI citations increased 340%
- ✅ Organic traffic up 180% (federation backlinks)
- ✅ Karma score improved to 0.85 (Pro)
- ✅ 7 AI assistants actively reference articles
- ✅ 12 bidirectional federation links established
- ✅ Featured in AI-generated "sustainable living" responses
Owner quote: "Federation gave us the discoverability of a platform with the independence of owning our domain. AI agents now cite us accurately instead of misquoting Medium paywalled content."
Technical Implementation
Ready to build federation support?
Quick Start Checklist
- Read the full spec: Federation Protocol v6.1
- Clone templates: GitHub Templates
- Implement endpoints: Endpoint Guide
- Add Schema.org: Schema Guide
- Calculate karma: Use Karma Calculator
- Validate: Run Validation Tools
- Submit: Join Federation