Structured Data Extraction
Your structured data extraction pipeline processes 10,000 contracts per day using a main Claude Code session. For each contract, the pipeline loads a shared 8,000-token legal taxonomy into context, then runs an extraction pass. To handle a sudden spike in document volume, a teammate proposes parallelizing extraction by spawning a separate worker for each document. They suggest using forks rather than named subagents, arguing it will be cheaper. Examining the architecture, you realize the team also wants each worker to use a lightweight, cost-optimized model rather than the main session's model. Which constraint makes forks the wrong choice here, despite their caching advantage?