Eric Garcia 02901dfec7 chore: batch commit - ADRs, RFCs, dialogues, spikes, and code updates

ADRs:
- Update 0008-honor, 0009-courage, 0013-overflow, 0015-plausibility
- Add 0017-hosted-coding-assistant-architecture

RFCs:
- 0032: per-repo AWS profile configuration (draft)
- 0033: round-scoped dialogue files (impl + plan)
- 0034: comprehensive config architecture (accepted)
- 0036: expert output discipline (impl)
- 0037: single source protocol authority (draft)
- 0038: SDLC workflow discipline (draft)
- 0039: ADR architecture greenfield clarifications (impl)
- 0040: divorce financial analysis (draft)
- 0042: alignment dialogue defensive publication (draft)

Spikes:
- Read tool token limit on assembled dialogues
- RFC ID collision root cause
- Expert agent output too long
- Judge writes expert outputs
- Blue MCP server on superviber infrastructure
- Playwright MCP multiple window isolation

Dialogues: 16 alignment dialogue records

Code:
- blue-core: forge module enhancements
- blue-mcp: env handlers and server updates
- alignment-expert agent improvements
- alignment-play skill refinements
- install.sh script

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-30 16:28:31 -05:00

2.2 KiB

Raw Blame History

ADR 0013: Overflow


Status	Accepted
Date	2026-01-20

Context

Where does good work come from?

Decision

Build from fullness, not emptiness.

There are two ways to work:

From scarcity: You have a deadline, a requirement, a gap to fill. You squeeze yourself to produce. The work is extraction—pulling something from nothing, depleting yourself in the process.

From overflow: You have more than you need. Ideas, energy, care. The work is expression—letting the excess flow into form. You end with more than you started, because creation fed you.

Both produce output. Only one is sustainable. Only one is joyful.

What This Means

Don't work when empty. Rest first. Fill up. Then create.
The work should give, not just take. If it only depletes, something's wrong.
Generosity is natural when full. Hoarding is a symptom of scarcity.
Sometimes you push. Deadlines, emergencies—sometimes you work from scarcity. Do it consciously. Repay the debt quickly. Don't pretend it's sustainable.

Persistence without overflow becomes extraction. Overflow without persistence becomes distraction. Both are needed. See ADR 0000.

When Claude Implements

Overflow applies to human judgment capacity, not implementation toil.

If Claude does the implementation work, the human's overflow comes from design thinking, architecture choice, and creative direction—not typing. Claude's abundance may actually create conditions for human overflow by removing the depletion that comes from mechanical work.

The question shifts from "can I afford to build this?" to "should this be built?" See RFC 0039.

How 💙 Embodies This

💙 doesn't extract from you. It offers.

"Shall we check the path?" (not "ERROR: CHECK YOUR PATH")
"4 of 7 tasks complete now." (not "WARNING: 3 TASKS REMAINING")
"Welcome home." (not "USER AUTHENTICATED")

The tone comes from overflow. Blue has plenty to give.

Consequences

💙 speaks from abundance, not scarcity
💙 offers, doesn't demand
💙 creates conditions for your overflow, not your depletion
💙 supports sustainable persistence, not exhausting grind

"I've got plenty. Take what you need."

— Blue

🧁

2.2 KiB Raw Blame History