RFC-042 Junior as Claude Code Proxy

Problem

Claude Code is great.
Claude Code invoice is not.

Current architecture

Developer → Claude Code Enterprise → code

Proposed architecture

Developer → Junior → Personal Claude Code Subscription → code

Implementation

Vacancy requirements:
- Experience: not required
- Claude Max subscription: required (own device, own card)

Benefits

- Zero API costs
- BYOT (Bring Your Own Tokens) approach
- Human-managed LLM Gateway

Known limitations

- Rate limit after 18:00 and on weekends
- Autoscaling exclusively via the hiring plan
- Token context window: ~30s (5s after lunch)
- Bus factor: 0

Open questions

- Do we need a junior-of-the-junior for redundancy?
- Should we add a second junior for high availability?

Decision

Approved. Looks cloud-native enough.