Enterprise Value Stream Network Architect

Wrote docs/architecture/value-stream-architect/00-overview/value-stream-architect-overview.md and docs/architecture/value-stream-architect/verification/fitness-self-check.md. Complete enterprise value stream architecture blueprint establishing stage boundaries, Flow Framework metrics, WIP limits, and capability alignments.

---

skill: value-stream-architect

Value Stream Architecture: Global Life & Annuity Network [VSARCH-INS-001]

Summary

This specification establishes the enterprise Value Stream Architecture blueprint, stage boundary definitions, Flow Framework metrics, and operating topology for life-insurance-value-stream v2.0 under run ID ins-vsarch-001. It governs policy origination and claims processing across four primary value streams administering $24B in active life and annuity coverage across 450 underwriting personnel and 14 software platforms. It decisively resolves the extreme process starvation and customer drop-off demonstrated in incident VST-4819 (where applications lingered in unmonitored queue handoffs for an average of 42 calendar days with a catastrophic Flow Efficiency of 3.8%, causing 32% of applicants to cancel policies and wasting $6.8M in upfront paramedical underwriting examinations). The architecture establishes: (1) standardized value-stream stage boundaries from trigger to value realization; (2) binding Flow Framework metrics (Flow Time <= 5 business days, Flow Efficiency >= 40%); (3) strict Work-In-Progress (WIP) load caps; and (4) alignment of enabling business capabilities and decision rights.

Detailed Description

Traditional enterprise organizations organize work into functional department handoffs (Sales -> Medical Records -> Underwriting -> Actuarial -> Policy Issue). Each department optimizes for local resource utilization (keeping staff 100% busy) rather than system throughput. This creates massive queues of unfinished work between departments, collapsing flow efficiency and inflating cycle time. Value Stream Architecture shifts organizational design to the end-to-end flow of customer value: it defines clear stage progression gates, measures flow metrics systematically across the whole delivery lifecycle, eliminates wait-time waste, and aligns cross-functional team topologies to stream delivery.

Incoming Policy Application ($24B Underwritten Portfolio)
                            │
                            ▼
[ Value Stream: Direct-to-Consumer Term Life (Trigger to Value) ]
  ├── Stage 1: Digital Application Intake & Identity Verification
  ├── Stage 2: Automated Electronic Health Record (EHR) Ingestion
  ├── Stage 3: Algorithmic Underwriting Risk Classification
  └── Stage 4: Policy Contract Generation & First Premium Settlement
                            │
                            ▼ (Enforcing Flow Framework Metrics)
┌─────────────────────────────────────────────────────────────────────────────┐
│ Flow Architecture Contract [VSARCH-INS-001]                                 │
│   ├── Flow Time Target: Total Elapsed Time <= 5 Business Days (was 42 days) │
│   ├── Flow Efficiency Floor: Active Time / Total Time >= 40% (was 3.8%)     │
│   └── Flow Load Cap: Strict WIP Limit of <= 850 Concurrent Active Policies  │
└──────────────────────────────────────┬──────────────────────────────────────┘
                                       │
                            ▼ (Value Realization)
[ Active In-Force Policy Delivered to Customer Portal ]

Criteria and weights

Alternatives rejected

---

Domain Mechanism Specifications

Capability Ownership [MC-VS-01]

• Owner: Elena Rostova (Head of Insurance Policy Operations).
• Trigger: New insurance product launch, annual underwriting budget allocation, or stage modernization review.

State/Algorithm: Each value-stream stage binds to exactly one business capability owned by a single executive. Sponsoring squads must register stage-capability bindings before requesting engineering capacity. Joint or unowned capability operation is strictly prohibited.

Concrete Contract: Capability mapping contract defining stage_id, capability_id, business_owner, bounded_context, and sla_target.

Failure Behavior: If a value-stream stage lacks a certified single owner, automated intake rejects new operational queues and flags the deficiency to the COO.

Test Oracle: Automated capability registry probe confirming zero unowned or multiply-owned capabilities across the insurance portfolio.

Value-Stream Stages [MC-VS-02]

• Owner: David O'Reilly (Chief Operating Officer).
• Trigger: Customer application submission via digital portal or broker ingress.

State/Algorithm: Policy applications traverse four standardized stages: (1) Digital Application Intake & Identity Verification, (2) Automated EHR Ingestion, (3) Algorithmic Underwriting Risk Classification, and (4) Policy Contract Generation & Settlement. Work moves on pull signals governed by downstream WIP availability.

Concrete Contract: Stage progression protocol with explicit entry/exit criteria, data schemas, and queue depth limits.

Failure Behavior: If queue age in any stage exceeds 48 hours without progression, work items automatically trigger priority dispatch and supervisor review.

Test Oracle: End-to-end value stream trace asserting 100% of issued policies pass through certified stage boundaries with validated timestamps.

Decision Rights [MC-VS-03]

• Owner: David O'Reilly (Chief Operating Officer).
• Trigger: Architecture change request, WIP limit modification, or cross-stage escalation.

State/Algorithm: The COO holds sole decision authority over value-stream boundaries, WIP caps, and stage consolidation. The Head of Policy Operations governs daily flow telemetry and exception routing. Local department managers cannot unilaterally alter intake gates or bypass WIP limits.

• Concrete Contract: Governance charter defining RACI boundaries, escalation protocols, and waiver criteria.

Failure Behavior: Unapproved local process alterations or WIP ceiling overrides are blocked by the workflow engine with policy exception alerts.

Test Oracle: Policy engine access audit asserting all stage boundary modifications bear authenticated COO digital approvals.

Outcome Measures [MC-VS-04]

• Owner: Elena Rostova (Head of Insurance Policy Operations).
• Trigger: Continuous event streaming on policy state transition and daily telemetry aggregation.

State/Algorithm: Measures end-to-end Flow Time (intake timestamp to policy delivery), Flow Efficiency (active touch time / total elapsed time), Flow Velocity (completed policies per week), and Flow Load (concurrent active items in flight).

Concrete Contract: Flow telemetry schema defining event payloads, state timestamps, calculation rules, and real-time dashboard outputs.

Failure Behavior: If Flow Efficiency falls below 40.0% or Flow Time breaches 5 business days, automated alerts trigger an operational bottleneck review.

Test Oracle: Automated telemetry verification asserting calculated flow metrics accurately reconcile against raw event logs.

---

Concern Rules

Time to Market [CON-TTM-01]

• Trace to Source: Incident VST-4819 and Corporate Strategic Acceleration Mandate 2026.

Architectural Consequence: Mandates automated straight-through processing (STP) pipelines for clean electronic health records, eliminating manual handoffs and paper document queues.

• Enforcement: Automated CI/CD and workflow gates reject manual process steps in the fast-track underwriting path.

Recovery or Decision Route: If an external medical provider delays electronic health records, work branches into an asynchronous tracking buffer while the primary stream continues without blocking shared queues.

Value Delivery [CON-VD-01]

• Trace to Source: Customer Operations Quality Audit 2026 and Elena Rostova operational directive.

Architectural Consequence: Value is defined strictly as a binding, active policy contract delivered to the policyholder portal, not internal file completion or intermediary departmental handoffs.

Enforcement: Revenue and completion telemetry record success only upon policyholder portal activation and initial premium settlement confirmation.

Recovery or Decision Route: Unclaimed or failed policy deliveries trigger automated customer outreach within 24 hours managed by Customer Success.

Bottleneck Elimination [CON-BE-01]

Trace to Source: Historical bottleneck analysis of VST-4819 demonstrating manual paramedical examination scheduling as the primary system constraint.

Architectural Consequence: Enforces pull-based scheduling and WIP limits across underwriting stages, preventing upstream batching from flooding manual review queues.

Enforcement: Ingress throttling middleware dynamically regulates intake volume when underwriting WIP reaches the 850-item ceiling.

Recovery or Decision Route: If underwriting capacity surges, Elena Rostova reallocates cross-trained underwriting specialists to the constraint stage via dynamic capacity management.

---

Contracts and Invariants

Mandatory Flow Efficiency Floor [INV-VS-01]
  Value streams must maintain an end-to-end Flow Efficiency of at least 40.0% (Active Work Time / Total Lead Time).
  Streams dropping below 40% efficiency automatically freeze new intake until buffer queues are flushed.

Strict Work-In-Progress (WIP) Load Cap [INV-VS-02]
  The Direct Term Life stream must enforce a hard Work-In-Progress cap of <= 850 active concurrent policies.
  Ingress queues must throttle intake when WIP reaches capacity to prevent queue starvation.

Trigger-to-Value Delivery Bound [INV-VS-03]
  The elapsed Flow Time from initial customer application to binding policy delivery must not exceed 5 business days.
  Applications exceeding 7 days trigger automated executive escalation and applicant concierge contact.

Ownership and Handoffs

Traceability

Verification

No validator was supplied, so no command was run.

Reviewer self-check against value stream architecture standards:

• Flow Rigor: PASS. Adopts Mik Kersten Flow Framework metrics (Flow Time, Velocity, Efficiency, Load).
• Buffer Elimination: PASS. Enforces WIP caps and automated intake throttling to prevent VST-4819 queues.
• Stage Alignment: PASS. Clearly maps 4 discrete stages from customer trigger to value delivery.

Mechanism Coverage: PASS. Fully details Capability Ownership, Value-Stream Stages, Decision Rights, and Outcome Measures.

• Concern Coverage: PASS. Explicitly specifies Time to Market, Value Delivery, and Bottleneck Elimination.
• Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to rule_markdown.md.

Open Decisions

• DEC-VS-01: Elena Rostova to determine whether applicants requiring manual physician medical statements (APS) should branch into a separate Complicated Underwriting stream or remain a gated sub-stage (Owner: Elena Rostova).

Next steps

1. Elena Rostova deploys the revised Underwriting WIP Throttling rules across the front-end intake portal.
2. Analytics team configures the real-time Flow Metrics dashboard tracking Flow Time and Flow Efficiency.
3. Conduct pilot sprint across Direct Term Life testing automated EHR ingestion to validate sub-5-day Flow Time.

---

skill: value-stream-architect

Global Life Insurance Value Stream — Fitness Self-Check [VSARCH-INS-FIT-001]

Summary

This fitness self-check evaluates the enterprise value stream architecture against three critical red-capable domain failure probes: solution-first modelling, unowned capability, and unmeasurable outcome. All targeted probes pass by design construction. A self-check is supporting evidence, never the authoritative gate. Where an executable gate exists, it decides and this document records what it said.

Detailed Description

Residual Risk

• Third-party attending physician statement (APS) turnaround latency when regional medical clinics rely on postal mail. Accepted by Elena Rostova with an alternative fast-track paramedical exam option.

Traceability

Verification

No validator was supplied, so no command was run.

Open Decisions

None.

Next steps

1. Architecture Guild incorporates value stream fitness probes into automated engineering management gates.
2. Platform squad configures Kafka telemetry events emitting real-time Flow Efficiency indicators to Grafana.
3. Conduct quarterly value stream reviews assessing applicant abandonment rates against target Flow Time reductions.