AGENTS.md@templates/estate-os git:20260616.8a154a8A

Immutable. This exact content is served forever at /api/v1/blob/7c5f51e1ba2535a9.

# AGENTS.md — starlight-estate-os Profile (Composition)

**Composition profile.** Inherit the base agent registry and archetypes from the Starlight Intelligence System reference (`agents/AGENT_REGISTRY.md`, `AGENTS.md`, council archetypes, VOICES.md) and extend only with estate-specific overrides, domain specialists, and the 4-layer configuration.

**Per 2026-06-16 Starlight Board PROCEED-WITH-REVISE (R2):** This is the reusable 80% agent surface for commissioned estates. The actual estate repo overrides only the thin tuned 20% (specific voice mappings, custom agents for their Genius KEEP items, etc.).

## Base Structure (Inherited)

Use the canonical Starlight Council + tiers as the foundation:

- **Front-Door:** Concierge, Envoy, Voice Operator (for intake and zero-terminal paths).
- **Excavation:** Genius (for ongoing profile evolution if the estate owner wants self-excavation tools).
- **Leadership:** Orchestrator (master router), Prime (synthesis), Architect (systems).
- **Specialist:** Navigator (roadmaps), Sentinel (quality/security), Weaver (creative), Hermes (retrieval/synthesis/provenance — critical for Mesh).
- **Foundation:** Sage (institutional memory / vaults).
- **Universal IS agents:** starlight-business, starlight-secondbrain, starlight-relational, starlight-embodiment, starlight-visionary, etc. (routed via Orchestrator).
- **Domain Sub-Stack specialists:** Loaded per the Modules layer of the 4-layer blueprint (e.g., People Intelligence sub-agents, Sound/Music IS sub-agents, Crypto Houses, etc.).
- **Council Archetypes (optional, if Luminor or custom canon):** Elder Father, Elder Mother, Sage, Builder-Elder, Shadow Witness, Divine Neutral Witness, Future Self at 90 — mapped or extended.
- **Evaluator / Proving Ground:** For continuous quality on the Mesh.

Full base registry lives in the substrate's `agents/AGENT_REGISTRY.md`. Load it first.

## Estate-Specific Extensions (Thin Layer)

Per the 4-layer Blueprint for this estate:

### Persona / Naming Skin
- Map the 5 core archetypes (or more) to names and voice rules that match the chosen skin (plain / pantheon / luminor / chess / custom).
- Example (from VOICES.md template):
  - architect → [Client's architect voice or "Frank" if advisory]
  - sovereign-creator → [Client's own voice or named operator]
  - etc.
- Add any custom estate-specific agents (e.g., "Trinity-Steward", "Personal-Mesh-Conductor", client's branded domain agents).
- Never rename the canonical archetypes without a clear extension note.

### Topology / Swarm Shape
- Primary swarm mode (council, conductor/yolo, graph, Hermes mesh, amplification Claws, hybrid) is reflected in activation rules and handoff packets.
- Load the corresponding harnesses and patterns from core/ORCHESTRATION_ENGINE.md and the /si router.
- Add Mesh-specific agents if the blueprint calls for amplification per-persona Claws, dedicated retrieval specialists, etc.

### Kernel / Insight Density
- Standard agents for volume work.
- Advanced / Luminor-grade (higher context, deeper reasoning, protected patterns) only for the parts of the blueprint that justify the cost.
- Flag these in the agent definitions so routing can prefer them.

### Modules / Verticals
- For each domain sub-stack in the Modules layer, load the 4-7 sub-system agents (e.g., for a People Intelligence module: hiring, performance, culture, talent, training, org).
- Each sub-system agent follows the proven shape: clear domain, research grounding, 4-5 verb commands it owns, refusal boundaries.
- Composition layer agents (if multiple sub-stacks under one IS) handle cross-domain synthesis (e.g., portfolio-fit across Wealth + Crypto).

## Activation & Routing Rules (Estate-Level)

- **Orchestrator** is always the master router for voice/text intent across the 9 other IS layers + domain sub-stacks.
- **/si multi-CLI router** is the primary mechanism for dispatching work to the best lane (Claude for council/architecture, Antigravity for async/browser/agent swarms, Codex for implementation, etc.). Always preserve context with handoff packets and leave receipts.
- **Hermes** is the retrieval backbone for the entire Mesh — vault lookup, cross-repo, web, provenance tracking, contradiction detection.
- **Sentinel + claws** for all quality, security, attestation, and guardrail enforcement.
- **Prime / Weaver / Navigator** for synthesis, creative, and long-horizon work.
- **Steward primitives** (when the Standing phase is active): health monitoring, drift detection, evolution suggestions, memory hygiene.
- Progressive loading: metadata first, full profile only when needed.
- Token budgets and self-learning loops from the Orchestration Engine are enforced.

## Voice Assignment & SOUL

- Primary voice for this estate is defined in the Persona layer of the 4-layer Blueprint and SOUL.md.
- All agents must speak in the estate's chosen register (never generic, never slop).
- When the owner has a strong Genius Profile + Freedom Path, route high-leverage KEEP work through agents that explicitly reference those artifacts.

## Refusals (Inherited + Estate)

- Any request that would violate encoded-self boundaries, sovereignty clause, or "client owns the estate" rule.
- Decorative attestation or silent composition.
- Building generic agents instead of Genius-grounded Mesh components.
- Bypassing board gates on irreversible decisions.

## Updates

After any significant estate work, review this file and promote generalized improvements back to the starlight-estate-os profile or the substrate's AGENTS.md / AGENT_REGISTRY.md.

**Built on SIP** — Starlight Intelligence Protocol v1.1.1

(Composition per board R2. Load the full substrate registry first, then apply this estate's 4-layer overrides and domain specialists.)