Pillars-Recall
Thematic anchors extracted from founder thought-streams. Each pillar is something he has lived and articulated — these are the load-bearing themes that future B1/B2 episodes can hook into without inventing new substance.
How to use: before drafting a new script (mode draft-script), scan this file. If the proposed hook overlaps a documented pillar, pull the founder’s own phrasing as the anchor. Verbatim > paraphrase.
How to add: when a thought-stream contains a thematic insight that could re-emerge in future episodes, append it here as ## P<NN> — <name> with:
- the founder’s original words (verbatim quotes)
- the captured-date + source Backlog/Inbox entry
- 1-3 future-episode angles where this pillar can re-anchor
P01 — Multi-domain founder load
Captured: 2026-05-18 via 2026-05-18-b1-ep2-rohessenz-fragmentation Source episode: 2026-05-28-b1-episode-2-fragmentation (Episode 2 of 1M Challenge)
Founder words (verbatim):
“Ich merke es einfach selbst, wie viele Bereiche ich auf einmal einnehme. Wie sich das in den Wochen entwickelt hat. Von dem, dass man überhaupt mal diese Pre-Page darstellen muss und den Wert sich überlegt, wie der Wert dann ankommt zu dem hin, dass das Goal der Kampagne Pre-Page von Indiegogo sich dann irgendwie zu dem wieder verschoben hat, dass wir eigentlich wissen, dass wir das Produkt gleichzeitig auch aufbauen müssen oder halt greifbar machen müssen zu dem hin, dass ich die Social-Strategie koordinieren sollte und da auch jeden Tag was machen sollte.”
Core thesis: Solo-/early-stage-founder gets pulled across 4+ domains of similar priority weight (Pre-page / Product / Social / Content-plan), each demanding daily attention. The number of fronts is the load, not the depth of any single front.
Future-episode angles:
- B1 Episode-N: A day-in-the-life cut. Show the 4 domains in sequence, time-on-task. Don’t narrate — let the visual carry it.
- B2 Reaction: when an AI-tooling tweet hits about productivity, react from this lived-experience angle, not from theory.
- A2 (Daniel-POV): Daniel films the founder in mid-context-switch. No script. Best-Friend-voice carries the recognition.
P02 — The fragmentation paradox (anti-fragmentation thesis)
Captured: 2026-05-18 via 2026-05-18-b1-ep2-rohessenz-fragmentation Source episode: 2026-05-28-b1-episode-2-fragmentation
Founder words (verbatim):
“Dann eigentlich immer wieder vor den Tools sitze, die eigentlich genau diese Schwierigkeiten mit sich bringen, die ich ja eigentlich lösen möchte mit A Friend und Onari und zwar, dass dieses, dass das alles an einem Ort leben kann und das tut halt das tut halt jetzt noch nicht und jetzt muss ich da fragmentieren auf allen Ebenen. Da ist die App, da ist Social Media, da landet die Content, der Contentplan.”
Core thesis: The founder is building the product (A Friend / Onari) that addresses the exact pain the founder lives daily. The product’s reason-to-exist is mirrored in his own struggle. Recursive irony anchored in lived experience.
This is the deep pillar. Not a beat — it’s the substrate beneath the whole 1M Challenge format. Episode-2 makes it explicit; future episodes can reference it implicitly.
Future-episode angles:
- B1 Episode-N: when shipping a new A Friend feature, frame it as “this is the slice of my own pain it kills”. Skin-in-the-game taken literal.
- B2 Reaction: any post about tool-overload, productivity-stacks, second-brain — react from “I am building the alternative AND I suffer from the current state”.
- C1 Substack cross: this thesis is Substack-essay-shaped. When written there, atomize → A Friend channels.
P02-resolution — “Die Technologie ist mein Freund” (Round-2 enrichment, 2026-05-18 evening)
Captured: 2026-05-18 (evening) via 2026-05-18-b1-ep2-rohessenz-fragmentation Round-2
Founder words (verbatim):
“Dann eben übergeleitet — das ist quasi die Resolution darin — dass ich gesehen habe, dass die Technologie nur mein Freund ist.”
The resolution-half of P02. P02-diagnosis (“I sit in front of the tools I want to replace”) and P02-resolution (“the technology is my friend”) are the SAME pillar in two arcs — problem-statement and personal-claim. Both must be voiced by the founder on-camera; never paraphrased.
Use rule: When P02-diagnosis is the body-beat, P02-resolution is the close-beat. Never use resolution-line without diagnosis preceding — it lands as slogan instead of arrival. Delivery direction: slow, quiet, almost relief. NOT triumphant. NOT product-tagline-cadence.
P03 — Productive Prokrastination
Captured: 2026-05-18 via 2026-05-18-b1-ep2-rohessenz-fragmentation Source episode: 2026-05-28-b1-episode-2-fragmentation
Founder words (verbatim):
“Das ist so, dass es halt leicht ist, was zu finden, das einem gefällt, zu tun. Aber es dann halt auch sich gleich mal wieder entpuppt als etwas, das eigentlich nicht das ist, was der Erfolg von dem, was du eigentlich machst, hier von dir eigentlich braucht.”
“Wie man in diese produktive Prokrastination gerät, wenn auf einmal verschiedene Ebenen vor einem aufkreuzen, die ähnliche Prioritäten in sich tragen und man dann wieder alles durchfiltern muss.”
Core thesis: When multiple domains of similar priority compete, the founder defaults to whatever feels good to work on — which is rarely what success actually needs. Productive on the surface, procrastination beneath.
Distinct from P01: P01 is the LOAD (how many domains). P03 is the BEHAVIOR (which one you actually pick when all scream).
Future-episode angles:
- B1 Episode-N: real-time confession. “I just spent 3h on X. Here is what I should have done instead. Here is why I chose X anyway.”
- B2 Reaction: pair with research on attention-residue or context-switching cost. Use founder-evidence, not just papers.
P04 — The filtering art (“Durchfiltern ist alles”)
Captured: 2026-05-18 via 2026-05-18-b1-ep2-rohessenz-fragmentation Source episode: 2026-05-28-b1-episode-2-fragmentation
Founder words (verbatim):
“Das ist so das größte Learning grad, dass dieses Durchfiltern halt einfach alles ist. Dieser Priorität, sie zu erkennen, aber trotzdem sich überlegen zu können, wie diese Kaskade an Handlungen in dem anderen Bezug das wieder steuern könnte.”
Core thesis: The founder’s actual skill (and the actual lever) is the act of filtering — recognizing which domain holds the load-bearing priority right now, AND cascading the secondary actions in the other domains so they don’t bleed back.
Future-episode angles:
- B1 Episode-N: walkthrough of a specific filter decision in the week. “Today I filtered out Social. Here’s how I handled Content and Pre-Page to compensate.”
- B2 Reaction: react against “do everything at once” productivity content with this filter doctrine.
- A2 (Daniel-POV): Daniel observes the founder filtering in real-time, narrates the observation.
P05 — Komplexität-nimmt-Edge
Captured: 2026-05-18 via 2026-05-18-b1-ep2-rohessenz-fragmentation Source episode: 2026-05-28-b1-episode-2-fragmentation
Founder words (verbatim):
“Auch wenn heutzutage alles so in dem umfanglichen Raum so zugänglich ist und man alles bauen kann und ist es genauso wieder die Komplexifizierung dieser Thematik, was dir im Endeffekt die Edge nimmt. Weil, was braucht es jetzt von mir? Wirklich. Was braucht das, was ich mache, wirklich von mir? Jetzt.”
Core thesis: The ability to build anything is the ability to lose your edge. Modern accessibility-of-everything is the disguise the complexity wears. The founder’s recurring filter-question is “Was braucht das wirklich von mir, jetzt?” — and the answer is almost always smaller than what’s available.
Future-episode angles:
- B1 Episode-N: deliberate constraint-reveal. “I disabled X. Here’s what came back.”
- B2 Reaction: react to any “you can build a unicorn with 3 AI tools” content from this anti-complexity angle.
- C1 Substack cross: this is essay-shaped — “The edge is what you don’t build”. Cross-eligible if not Onari-internal.
P05-mandate — Bootstrap-to-perfect-form (Round-2 enrichment, 2026-05-18 evening)
Captured: 2026-05-18 (evening) via 2026-05-18-b1-ep2-rohessenz-fragmentation Round-2
Founder words (verbatim):
“Ich halt aber bis dorthin in der Vereinfachung, ohne alles gleich abbilden zu wollen, in der perfekten Form des Produkts jetzt zu Lösungen kommen muss, effizient, um natürlich den Ausdruck wahren zu können, dem ich am nächsten stehe — und der diese verdammt harte, aber so lehrreiche Reise erst so richtig ausmacht.”
“Es muss jetzt halt mal zu diesem Bootstrap kommen.”
Action-side of P05. P05’s filter-question is “Was braucht das wirklich von mir, jetzt?” — Bootstrap-mandate is the answer. Simplification, refusal to map-everything, perfect-form-of-product-now, preserve-the-expression-closest-to-the-founder. The mandate operationalizes the question.
Use rule: This is the close-beat candidate when an episode opens with the filter-question and needs to land somewhere. Never use without earning it — bootstrap-language without the diagnostic struggle preceding reads as productivity-gospel. Pair with P02-resolution for full arc.
P06 — Marco-divergence (role-team-shift) (Round-2 capture, 2026-05-18 evening)
Captured: 2026-05-18 (evening) via 2026-05-18-b1-ep2-rohessenz-fragmentation Round-2 Source episode: 2026-05-28-b1-episode-2-fragmentation
Founder words (verbatim):
“Zum Beispiel könnte man da das letzte Szenario nehmen, wo Marco durch Media abgedreht hat, damit wir Geld sparen und jetzt andere Metriken wichtiger sein sollten oder wie auch immer. Es ist halt einfach diese Divergenz auch wahrscheinlich zwischen den Vorstellungen, was uns zum Success bringt, weil Marco nicht so vorhanden ist.”
“Vielleicht hat er ein anderes Bild von Socials … durch diese Situation jetzt natürlich noch mehr Aufgabe bei mir liegt. Zuvor hatte ich zumindest den Support, jetzt ist quasi [nur noch] zwischen Daniel und mir.”
Core thesis: Team-composition changes (cost-driven scale-back, role-pivot, partner-departure) cascade into structural load on the founder. The work doesn’t vanish with the role — it redistributes. AND the success-metric expectations diverge between the remaining roles, because the absent partner used to anchor a specific success-frame. The founder must now hold the metric AND the load.
Distinct from P01: P01 is multi-domain load over weeks/months. P06 is a SPECIFIC role-shift event that resets the load distribution. P06 is the “what changed this quarter” pillar — P01 is the “what’s chronic” pillar.
Hard rule on use (per Backlog/Ep2 anti-patterns):
- NEVER frame as grievance or blame.
- Cost-saving = joint call. Structural-shift framing only.
- Optics-risk: if naming the partner reads as fault-assigning, OMIT the name and retain only the structural-fact (“we scaled back our media collaboration for cost reasons”).
- This pillar IS sensitive — burns trust if mishandled. Founder-tone must be matter-of-fact, never wounded.
Future-episode angles:
- B1 Episode-N: any week when a tooling/team/process decision was made for cost-reasons that cascaded back. Anchor in this pillar — same structural-shift logic.
- B2 Reaction: any creator-post about solopreneur vs team-of-two vs team-of-N — react from this specific lived-shift, not theory.
- A2 (Daniel-POV): Daniel observes the founder absorbing the redistributed load. Wordless observation can carry the pillar without the founder needing to articulate the team-shift directly.
Use in script-draft
When triggering mode draft-script for a B1/B2:
- Open this file.
- Check if proposed hook overlaps any P01-P05.
- If yes: pull the founder’s verbatim phrasing into the script-pool prompt as a primary-source anchor. Tell script-pool: “Hook must align with P0N — use these exact words as the lexical anchor”.
- If no: don’t force a pillar. New thematic territory is fine. After the episode, consider adding a P0N entry.
Hard rule: never rephrase a founder-pillar in the skill’s own words. The pillars are sacred verbatim anchors. They lose their truth-claim under paraphrase.