Capability Map
What can we actually do — and where are the gaps?
Capability Maturity
| Capability | Maturity | Evidence | Category | Gap? |
|---|---|---|---|---|
| Venture schema (18 tables × 5 domains) | 3 — Defined | Migration applied, tables exist in prod | Core | No |
| WorkChart venture scoping | 1 — Ad-hoc | 3 nullable columns added, no data yet | Core | P1 |
| Sprout generator | 3 — Defined | Templates built, registered, not executed | Core | P1 |
| Safe Nx runner | 4 — Managed | Built, tested, handles hang edge case | Supporting | No |
| Acceptance test script | 3 — Defined | Written, 7-line spec, not executed | Supporting | No |
| Venture self-creation (boot) | 2 — Repeatable | Designed, coded in template, untested | Core | P1 |
| Agent card auto-registration | 2 — Repeatable | Designed, coded in template, untested | Core | P1 |
| A2A endpoints | 1 — Ad-hoc | Stubs only | Core | P2 |
| Feature scaffold (per-entity CRUD) | 3 — Defined | Works for drmg-sales, untested standalone | Supporting | P2 |
| Shared lib independence | 0 — Not Built | Never tested outside drmg-sales | Core | P1 |
| Domain-specific entities | 0 — Not Built | No tables for spots/reports/catches | Generic | P2 |
| Venture access control | 0 — Not Built | No design yet | Supporting | P3 |
| Cross-venture A2A | 0 — Not Built | Requires two working ventures | Core | P3 |
Maturity Distribution
| Level | Count | % |
|---|---|---|
| 0 — Not Built | 3 | 23% |
| 1 — Ad-hoc | 2 | 15% |
| 2 — Repeatable | 2 | 15% |
| 3 — Defined | 4 | 31% |
| 4 — Managed | 1 | 8% |
| 5 — Optimised | 0 | 0% |
Average maturity: 1.8 — between Ad-hoc and Repeatable. The generator lifts the average significantly once run.
Investment Strategy
| Category | Capabilities | Strategy |
|---|---|---|
| Core (differentiating) | Venture schema, WorkChart scoping, generator, self-creation, agent registration, shared lib independence, cross-venture A2A | Invest — these ARE the platform thesis |
| Supporting (necessary) | Safe Nx runner, acceptance test, feature scaffold, access control | Maintain — solve once, reuse everywhere |
| Generic (commodity) | Domain-specific entities | Outsource to generator templates |
Key Finding
The riskiest capability is also the most revealing: shared lib independence (maturity 0). Everything else could score 5 and the platform thesis still fails if shared libs carry hidden drmg-sales coupling. The generator run (Phase 1 Step 1.6) is simultaneously the most important test and the most dangerous one.
Context
- Outcome Map — What success looks like when these gaps close
- Dependency Map — Which gaps block which phases
- A&ID — How agents and instruments orchestrate these capabilities