Team Split Assessment: Arda API Proxy

Plan Under Review

• File: Specification § Implementation Phases
• Date: 2026-03-31

Complexity Analysis

Factor	Value	Threshold	Assessment
Total tasks	18	15	Over
Distinct phases with sequential dependencies	4	2	Over
Distinct persona types needed	1 (TypeScript engineer)	4	Under
Estimated working directories	1 (api-proxy worktree)	1	Under
Cross-cutting concerns (handoffs, gates)	1 (type derivation from OpenAPI)	1	Under
Tasks with external validation (builds, tests)	4 (npm install, typecheck, lint, test)	5	Under

Qualitative Factors

• Context window pressure: Low — single repo, repetitive proxy pattern. Each proxy follows the same template, so context from earlier proxies directly informs later ones.
• Error blast radius: Moderate — if shared infra (HttpClient, types, errors) is wrong, all proxies are wrong. Isolating the foundation into Run 1 limits blast radius.
• Natural phase boundaries: Clear checkpoint after Phase 1 — once shared infra + tenant reference + CI are validated end-to-end, the remaining proxies are mechanical.

Recommendation

Split into 2 runs — The project has a natural boundary between establishing the pattern (shared infra, reference proxy, CI) and replicating the pattern (remaining 7 proxies). Splitting here:

1. Validates the entire toolchain (build, test, lint, coverage) before investing in the repetitive work.
2. Limits blast radius — if the shared infra design is wrong, only Run 1 is affected.
3. Keeps each run within a manageable context window.

Proposed Runs

Run	Directory	Description	Tasks	Personas	Est. Duration
1	run-1-foundation/	Repo scaffolding, shared utilities, TenantProxy (reference), CI/CD, spec path corrections	10	back-end-engineer	Medium
2	run-2-proxies-and-publish/	Remaining 7 proxies + types + tests, barrel exports, README, CHANGELOG	12	back-end-engineer	Medium-Large

Artifact Flow

Run 1 produces:

• Initialized api-proxy repository with working build toolchain
• src/shared/ — HttpClient, types, errors (the foundation all proxies depend on)
• src/system/tenant.ts + tenant.types.ts — reference implementation proving the pattern
• tests/shared/ + tests/system/tenant.test.ts — test patterns for subsequent proxies
• .github/workflows/ci.yml + publish.yml — CI/CD pipeline
• Green CI: npm run format:check && npm run typecheck && npm run lint && npm run test:coverage && npm run build

Run 2 consumes:

• The entire Run 1 output as its starting point
• The established proxy pattern (tenant as template) for the remaining 7 proxies

Run 2 produces:

• Complete package with all 8 proxies, full barrel exports, README, CHANGELOG
• Package ready for PR and publish

Risk Analysis

Splitting mitigates:

• Foundation defects propagating into 7 proxy implementations before being caught
• Wasted work if the HttpClient API or type conventions need revision after tenant validation
• Context window exhaustion from a single long session

Coordination overhead is minimal:

• Single agent, sequential runs — no merge conflicts or parallel coordination
• Hand-off is filesystem-only (the worktree state after Run 1 is Run 2’s input)
• Single repository — no cross-repo dependencies

Open Questions and Decisions

#	Question	Options	Recommendation	Decision
	No open questions — all decisions resolved in Decision Log