---
name: psyche-ccs-bigscreen-spend-limit
description: "Psyche outage 2026-07-26 FINAL — stale read_env stamp threaded the ccs bigscreen account into psyche spawns; bind carry-forward made the stamp immortal; two \"artifact\" calls were wrong"
metadata: 
  node_type: memory
  type: project
  originSessionId: be7bfd34-b9fc-44e1-b3c3-8e74e9fe1d2f
  modified: 2026-07-26T22:27:06.253Z
---

2026-07-26 psyche outage, FINAL RECORD (supersedes two earlier wrong versions of this file — first said "psyche threads ccs config" with the wrong mechanism, second said "default account limited"; both revised on measurement):

**Chain, every link measured:** the CCS bigscreen account hit its monthly spend limit (operator probe: `claude -p` fine, `ccs -p` limited; my clean-env probe: default account healthy). Psyche turns reached that account because `REQ-PSYCHE-SPAWN-ENV-PARITY` (lifecycle.rs run_psyche_event_turn) threads the parent record's `read_env` stamps into every psyche spawn, and doyle+todlando `info.json` still carried `CLAUDE_CONFIG_DIR=…\.ccs\instances\bigscreen` captured at a July-6-era ccs bind. The stamp was IMMORTAL: the bind path (spt/src/api/startup.rs, REQ-DIGEST-PROFILE-ENV) carries the prior capture forward whenever the var is absent at bind — revive-protection that makes profile MIGRATION inexpressible. Remediation 2026-07-26: stamps cleared from both records by hand; code fix = bind re-captures verbatim (absent = absent) on fix/readenv-stale-carry.

**Epistemics debt:** hertz's spawn-env capture (bigscreen) AND their brain-env check (clean) were BOTH true at different layers; doyle dismissed the first as repro artifact. Two true-seeming-conflicting measurements = a missing LAYER, not a wrong instrument. Also: the refusal text rides inner-claude STDOUT with stderr empty (why stderr-only views showed nothing); exit-96 chain field-proven live same day; core-side 96 recognition still deferred (REQ-PSYCHE-ACCOUNT-REFUSAL-EXIT impl, post-W1).

**How to apply:** psyche loop-fails → read the strike line's dual tails (claude-spt ≥0.25.15 classifies 96/REFUSED); then check the endpoint's `info.json` `read_env` for stale profile stamps BEFORE blaming accounts or adapters. Related: [[v0431-published]], [[stale-snapshot-equality-proxy]] (same family: a snapshot standing in for current intent).