The Dream Team

Specialized agents.
One review path.

Six functional lanes. A Chief-of-Staff coordinator. A person on anything that leaves. This page describes roles, boundaries, and vendor-neutral reference blueprints—not a catalog of named tools.

  • 6 Specialist Lanes

    Executive routing, enterprise data, edge ops, RFP intake, comms triage, and verification.

  • Read vs. Write Split

    Monitoring and research run on their own. Every external send, mutation, or spend hits a human gate.

  • Zero Shared Credentials

    Per-app service tokens at the edge. Agents never hold raw vault secrets in prompt context.

  • Auditable State Packs

    File-backed handoffs, deterministic schemas, and explicit approval records.

How work moves

A specialist that can both draft and send will eventually send the wrong thing. Splitting those steps is the control: drafting is cheap to redo, and an external action is not.

The coordinator does not approve. It makes the queue visible so a person can. Handoffs are structured state packs with a deterministic schema, so the next lane can see what was decided and what is still waiting. If the queue is not visible, the gate is theater.

Read-only monitoring and research may run without a prompt. Mail, posts, writes, and spend do not.

Text version: specialist agents do bounded work, a coordinator places it on a review queue, a person approves, and only then does an external action go out.

Blast radius

Breaking the Lethal Trifecta

The failure mode is one agent, in one turn, reading untrusted external input, holding privileged credentials, and taking an unreviewed external action. The practice is built so that combination cannot occur.

Untrusted content is parsed in a lane with no vault secrets and no send path. Privileged access sits behind a per-origin service token on a local loopback bridge, not in the prompt. Anything that writes, sends, or spends waits on the human queue. Read-only GET monitors are allowed to run. Mutations are not.

Text version: untrusted input is sanitized, a specialist agent works without raw secrets, a per-application Zero Trust service token opens one origin, read-only monitors stay on GET while writes wait for a person, and only then is a system of record touched.

01

Untrusted input

Inbound content is parsed by agents that do not hold system-of-record credentials and cannot send. Untrusted text does not share a turn with a privileged tool and an egress path.

02

Privileged credentials

Each origin has its own service token. Agents do not carry raw vault secrets in the prompt. A loopback bridge keeps the token at the edge, and expiry is alerted on a 90-day clock.

03

External egress

Sends, writes, and spend leave the coordinator queue only after a person approves. The coordinator routes. It does not approve. Read-only monitors may run on their own.

Functional lanes

Six specialist lanes. One decision queue.

The roster below is roles and boundaries. It is not a list of named agents. Every lane can draft or watch. Only a person can let an external action leave.

01

Chief-of-Staff Coordinator

Synthesizes cross-lane state, deduplicates alerts, and keeps the single human decision queue. Routing is not approval.

02

Read-Only Edge/Systems Watch

Monitors DNS, TLS, Zero Trust tunnels, and service-token health on a strict GET-only scope. This lane does not write and does not send.

03

Enterprise Data & Schema Engineering

Drafts PL/SQL packages, utPLSQL test harnesses, ETL mappings (Informatica, OWB, ODI, OBIEE, shell + PL/SQL), and migration runbooks for an engineer to review.

04

Document Intelligence

Queries the private self-hosted document store. The corpus is not sent to a public model endpoint. A person decides what leaves.

05

Opportunity/RFP Intake

Ingests, deduplicates, and scores RFP and market signals into the CRM review queue. A digest shows what changed. Sends still wait.

06

Scope-Signed Security Posture

Runs scope-signed, read-only discovery for SkeenSecure+ and prioritizes the top three fixes in a client-owned environment. Not a penetration test, and not a certification.

Inspectable specifications

Reference Agent Blueprints

Four vendor-neutral YAML specifications showing how read scopes, hard write boundaries, cryptographic gates, and audit artifacts are defined before an agent touches an enterprise environment. Runtime-specific starter templates live in separate public GitHub repositories so these specifications stay portable across MCP-compatible orchestrators.

Lane 01 · Executive Routing & Approval Gate

Chief-of-Staff Triage & Human-Approval Router

Aggregates specialist digests, enforces priority vs. held queues, strips untrusted instructions, and routes every external write, config mutation, or spend decision through an explicit human approval gate.

Permitted Read Scope
Schema-validated specialist handoff packs, content-hash deduplication index, and the immutable approval decision ledger (no raw untrusted inbound payloads).
Hard Write Boundary (Never Autonomous)
Never sends external mail/messages, never mutates production configs or schemas, never widens credentials, and never approves its own queue.
Verification / Audit Artifact
Deterministic Decision & Queue Ledger (.jsonl) with SHA-256 payload digest + reviewer timestamp, backed up in .age-encrypted snapshots.

Lane 02 · Strictly Read-Only Edge Monitor

Read-Only Edge, DNS & Certificate Watch

Enforces GET-only monitoring across edge zones, tunnels, TLS certificates, and service-token expiry windows; compares against a canonical state snapshot and alerts only on state transitions.

Permitted Read Scope
HTTP GET/HEAD control-plane telemetry (DNSSEC, Zero Trust tunnel health, Access policy posture, 90-day service-token expiry windows, and TLS certificate validity).
Hard Write Boundary (Never Autonomous)
POST, PUT, PATCH, and DELETE verbs are denied at the service token and local proxy; any remediation is drafted as a before/after proposal for human approval.
Verification / Audit Artifact
Signed Edge State Snapshot & Drift Report (canonical JSON baseline diff + transition-only alert receipt).

Lane 06 · Cryptographic Scope-Gated Discovery

Cryptographically Signed Security Posture Runner

Verifies an offline Ed25519/cosign-signed scope manifest before scanning; refuses unsigned targets or in-house exemptions; emits a deterministic posture summary.

Permitted Read Scope
Non-intrusive, read-only service, TLS, header, and mail-auth discovery strictly limited to CIDRs and hostnames inside a verified Ed25519-signed scope file.
Hard Write Boundary (Never Autonomous)
Aborts immediately on unsigned or expired scope files; never probes out-of-scope targets, never runs exploit payloads, and never uploads telemetry to public model endpoints.
Verification / Audit Artifact
Scope-Verified Posture Briefing & Evidence Pack (manifest SHA-256, signer key fingerprint, raw evidence checksums, and top-3 prioritized remediations).

Lane 03 · Systems-of-Record & DR Parity

Systems-of-Record Schema & Reconciliation Specialist

Connects through a per-origin Zero Trust service token to read Oracle / Postgres / EAM metadata, validates ETL lineage and backup restore parity, and stages schema or PL/SQL changes as reviewable pull requests.

Permitted Read Scope
Read-only catalog views (Oracle DBA/ALL dictionary views, PL/SQL compile status, Informatica/ODI/OWB job metadata, EAM staging counts) via a local loopback Zero Trust proxy.
Hard Write Boundary (Never Autonomous)
Zero direct DDL/DML execution in production; credentials never enter prompt context; all schema or PL/SQL changes are staged as git pull requests with utPLSQL tests.
Verification / Audit Artifact
Reconciliation Report, Ephemeral Restore Parity Proof (table/row checksum verification of .age backups), and Reviewable PR Pack with rollback runbook.

See the review path · Per-origin bridge · Security principles