VisionVolve — Internal
Greenfield install · GroupWide
Workstreams · Cynefin diagnostic
Candidate AI workstreams classified by kind-of-problem (Cynefin) and ranked by benefit × foundation readiness. The classification drives which methodology pattern fits each track.
Cynefin classificationKind-of-problem axis per workstream
UNORDERED · ← · → · ORDERED
COMPLEX
Probe → Sense → Respond
WS1Ship RADAR + the signal contractDiscovery
WS2Build the S3 organ: Engage delivery appDiscovery
COMPLICATED
Sense → Analyze → Respond
WS3Extract shared method/render engine (operate ↔ AITP)Foundation
WS5Productize the ambient ear⚠ regulatoryDiscovery
WS7Encrypted client-data + consent/retention pipeline⚠ regulatoryDirect
WS8Run VV through operate as the reference engagementDirect
WS9Sequence a single suite roadmapFoundation
CHAOTIC
Act → Sense → Respond
— no workstreams here —
CLEAR
Sense → Categorize → Respond
WS4Harden the IAM/auth spine + operate authorization⚠ regulatoryDirect
WS6Version and govern the methodology IPFoundation
Benefit × readiness heatmapQuick wins · foundation-blocked · defer · fill-ins
Workstreams9 total
| # | Name | Cynefin | Pattern | Benefit | Readiness | Track | Reg. | |
|---|---|---|---|---|---|---|---|---|
| WS1 | Ship RADAR + the signal contract Build the S4 sensing plane (radar service, revive VV-NEWS) and define/implement the 'signal' contract — the sense→reason seam that feeds structured external signals into operate. | Complex | Discovery | 5/5 | 2/5 | T1 | ||
| WS2 | Build the S3 organ: Engage delivery app Stand up VV's operational-management layer — Engage (delivery/CRM: won-deal→kickoff→delivery→close) integrated with vv-ops and backlog — so the suite has a functioning System 3. | Complex | Discovery | 5/5 | 2/5 | T3 | ||
| WS3 | Extract shared method/render engine (operate ↔ AITP) Resolve the open architectural decision: factor the strategy-canvas/method engine (BDN/OST/Wardley rendering and graph substrate) into a shared library consumed by both operate and aitransformers-platform, keeping their kernels distinct. | Complicated | Foundation | 4/5 | 3/5 | T3 | ||
| WS4 | Harden the IAM/auth spine + operate authorization Finish operate SSO against visionvolve-iam and add action-level authorization to the ~15 presence-gated server actions; sweep the suite for the same pattern. | Clear | Direct | 3/5 | 5/5 | T5 | ⚠ | |
| WS5 | Productize the ambient ear Turn the ad-hoc capture→transcribe→structure pipeline for client conversations into a governed product: consented capture, transcription, structuring into evidence, feeding the AIT evidence graph. | Complicated | Discovery | 4/5 | 3/5 | T2 | ⚠ | |
| WS6 | Version and govern the methodology IP Move the canonical methodology .md corpus off Anton's laptop into a git-governed repo with review discipline, change log, and stable IDs, treating canon edits as schema migrations. | Clear | Foundation | 4/5 | 5/5 | T5 | ||
| WS7 | Encrypted client-data + consent/retention pipeline Encrypt the ~10GB of client audio at rest, and build the consent-capture, retention-schedule, and deletion pipeline for all client-derived data across the suite (GDPR Art. 5/17/32). | Complicated | Direct | 3/5 | 3/5 | T5 | ⚠ | |
| WS8 | Run VV through operate as the reference engagement Seed and maintain VisionVolve's own strategy as a first-class engagement in operate — suite graph, Wardley/AIR positioning, these workstreams, stock-flow of the tool estate — as the canonical dogfood. | Complicated | Direct | 4/5 | 4/5 | T6 | ||
| WS9 | Sequence a single suite roadmap Produce and maintain one sequenced roadmap across all ~20 repos — dependencies, contract milestones, capacity — replacing per-repo backlogs as the source of build order. | Complicated | Foundation | 4/5 | 3/5 | T4 |
Add workstream