Unclassified

Hierarchical Agent Orchestration & Twin Stewardship Doctrine

1. The Master Doctrine

One Workspace. One Spine. One shared Agent Home. One Twin. Many invisible capabilities.

Users work with their business. Twin carries continuity. Agents operate backstage. The system surfaces outcomes, evidence, decisions and required human attention—not agent machinery.

2. Refined Architectural Boundaries

Spine      = operational truth (canonical entities, graph topology, live projections)
Knowledge  = evidence / semantic structures (grounded manuals, playbooks, SLAs)
Memory     = governed continuity (episodic, semantic, operational)
Agent Home = runtime / working state (shared engine room, A2A bus, sub-workers)
Fortress   = verifiable audit history (append-oriented, tamper-evident execution ledger)

Fortress: Append-oriented, tamper-evident, retention-governed audit and execution ledger supporting governance, traceability, signed proposals, incident reconstruction, and compliance controls.
(Fortress is an audit and evidence plane adjacent to the operational architecture, not a direct operational partition of Spine).

3. Core Principle: Single Face to the User, Invisible Capabilities Backstage

In IntegrateWise, the human user has ONE user-facing relationship: their Twin.

Twin is the sole user-facing orchestrator.

Specialist agents operate inside the shared Agent Home and may be orchestrated by Twin, workflows, events, or runtime policy. Their outputs surface to users through Twin or the appropriate SpineWorkspace projection—not as competing agents.

Why this design wins: A reconciliation agent, sync agent, schema agent, monitoring agent, or scheduled automation does not require Twin to sit synchronously in every internal execution path. One Twin externally does not require one centralized execution bottleneck internally.

ONE SPINEWORKSPACE
        │
        ▼
ONE SHARED AGENT HOME
        │
        ▼
      TWIN
single continuity-bearing,
user-facing orchestrator
        │
        ├── specialists (Triage, Schema-AI, Coworker)
        ├── skills & playbooks
        ├── workflows & state machines
        ├── models (dynamic cost/latency routing)
        ├── tools / MCP connector pool
        ├── jobs & normalizers
        ├── schedules & crons
        └── runtime workers

            invisible (engine room)

USER
 │
 ▼
Work → Awareness → Decide → Act → Continue

4. The Specialized Worker Fleet (Internal Engine Room)

Specialized Capability	Role & Responsibility	Orchestration & Surfacing Rule
Triage Agent	Continuously scans webhooks, emails, tickets, telemetry, and anomalies. Categorizes severity and domain.	Triggered by event ingress. Surfaces classified insights to Twin / Workbenches. Never pings users directly.
Schema Agent	Ingests unstructured and multi-source data (Salesforce, Stripe, Jira, Zendesk) and normalizes it into canonical Spine schemas.	Triggered by data pipelines & sync events. Reconciles schemas backstage; never prompts user for mapping chores.
Coworker Agent	Performs complex, domain-specific background reasoning (churn analysis, expansion models, reconciliation).	Orchestrated by Twin or domain workflows. Submits structured drafts for Twin synthesis or projection rendering.
Adaptive Auto-Tuner	Monitors tool invocation latency, token cost, and accuracy; dynamically switches model routing (Claude / GPT / Groq / Gemini).	Autonomous runtime policy. Optimizes model selection invisibly backstage.
Hermes Executor	Dispatches authenticated API mutations and tool actions against external SaaS endpoints once human cryptographic sign-off is granted.	Triggered upon HITL proposal approval. Logs execution proofs directly to Fortress Ledger.

5. The 4 Golden Rules of Twin Stewardship & User Experience

Sole User-Facing Presenter:
- The Twin is the only agent that speaks to, summarizes for, or generates interactive proposals for the human user.
Context & Continuity Stewardship:
- While specialist agents execute bounded tasks statelessly or within ephemeral scratchpads, the Twin preserves cross-session continuity, role awareness, and working context.
Decoupled Internal Execution:
- Internal workers run asynchronously, triggered by events, crons, or workflow DAGs without blocking the Twin or polluting the user's focus.
Governed Human Sign-Off (HITL Gate):
- When any backstage worker determines a write mutation or sensitive external action is needed, the action is encapsulated into a cryptographically verifiable Proposal Card presented through the Twin or domain projection for 1-click human approval.