Agent & Instrument Diagram
How do agents and instruments orchestrate venture creation?
Nomenclature
| A&ID Element | Instance | Domain |
|---|---|---|
| Agent (Yang) | Sprout Generator | Creates venture structure |
| Agent (Yang) | Venture Bootstrap | Self-creates venture row + registers agent card |
| Agent (Yang) | Engineering Team | Runs generator, validates output |
| Instrument (Yin) | Acceptance Test | Verifies 7-line contract |
| Instrument (Yin) | Agent Card | Identity verification for mycelium discovery |
| Instrument (Yin) | WorkChart Seed | Measures venture-scoped execution |
| Instrument (Yin) | Cold Boot Test | Validates "serves a request" not "compiles" |
System Diagram
VENTURE CREATION PIPELINE
═══════════════════════════
┌─────────────────┐ ┌──────────────────────┐
│ SPROUT │ │ VENTURE BOOTSTRAP │
│ GENERATOR │────▶│ (runs on app boot) │
│ (nx g sprout) │ │ │
└────────┬────────┘ └──────────┬───────────┘
│ │
│ creates │ self-creates
▼ ▼
┌─────────────────┐ ┌──────────────────────┐
│ App Structure │ │ venture_ventures │
│ + Templates │ │ row (slug-scoped) │
│ + Stubs │ │ │
└─────────────────┘ └──────────┬───────────┘
│
┌────────────────┼────────────────┐
▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ AGENT CARD │ │ WORKCHART │ │ A2A │
│ (identity) │ │ SEED │ │ ENDPOINTS │
│ │ │ (execution) │ │ (stubs) │
└──────┬───────┘ └──── ──┬───────┘ └──────┬───────┘
│ │ │
└────────────────┼────────────────┘
▼
┌──────────────────┐
│ ACCEPTANCE TEST │
│ (7-line binary) │
│ │
│ 1. Generator ran │
│ 2. Venture exists│
│ 3. Card registered│
│ 4. WorkChart seeded│
│ 5. A2A responds │
│ 6. Entities stub │
│ 7. drmg-sales ok │
└──────────────────┘
Feedback Loops
| Loop | Agent | Instrument | Signal | Action |
|---|---|---|---|---|
| Creation → Verification | Generator | Acceptance test | Pass/fail per line | Fix template or dependency |
| Boot → Discovery | Bootstrap | Agent card | Card written to registry | Mycelium discovers new venture |
| Execution → Scoping | Bootstrap | WorkChart seed | ventureId on definition row | Proves venture-scoped execution |
| First → Second | Generator | "Second consumer" rule | Two apps compose same lib | Shared lib commissioned |
| Template → Legacy | Engineering | Template improvement | Post-run learnings | Generator gets better each use |
Key Design Principles
| P&ID Element | A&ID Equivalent | Application |
|---|---|---|
| Process | Sprout Generator | The agent that applies force to create structure |
| Instrument | Acceptance Test | The instrument that verifies the process worked |
| Pipeline | Boot Sequence | The protocol connecting generator → bootstrap → instruments |
| Control Loop | Legacy Principle | Template improves after each run — the generator IS continuous improvement |
Key Finding
The acceptance test is the single instrument that validates the entire pipeline. Seven binary measurements — no partial credit. This is the P&ID equivalent of a commissioning test on a new process line: every sensor reads, every valve opens, every flow confirms before the line goes live.
Context
- Outcome Map — Success measures the acceptance test checks
- Value Stream Map — The pipeline this diagram orchestrates
- Capability Map — Maturity of each agent and instrument
- A&ID Template — The nomenclature standard