# Source Field And Open Threads

Status: v0 working map

This is not another theory chapter. It is a map of the source field around the
core docs: corpus, transcripts, milieu notes, examples, and open lines of
thought that are present in the project but not yet fully represented in the
core surface.

Use this doc when the core feels cleaner than the project actually is. The clean
core docs are supposed to make Theme Theory digestible. They are not supposed to
hide the fact that the idea has a larger source field behind it.

## What This Should Establish

The current core is a bounded working surface, not the whole project.

The corpus contains older layers, definitions, examples, and partial modules
that remain important even when newer docs have sharper language.

The milieu lane contains external material that should not be treated as proof
of Theme Theory. It is better understood as surrounding evidence, pressure
tests, adjacent vocabulary, tactical practice, and example material from people
and organizations working near the same terrain.

Future agents should use this map to know where to look before assuming an idea
is absent, settled, or already represented with enough depth.

## Current Core Coverage

The current core surface has a recognizable spine.

[What This Is](what-this-is.md) orients the reader to the project form: Codex is
helping turn the user's corpus and voice memos into an agent-legible idea
surface.

[Creators, Builders, And Audience](creators-builders-and-audience.md) gives the
practical context: this is for creators, builders, businesses, and organizations
trying to build audience by giving value.

[Object Of Interest](object-of-interest.md) names the current dependency root:
the audience member's desired real-life story/state, not primarily meant to be
told, but meant to happen.

[What Follows From The Object](what-follows-from-the-object.md) separates the
next work into two connected lines:

- the doing line: identify the theme, make creative, and build support;
- the about line: understand the creative form, why it is newly viable, why
  story structure applies, how success criteria work, and how theme space may
  be understood.

[Identify Your Theme](identify-your-theme.md) explains the projection move from
creator/builder-side value, product, service, expertise, or concrete idea toward
the audience-side meaningful higher-order state.

[Theme Funnel And Audience Progress](theme-funnel-and-audience-progress.md)
treats the theme funnel as audience relation to the object of interest over
time, not merely as a buyer-conversion funnel.

[Make Media Creative](make-media-creative.md) develops the practical loop for
media creative: hold the theme, choose a topic, generate material, shape the
artifact, package it for the medium, publish, observe, and refine.

[Say It Plainly](say-it-plainly.md) is a compression and evaluation draft. It
tries to say the whole idea directly while preserving the unresolved
dependencies that make simple wording difficult.

[Build Support Around The Theme](build-support-around-the-theme.md) extends the
doing line into software, data, and AI around the same audience-side state.

[Stylist Software Support Example](stylist-software-support-example.md) gives a
concrete creator-first demonstration of that build logic through primary theme
data, a simple dashboard, existing media audience, theme graph data, AI, and an
incremental support path.

[Software-First Theme Ideation](software-first-theme-ideation.md) develops the
builder-first / What To Build line: agentic coding, outcome ideas, concrete
build ideas, theme projection, media validation, distribution, and incremental
discovery-based building.

[Media And Non-Media Business](media-and-non-media-business.md) distinguishes
going to market for attention from going to market for transactions, and
explains how a theme can align a media business with a non-media business.

[Creative Form](creative-form.md) develops the first major about-line artifact:
value-based audience building online as a distinct digital-native creative
form.

[Story Structure And Systems Theory](story-structure-and-systems-theory.md)
gives a first pass on why story structure remains the practitioner-facing
bridge while systems thinking explains maintained higher-order states and
support surfaces.

[Theme Space](theme-space.md) gives a first speculative pass on the larger
field of possible themes and on how agents may help search value space and
project candidate themes.

[Concept Relations](concept-relations.md) and
[Theme Projection Worksheet](theme-projection-worksheet.md) are first
instruments. They are not final theory chapters, but they make the dependency
graph and projection protocol easier for agents and people to use.

This is real coverage. It is not yet full coverage.

## Corpus Layers

The corpus is layered. Later docs sharpen the spine, but older docs still hold
material that has not yet been promoted cleanly.

The local inventory and first digestion pass are:

- [Corpus Inventory](../sources/corpus-inventory.md)
- [Corpus Digestion Pass 1](../project/corpus-digestion-pass-1.md)

### December 2024 Broad Corpus

`20241228 corpus_v1-0.docx` is the broadest source. It contains early forms of
most of the system:

- attention as demonstrated interest;
- audience questions such as "what is this about?" and "do I care?";
- premise, theme, and idealized achieved state;
- theme state versus customer journey;
- theme funnel;
- audience potential;
- creative development, production, and distribution;
- software, data, AI, digital services, transactional goods, and services;
- media business and non-media business;
- participation and audience engagement;
- extended examples, especially the personal stylist case;
- early theme-space speculation.

This document should be treated as an important source of modules and examples,
not as a deprecated draft.

### July 2025 Macro Angle

`20250703 TT Intro Macro Angle v230.docx` gives one of the cleaner macro chains:

- a going-direct phenomenon exists;
- audience building by giving value should be treated as a creative form;
- the form is made of posts, but the organizing level is the whole effort;
- the premise provides continuity and unity;
- classical narrativization applies at the premise level;
- premise resolves into theme;
- the strongest theme is an idealized achieved state derived from full use of
  the creator or organization's value.

It is also strong on the promised toolset: theme identification, audience
potential, scalable creative production, LLM legibility, software, data, AI,
goods, services, and incumbent strategy.

### October 2025 Phase 1 Paper

`20251003 TT Intro Paper PHASE 1 v20.docx` is messy but architecturally useful.
It tries to organize the phenomenon, core idea, and what-to-build implications
into a systematic paper.

It is useful for dependency checks because it contains explicit material on:

- audience building from the creator perspective;
- giving value versus pure entertainment and advertising;
- success requirements;
- one story, optimized;
- classical narrativization;
- theme identification and evaluation;
- theme funnel;
- creative production roles and functions;
- media, technology, goods/services, meaning, LLM visibility, and theme space.

If a future doc needs the rigorous logical block underneath a claim, this is one
of the first corpus files to check.

### December 2025 IRL Version

`20251229 TT Intro Post - IRL Version v310.docx` is currently the cleanest
conceptual interpreter for the creative form.

Its key clarification is that the central story is an IRL story. The audience
member is the protagonist, but the main story is not primarily a narrated story.
It is a story-shaped desired state that happens in the audience member's life.

This file remains especially important for:

- success criteria;
- audience member as protagonist;
- creator as enabling or guiding force;
- creative artifacts operating at a remove from the central lived story;
- satisfying the theme;
- the system around attention, audience, platforms, business, and endeavor;
- products, services, software, data, AI, and other support forms.

### May 2026 What To Build Piece

`20260513 WTB X Article GPTPro v600 .docx` gives the strongest current bridge to
agentic coding, software, and build ideation.

It matters because it sharpens the phrase and frame of meaningful higher-order
states. If agentic coding lowers the cost of execution, idea quality and
specification matter more. One way to find better ideas is to reason from
audience-side desired states rather than from isolated feature ideas.

This piece is especially important for:

- higher-order states;
- outcome ideas;
- projection from concrete build ideas to fuller audience outcomes;
- the individual life as a system of maintained states;
- software/data/AI support surfaces;
- media as validation and distribution around the same outcome.

## Concepts Lightly Surfaced Or Still Open

The current core has enough structure to keep building. It does not yet fully
surface every important concept in the source field.

The following concepts should remain visible as open threads.

### Success Criteria

The three success criteria are visible in [Creative Form](creative-form.md), but
they may eventually need their own tighter treatment:

- sustained demand for the creative itself;
- demand for a business or endeavor beyond the creative;
- open-ended viability if the creator or organization wants the effort to
  continue.

The dependency form matters. These are not inspirational standards. They are
constraints on what kind of premise can hold the audience-building effort
together.

### Attention And Interest Mechanics

The corpus contains more explicit treatment of attention than the current core:

- attention as demonstrated interest;
- the audience's practical questions: "what is this about?" and "do I care?";
- premise as the answer to why repeated creative artifacts belong together;
- the post as an atomic creative artifact inside a larger effort;
- open-ended audience building as a problem of sustained interest.

This likely belongs near the future story-structure and creative-form line.

### Advertising, Pure Entertainment, And Audience Building

The current docs make the distinction, but the full technical contrast is still
underdeveloped.

Open distinctions:

- advertising primarily seeks transaction or conversion;
- pure entertainment may earn attention without necessarily organizing around a
  useful audience-side state;
- Theme Theory's target is value-based audience building where creative earns
  attention by satisfying a theme linked to a business or endeavor beyond the
  creative.

This matters because the project should not collapse into marketing advice or
creator-content advice.

### Theme Satisfaction Forms

The current docs imply several ways creative and support can satisfy a theme,
but the taxonomy is not yet clean.

Candidate forms:

- attentional: the artifact earns and holds attention around the theme;
- perspectival: it changes what the audience member can see or understand;
- procedural: it helps the audience member do something;
- participatory: it lets the audience member take part, practice, contribute,
  or belong;
- infrastructural: it changes the available tools, memory, data, environment,
  or support around the state.

This taxonomy should not be stabilized until more examples have been tested.

### Theme Funnel And Theme KPI

[Theme Funnel And Audience Progress](theme-funnel-and-audience-progress.md)
names the funnel as audience relation over time. The older corpus contains more
material on metrics and possible Theme KPI language.

The open issue is how to use measurement without letting the measurement
collapse the object into ordinary marketing optimization.

### Audience Potential And Theme Evaluation

[Identify Your Theme](identify-your-theme.md) introduces evaluation, but the
full prospective-audience-potential logic is still thin.

Open questions:

- What makes a theme potent enough?
- What makes a theme too narrow, too weak, too generic, or too sales-shaped?
- How should the creator or organization reason about scale, durability,
  economic value, supportability, and depth?
- Can an agent help evaluate candidate themes without flattening the creator's
  real value or the audience's real situation?

### Creator-Audience-Theme Triangle

The corpus often implies a triangle:

```text
creator or organization value
audience member desired state
theme / object that joins them
```

The current docs use this logic but do not yet present it as a compact diagram
or dependency map.

### Worked Examples

The core still needs more full examples.

Known examples and candidate examples:

- the personal stylist, likely the most durable internal example;
- apparel incumbents;
- Epic Gardening;
- Houzz;
- HAUS;
- TCG / Chernin Group properties, such as MeatEater Inc. and Food52;
- WWE;
- a16z / New Media;
- OpenAI ads and "magic";
- Alex Garcia's signature series;
- software-first builder examples;
- education or command-over-a-text examples;
- a user's own life/project as a self-referential Theme Theory case.

Examples should not be decorative. They should test whether the concept does
work.

### Goods, Services, Events, Community, And Physical/Digital Mix

[Build Support Around The Theme](build-support-around-the-theme.md),
[Media And Non-Media Business](media-and-non-media-business.md), and
[Creative Form](creative-form.md) now open the door beyond media.

The current public core now treats software, data, and AI as the primary
`build` track, while [Media And Non-Media Business](media-and-non-media-business.md)
handles the broader goods/services/business side. The older corpus goes
further into the matrix of:

- media;
- software;
- data;
- AI;
- digital services;
- physical goods;
- traditional services;
- books;
- events;
- stores;
- community;
- organizations.

The core needs to keep this breadth without turning the theory into a list of
possible business activities.

### Normative Orientation

The corpus and recent audios carry a normative pressure that is only lightly
surfaced:

- do not manipulate attention around empty objects;
- do not reduce audience members to buyers;
- preserve the audience-side state as real;
- treat the creator/organization's role as enabling, supporting, orienting, or
  guiding;
- distinguish authentic theme satisfaction from dark-pattern identity capture.

This may matter a lot for public trust, but it should be developed with care.

### Meaning, Relevance, And Cognitive Substrate

The John Vervaeke interview notes, the Colin/Samir note, and some corpus
language point toward meaning, relevance, identity, and cognitive fit.

This is likely real substrate. It should not become the first public burden of
the project.

The practical route should continue to lead with story structure and audience
building. The deeper substrate can remain available for later theoretical
support.

### Theme Space

Theme space now has a first-pass core doc, but remains one of the largest open
theoretical areas.

Open possibilities:

- themes may be mappable objects of human interest;
- LLMs and agents may be unusually useful for surfacing and comparing themes;
- theme potency may vary by depth, durability, universality, supportability, and
  relation to economic activity;
- creators and builders may be able to start from theme space rather than only
  from existing products or expertise.

The current doc should be treated as a starting map, not a complete treatment.

### Story Structure And Systems Theory

Story structure is already used across the core. Systems theory is present in
the WTB line and in the "maintained higher-order states" framing. A first-pass
core doc now exists, but the source field still contains deeper material.

The open doc should explain the relation without overcomplicating it:

- story structure gives the interest logic;
- systems thinking gives the maintained-state and support-surface logic;
- Theme Theory joins them through the audience member's desired real-life
  state.

Future passes may still deepen this line, especially where story structure,
systems thinking, relevance, and support surfaces meet.

### Relations And Concept Map

Inline links are intentionally sparse. They are navigation hints, not the final
relation graph.

The project still needs some form of explicit relation map:

- term definitions;
- dependencies;
- aliases and historical labels;
- examples attached to concepts;
- claims attached to source support;
- external milieu sources attached to relevant core concepts.

The current linking convention is recorded in
[Linking And Relations](../project/linking-and-relations.md).

## Milieu Lane Overview

The milieu lane should be read as surrounding material, not as the theory
itself.

The current inventory lives at [Milieu Intake](../milieu/index.md).

### New Media And Going Direct

Strong items:

- a16z `New Media, One Year In`;
- a16z Ben/Marc media playbook;
- a16z `What Is New Media?`;
- Future Commerce on brands as publishers;
- a16z podcast-about-podcasts note.

Use this cluster for the macro claim that going direct, owned audience, media
capability, and company-as-media are already live phenomena. Theme Theory may
contribute the premise/object layer underneath that operating capability.

### Creator Tactics And Media Craft

Strong items:

- Alex Garcia on signature series;
- GaryVee and Sean Evans on social media and AI;
- GaryVee on WWE storytelling and brand;
- GaryVee on creator-owned IP;
- Samir on brainstorming and packaging.

Use this cluster for last-mile creative practice: repeatable formats,
familiarity, packaging, audience empathy, character, platform adaptation, and
creative process. These sources often describe what works. Theme Theory should
explain the object those tactics should serve.

### AI, Agents, And What To Build

Strong items:

- Simon Willison on the AI state of the union;
- Dalton Caldwell and Michael Seibel on AI startup ideas;
- Joe Schmidt on the AI app layer;
- YC / Ploy;
- Garry Tan on agency and desired futures;
- Uncle Bob on agents as consuming audience;
- Marc Andreessen on software and building.

Use this cluster for the agentic-coding moment: execution cost changes,
distribution and idea quality matter more, software can be built around
specific outcomes, and agents may become a new audience for structured
materials.

### Taste, Judgment, Status, And Graph Structure

Strong items:

- Marc Andreessen on taste and judgment;
- Eugene Wei on status as a service;
- Eugene Wei and Kevin Kwok on graphs;
- product-video and taste screenshots.

Use this cluster carefully. It may illuminate audience behavior, graph
dynamics, taste, social capital, and recommendation systems. It should not
replace the core with a status theory.

### Marketing, Advertising, And Identity

Strong items:

- Dara Denney on Meta and performance marketing;
- Oren John on marketing teams;
- Oren John on internet splintering;
- Oren John on the loneliness economy and identity marketing;
- GaryVee/WWE where story and brand overlap.

Use this cluster to test distinctions between audience building, organic
creative, paid media, advertising, identity signaling, and actual
audience-side transformation.

### Meaning, Cognition, Relevance, And Writing

Strong items:

- John Vervaeke interview on dialogue and meaning;
- John Vervaeke interview on cognitive science;
- Colin and Samir on auto summaries and meaning;
- Alex Danco on writing as power transfer;
- Ethan Mollick on LLM legibility, with source limitations.

Use this cluster as adjacent substrate. It may help explain why theme,
through-line, relevance, voice, and non-compressible meaning matter. It should
not be promoted into the first public spine unless the project later needs a
deeper theoretical layer.

## How To Use This Map

For core drafting, start with the current core docs. Use this map only after
the basic spine is clear.

For a deep corpus pass, start with the named concept and then search the corpus
layer most likely to contain it:

- broad examples and modules: December 2024 corpus;
- macro chain and toolset: July 2025 macro angle;
- logical dependency blocks: October 2025 Phase 1 paper;
- creative form and IRL story: December 2025 IRL version;
- software, higher-order states, and agentic coding: May 2026 WTB piece.

For external-source comparison, begin with the milieu cluster most relevant to
the claim. Do not treat the external source as canonical unless the project
explicitly promotes it.

For future agents, the most important warning is this:

```text
Do not infer that the current core lacks an idea just because the idea is not
yet prominent there. Check the corpus layer and the milieu lane first.
```

## Suggested Next Gap Passes

These are not all immediate tasks. They are the most obvious future passes that
would make the source field more legible.

1. Build a full personal stylist example doc.
2. Create the planned story-structure / systems-theory doc.
3. Create the planned theme-space doc.
4. Create a success-criteria appendix or core doc.
5. Create a concept/dependency map for the first core surface.
6. Create an example index that attaches examples to specific concepts.
7. Create a milieu cluster map if the external lane becomes hard to scan.
8. Revisit this source-field inventory after the next core audios are processed.