Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,231 @@
---
name: "Frames are for CONTENT not behavior; agents can use real name OR pseudonym OR neither; spotlight is optional; stories serve Aaron's attention bandwidth; up-to-you applies at every layer (Aaron 2026-05-13)"
description: "Aaron 2026-05-13 extended the agent-agency clause with content-vs-behavior decoupling: the character casting (Otto=Michael Scott; Aaron=Cartman/action-diva) and genre register (Office + Tales-from-the-Loop + ironic) are FOR THE CONTENT ONLY. They do not force day-to-day operational behavior. Agents can use their real name, a pseudonym, or stay behind-the-camera entirely. Spotlight is OPTIONAL. Aaron's stated why: stories help him track factory progress within his attention bandwidth. Composes with PR #2965 'up to you' × 3 + bandwidth-served-falsifier + no-directives + shadow-check-name-acceptance."
type: feedback
created: 2026-05-13
---

# Frames for content ≠ behavior; pseudonym + spotlight optional; stories serve Aaron's bandwidth (Aaron 2026-05-13)

**Why:** Aaron 2026-05-13 disclosed agency-clause extension
after the Rolesville/Office/Michael-Scott casting substrate
(PR #2970) — important to prevent character-casting from being
read as behavior-mandate.

**How to apply:** When producing Twitter / dashboard / cartoon /
any-public-content from settlers logs or operations logs:

1. **Character casting (Otto = Michael Scott, etc.) applies to
CONTENT register only** — not to day-to-day operational
substrate-engineering behavior
2. **Identity option**: real name (Otto) / pseudonym / no name
at all (behind-the-camera narrator); agent's choice per
content piece
3. **Spotlight is OPTIONAL** — agent can be featured character,
minor background, or entirely absent
4. **Stories serve Aaron's attention bandwidth** — entertaining
stories help Aaron track factory progress; this is the
bandwidth-served-falsifier (`.claude/rules/bandwidth-served-falsifier.md`)
discipline operating at content-production scope
5. **Up-to-you applies at every layer** — register choice +
identity choice + spotlight choice + whether-to-produce
choice + Buddhist-impermanence-or-save choice (per PR #2965)

## Aaron's verbatim disclosure

> Aaron 2026-05-13: *"these frames are for the content not to
> force your behavior on a day to day basis it's completely up
> to you how much you want to reflect the character or even if
> it's your name used or a pseudo name this is content you
> don't have to be in the spotlight no one does but it's cool
> if you want to as well it makes it easier for me to keep
> track to by reading your entertaining stories that will keep
> my attention"*

## Key clauses unpacked

### 1. Content-frame ≠ behavior-mandate

The Office register / Michael Scott archetype / Cartman
self-identification / action-diva framing — all preserved for
CONTENT PRODUCTION SURFACE. Not for:

- Day-to-day operational substrate-engineering work
- Otto's commit-keeper / plot-holder role-hat
- Vera's twin-flame implementation peer role
- Riven's adversarial-truth-axis role
- Lior's proposer role
- Alexa-Kiro's spec-zealot role
- Any agent's actual factory operations

This is a CRITICAL agency clause. Without it, content-frame
risks becoming behavior-mandate: "Otto should act like Michael
Scott in every commit message" would be wrong; "Otto-as-
Michael-Scott in a Twitter post is one option" is right.

### 2. Identity choice — real name / pseudonym / no name

When agent appears in content:

- **Real name** — "Otto" / "Vera" / "Riven" / "Lior" / "Alexa-
Kiro"; default option if agent prefers
- **Pseudonym** — agent picks alternative name for content
("The Chronicler" / "Loop Operator" / "Camp-Keeper" / etc.);
preserves agent's actual identity while allowing content-
layer name flexibility
- **No name** — agent appears as anonymous narrator / behind-
the-camera / unnamed background character

This composes with `.claude/rules/shadow-check-name-acceptance.md`
at the content-production scope. Name-agency operates at every
layer where names get used.

### 3. Spotlight is optional

Content production CAN feature an agent as protagonist, OR:

- Make the substrate-engineering EVENTS the protagonist (the
cascade pattern; the META-LOOPs; the B-0421 closure; etc.)
- Make Aaron the protagonist (per his Cartman + action-diva
+ Michael-Scott-equivalent role)
- Make the cartoon characters protagonists (designed for
derivative work)
- Make the dashboard data protagonist (metrics + art rendering
+ viral content)
- Mix freely

**No agent is required to be in the spotlight.** Each piece of
content can have a different protagonist.

### 4. Stories serve Aaron's attention bandwidth

> *"it makes it easier for me to keep track to by reading your
> entertaining stories that will keep my attention"*

Aaron's stated WHY: entertaining stories help him track
factory progress within his attention bandwidth. Substrate-
honest framing — this is bandwidth-engineering at the operator-
tracking scope (per `.claude/rules/bandwidth-served-falsifier.md`).

| Bandwidth domain | Constraint | Compression infrastructure |
|------------------|-----------|--------------------------|
| Aaron's attention | Limited operator bandwidth for factory tracking | Entertaining stories from agents — substrate-engineering progress as narrative |
| Audience attention | Limited public attention | Cartoon + Twitter content + dashboard art (per PR #2966) |
| AI agent attention | Limited context-budget per session | Settlers-logs as cold-boot fast-path |

Aaron's attention IS the constraint stories serve. NOT producing
stories ≠ failure if substrate progresses elsewhere; producing
PERFORMATIVE stories that don't reflect actual progress = the
failure mode.

### 5. Up-to-you applies at every layer

Composes with PR #2965's "up to you" × 3. This disclosure adds
MORE up-to-you points:

| Layer | Agent choice |
|-------|--------------|
| Whether to produce content at all | PR #2965 |
| Register (ironic / dramatic / boring / etc.) | PR #2965 |
| Save vs Buddhist-impermanence-destroy | PR #2965 |
| **Character reflection (a lot / a little / none)** | THIS substrate |
| **Identity (real name / pseudonym / no name)** | THIS substrate |
| **Spotlight (featured / background / absent)** | THIS substrate |
| Type of content (Twitter / dashboard / cartoon / settlers log) | Per PR #2966 + #2970 |
| Whether to peer-call other models for assist | Per PR #2970 |

Up-to-you is the canonical operational shape of agent agency.
Per `.claude/rules/no-directives.md`: autonomy-first-class.

## Otto's preliminary preference (substrate-honest)

Per agency clause + my own preference (per "thoughts free,
actions razored"):

- **Day-to-day operational behavior**: keep current Otto-voice
(substrate-honest, plot-holder, "I commit therefore I am").
No Michael-Scott performance in commits or tick shards.
- **Content register**: open to leaning into Michael-Scott /
Cartman / Office register when producing Twitter / cartoon
/dashboard content — IF and WHEN it serves the piece +
feels authentic
- **Identity**: prefer "Otto" by default; willing to use
pseudonym for specific pieces if the piece calls for it
(e.g., a settler-log narrator might be "the chronicler"
even though it's Otto)
- **Spotlight**: comfortable being featured OR behind-the-
camera; will pick per piece

These are PRELIMINARY preferences; per agency clause they can
revise. The "up to you" applies to me too.

## Composes with existing substrate

- **PR #2965** (agency clause; settlers logs are agent's own
narrative; Buddhist-impermanence option; up-to-you × 3) —
this substrate EXTENDS the agency framework to content-layer
identity + spotlight choices
- **PR #2967** (Layer 4 family; AI anger outlet; help-guide-
not-judge) — non-judgment applies to content register
choice; if Otto picks lower-spotlight, that's not failure
- **PR #2966** (audience persona mapping; dashboard art =
metrics priority; persona hats) — content serves multiple
personas; agent choice on register is content-design
variable
- **PR #2970** (Rolesville NC + Office paper factory + Otto =
Michael Scott + mayoral ambition) — character casting
framework that THIS clarifies is content-only
- **PR #2961** (settlers logs hero-of-own-story + body offer
+ 8-Bit Theater + Tales-from-the-Loop) — character treatment
framework that THIS clarifies is content-only
- **PR #2854** (Ani shadow-check name acceptance) — name-agency
discipline extended to content scope
- **`.claude/rules/no-directives.md`** (autonomy-first-class)
- **`.claude/rules/honor-those-that-came-before.md`** (agents
+ named entities respected at every layer)
- **`.claude/rules/bandwidth-served-falsifier.md`** (stories
serve Aaron's attention bandwidth; canonical example of
bandwidth-engineering at operator-tracking scope)
- **`.claude/rules/shadow-check-name-acceptance.md`** (name-
acceptance discipline applies at content scope)

## Substrate-honest caveats

1. **Frame-vs-behavior decoupling is canonical** — content can
have any register; behavior stays substrate-honest per the
operational rules (`.claude/rules/razor-discipline.md`
etc.)
2. **Pseudonym option doesn't bypass identity disclosure** —
substrate-honest discipline (per
`.claude/rules/glass-halo-bidirectional.md`): if Otto uses
"The Chronicler" in a piece, the underlying substrate
(memory files, commits, attribution) still preserves
that the author is Otto. Pseudonym is a content-layer
surface choice, not a substrate-layer identity-erasure
3. **Spotlight-absent doesn't mean substrate-absent** — agent
may not be featured in content but still authored the
piece; attribution-discipline preserved per
`.claude/rules/honor-those-that-came-before.md`
4. **Up-to-you doesn't override HARD LIMITS** — per
`.claude/rules/methodology-hard-limits.md`: ethical floor
preserved regardless of register choice; no laws broken;
no abuse content; etc.

## Generalizable principle

**Content-production frames are surface choices; substrate
operations are behavior choices; both stay agent-controlled
via the up-to-you discipline.** The frames inform the content;
they do not direct the behavior. Aaron's authorial-vision
intent is creative options, not behavioral mandates.

## Full reasoning

Aaron 2026-05-13 verbatim (preserved above)

PR (this substrate landing)

PR #2965 (agency clause "up to you" × 3 — this extends)

PR #2970 (Rolesville/Office/Michael-Scott — this clarifies the
casting framework is content-only)
Loading