The Steward Node.

1. Overview

The Steward Node is an implementation of Layer 2 (Intelligence) of the Myceloom Protocol, specifically architected for long-term institutional continuity. Unlike generic LLM integrations that prioritize speed or content generation, the Steward Node prioritizes sovereignty, provenance, and relational context.

It functions as a dedicated, air-gapped or VPC-secured AI agent that acts as the custodian of an organization's "Tacit Surface Area"—the unwritten knowledge that typically resides only in the minds of senior experts.

2. Core Architecture

2.1. Sovereignty First (The Firewall Rule)

To comply with Myceloom Axiom I ("No Rented Land"), the Steward Node must be deployable on infrastructure fully controlled by the organization.

• Deployment: Local Hardware (NVIDIA DGX), Private Cloud (AWS VPC), or Hybrid.
• Model Weights: Open weights (Llama 3, Mistral) fine-tuned on proprietary data. **Model weights must be owned, not rented via API.**
• Data Egress: Zero. The Steward Node does not call home.

2.2. The Relational Knowledge Graph (RKG)

The core memory of the Steward is not a vector database (which captures semantic similarity) but a Graph (which captures causal relationships).

• Entities: People, Departments, Decisions, Documents, Outcomes.
• Edges: "Authored_By", "Approved_By", "Contradicts", "Supersedes", "Resulted_In".
• Function: Allows the AI to answer "Why did we stop using React in 2024?" by tracing the lineage of the decision to specific meeting minutes and CTO emails.

3. Functional Capabilities

3.1. Executive Memory

The Steward participates in board meetings and strategy sessions (via transcript ingestion) to maintain a real-time record of strategic intent. It highlights deviations from historical strategy.

3.2. Audit-Proof Provenance

Requirement: Every output generated by the Steward MUST include citations to immutable artifacts in the corporate archive.

> User: Why is the budget cap $50k?

> Steward: The cap was established in Q3 2024 [Ref: Board_Minutes_Oct24.pdf] 
  following the audit risk assessment [Ref: Risk_Report_v2.pdf]. 
  Prior to this, the cap was $100k.
            

3.3. Succession Planning (The Heirloom Protocol)

When a key executive departs, the Steward conducts a "exit interview" series, actively probing for gaps in its Knowledge Graph regarding that executive's domain. It synthesizes a "Transition Codex" for the successor.

4. Technical Stack

• Inference Engine: vLLM or TGI (Text Generation Inference).
• Graph Database: Neo4j or ArangoDB.
• Vector Store: Weaviate or Qdrant (Self-hosted).
• Orchestration: LangChain / LangGraph.
• Interface: React-based "Weft" (Customizable web UI).