Deliverables Library

Recent briefs, plans, trackers, and other artifacts saved from the workspace.

Michael Plaster Identity Backup (Mar 29, 8:51 PM)

---
type: deliverable
topic: michael-plaster-identity-backup
created: 2026-03-29
source_system: codex
---

# Michael Plaster Identity Backup

## Verified Public Identity Links

- LinkedIn: <https://www.linkedin.com/in/michaelplaster/>
- YouTube: <https://www.youtube.com/@Plaster10p>
- Instagram: <https://www.instagram.com/plaster10p/>
- Facebook: <https://www.facebook.com/michael.plaster.278009>
- SoundCloud: <https://soundcloud.com/michael-plaster>
- IMDb: <https://www.imdb.com/name/nm4013879/?ref_=fn_t_4>
- Canyon News profile/interview: <https://www.canyon-news.com/producer-michael-plaster-tells-it-the-way-it-is/>
- Canyon News article: <https://www.canyon-news.com/long-beach-explode-in-protest-fire/>

## Identity Relationships

- LinkedIn -> Michael Plaster -> The Grappling Network
- YouTube -> `@Plaster10p` -> Michael Plaster
- Instagram -> `@plaster10p` -> Michael Plaster
- Facebook -> Michael Plaster page -> Instagram `@Plaster10p`
- SoundCloud -> `michael-plaster` -> Michael Plaster
- IMDb -> `nm4013879` -> film/production credits for Michael Plaster
- Canyon News -> profile/interview + article byline cluster for Michael Plaster

## Known False Matches

- PGC / NEMA / ABB executive Michael or Mike Plaster
- `@soulwhirling` / Soul Whirling Somewhere
- Plaster Mike Venetian Plaster Artist
- College of Idaho football player Mike Plaster

## Media Backup

- Local manifest: `/Users/walter/Documents/New project/deliverables/2026-03-29-michael-plaster-identity-media-assets.json`
- Local download folder: `/Users/walter/Documents/New project/deliverables/2026-03-29-michael-plaster-identity-media`
- Local Drive upload ledger: `/Users/walter/Documents/New project/deliverables/2026-03-29-michael-plaster-identity-drive-upload.json`
- Drive folder: <https://drive.google.com/drive/folders/1wN5EC3ZA2kvakR7gM5sfl7mFK6mzNtRG>
- Drive path: `Walter Remote Reference Library / 03 Walter Workspace / Identity Backups / Michael Plaster / 2026-03-29 Identity Backup`
- Capture notes:
- All six resolved media assets were downloaded and uploaded.
- LinkedIn and Facebook page HTML could not be fully archived because of platform anti-bot responses, but their profile images and structured metadata were preserved.
- The Canyon News protest-fire article image referenced on-page returned `HTTP 404` during backup; the page HTML snapshot and an unavailability note were backed up instead.

README (Mar 29, 3:58 PM)

---
type: deliverable-bundle
bundle: ebi-application-packets
source_system: obsidian
domains:
  - business
  - operations
  - creative
---

# EBI Application Packets

## Parent Deliverables

- [[../2026-03-24-ebi-application-attachment-checklist]]
- [[../2026-03-24-ebi-application-factory]]
- [[../2026-03-24-ebi-doc-application-master-profile]]
- [[../2026-03-24-ebi-live-application-master-profile]]
- [[../2026-03-24-pgf-application-master-profile]]
- [[../2026-03-24-ebi-jurisdiction-application-tracker]]
- [[../2026-03-24-ebi-jurisdiction-launch-checklist]]
- [[../2026-03-24-ebi-jurisdiction-send-matrix]]
- [[../2026-03-24-ebi-local-partner-requirements]]

## Scope

Use this bundle when the EBI / PGF application work branches into per-jurisdiction packet files. The packet notes are not independent strategy notes; they are submission-ready derivatives attached to the master application system.

Current packet count: 31

## EBI Doc Packets

- [[ebi-doc-abu-dhabi-uae-35-cashback-rebate]]
- [[ebi-doc-austria-fisaplus]]
- [[ebi-doc-belgium-audiovisual-tax-shelter]]
- [[ebi-doc-british-columbia-canada-production-services-tax-credit-pstc]]
- [[ebi-doc-canary-islands-spain-foreign-production-deduction]]
- [[ebi-doc-france-trip]]
- [[ebi-doc-germany-dfff]]
- [[ebi-doc-ireland-section-481]]
- [[ebi-doc-malta-malta-cash-rebate]]
- [[ebi-doc-new-zealand-new-zealand-screen-production-rebate-international]]
- [[ebi-doc-portugal-scri-pt-portugal-production-incentive-transition]]
- [[ebi-doc-singapore-singapore-on-screen-fund]]
- [[ebi-doc-united-kingdom-audio-visual-expenditure-credit-avec]]

## EBI Live Packets

- [[ebi-live-new-zealand-events-boost-fund]]
- [[ebi-live-singapore-business-events-in-singapore-beis]]
- [[ebi-live-singapore-kickstart-fund]]
- [[ebi-live-singapore-leisure-events-fund]]
- [[ebi-live-texas-texas-moving-image-industry-incentive-program-tmiiip]]

## PGF Packets

- [[pgf-abu-dhabi-uae-35-cashback-rebate]]
- [[pgf-austria-fisaplus]]
- [[pgf-belgium-audiovisual-tax-shelter]]
- [[pgf-british-columbia-canada-production-services-tax-credit-pstc]]
- [[pgf-canary-islands-spain-foreign-production-deduction]]
- [[pgf-france-trip]]
- [[pgf-germany-dfff]]
- [[pgf-ireland-section-481]]
- [[pgf-malta-malta-cash-rebate]]
- [[pgf-new-zealand-new-zealand-screen-production-rebate-international]]
- [[pgf-portugal-scri-pt-portugal-production-incentive-transition]]
- [[pgf-singapore-singapore-on-screen-fund]]
- [[pgf-united-kingdom-audio-visual-expenditure-credit-avec]]

## Rule

Treat packet files as children of the application factory and jurisdiction tracker. If one packet becomes the live send-ready version for a market, keep it linked here and in the higher-level EBI deliverable notes rather than promoting it to a standalone workstream.

Codex Task Thread Launcher (Mar 29, 3:38 PM)

# Codex Task Thread Launcher

Use each block below as the opening message for a separate Codex app thread.

## 1. Walter Workflow System

```text
Resume the Walter Workflow System thread.

Context:
- This project is active but unfinished.
- The main unresolved work is making Codex the default execution surface, restoring Google Drive backup reliability, reducing oversized-file friction, and tightening the repo/vault operating loop.

Primary references:
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/projects/WALTER WORKFLOW SYSTEM.md
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/TODO.md
- /Users/walter/Documents/Walter Workspace/walter/memory.md
- /Users/walter/Documents/Walter Workspace/walter/chat-archive/entries/2026-03-28-big-brain-work-walter-workflow-system-resume-thread.md

What needs to happen next:
1. Fix Drive backup auth.
2. Decide whether to enable daily backup automation now or after auth repair.
3. Reduce large-file / repo friction.
4. Tighten the daily operating loop across TODO, deliverables, and Obsidian.

Please inspect the current repo state, identify the real blocker, and move this thread forward end-to-end.
```

## 2. MTS Distribution Engine

```text
Resume the MTS Distribution Engine thread.

Context:
- The strategy and system map exist, but execution paused before MTS became a stable shipping engine.
- The immediate issue is turning MTS back into a repeatable publishing and conversion system.

Primary references:
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/projects/MTS DISTRIBUTION ENGINE.md
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/TODO.md
- /Users/walter/Documents/Walter Workspace/walter/chat-archive/entries/2026-03-28-big-brain-work-mts-distribution-engine-resume-thread.md

What needs to happen next:
1. Ship MTS 253.
2. Lock YouTube membership publishing cadence.
3. Clarify the weekly BMac editing dependency.
4. Tie each drop to the broader funnel.

Please review the available assets and turn this into a concrete next-action plan with the first executable move.
```

## 3. Cinematic Family Stories

```text
Resume the Cinematic Family Stories thread.

Context:
- The offer stack, outreach assets, partner lists, send-ready drafts, and Jay handoff materials already exist.
- The unfinished work is making the warmed outreach pipeline actually run in live operations.

Primary references:
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/projects/CINEMATIC FAMILY STORIES.md
- /Users/walter/Documents/Walter Workspace/walter/notes/operating/Current Goals.md
- /Users/walter/Documents/Walter Workspace/walter/chat-archive/entries/2026-03-28-big-brain-work-cinematic-family-stories-resume-thread.md

What needs to happen next:
1. Confirm owner model with Jay.
2. Put send-ready drafts into use.
3. Launch the first real outreach block.
4. Track replies, objections, and conversion friction.

Please determine the shortest path to restart execution and prepare the active operating setup.
```

## 4. EBI International Expansion

```text
Resume the EBI International Expansion thread.

Context:
- A large research and application system already exists.
- The unfinished work is turning it into a real market-priority and send-ready execution sequence.

Primary references:
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/projects/EBI INTERNATIONAL EXPANSION.md
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/TODO.md
- /Users/walter/Documents/Walter Workspace/walter/chat-archive/entries/2026-03-28-big-brain-work-ebi-international-expansion-resume-thread.md

What needs to happen next:
1. Choose immediate target jurisdictions.
2. Confirm rights / entity structure.
3. Turn the application factory into a send schedule.
4. Build the next outward motion: host, sponsor, or funding outreach.

Please review the current materials and tell me what we should execute next, not just what else we could research.
```

## 5. Third Space In Austin

```text
Resume the Third Space In Austin thread.

Context:
- The roadmap, architect brief, and investor-outline work exist.
- The unfinished work is connecting property, underwriting, capital, launch, and attached 10pATX relationship work into one visible operating chain.

Primary references:
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/projects/THIRD SPACE IN AUSTIN.md
- /Users/walter/Documents/Walter Workspace/walter/memory.md
- /Users/walter/Documents/Walter Workspace/walter/chat-archive/entries/2026-03-28-big-brain-work-third-space-in-austin-resume-thread.md

What needs to happen next:
1. Identify the true next bottleneck: property, capital, or demand.
2. Tie current assumptions into one roadmap.
3. Separate real-estate / launch work from grappling-network and attached relationship marketing tasks.
4. Build one visible operating dashboard for the project.

Please inspect the current state and turn this back into an actionable build thread.
```

## 6. Grappling Network / TGN

```text
Resume the Grappling Network / TGN thread.

Context:
- The archive has been partially extracted and organized.
- The unfinished work is converting historical TGN findings into current reusable systems for 10pN and related work.
- A larger Google Workspace review is deferred until mid-May 2026.

Primary references:
- /Users/walter/Documents/Walter Workspace/walter/legacy/walterclaw/projects/GRAPPLING NETWORK.md
- /Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-25-tgn-may-review.md
- /Users/walter/Documents/Walter Workspace/walter/chat-archive/entries/2026-03-28-big-brain-work-grappling-network-tgn-resume-thread.md

What needs to happen next:
1. Convert the strongest TGN learnings into live system notes.
2. Decide whether to keep TGN fully under Grappling Network or split out a tighter historical systems note.
3. Prepare for the mid-May 2026 source review.
4. Keep 10pN as the forward branch.

Ple
…

Tgn Next Conversion Decision (Mar 29, 3:38 PM)

# TGN Next Conversion Decision

## Decision

The highest-leverage conversion to do now is:

`10pN federated creator network with centralized ops`

This should be converted into a live current-system note for 10pN, not left as a historical TGN summary.

## Why this is the best next move

This is the conversion that best matches the forward branch.

- It keeps `10pN` as the live expression of the work.
- It absorbs the strongest TGN logic without pretending TGN is being resumed.
- It creates a parent operating model that narrower SOPs can plug into later.
- It links directly to an existing `10pATX` attached-project opportunity inside the broader 10th Planet relationship network.
- It does not require waiting for the mid-May 2026 Google Workspace review to be useful.

Compared with the other candidate conversions:

- the tournament packaging SOP is strong but narrower
- the rights checklist is important but mostly defensive
- the screen-distribution offer is promising but still a wedge, not the whole operating system
- the sports-doc checklist is reusable but not the main 10pN engine

The creator-network system is the one that can organize:

- local gym capture
- centralized editing and publishing
- coach and athlete packaging
- affiliate and commerce experiments
- venue-screen distribution
- future packaging SOPs

## What the live note should cover

Create one current-system note that turns the TGN lesson into a reusable operating model for 10pN.

Suggested scope:

1. Core model
2. Node roles
3. Central ops roles
4. Content flow
5. Monetization layers
6. Minimum starter stack
7. Pilot sequence

### 1. Core model

Use the durable pattern:

- federated local creators close to each gym
- centralized editorial, publishing, and standards
- commerce attached to distribution

### 2. Node roles

Each gym or local branch can be treated as a node with:

- one capture lead or videographer
- coach and athlete personalities
- repeatable local formats
- local sponsor and promo opportunities

### 3. Central ops roles

Central 10pN ops should own:

- editorial standards
- publishing cadence
- asset intake rules
- packaging templates
- performance tracking
- sponsor and affiliate coordination

### 4. Content flow

The note should define the repeatable path:

capture -> ingest -> select -> package -> publish -> monetize -> review

This is the place where later SOPs can attach:

- post-production SOP
- tournament cutdown SOP
- social triage SOP
- sports-doc checklist

### 5. Monetization layers

The note should explicitly include:

- affiliate links
- inventory-aware commerce
- direct sponsor inventory
- gym-specific promo inventory
- venue-screen inventory
- subscriptions or paid access where relevant

### 6. Minimum starter stack

Define the smallest live version that can actually run:

- one gym pilot
- one local creator or capture lead
- one recurring show or short-form format
- one editorial owner
- one commerce path

### 7. Pilot sequence

Recommended sequence:

1. if the relationship is active, start with `10pATX` as an attached test case rather than an owned default node
2. define one recurring format and one shoppable or affiliate path
3. set intake and publishing rules
4. test whether local capture plus central ops can sustain cadence
5. add venue-screen or sponsor inventory only after the content flow is stable

## Structure decision

Keep `GRAPPLING NETWORK.md` as the canonical project anchor.

Also create or plan a tighter TGN historical systems note.

Reason:

- `GRAPPLING NETWORK.md` should remain the umbrella project note
- a separate TGN historical systems note will keep archive-specific findings cleanly separated from live 10pN operating notes
- this prevents the current branch from getting buried inside historical company material

Recommended split:

- `GRAPPLING NETWORK.md` = umbrella and routing note
- `TGN historical systems` = historical extracted logic
- `10pN current system` = live forward operating note

## Mid-May 2026 review prep

Use the May review to strengthen the new live note, not to reopen the whole question from scratch.

Highest-value sources to inspect then:

1. `10p Network Content Master List 050924`
2. `TGN Post Guidelines and Procedures SOP 120823.docx`
3. `Videography SOP`
4. `TGN Accounts Billable`
5. `MVMT TGN PLASTER Payments`
6. `PGF GRAPPLING Run of Show & Checklist`

Questions for that review:

- Which content formats were actually repeatable?
- Which activities were actually monetized?
- Which SOP steps were strict enough to preserve quality across operators?
- Which parts of the system were operational versus aspirational?

## Bottom line

If only one conversion gets done now, it should be the live `10pN` creator-network operating note.

That note creates the parent system that the other TGN-derived SOPs and checklists can attach to later.

10patx Content And Growth Strategy (Mar 29, 3:38 PM)

# 10pATX Content And Growth Strategy

## Core Role

The 10pATX notes are not just local gym reminders. They describe a gym-growth system built from content, coach visibility, commerce, and repeatable social distribution.

## Strongest Signals From The Archive

From `10p Austin.md`, `10patx.md`, and `10patx rtmp.md`, the recurring priorities are:

- use content to increase engagement and enrollment
- turn coaches and athletes into niche influencers
- connect gym media to merchandise and subscription revenue
- build repeatable short-form and live commerce systems
- create a portable recording setup and recurring show formats

## Strategy Layers

### 1. Audience and cultural identity

- highlight the unique vibe of the gym
- sell community and lifestyle, not only technique
- aim at new students, teens, families, and MMA-adjacent audiences

### 2. Coach and athlete packaging

- identifiable coach assets include Gabe Tuttle, Ben Eddy, Andrew Craig, Austin `Baby Goat`, and Dallas Dodd
- the notes repeatedly point toward making coaches and athletes visible as individual personalities, not faceless staff

### 3. Commerce stack

- memberships
- apparel
- subscription content
- TikTok Shop
- YouTube Shop
- Shopify-linked shoppable videos
- affiliate or creator seeding

### 4. Content engine

- daily short-form consistency
- 2 shoppable videos per week
- live workout / live sport commerce moments
- testimonials and UGC
- modular podcast or show setup
- `Thursday Night Jiu Jitsu` as a recurring flagship format

## Operational Read

- this is a real growth playbook, not random posting advice
- the notes combine brand, content, product, creator seeding, and live selling into one system
- the RTMP note confirms that live infrastructure was part of the intended operating model

## Present-Day Reuse Value

- gym-growth offer design
- social commerce packaging
- coach-led content systems
- show-format development for local communities

## Rule

Use this note as the canonical strategy note for the `10pATX` attached-project branch under grappling-network work.
Treat `10pATX` as `10th Planet Austin`, a relationship-attached opportunity rather than an owned Walter project.
Do not scatter future 10pATX strategy fragments across unrelated Austin or real-estate notes.

Walter Workflow System Resume Note (Mar 28, 8:58 PM)

# Walter Workflow System Resume Note

Date: 2026-03-28

## What Was Actually Blocking

- Google Drive auth was not the live blocker.
- The real failure was stale user LaunchAgents in `~/Library/LaunchAgents/` still pointing at `/Users/walter/Documents/New project`.
- That mismatch made the daily backup jobs look broken even though the live `walter` repo still had working Google auth and a valid `BACKUPS_DRIVE_FOLDER_ID`.

## What Was Fixed

- verified Google Workspace auth against Drive in the live repo
- verified the configured backup folder resolves correctly
- reinstalled `com.walter.drive-backups` from `backups-drive-launchd.plist`
- reinstalled `com.walter.shareable-stack-drive-backup` from `shareable-stack-drive-backup-launchd.plist`
- reran the shareable-stack backup successfully from the live repo path
- reran the backup-repos Drive snapshot successfully from the live repo path

## Repo Friction Reduction

- added `scripts/install-backup-launch-agents.js` so backup LaunchAgents can be reinstalled from the current repo instead of drifting silently
- added local retention to `scripts/backup-repos-drive-backup.js` and `scripts/shareable-stack-drive-backup.js`
- default retention now keeps recent local exports and prunes older uploaded tarballs automatically
- expanded `.gitignore` to reduce noise from local browser profiles, temp work, generated exports, and local environment folders
- added `npm run organization:repo:friction` so repo-weight hotspots are captured in a reusable audit instead of repeated ad hoc checks
- added `npm run organization:repo:guard` plus `docs/repo-weight-boundary.md` so new oversized tracked files are blocked outside the known archive-heavy zones

## Current Constraints

- the repo is still structurally heavy because `legacy/` is about 63G and `.git/` is about 2.7G
- the worktree is still broadly dirty across many unrelated areas, so this thread did not attempt git cleanup or historical surgery
- the right near-term goal is to stop friction from growing, not to rewrite history during an already-dirty state
- the repo friction audit points to tracked Gandalf/MBT archive files as the first serious slimming target if performance pressure increases

## Recommended Daily Loop

1. Use `legacy/walterclaw/TODO.md` as the active queue, not chat memory.
2. When a workflow-system fix lands, write one short deliverable note like this one.
3. Keep `legacy/walterclaw/projects/WALTER WORKFLOW SYSTEM.md` as the current project-state anchor.
4. Use `notes/operating/Active Projects Review.md` as the Obsidian control layer that links back into the project anchor and the latest deliverable.

## Commands

```bash
npm run backups:install-launch-agents
node scripts/backup-repos-drive-backup.js --upload --skip-sync
node scripts/shareable-stack-drive-backup.js
```

Workspace Repo Friction Audit (Mar 28, 6:25 PM)

# Workspace Repo Friction Audit

Date: 2026-03-28

## Largest Root-Level Areas

- `legacy`: 63.3 GB (directory)
- `.git`: 2.67 GB (directory)
- `.venv-gandalf-transcribe`: 664 MB (directory)
- `backup-repos`: 403 MB (directory)
- `cloudflare-sites`: 260 MB (directory)
- `node_modules`: 179 MB (directory)
- `.browser-profile-wellsfargo`: 65.6 MB (directory)
- `.browser-profile`: 40.1 MB (directory)
- `.venv-mbt-tools`: 32.6 MB (directory)
- `.venv-audible-audit`: 27.5 MB (directory)
- `data`: 26.3 MB (directory)
- `MTS Mastering The System`: 19.0 MB (directory)
- `tmp`: 11.3 MB (directory)
- `dashboard`: 3.01 MB (directory)
- `genealogy`: 1.63 MB (directory)

## Largest Tracked Files

- `legacy/walterclaw/references/gandalf/mbt-forum/index/documents.json`: 88.4 MB
- `legacy/walterclaw/references/gandalf/mbt-forum/crawl-state.json`: 9.03 MB
- `legacy/walterclaw/references/gandalf/mbt-forum/crawl-index.json`: 7.59 MB
- `legacy/walterclaw/references/gandalf/sources/joseph-campbell/hero-with-a-thousand-faces.html`: 1.56 MB
- `legacy/walterclaw/references/gandalf/sources/joseph-campbell/thou-art-that.html`: 1.56 MB
- `legacy/walterclaw/references/gandalf/sources/esotericism/mythic-imagination.html`: 1.56 MB
- `genealogy/generated-images/plaster-family-line.png`: 1.51 MB
- `legacy/walterclaw/references/gandalf/sources/joseph-campbell/jcf-home.html`: 1.11 MB
- `legacy/walterclaw/references/gandalf/mbt-forum/index/tags.json`: 988 KB
- `legacy/walterclaw/references/gandalf/mbt-forum/index/summary.json`: 757 KB
- `legacy/walterclaw/references/gandalf/sources/tony-robbins/tony-home.html`: 716 KB
- `legacy/walterclaw/references/gandalf/sources/robert-greene/laws-of-human-nature.html`: 405 KB
- `Nikky Macy 2025 1099-NEC filled.pdf`: 363 KB
- `legacy/walterclaw/references/gandalf/sources/tony-robbins/personal-power.html`: 331 KB
- `legacy/walterclaw/references/gandalf/sources/robert-greene/mastery.html`: 305 KB
- `src/index.js`: 294 KB
- `legacy/walterclaw/references/gandalf/sources/robert-greene/48-laws-of-power.html`: 289 KB
- `legacy/walterclaw/references/gandalf/sources/joseph-campbell/power-of-myth.html`: 270 KB
- `legacy/walterclaw/references/gandalf/sources/tony-robbins/unleash-the-power-within.html`: 269 KB
- `legacy/walterclaw/references/gandalf/sources/jordan-peterson/jbp-books.html`: 249 KB

## Pressure Zones

- `historical corpus weight`: The `legacy/` tree dominates local footprint and should be treated as archive-weight, not normal repo-weight.
- `git history weight`: `.git/` is already multi-gigabyte, which means future history rewrites or large generated commits will stay expensive.
- `local backup export drift`: Backup bundles are useful, but they should stay capped locally and treated as disposable local cache after upload.
- `tracked archive blobs`: The heaviest tracked files are mostly Gandalf/MBT archive artifacts rather than active runtime code.

## Recommendations

- Keep backup/export folders ignored and pruned locally; do not let tarballs become a second archive layer inside the repo.
- Treat `legacy/` as an archival boundary. Future large imports should land in clearly isolated archive paths instead of broad root-level sprawl.
- Avoid adding new generated browser profiles, virtualenvs, or site builds to root tracking; the ignore rules should remain strict.
- If repo performance becomes unacceptable, the first serious slimming candidate is the tracked Gandalf/MBT corpus, not current application code.
- Revisit whether `cloudflare-sites/` should stay as generated build output in the main repo root or move behind an explicit build/export boundary.

Zoltan Documentary First Cut Plan (Mar 28, 6:03 PM)

# Zoltan Documentary First-Cut Plan

## Project

- Project: Zoltan Documentary
- Date: 2026-03-28
- Current stage: relationship follow-through, asset gathering, first mock-trailer pass
- Producer: Michael Plaster
- Subject: Zoltan Bathory

## Current Read

The documentary branch is correctly framed, but it is still blocked by one gap: there is no live bridge between story development and an actual cut workflow.

That bridge now needs to be:

1. relationship follow-through with Zoltan
2. a minimum viable asset package
3. a locked purpose for the mock trailer
4. a first assembly built from what already exists

The planning work is already done well enough to move.

## Confirmed Working Materials

### Core story and framing

- `deliverables/2026-03-22-zoltan-documentary-source-package.md`
- `deliverables/2026-03-22-zoltan-documentary-post-handoff.md`
- `deliverables/2026-03-23-zoltan-documentary-trailer-objective.md`
- `deliverables/2026-03-23-zoltan-documentary-shot-and-asset-request-list.md`
- `legacy/walterclaw/projects/ZOLTAN DOCUMENTARY.md`

### Story thesis already established

- Zoltan escaped communist restriction
- he engineered his own American success
- he returned home as a symbol of possibility

This remains the correct documentary engine.

### Additional useful context found

- `notes/inbox/phone-imports/notes-archive-0326-0219/05-zoltan-production/Zoltan Balthory.md`
- `deliverables/2026-03-24-media-project-playlist-manifest.csv`
- `legacy/walterclaw/references/gandalf/markdown/library/thomas-campbell/mbt-video-archive/media/@whatifitreallyworks/playlist_id｜NA/2012-03-03-fT8LaMrn_MM-Tom Campbell - My Big Toe - Part 1.info.json.md`

### What appears available right now

- one strong written documentary source: `Epic Tribe: Road From Hungary`
- one small public reference/watchlist for Zoltan-related video
- one archived production note indicating a documentary/social-content window
- one concrete `My Big Toe` reference link ready to send

### What is still missing

- no consolidated footage bin
- no confirmed Hungary footage package in the vault
- no interview line-selects
- no working edit project path
- no active review loop

## Exact Purpose Of The Mock Trailer

The first mock trailer should not try to prove the whole finished film.

Its job is narrower:

- prove that the Zoltan story is a prestige documentary with a real thematic spine
- show that the film has a structure stronger than musician biography or lifestyle montage
- create enough emotional and strategic clarity that a collaborator, editor, or stakeholder can immediately see the film
- function as a relationship and financing tool, not only a public-facing teaser

## Decision

The mock trailer should primarily serve as:

1. a story-proof trailer
2. a tone-and-access trailer
3. a stakeholder persuasion asset

It should not yet be treated as:

- a final public trailer
- a polished fan-facing music promo
- a comprehensive career summary

## Working Runtime

- Target runtime for pass 1: `75-105 seconds`

Reason:

- long enough to establish origin, build phase, and return
- short enough to cut around missing source and avoid over-explaining

## First-Cut Thesis

The cut should leave the viewer with one clear feeling:

This is the story of a man who escaped a closed system, built himself inside America with intent, and returned home carrying a different meaning than fame alone can explain.

## Relationship Follow-Through

## Immediate send

Send Zoltan the promised `My Big Toe` reference now so the thread is not only extractive.

### Reference to send

- Title: `Tom Campbell - My Big Toe - Part 1`
- URL: <https://www.youtube.com/watch?v=fT8LaMrn_MM>

### Suggested message draft

```text
Hey Zoltan, sending over the My Big Toe reference I mentioned:
https://www.youtube.com/watch?v=fT8LaMrn_MM

Also pushing the documentary thread forward on my side. I’m organizing the first mock-trailer pass now around the Hungary -> build -> return arc so we can get something real to react to instead of keeping it abstract.
```

### Why this matters

- it closes the open loop in the relationship
- it gives a natural bridge back into documentary discussion
- it keeps the trailer work attached to live subject access rather than isolated planning

## Priority Asset Gathering

## Must gather first

These are the minimum assets worth chasing immediately because they directly support the trailer thesis:

1. any Zoltan-in-Hungary footage or stills
2. any interview material where he discusses escape, ambition, reinvention, or return
3. any public or owned media that shows scale in America without becoming generic concert coverage
4. any stills, press, or archival material tied to youth, communist-era context, or early Hungary
5. any images or clips that frame him as builder, operator, designer, or strategist

## Asset buckets to build

Create and fill these six bins:

1. `Hungary / origin`
2. `American build phase`
3. `Return home`
4. `Interviews / statements`
5. `Archive / press / stills`
6. `Music / pitch references`

## Priority asks to Zoltan or team

If there is one asset request round, ask for:

- Hungary footage, especially walking, arrival, crowds, city, or symbolic return moments
- any interview files or voice notes about leaving Hungary, early struggle, building success, or what returning means
- any archival family or youth material that can visually signal the old world
- any behind-the-scenes or operational material that shows business, systems, design, touring logistics, or ownership
- any press or public-recognition moments from Hungary

## Best currently available materials for pass 1

Until owned source is consolidated, pass 1 can still be built from:

- the existing written thesis and trailer objective
- public reference clips from the Zoltan watchlist
- stills, thumbnails, article grabs, map cards, and text cards
- any already-owned production or archive fragments found during binning

This means the first pass should be trea
…

Cinematic Family Stories Live Outreach Block (Mar 28, 6:02 PM)

wave,priority,recipient,segment,contact_route,primary_angle,subject_line,followup_1_subject,followup_2_subject,send_owner,followup_owner,quote_owner,close_owner,send_date,followup_1_due,followup_2_due,status,last_touch_date,next_action_date,reply_type,objection_type,conversion_friction,escalated_to_michael,outcome,notes
1,1,Laura Hedgecock,speaker_educator,Laura@LauraHedgecock.com,storytelling_overlap,your storytelling work overlaps strongly with a new family-film offer,quick follow-up on storytelling overlap,closing the loop on this story-to-film idea,Jay,Jay,Michael,Michael,2026-03-30,2026-04-03,2026-04-08,ready_to_send,,2026-03-30,no_reply,none,none,no,,Use storytelling and ancestry framing
1,1,Kate Townsend,professional_genealogist,kate@familyhistoryinvestigations.com,research_to_film_referrals,possible research-to-film referral fit for your clients,quick follow-up on research-to-film,closing the loop,Jay,Jay,Michael,Michael,2026-03-30,2026-04-03,2026-04-08,ready_to_send,,2026-03-30,no_reply,none,none,no,,Lead with premium downstream offer
1,1,Diane L. Richard,professional_genealogist_educator,dianelrichard@mosaicrpm.com,education_plus_referral,possible fit between family-history education and legacy film delivery,quick follow-up on legacy film idea,closing the loop on this idea,Jay,Jay,Michael,Michael,2026-03-30,2026-04-03,2026-04-08,ready_to_send,,2026-03-30,no_reply,none,none,no,,Good webinar or collaboration candidate
1,2,Jennifer Dunn,apg_chapter_officer,writerjenniferdunn@gmail.com,chapter_network_intro,APG chapter network and a simple family-film referral angle,quick follow-up on chapter-level fit,closing the loop,Jay,Jay,Michael,Michael,2026-03-30,2026-04-03,2026-04-08,ready_to_send,,2026-03-30,no_reply,none,none,no,,Use chapter-network and writer angle
1,2,Lisa Weaver,apg_chapter_officer,lisa@weavergenealogy.com,chapter_visibility,possible APG chapter-level visibility for a legacy-film offer,quick follow-up on chapter visibility,last note on this idea,Jay,Jay,Michael,Michael,2026-03-30,2026-04-03,2026-04-08,ready_to_send,,2026-03-30,no_reply,none,none,no,,Resource or referral framing over hard sell

Cinematic Family Stories Active Operating Setup (Mar 28, 6:02 PM)

# Cinematic Family Stories Active Operating Setup

Date: 2026-03-28

Purpose:

- restart execution without rebuilding strategy
- convert warmed outreach assets into one live operating motion
- make Jay's ownership clear enough that the pipeline can actually run

## Shortest Path

The shortest path is:

1. confirm the live owner model with Jay using one explicit message
2. use only the first `5` contacts that already have direct email paths
3. send wave 1 on Monday, `2026-03-30`
4. track every reply, objection, and handoff in one live CSV
5. review on Friday, `2026-04-03`, then release wave 2 only after real reply data exists

This avoids three common stalls:

- no waiting on more list-building
- no waiting on new copy
- no trying to operationalize all `25` prospects at once

## Proposed Owner Model

Proposed live model to confirm with Jay:

- Jay owns:
  - day-0 sends from the warmed inbox
  - follow-up timing
  - reply triage
  - reply logging
  - objection tagging
  - simple soft-pass and housekeeping responses
- Michael owns:
  - quotes
  - calls
  - memorial urgency
  - premium or archive-heavy leads
  - pricing exceptions
  - custom-scope negotiation
  - closing

Decision rule:

- if a lead wants a quote, call, rush timeline, premium scope, or non-standard package framing, Jay escalates same day
- if a lead is a clear no, not now, unsubscribe, or routing issue, Jay closes the loop and logs the outcome

## Jay Confirmation Message

Use this message to lock the model fast:

```text
Jay,

I want to restart Cinematic Family Stories as a live outbound motion on Monday, March 30, 2026.

Proposed owner model:

You own:
- day-0 sends from the warmed inbox
- follow-up timing
- reply triage
- logging replies / objections / friction
- handing qualified conversations to me

I own:
- quotes
- calls
- memorial urgency
- premium or custom-scope conversations
- pricing exceptions
- closing

If you're good with that, wave 1 is the first 5 direct-email contacts on Monday, with review on Friday, April 3, 2026 before wave 2.
```

## Wave 1 Live Outreach Block

Use the first block that requires no new research:

1. Laura Hedgecock
2. Kate Townsend
3. Diane L. Richard
4. Jennifer Dunn
5. Lisa Weaver

Why this block:

- all `5` already have a direct email route in the send sheet
- all `5` already have send-ready subjects and positioning
- this is enough volume to generate reply data without overwhelming the warmed inbox

Source files:

- [2026-03-24-cinematic-family-stories-first25-send-sheet.csv](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-24-cinematic-family-stories-first25-send-sheet.csv)
- [2026-03-22-cinematic-family-stories-first10-send-ready.md](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-22-cinematic-family-stories-first10-send-ready.md)
- [2026-03-24-cinematic-family-stories-first25-send-ready.md](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-24-cinematic-family-stories-first25-send-ready.md)

## Operating Dates

Use these dates for the first live block:

- Monday, `2026-03-30`: send initial `5`
- Friday, `2026-04-03`: send follow-up 1 to non-responders and review replies
- Wednesday, `2026-04-08`: send follow-up 2 to non-responders still worth keeping open
- Thursday, `2026-04-09`: categorize objections and decide whether to release wave 2

## Live Tracking Rules

Use one row per contact in the live block CSV.

Track these items on every touch:

- current status
- last touch date
- next action date
- reply type
- objection type
- conversion friction
- escalated to Michael or not
- outcome

Use these controlled values where possible.

Reply type:

- no_reply
- interested
- referral_curious
- wants_sample
- wants_quote
- wants_call
- not_now
- no
- wrong_contact
- out_of_office

Objection type:

- none
- price
- timing
- old_photos
- premium_scope
- call_friction
- payment
- revision_pressure
- fit_unclear

Conversion friction:

- none
- unclear_offer
- unclear_next_step
- trust_gap
- too_early
- low_urgency
- inbox_mismatch
- no_direct_contact

## Review Gate For Wave 2

Only release wave 2 after:

- all `5` wave-1 rows are updated
- objections are tagged, not just described loosely
- qualified replies are handed off same day
- there is at least one clear lesson to apply to the next block

Do not rewrite the positioning mid-block unless there is a repeated pattern across multiple replies.

## Active Operating Surfaces

Primary live tracker:

- [2026-03-28-cinematic-family-stories-live-outreach-block.csv](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-28-cinematic-family-stories-live-outreach-block.csv)

Reference rules:

- [2026-03-24-cinematic-family-stories-jay-handoff-pack.md](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-24-cinematic-family-stories-jay-handoff-pack.md)
- [2026-03-24-cinematic-family-stories-objection-sheet.md](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-24-cinematic-family-stories-objection-sheet.md)
- [2026-03-24-cinematic-family-stories-revenue-ops-setup.md](/Users/walter/Documents/Walter Workspace/walter/deliverables/2026-03-24-cinematic-family-stories-revenue-ops-setup.md)

## Immediate Next Moves

1. send the owner-model confirmation to Jay
2. once Jay confirms, send the `5` wave-1 emails on Monday, `2026-03-30`
3. log replies directly into the live tracker instead of updating scattered notes
4. escalate quote/call/premium/memorial replies to Michael the same day