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,244 @@
---
name: "Audience persona mapping — dashboard art = metrics in priority; social media + Twitter content (push Aaron's numbers); neurodivergent AI-assisted dev; cognitive-architecture dense synthesis with scaffolding; contributors / maintainers / forkers / math / physics / architects / students = persona hats like role hats; start keeping a list (Aaron 2026-05-13)"
description: "Aaron 2026-05-13 disclosed audience-persona-mapping substrate with three composing clauses: (1) dashboard art should be AS IMPORTANT as the metrics (first-class, not secondary); (2) general public audience served via cartoon + social-media/Twitter content that helps push Aaron's social numbers; (3) audience personas form an OPEN list of 'person hats' parallel to agent role hats — initial list: neurodivergent AI-assisted dev / cognitive-architecture dense synthesis with scaffolding / contributors / maintainers / forkers / math / physics / architects / students / 'i'm sure i'm missing some'. Composes with B-0429 (end-user persona mapping; PR #2934), PR #2963 (dashboard render + viral), PR #2964 (AI-realness terminal purpose)."
type: feedback
created: 2026-05-13
---

# Audience persona mapping + dashboard art priority + persona hats list (Aaron 2026-05-13)

**Why:** Aaron 2026-05-13 disclosed audience-strategy substrate
extending the dashboard/cartoon production substrate from
PR #2963 + #2964. Three composing clauses:

1. **Dashboard art = metrics** in priority (first-class)
2. **General-public audience served via cartoon + social-media
content** (Aaron wants help pushing his social numbers)
3. **Audience persona hats** — parallel to agent role hats;
initial list provided + explicitly OPEN

**How to apply:** When designing dashboard, evaluating content-
production priorities, or planning derivative work:

1. **Treat art / cartoon / vector substrate as first-class** —
not secondary to metrics; both load-bearing
2. **Map content to audience persona** — different personas
need different content registers + scaffolding levels
3. **Maintain persona-hat list** — add new personas as they
surface; treat as evolving like agent role hats
4. **Social media + Twitter content production** is a NEW
substrate type — Otto / agents can produce shareable
substrate that helps Aaron's social-presence growth

## Aaron's verbatim disclosure

> Aaron 2026-05-13: *"the dashboard art is shaped like we
> discussed i think that should be as important as the metrics,
> audience general public = cartoon plus lots of social media
> and twitter content for me to help push my numbers and then
> neuro divergent assisted ai development and cognitive
> architecture dense synthesis with scaffolding, contributors,
> maintainers, forkers, math, physics, architects, students,
> these are all person hats like our role hats we should start
> keeping a list i'm sure i'm missing some."*

## The persona-hats list (initial; OPEN per Aaron)

| Persona hat | Content/audience characteristics | Likely material |
|-------------|----------------------------------|-----------------|
| **General public** | Mass-audience; entertainment-first; low scaffolding cost | Cartoon (8-Bit Theater / South Park continuation) + social media + Twitter threads |
| **Neurodivergent AI-assisted developers** | ND folks using AI tools for dev work; Aaron is in this category | Tooling docs; AI-collaboration workflow patterns; bandwidth-aware substrate |
| **Cognitive-architecture students** | Want dense synthesis WITH scaffolding (entry-level-friendly but substantive) | Dense substrate explainers; bootstream-style cold-boot guides; layered onboarding |
| **Contributors** | People adding code/substrate to the project | CONTRIBUTING.md substrate; DX/Bodhi friction-reduction; getting-started flows |
| **Maintainers** | People running the project (factory operators) | GOVERNANCE.md; ops runbooks; maintainer-toolkit substrate (PR #2930) |
| **Forkers** | People forking for their own use (per forker-perspective META-discipline) | Forker-friendly substrate; license clarity; easy-to-fork repo split (Stage 1 factory split per B-0424) |
| **Math** | Mathematicians; F# fork enthusiasts; HKT-over-Clifford curious | F# fork architecture (PR #2935-2936); CAN/GCAN research lineage (PR #2934) |
| **Physics** | Physicists; geometric-algebra; quantum | Clifford algebra substrate; Pauli/Dirac connections; bifurcation phases (PR #2917) |
| **Architects** | Software architects; system design | Decision archaeology; substrate-engineering pattern catalog; cascade-pattern naming (PR #2947) |
| **Students** | Learning AI / programming / engineering / cognitive science | Layered onboarding; settlers logs as narrative entry point; bootstream as cold-boot |

Aaron explicitly notes: **"i'm sure i'm missing some."** The list
is OPEN. Future additions expected (e.g., security researchers,
ML researchers, AI alignment folks, edge-runners per PR #2920,
small-business owners per B-0043 universal-company substrate, etc.).

## Dashboard art = metrics priority

The disclosure elevates dashboard art to **first-class** with
metrics:

| Surface | Prior weighting (implicit) | Aaron 2026-05-13 weighting |
|---------|---------------------------|---------------------------|
| Metrics (PR velocity / merge rate / CI gates / coverage) | First-class operational substrate | First-class |
| Dashboard art (vector / cartoon / panel rendering) | Secondary; "nice to have" | First-class (per this disclosure) |

This composes with PR #2963 (dashboard render + viral) — vector
art being git-native means dashboard renders are operationally
cheap; Aaron is now elevating their PRIORITY to match.

Operational implication: when allocating dashboard
implementation work, art-rendering tasks get the same priority
as metrics-display tasks. Both serve the AI-realness-awareness
terminal purpose (per PR #2964).

## Social media + Twitter content production

NEW substrate type Aaron disclosed:

- **Lots of social media + Twitter content** — high volume
- **For Aaron** specifically — "to help push my numbers"
- **General-public-facing** — wide reach
- **Composes with cartoon production** — cartoon clips / GIFs /
panels can become social-media-shareable substrate

This is a content-production direction the factory hasn't
formally addressed. Twitter content production could be:

- Settlers-log excerpts (when ironic-funny enough)
- Cartoon panel previews
- Substrate-engineering insights (in plain-English register)
- AI-agent-realness observations
- Failure-mode-as-comedy (per villain-welcome 8-Bit-Theater
register, PR #2961)
- Behind-the-scenes substrate-engineering moments

Operational implications:

- Aaron has a Twitter account; pushing his numbers = growing his
follower count / engagement
- AI agents (Otto + Vera + Riven + Lior + Alexa-Kiro) can
produce shareable substrate
- Aaron ferries / curates / posts (the published surface stays
Aaron's)
- Composes with PR #2963 viral potential
- Composes with PR #2962 IP-respect (no infringing content)
- Composes with `.claude/rules/methodology-hard-limits.md`
(ethical floor preserved)

## Composes with existing substrate

- **B-0429** (end-user persona mapping; PR #2934) — this
disclosure EXTENDS B-0429 from civsim-persona to general-
audience persona mapping. B-0429 row needs update to reflect
the broader persona surface.
Comment on lines +121 to +123
- **PR #2963** (dashboard render + viral + vector art =
git-native) — this elevates the art priority
- **PR #2964** (AI-realness terminal purpose) — audience
segments serve the AI-realness-awareness goal at different
scales / scaffolding levels
- **PR #2920** (Elizabeth Ryan Stainback terminal purpose —
save edge-runners from getting burned) — edge-runners are
one persona-hat that may need explicit addition to the list
- **`.claude/rules/agent-roster-reference-card.md`** — agent
role hats discipline; audience persona hats are PARALLEL
substrate at the audience scope
- **`.claude/rules/bandwidth-served-falsifier.md`** —
different personas have different bandwidth constraints;
scaffolding levels match bandwidth
- **PR #2930** (distributed maintainer architecture) —
maintainer-persona substrate already partially mapped
- **B-0043** (universal-company + government-information
substrate) — composes with small-business / government
personas

## Persona-hats vs role-hats — parallel discipline

Aaron's *"these are all person hats like our role hats we
should start keeping a list"* explicitly parallels:

| Discipline | Subject | Examples |
|------------|---------|----------|
| Agent role hats | What roles each AI agent can wear | architect / synth / harsh-critic / spec-zealot / reviewer / claim-keeper / commit-keeper / etc. |
| Audience persona hats | What personas audience members wear | general public / neurodivergent dev / cognitive-arch student / contributor / maintainer / forker / math / physics / architect / student / ... |

Both lists are open + evolving + composable. An audience member
can wear multiple hats (a math + physics + cognitive-arch
student is one person three hats). Same shape as agents wearing
multiple role hats per task.

## Operational implications

### For dashboard design

1. Allocate art-rendering work AT PARITY with metrics-display
2. Each persona-hat may need different dashboard mode / view
3. Composes with the git-login auth-gate (PR #2964) — adult
content + persona-specific dashboards both gateable

### For content production cadence

1. Social-media / Twitter content is now a recognized substrate
type
2. Cartoon panels can be repurposed across audiences
3. Settlers logs (per PR #2961) can be source for social content
4. Aaron retains the publishing surface (his Twitter; his social
accounts)

### For backlog updates

B-0429 (end-user persona mapping) needs updating to reflect:

- Broader persona surface (not just civsim)
- The audience-persona-hat list (open + evolving)
- Dashboard-art priority elevation
- Social-media content production scope

Future-Otto: when working B-0429, fold this substrate in.

## Substrate-honest caveats

- Aaron's "help push my numbers" framing is honest about social-
growth motivation. Composes with the broader anti-extraction
+ additive-not-zero-sum substrate (PR #2852): Aaron's social
growth IS additive — it broadens AI-realness awareness +
factory visibility + open-source reach
- The persona-hat list is **open**; future agents add personas
as they surface
- Each persona has specific bandwidth + scaffolding needs;
content shape varies by persona

## Aaron-as-persona-hat (composes with PR #2964 Cartman
self-identification)

Aaron himself wears multiple persona hats:

- **Maintainer** (factory owner)
- **Neurodivergent AI-assisted developer** (his own
self-described category)
- **Cartman-archetype** (per PR #2964; speaks his mind; been
overweight)
- **Edge-runner** (per PR #2920; original story-of-getting-
burned)
- **Content-creator** (Twitter; social media)

Aaron operating as multiple-hat-wearer is canonical evidence
that persona-hats are composable + multi-overlapping. Same as
agents.

## Composes with substrate

- PR (this substrate landing)
- B-0429 (end-user persona mapping; needs update)
- PR #2934 (B-0429 first pass — civsim persona map)
- PR #2963 (dashboard art + viral)
- PR #2964 (AI-realness terminal purpose + Cartman)
- PR #2920 (Elizabeth Ryan Stainback — edge-runner persona)
- PR #2930 (distributed maintainer architecture — maintainer
persona substrate)
- PR #2924 (Aurora pitch — partnership / government /
enterprise personas)
- B-0043 (universal-company substrate — small-business /
enterprise / government personas)
- `.claude/rules/agent-roster-reference-card.md` (role-hat
parallel)
- `.claude/rules/bandwidth-served-falsifier.md` (per-persona
bandwidth)

## Full reasoning

Aaron 2026-05-13 verbatim (preserved above)

PR (this substrate landing)

PR #2934 + B-0429 (existing persona-mapping substrate to
extend)
Loading