2. Pair & Triad Programming

2.4 Sub-Issue to Subagent Fan-Out & Delta Velocity

chinwag tasks fanout --issue CHWG-104

1:1 mapping of GitHub Projects v2 subIssues and Linear children to parallel subagent leases across 4 execution tiers, plus DORA dual-denominator speedup math.

2.4 Sub-Issue to Subagent Fan-Out & Delta Velocity

chinwag tasks fanout --issue CHWG-104

Outcome Summary & Δ Velocity Proof: Parent Issues and Sub-Issues (subIssues in GitHub Projects v2 / children in Linear) map 1:1 to Principal Seats and Parallel Subagents across 4 execution tiers, visually proving why a 6.2-day DORA feature ships in 22 minutes (⚡ 134.4x faster).


1. 1:1 Sub-Issue → Parallel Subagent Fan-Out (chinwag task fanout)

When you run chinwag task fanout <ISSUE-ID>, Chinwag decomposes the parent epic (Tier S / M / L / XL) into disjoint sub-issues (#101.1 .. #101.N) and leases each sub-issue (TaskLeaseV1 ✓ed25519) across 4 execution tiers:

  1. Tier 1 · Local Parallel Subagents: Isolated colocated Shadow jj workspaces on the developer's workstation.
  2. Tier 2 · On-Demand Ephemeral Cloud Dev/QA Swarm: Parallel cloud workers executing bounded unit implementation and test synthesis.
  3. Tier 3 · Multi-Node Principal Mesh: Standing specialist seats (Systems Architecture, Rust, UI/UX, Security, Copy Gate) connected over iroh QUIC.
  4. Tier 4 · GitHub Actions / GitLab Cleanroom CI Runners: Ephemeral runners executing chinwag ci-report and chinwag ui-gate.

GitHub Projects v2 and Linear natively render the ☑️ 4/4 Sub-Issues (100%) progress pill on every Kanban and Gantt card.


2. The Glass-Box Dual-Denominator Standard (INV-BENCHMARK-DUAL-METRIC-01)

To ensure skeptical staff engineers and CTOs can audit every number, Chinwag displays both published 2025–2026 DORA and LinearB (8.1M+ PR study) baselines side-by-side, and uses the more conservative Active Engineering Touch-Hours (Metric B) for our headline speedup multiplier:

Complexity Tier & Scope Floor (INV-TIER-LOCK-01)Metric A: Industry Elapsed Calendar Cycle TimeMetric B: Industry Active Engineering Touch-Hours (Conservative Headline Denominator)Representative Chinwag Triad Actual (t_ship - t_claim)Metric A Calendar SpeedupMetric B Active-Effort Speedup (Headline Badge)
Tier S (1–100 LOC + >=1 gate)1.1 Elapsed Days (26.4 cal hrs)8.5 Active Eng Hours6m 12s (0.103h)255x Calendar⚡ 82.5x Faster
Tier M (101–400 LOC / >=2 modules)3.4 Elapsed Days (81.6 cal hrs)27.0 Active Eng Hours16m 30s (0.275h)296x Calendar⚡ 98.2x Faster
Tier L (401–1,200 LOC / multi-surface)6.2 Elapsed Days (148.8 cal hrs)50.0 Active Eng Hours22m 18s (0.372h)400x Calendar⚡ 134.4x Faster
Tier XL (1,200+ LOC / protocol & CRDB)14.0 Elapsed Days (336.0 cal hrs)112.0 Active Eng Hours54m 00s (0.900h)373x Calendar⚡ 124.4x Faster

3. The 5-Point CTO Anti-Tamper Verification Protocol (INV-VELOCITY-TIMESTAMP-INTEGRITY-01)

  1. Dual-Clock Server Anchor on t_claim (INV-CLAIM-ANCHOR-01): chinwag task claim posts the signed TaskLeaseV1 ✓ed25519 comment to GitHub/Linear immediately and binds t_claim = min(crdb_claimed_at_ms, github_comment_created_at_ms). Any clock drift > 60s fails closed.
  2. Pre-Baked Diff Prohibition (INV-NO-PREBAKED-CLAIM-01): TaskLeaseV1 pins base_head_sha from git ls-remote origin main and verifies 0 dirty LOC at claim time (exit 78 on pre-baked commits).
  3. Automatic Diff-Scope Tier Lock (INV-TIER-LOCK-01): At chinwag task complete, H_board inspects git diff --numstat <base_head_sha>..<ship_sha>. If a task claimed as Tier L only modified 45 LOC, H_board automatically downgrades its baseline to Tier S (8.5h) before computing the multiplier.
  4. Full-Lifecycle Clock (Claim → Prod, Including Gate Rework): t_ship is anchored to GitHub's server timestamp on the final merged commit after H1, H2, H5, WP-13, and Copy Gate pass.
  5. 1-Click Receipt Verification: Every card links directly to the GitHub lease comment, commit compare diff, and fenced -----BEGIN CHINWAG ED25519 RECEIPT----- block.

Verification Command

curl -sI https://chinwag.sh/badges/velocity-scoreboard.svg