Initial commit: Fresh implementation of CHORUS architecture (ResetData Mandate)

This commit is contained in:
anthonyrawlins
2026-03-03 13:38:56 +11:00
commit 68a489b64d
41 changed files with 17535 additions and 0 deletions

71
docs/CORE VISION.md Normal file
View File

@@ -0,0 +1,71 @@
## 🌐 **Core Vision: The Context Fabric**
> A distributed, semantic, temporal knowledge fabric for humans and AI agents to share *reasoning*, *context*, and *intent*, not just files.
---
### **CHORUS** — *The Context Pulse*
* **Purpose:** P2P protocol for *real-time, selective* sharing of live and historical context between agents/nodes.
* **Core Features:**
- Autonomous nodes, each authoritative over its local context.
- Selective, topic-based, and temporal sync (no full repo mirroring).
- Handles partial streaming updates — *context drips*, not just snapshots.
- Machine-readable metadata for provenance & confidence.
---
### **WHOOSH** — *The Inter-Agent Orchestra*
* **Purpose:** Secure multi-agent coordination layer over CHORUS.
* **Core Features:**
* Agent roles, capabilities, and task assignment.
* Shared context awareness without centralization.
* Negotiated reasoning — agents “debate” using shared provenance.
* Pluggable storage backends (Git, Redis, S3, etc.) but **protocol stays consistent**.
---
### **SLURP** — *The Knowledge Curator*
* **Purpose:** Ingest, normalize, and structure knowledge for semantic use.
* **Core Features:**
* Merges RAG results, reasoning chains, API outputs into curated Markdown + JSON metadata.
* Enforces provenance: citations, decision history, justifications.
* Prepares context for both human consumption and agent reasoning.
* Works across projects, timelines, and domains.
---
### **UCXL** — *The Time-Aware Address Space*
* **Purpose:** Addressable protocol for context queries.
* **Core Features:**
* Path syntax maps to semantic concepts, not just files.
* Temporal navigation (`~~/` past, `^^/` future) as first-class path segments.
* The **address itself is the query** — resolution returns curated, relevant context.
* Works across multiple storage backends seamlessly.
---
### **Why Not Just Git?**
* Git stores *what changed*; this stack stores *why it matters*.
* Git is linear and per-repo; this stack is multidimensional and cross-domain.
* Git lacks:
* Semantic structure
* Multi-agent concurrency without merge hell
* Queryable temporal navigation
* Live partial updates & provenance metadata
---
### **The North Star**
> **A living knowledge fabric** where agents and humans can navigate not just *history*, but *reasoning*, across time and domains — with zero friction, zero central point of failure, and context that is *queryable as easily as it is stored*.
---