Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. The one Claude account behind Clara's draft replies and other background AI work is used up for the week and comes back Nov 10. Should we add a second account to it, or wait out the six days?
The full question, as raised
claude-pool-remote holds ONE account (status.json 2026-11-04T23:35Z: state=capped, status_7d=rejected, util_7d=1.0), published as the single bearer to propflow-anthropic-background-auth-token (ECS worker), SSM /propflow/prod/ANTHROPIC_BACKGROUND_AUTH_TOKEN (Lambdas) and Vercel production. The shadow lane hit its cap with reset 2026-11-10T15:00Z, i.e. the week's allotment went in ~33h. Until then shadow runs and staff drafts are parked (shadow_pool_cap_resume_v1 resumes them after reset; RESUME_GIVE_UP_MS is 7 days, so they will draft ~6 days late). Gera 2026-10-28 made this pool one dedicated account never shared with the fleet. Add a second dedicated account to claude-pool-remote (remote-pool step republishes a 2-bearer rotation), or hold to one account and accept the pause?
Why, and what was tried
The session raising this recommends: Add a second account to it One account lasted about 33 hours of a 7-day week, so the drafts staff rely on are off for six days; a second subscription account costs no metered money. Tried first, unsuccessfully: Confirmed the code is behaving as designed: the capped pool parks the runs and resumes after the reset, nothing billed metered, nothing sent. Read the remote-pool status: exactly one account, weekly usage at 100%, publish in sync on all three targets. Checked open decisions for an existing one on this pool: none. Did not touch the pool or any secret: adding an account reverses the one-dedicated-account design and is a production secret change.