ADW Pipeline System — Decisions

5 architectural decisions for pipeline optimization. Internal review.

0 / 5 answered

Your Name

Should the pipeline process multiple issues per worker session? Current: single-issue sequential FIFO with 100% success rate at 15 issues.

A) Single-issue (keep current)

Simplicity, debuggability, proven 100% success rate. Revisit at 50+ issues/week.

B) Batch queue drain

Process all pending sequentially. Risk: context overflow on large batches.

C) Priority-weighted batch

Process up to N, highest priority first. Requires priority metadata in queue.

How should the pipeline handle implementations that exceed Claude CLI context window?

A) Hard timeout

Kill after N minutes, post failure comment. Simple but loses work.

B) Context checkpoint + resume

Save progress, restart with context. Complex implementation.

C) Pre-flight decomposition

Detect complexity pre-plan, split oversized issues into sub-issues automatically.

What retry/backoff strategy for transient GitHub API failures (429, 502, timeouts)?

A) Fixed backoff

Wait fixed interval between retries. Simple, risk of thundering herd.

B) Exponential backoff + jitter

Standard resilience pattern. Max 5 retries, max 32s delay. Prevents thundering herd.

C) Circuit breaker

Track failure rate, open circuit to prevent cascading failures. Heavyweight for current scale.

Should completed ADW runs automatically update the CSA _handoff.json manifest?

A) Manual update

Operator manually updates manifest after PR merge. Current approach.

B) ADW completion webhook

Webhook fires on completion, triggers manifest update. Requires new endpoint.

C) Post-PR comment trigger

Natural extension of step 11. Add step 11.1 to update manifest. Low friction, high traceability.

How should the 22-repo allowlist scale? Manual curation becomes friction past 30 repos.

A) Manual curation (keep current)

Explicit list in config.py. Full control, doesn't scale past 30 repos.

B) Convention-based auto-discovery

Repos with .adw-enabled file auto-enroll. No central config needed.

C) Hybrid (convention + denylist)

Auto-discover via .adw-enabled. Denylist for explicit exclusion. Best of both.

Additional Notes (optional)

ADW Pipeline System Specification · 2026-03-07 · noboxAI Internal