The Cypher Framework is the reusable public framework ecosystem. The private architect-side orchestration architecture remains separately bounded. CMP, MCP Orchestrator, and runtime hosts are shown according to their own evidenced maturity—not flattened into peer repositories.
Architecture record
The Cypher Framework
Reusable multi-model framework ecosystem
operational
A public, reusable framework ecosystem for multi-model collaboration, governed capability access, persistent continuity, and user-facing Cypher surfaces.
The public framework spans multiple reusable surfaces and generations; the historical hosted gateway remains one implementation in that broader ecosystem, distinct from private architect-side orchestration.
- Source
- Source: public
- Interface
- Interface: public
- Publication
- Publication: public-release
- Python
- FastAPI
- Transformers
Architecture record
MCP Orchestrator
Governed MCP capability gateway
validated
A governed, config-driven MCP gateway and launcher with protocol-neutral tool, resource, transport, and policy surfaces.
Candidate modernization is validated; this does not imply every candidate capability is promoted to production.
- Source
- Source: private
- Interface
- Interface: private
- Publication
- Publication: private
- Python
- Model Context Protocol
Evidence
- Governed MCP Orchestrator package acceptance report
Architecture record
Conversation Memory Project
Persistent conversation and artifact continuity substrate
operational
The persistent memory substrate for conversations, artifacts, provenance, and context continuity across the Federation.
Current generation uses PostgreSQL-backed services; earlier generations remain provenance rather than current-runtime claims.
- Source
- Source: private
- Interface
- Interface: private
- Publication
- Publication: private
- Python
- FastAPI
- PostgreSQL
- SQLAlchemy
- pgvector
Evidence
- Current CMP architecture documentation
Architecture record
Federation Heart
Shared Federation capability foundation
implemented
The shared Federation foundation that exposes bounded capability pillars while keeping lower-level clients behind enforced dependency boundaries.
Current documentation defines six public-to-consumer pillars and enforced client import boundaries; this record does not claim every downstream Federation system is equally mature.
- Source
- Source: private
- Interface
- Interface: private
- Publication
- Publication: private
Evidence
- Current Federation Heart architecture documentation
Architecture record
Private architect-side orchestration architecture
implemented
A private governed orchestration architecture for deliberation, specialist coordination, and bounded execution.
Active development; public copy describes the architecture without exposing private Federation internals.
- Source
- Source: private
- Interface
- Interface: private
- Publication
- Publication: private
Evidence
- Current private orchestration architecture documentation
Architecture record
Browser Runtime Host
Planned authenticated browser transport host
planned
A planned independent host boundary for authenticated browser transport and browser-job supervision.
The build program is on hold; the manifest defines a boundary, not a deployed service.
- Source
- Source: private
- Interface
- Interface: unavailable
- Publication
- Publication: private
Evidence
- Federation runtime-host boundary manifest