Architecture
Swarm architecture lead
Own agent roles, task graphs, state, memory, tool boundaries, coordination, failure, and control-plane interfaces.
Partners
Specialist machine intelligence depth for platforms, primes, and delivery partners
Add named specialist depth without hiding responsibility. Workshare, access, interfaces, artifacts, acceptance, and client communication are explicit.
PartnersGovernmentEnterprise
Workshare patterns
Where a specialist workstream fits
The work complements product, platform, security, cloud, data, and program teams.
Evaluation
Evaluation and release workstream
Own scenario design, instrumentation, metrics, human calibration, triage, and release evidence.
Implementation
Control-plane integration
Own policy points, agent identity, entitlements, budgets, routing, observability, approvals, and shutdown.
Evidence
Technical evidence and review
Produce architecture, data flow, authority, system cards, risk records, and decision briefs.
Advisory
Client-side technical advisor
Translate between buyer decisions, delivery architecture, control expectations, and implementation evidence.
Capture
Joint discovery and proposal scope
Test fit, define workshare, identify prerequisites, and create a credible technical next step.
Delivery model
Teaming principles
Clear interfaces reduce delivery and relationship risk.
| Principle | What it means |
|---|---|
| Named responsibility | The specialist workstream, accountable lead, artifacts, and acceptance are visible. |
| Direct technical access | Architecture work is not performed through a long relay of partial context. |
| No hidden labor | Client-facing role, subcontract status, and attribution follow the agreed model. |
| Evidence travels | Artifacts are usable by engineering, security, leadership, procurement, and operations. |
| Bounded presales | Detailed architecture begins in a paid discovery or delivery scope. |
| Explicit handoff | The partner and client retain the system context, decisions, evidence, and operating runbooks. |
Start with a bounded decision
Test the workstream with a paid joint-discovery step.
Bring the public solicitation, client problem, capture stage, expected role, access model, and proposal date.