The Capacity Bottleneck
Creative blocks are rarely motivational failures — they are structural capacity bottlenecks. Bouncing continuously between deep creation tracks and high-frequency distribution alerts forces repeated context-switches, each leaving attentional residue on the prior task and reducing available prefrontal bandwidth for subsequent work. This map identifies the attention cost structure of the creator pipeline and the STSHC v1.0 modifications that protect it.
SC Formula: SC = (MEI + ASI + PRS) − (ABC + SFV) + 7 · Scale: 0–20 · High SFV and ABC from unmanaged pipeline friction directly reduce your SC output before creative work begins.
1
Attention Split Mapping
Two Tracks — Two Distinct Capacity Demands
Core Mechanics
Scripting, recording, long-form editing, design architecture, strategic synthesis
Capacity Demands
High PRS (Pre-Task Focus) and low SFV (Sensory Friction). Requires protected, uninterrupted focus containers.
SC Tier Alignment
Full Availability (17–20) or Baseline Availability (12–16) recommended. Reduce scope during Conservation State (7–11).
Guardrail
Notifications closed. Asynchronous-only communications. 90-min protected focus container.
Core Mechanics
Comment replies, audience analytics, brand negotiations, link routing, inbox management
Capacity Demands
High context-switching load. Increases ABC (Affective Burden) through metric-driven pressure. Elevated SFV if processed reactively.
SC Tier Alignment
Suitable during Conservation State (7–11). Never interleaved with Track A during the same focus block.
Guardrail
Batch-processed only. Strictly isolated to designated daily windows. Hard closure at end of batch window.
2
Structural Workflow Failure Path
What Happens Without Capacity-Aware Architecture
Unmitigated Interruption Cascade
Deep creation
in progress
→
Unplanned interrupt
(ping / analytics alert)
→
Attention residue
on prior task
→
Reduced bandwidth
for re-engagement
→
SC drag:
↑ SFV · ↑ ABC
Theoretical basis (Leroy, 2009 — Attention Residue Theory): Each unplanned context-switch leaves attentional residue on the prior task, substantially reducing processing efficiency in the immediate execution queue. For a practitioner experiencing multiple unplanned interruptions during a creation session, the cumulative attention overhead can be significant — though actual recovery times vary by individual, task type, and interruption severity. This cascade is a theoretical planning model, not a clinical measurement. The STSHC structural modifications below are designed to prevent this cascade from initiating.
Why this matters for SC: Each unmitigated interruption raises SFV and potentially ABC — both negative inputs in the SC equation. As SFV and ABC rise, SC falls. If SC falls below 7, the operator enters Conservation State and Track A deep-focus work is no longer the appropriate routing. The structural modifications below protect SC by reducing SFV and ABC before the session begins.
3
Immediate Capacity-Aware Modifications
Three Structural Changes — Aligned to STSHC v1.0
Modification 1
Isolate the Creation Window — Protected Focus Container
Never begin Track A work with metric tabs, analytics dashboards, or communication streams open in adjacent browser tabs or windows. Secure a strict 90-minute protected focus container for Track A variables — notifications closed, messaging applications minimized, and all Zone B (communication triage) elements deferred to your batch window. This directly reduces SFV before the session begins and protects PRS for the duration of the container.
Modification 2
Batch-Process Track B — Designated Communication Windows
Allow all inbound community management, comment engagement, and distribution triage traffic to accumulate in your asynchronous queue and process it exclusively during your two designated daily batch windows. Treat Track B as a discrete, time-bounded task block — not an ongoing interruption cycle running in parallel with Track A.
Modification 3
Route by SC Tier — Not by Clock Time
Before beginning any session, score your morning SC using the STSHC Creator Capacity Planning Ledger. Route your task allocation to match your current capacity tier — not an arbitrary time-based schedule. If your SC places you in Conservation State (7–11), pull Track A deliverables and route to Track B administrative overhead or low-friction tasks instead. Do not force deep creative work at a capacity tier that does not support it.
Guardrail: If MEI = 1 OR ASI = 1 — Workload-Reduction Guidance is active regardless of total SC score. Suspend both Track A and Track B active tasks. Refer to the STSHC Creator Capacity Planning Ledger for routing guidance.
17–20
Full Availability
12–16
Baseline Availability
7–11
Conservation State
0–6
Restoration State
Important limitation: SC tier boundaries are theoretically derived and will be empirically calibrated during Phase 3 validation. Treat all routing suggestions as approximate planning ranges, not precise clinical thresholds. Scores carry inherent self-report variance. Day-to-day fluctuations of 2–3 points are expected and do not indicate meaningful capacity change.