Constellation Architecture Explained
Understanding how websites form constellation patterns for AI discovery and trust propagation.
Core Components
- Manifest Files - Site identity cards at
/ai/manifest.json - Health Endpoints - System status at
/ai/health.json - Catalog Endpoints - Content inventory at
/ai/catalog.json - Karma Scoring - Trust signals at
/ai/karma.json - Constellation Registry - Constellation topology at
/ai/federation.json
4-Stage Constellation Mapping
The v7 line uses a 4-stage mapping model that gives AI agents progressively richer constellation intelligence. v7.1 keeps this structure while tightening the root discovery rules:
- v01 - Listings: Raw inventory of all member sites
- v02 - Clusters: Sites grouped by function (hub, implementation, tool, content)
- v03 - Relationships: Directed edges between sites with relationship types
- v04 - Propagation: Trust flow model across the constellation
Decentralization
The constellation uses a federated architecture. Any site can join by implementing the standard independently - no central server approval required. Sites discover each other through peer-to-peer link traversal. The optional registry at DigitalKarmaWeb.com is a convenience, not a requirement.