## Asset Header

- **Asset ID:** OUT-MIN-EL-BMF-VPF-ArchitectureAnalysis-v01
- **Version:** v01
- **Status:** Draft
- **Owner:** Victor Heredia
- **IntellBank:** IB-EL-EmpowerLabs
- **Tipo:** OUT-MIN — Output MIN
- **Propósito:** VPF — Victor Publishing Factory — Analysis & Architecture v0.1
- **Última actualización:** 2026-04-11

---

# VPF — Victor Publishing Factory — Analysis & Architecture v0.1

**Asset ID:** VPF-Architecture-Analysis-v01
**Versión:** v0.1
**Status:** Analysis → Decision Pending
**Owner:** Victor Heredia
**Fecha:** 2026-03-01
**Layer:** L2 (MetaFactory) — within Big MetaFactory Architecture

---

## 0. Executive Summary (One-Screen)

```
═══════════════════════════════════════════════════════════
VICTOR PUBLISHING FACTORY (VPF) — Architecture Decision
═══════════════════════════════════════════════════════════

SITUATION
- You have a well-designed MPMF v0.1 (for full MasterPlaybooks)
- You now need to produce MANY mini guides/playbooks (2-3 pages)
- Your inputs are: draft / structure / idea (no recording required)
- Goal: a personal publishing system that handles ALL content types

ANALYSIS VERDICT
- MPMF v0.1: KEEP AS-IS → it's well-designed for full books
- Gap identified: NO lightweight factory exists for mini content
- Solution: build a 3-tier VPF umbrella with a new Sprint Factory

ARCHITECTURE
- Tier 1: Sprint Factory     → 2-3 page mini guides/playbooks
- Tier 2: Standard Factory   → 5-30 page expanded playbooks
- Tier 3: MasterPlaybook MF  → Full books (existing MPMF v0.1)

COWORK ANSWER
- One persistent VPF Hub session → Registry + Control Plane
- Mini/Standard content → produced in Hub or batch sessions
- Full books → ONE dedicated Cowork session PER BOOK

IMMEDIATE ACTION
- Approve this document → Build Sprint Factory first (highest volume)
- Run MPMF v0.1 Sprint 0 in parallel (full books)
═══════════════════════════════════════════════════════════
```

---

## 1. What You Currently Have (Inventory)

Reading your vault, you already have a richer publishing system than you may realize. Here's what exists:

### 1.1 The Infrastructure You've Already Built

**Big MetaFactory (BMF) — L0 Architecture**
The master operating system. Pipeline invariant, Track A/B governance, WIP limits, QA gates, Control Plane. Everything you build lives inside this.

**MasterPlaybooks Publishing MetaFactory (MPMF) v0.1**
Your most developed publishing plan. Designed specifically for full MasterPlaybooks (8–15 chapters). Has 8 phases, Author OS, Viability Research, Marketing Kit. Requires 12–16 hours of human time per book. Status: Design → awaiting Sprint 0 approval.

**MPlaybooks Factory Plan v2 (Feb 2026)**
A solid 7-station editorial pipeline (Inventory → Book Spec → Editorial → Research → Copyedit → Art Direction → Packaging → Publish). Has Voice Packs, Track A/B, pilot-first logic. Overlaps heavily with MPMF v0.1 but focuses more on your existing backlog of ~20 books.

**Quick AI Publishing MetaFactory Playbook (QPMFP) — Team Edition v1**
The most operational document you have. Full team governance, daily cadence, roles (Ángeles/Anaí/Juan Carlos), copy-paste templates. This is the operating manual, not the pipeline design.

**MetaFactory Layers (L0→L4)**
The classification system: L0 = Kernel, L1 = MetaPlaybook Builder, L2 = Individual MetaFactories, L3 = Operations Playbooks, L4 = Production Playbooks.

**Existing Content Type Evidence**
- Nate Jones Mini Playbooks (produced in Google Docs)
- Book Summaries (via Starter Pack → soporte@mplaybooks.com)
- Full MasterPlaybooks (backlog of ~20 books)
- MetaPlaybooks (strategic frameworks)
- Content pieces: newsletters, cards, shorts, carousels

### 1.2 The Critical Gap

**NONE of your current systems are designed for mini content (2-3 pages).**

The MPMF v0.1 is an 8-phase machine built for 8-15 chapter books. Using it to produce a 2-page mini guide would be like using a factory assembly line to make a single sandwich. The overhead would kill the volume advantage.

The Nate Jones Mini Playbooks were apparently produced ad-hoc in Google Docs — no pipeline, no QA, no control plane. That's the proof: you have the demand for mini content but no factory for it.

---

## 2. Content Taxonomy (What VPF Must Produce)

Based on your vault, here is the full content spectrum you need to cover:

| Format | Pages | Depth | Input Needed | Volume | Pipeline Weight |
|--------|-------|-------|--------------|--------|-----------------|
| Mini Guide / Mini Playbook | 2–3 | Focused, one topic | Draft / idea / structured outline | HIGH | Ultra-lean |
| Expanded Playbook | 5–20 | Multi-section, frameworks | Draft + structure | MEDIUM | Standard |
| Book Summary (Resume) | 8–15 | Research-based | Book title/PDF | MEDIUM | Standard |
| MasterPlaybook Standard | 30–80 | Full methodology | Author interviews + draft | LOW | Heavy (MPMF v0.1) |
| MasterPlaybook Inteligente | 30–80 + templates | Full methodology + AI artifacts | Author interviews + draft | LOW | Heavy (MPMF v0.1) |
| MetaPlaybook | 15–40 | Strategic framework | Deep thought / existing material | LOW | Standard–Heavy |

**The key insight:** Volume is inverse to complexity. Mini guides will be your highest-volume output, but your current infrastructure only serves the lowest-volume end (full books).

---

## 3. Should You Use MPMF v0.1 or Build Something New?

### 3.1 MPMF v0.1 Assessment

**Verdict: KEEP IT. Don't modify it for mini content. Approve Sprint 0.**

MPMF v0.1 is well-designed for its scope. It has:
- Clean 8-phase pipeline with clear I/O at each gate
- Proper Author OS concept (Voice Pack equivalent)
- Kill criteria, WIP limits, severity model
- Pricing framework and market research built in
- Marketing kit generation included

The only issue: it was designed for one type of output (full MasterPlaybooks). It is NOT designed for:
- Mini content (2-3 pages) — the phases are disproportionately heavy
- No-recording inputs — it assumes author interviews as a key input
- High-volume, fast-turnaround production

**Action: Approve MPMF v0.1 for Sprint 0 (full books). Run it in parallel with the new Sprint Factory.**

### 3.2 What You Need to Build

You need a **Sprint Factory** — a dramatically lighter pipeline designed specifically for mini content (2-3 pages). And a **Standard Factory** for the middle tier (5-30 pages).

Together these form the **Victor Publishing Factory (VPF)**: a 3-tier umbrella that covers your entire content spectrum while staying compliant with the BMF architecture.

---

## 4. The Victor Publishing Factory (VPF) — Architecture

VPF is an L2 MetaFactory inside BMF. It contains three factories operating in parallel, each with its own pipeline weight, matching the content format they produce.

```
┌─────────────────────────────────────────────────────────────────┐
│              VICTOR PUBLISHING FACTORY (VPF)                     │
│              L2 MetaFactory — inside BMF                         │
├──────────────┬──────────────────┬──────────────────────────────┤
│   TIER 1     │    TIER 2        │    TIER 3                     │
│ Sprint       │ Standard         │ MasterPlaybook                │
│ Factory      │ Factory          │ Factory                       │
│              │                  │                               │
│ 2-3 pages    │ 5-30 pages       │ 30-80+ pages                  │
│ Mini guides  │ Playbooks        │ Full MasterPlaybooks          │
│ Mini plybks  │ Book Summaries   │ MasterPlaybook Inteligente    │
│              │ MetaPlaybooks    │                               │
│ 3 stations   │ 5 stations       │ 8 phases (MPMF v0.1)          │
│ ~30-60 min   │ ~2-4 hours       │ ~12-16 hrs human time         │
│ Track B      │ A or B           │ Track A                       │
│ default      │                  │                               │
└──────────────┴──────────────────┴──────────────────────────────┘
         Shared: BMF Pipeline Invariant + Control Plane
```

### 4.1 Tier 1 — Sprint Factory (Mini Guides / Mini Playbooks)

**Purpose:** Produce 2-3 page focused guides from a draft, idea, or structured outline.
**Input options:** (a) raw draft from Victor, (b) structured outline, (c) fully fleshed idea in bullet form.
**Output:** Formatted mini guide/playbook ready for MasterPlaybooks platform (MD + PDF).
**Human time per piece:** ~10-15 minutes (review + approval only).

**Pipeline — 3 Stations:**

```
STATION 1: INTAKE BRIEF (Transfer Packet)
- Input: Victor's draft / idea / outline (text, voice memo transcript, notes)
- Cowork: Creates the Mini Brief (topic, target reader, transformation promise, format, length)
- Gate: Victor approves brief in < 5 min (or auto-approve if Track B)
- Output: Mini Brief locked

STATION 2: PRODUCTION
- Input: Approved Mini Brief + Victor's raw material
- Cowork: Expands + structures + writes the 2-3 page guide
- Applies Victor Voice Pack throughout
- Output: Draft mini guide (structured, formatted)

STATION 3: QA + PACKAGE
- Input: Draft mini guide
- Cowork: QA checklist (truth, voice, length, structure)
- Cowork: Formats to MasterPlaybooks standard (MD + PDF)
- Gate: Victor reviews in < 5 min (or auto-ship on Track B fast items)
- Output: Published-ready mini guide with ID + version
```

**Key rules:**
- Victor Voice Pack is the default (no Author OS setup needed for Victor content)
- No market research required — these are tactical, focused, fast
- Track B default: most mini content is low-stakes, fast-lane
- Batch production enabled: can run 5-10 mini guides in a single Cowork session
- WIP limit: max 5 mini guides in production simultaneously

### 4.2 Tier 2 — Standard Factory (Playbooks, Summaries, MetaPlaybooks)

**Purpose:** Produce 5-30 page expanded playbooks, book summaries, or strategic frameworks.
**Input options:** Draft, structured outline, or "research + write" brief (for book summaries).
**Output:** Complete playbook/summary document in multiple formats.
**Human time per piece:** ~30-60 minutes.

**Pipeline — 5 Stations:**

```
STATION 1: BRIEF (Transfer Packet)
- Defines scope, audience, format, depth, track

STATION 2: RESEARCH / EXPAND (if needed)
- For book summaries: web research + source pack
- For original playbooks: expand Victor's draft material
- For MetaPlaybooks: framework synthesis

STATION 3: PRODUCTION
- Full draft with Voice Pack applied
- Sections, frameworks, examples, CTAs

STATION 4: QA GATE (PASS/FAIL)
- Truth, voice, structure, completeness

STATION 5: PACKAGING
- Format to delivery standard
- Multiple outputs if needed (MD, PDF, DOCX)
```

### 4.3 Tier 3 — MasterPlaybook Factory

**This is your existing MPMF v0.1. Keep it exactly as designed.**
Run Sprint 0 now. It's ready.

---

## 5. The Victor Voice Pack (VVP) — The Critical Asset

Across all three tiers, the Victor Voice Pack (VVP) is the single most important shared asset. It's what makes all content unmistakably Victor's, regardless of which pipeline produced it.

**VVP must be built first, before any production starts.** It should cover:

- Tono y ritmo (directivo, claro, práctico — no académico)
- Nivel de tecnicismo (experto que explica sin jerga innecesaria)
- Frases características ("MetaFactory", "pipeline invariant", "Factory Ready", etc.)
- Estructura preferida (diagnóstico → framework → acción)
- DO's: concreto, orientado a resultados, con ejemplos del mundo real
- DON'Ts: sin fluff motivacional, sin afirmaciones sin evidencia, sin listas vacías
- Ejemplos de párrafos modelo (extraídos de tus mejores escritos)

**You already have the structure for this from MPlaybooks Factory Plan v2 (Voice Pack section) and QPMFP (Writer Profile / Writer OS). You just need to populate it with actual Victor writing samples.**

---

## 6. Cowork Architecture — One Space vs. Many

This is one of the most important decisions for execution. Here is the analysis:

### 6.1 The Context Problem

Cowork sessions have context limits. Full book production spans many hours and many documents. If all books are in one session, context will overflow and important decisions/documents get lost.

### 6.2 Recommended Architecture

```
┌─────────────────────────────────────────────────────────────┐
│         VPF HUB SESSION (persistent, always-on)             │
│  • Registry Master (all content in production)              │
│  • VVP (Victor Voice Pack) — loaded always                  │
│  • Control Plane (WIP tracking, RunLogs)                    │
│  • Sprint Factory production (Tier 1 — batches)             │
│  • Standard Factory production (Tier 2 — batches)           │
└─────────────────────────────────────────────────────────────┘
           │
           ├── BOOK SESSION: [Title-1]  (Tier 3 only)
           │   One dedicated Cowork session per full book
           │   Context: Author OS + Chapters + Research Pack
           │
           ├── BOOK SESSION: [Title-2]  (Tier 3 only)
           │
           └── BOOK SESSION: [Title-N]  (Tier 3 only)
```

### 6.3 The Rule

| Content Type | Where It Lives |
|---|---|
| Mini guides (Tier 1) | VPF Hub session — batch production |
| Standard playbooks (Tier 2) | VPF Hub session — one at a time |
| Book summaries (Tier 2) | VPF Hub session |
| Full MasterPlaybooks (Tier 3) | Dedicated session per book |

**Rationale:**
- Mini and Standard content is context-light. 10 mini guides can be produced in one session without context overflow.
- Full books are context-heavy: chapters accumulate, the Author OS needs to persist, research packs are large. A dedicated session per book keeps context clean and allows you to return to that book across multiple work sessions.
- The Hub session is your Command Center: it always has the Registry and Voice Pack loaded.

### 6.4 Session Naming Convention

```
VPF-HUB               → Master Registry + Tier 1 + Tier 2 production
VPF-BOOK-[SLUG]        → One dedicated session per Tier 3 book
VPF-BATCH-[DATE]       → Optional: batch sprint for mini content days
```

---

## 7. The Pendientes 2026 Sheet — How It Maps to VPF

Based on what I can see from your MPlaybooks Home.md references, your MPbs-Factoria catalog contains your pending books backlog. These items should be classified across the three tiers:

**Classification exercise (to run in VPF Hub):**
1. Pull all pending items from the Pendientes sheet
2. Classify each as Tier 1 (mini), Tier 2 (standard), or Tier 3 (full book)
3. Assign initial status and Track (A/B)
4. Prioritize Tier 1 items for the Sprint Factory (highest volume, fastest wins)

**Early signal:** You mentioned mini guides/playbooks as the primary volume driver now. This means the Sprint Factory (Tier 1) is your highest-priority build — even before completing the MPMF v0.1 Sprint 0.

---

## 8. Build Priority — What to Do First

Given your goal of producing MANY smaller guides fast, here is the recommended sequence:

### Priority 1 — Victor Voice Pack (do this in one session, today)
Build VVP v0.1. Collect 5-10 examples of your best writing from the vault. Extract tono, estructura, frases características. This unlocks all production across all tiers.

### Priority 2 — Sprint Factory (Tier 1) — Build + First Batch
Build the Sprint Factory pipeline (3 stations). It's simple enough to design and run in Cowork without a formal Sprint 0. Produce your first 5 mini guides as the pilot. Capture RunLogs.

### Priority 3 — MPMF v0.1 Sprint 0 (Tier 3, parallel)
Approve MPMF v0.1 as-is. Run Sprint 0 deliverables (Book Brief Template, Author OS Template, QA Checklist, Registry Master, Viability Report Template). These can be produced in a dedicated MPMF session.

### Priority 4 — Standard Factory (Tier 2)
Once Tier 1 is running and Tier 3 Sprint 0 is complete, formalize the Standard Factory pipeline. Many of its patterns come naturally from the experience of running Tier 1 and Tier 3.

### Priority 5 — Classify Pendientes Backlog
Run the full classification of your ~20+ pending items across the three tiers. This gives you a production queue with realistic timelines.

---

## 9. What NOT to Do

**Do not merge the three tiers into one mega-pipeline.** The temptation will be to create a "universal" pipeline that covers everything from 2-page mini guides to 80-page books. This creates the worst of both worlds: too heavy for mini content, too light for full books.

**Do not start full book production before the Sprint Factory is running.** You said the priority is many smaller guides. Honor that. Sprint Factory first.

**Do not run more than 3 books simultaneously in Tier 3.** MPMF v0.1 already has this WIP limit. Respect it.

**Do not skip the Victor Voice Pack.** Every piece produced without it will sound generic and need rework.

---

## 10. Decision Summary

| Question | Answer |
|---|---|
| Use MPMF v0.1? | YES — for full MasterPlaybooks (Tier 3). Approve Sprint 0 now. |
| Build new factory for mini content? | YES — Sprint Factory (Tier 1). Build first. |
| One Publishing MetaFactory or multiple? | VPF umbrella with 3 internal tiers. One registry, three pipelines. |
| One Cowork space or per-book? | One Hub session for Tier 1 + Tier 2. Dedicated session per book for Tier 3. |
| First action? | Build Victor Voice Pack v0.1 → then Sprint Factory pilot. |

---

## 11. Immediate Next Steps (Sprint 0 for VPF)

Cowork can execute the following today:

1. **Victor Voice Pack v0.1** — Collect your best writing samples from the vault, build the VVP document
2. **Sprint Factory Pipeline Doc** — Formalize the 3-station pipeline (Transfer Packet template, QA checklist, Output format spec)
3. **VPF Registry Master (XLSX)** — Control Plane spreadsheet for all three tiers
4. **Classify first batch of Pendientes** — Pull the pending items, classify as Tier 1/2/3, create production queue

---

*This document is the architecture brief for the Victor Publishing Factory (VPF). Requires Victor's approval to proceed with Sprint 0.*

**Status:** Pending Victor approval → Sprint 0 execution