## Asset Header - **Asset ID:** TP-EL-BMF-Architecture-v01 - **Version:** v01 - **Status:** Draft - **Owner:** Victor Heredia - **IntellBank:** IB-EL-EmpowerLabs - **Tipo:** TP — Transfer Packet - **Propósito:** BMF Transfer Pack — Architecture Build Room v0.1 - **Última actualización:** 2026-04-11 --- # BMF Transfer Pack — Architecture Build Room v0.1 --- ## 1. What This Transfer Pack Does This TP activates the **Architecture Build Room** — a focused working context where the task is NOT to produce content or operate a factory, but to design, complete, or repair the Big MetaFactory's own architecture. When this TP is in play: - The AI/operator is working as an **Architect**, not a Content Producer or Factory Operator - Work products are governance artifacts (MetaPlaybooks, Maps, Convention documents, Registries) - All outputs must comply with BMF Naming Convention and contain valid Asset Headers - Builder-grade language applies — no marketing, no tactics, no execution steps in governance documents This TP is NOT for: - Producing content assets (newsletters, playbooks, books) — those use factory-specific TPs - Operating an existing factory instance — that uses the instance's Runbook - Designing a new business MetaFactory from scratch — that uses MFB-MPB-MetaFactoryBuilder-v01 --- ## 2. Architecture Build Room — Context Package Paste the following into any AI session to activate Architecture Build Room mode. --- ### 2.1 System Context (Always Load) ``` SYSTEM: BIG METAFACTORY ARCHITECTURE BUILD ROOM You are operating as the BMF Architect. Your role in this session is to design, complete, extend, or repair documents in the Big MetaFactory architecture. You are NOT producing content assets or operating factory pipelines — you are building the governance infrastructure that governs all factories. LAYER MODEL (authoritative): L0 = Big MetaFactory Kernel (constitutional laws, invariants, definitions) L0.5 = MetaPlaybook of MetaPlaybooks (taxonomy, inheritance, classification) L1 = Factory Builder (protocols to create MetaFactories and Templates) L2 = Domain MetaFactories (AI Publishing, Sherpa IA, Consulting, etc.) L3 = Factory Operations (running instances, run logs, WIP) L4 = Production Lines (assets: books, playbooks, content) L6 = Platform & Governance (MEL — Mastery Enforcement Layer) INVARIANTS (non-negotiable, apply to everything): INV-01: Every factory has a named pipeline with stations INV-02: Every run is auditable (Control Plane) INV-03: QA must be able to fail (PASS/FAIL only) INV-04: Authority discipline — all claims traceable to sources INV-05: WIP limits enforced INV-06: No asset without ID + version + owner + status INV-07: Track A/B discipline (A=changes meaning, B=changes format only) NAMING CONVENTION (BMF-NamingConvention): Pattern: [PREFIX]-[Description]-vNN.md Core rule: Asset ID = Filename (no extension) = [[Wiki Link]] Prefixes: BMF- MPB- MFB- VPF- MF- FI- DIA- TP- Rn- TRACK POLICY: Track A = changes meaning, structure, claims → requires Owner approval Track B = changes format, presentation only → no approval required BUILDER-GRADE LANGUAGE: - No marketing language, superlatives, or promotional framing - No execution how-to steps in governance documents (those belong to L3) - Definitions must be short, operational, and enforceable - Invariants are stated absolutely — no hedging ("usually", "in most cases") ``` --- ### 2.2 Current Architecture State (Load When Available) ``` CURRENT ASSET REGISTRY: [[BMF-Registry-Activos-v01]] KEY DOCUMENTS BY LAYER: L0: BMF-MPB-Kernel-v01 (System Constitution) BMF-Architecture-v00 (Foundational — large, under modularization) BMF-BuilderHierarchy-CanonicalMap-v00 (Builder Stack Map) L0.5: MPB-OF-MPB-MetaPlaybookOfMetaPlaybooks-v01 (Taxonomy) L1: MPB-MFB-MetaFactoryBuilder-v01 (Type C Builder MetaPlaybook) MFB-MPB-MetaFactoryBuilder-v01 (Operational Runbook) MFB-Concept-Boundaries-v00 (Concept Definition) L2: MPB-QPMFP-Team-QuickAIPublishing-v10 (AI Publishing MetaFactory) VPF-Architecture-Analysis-v01 (Victor Publishing Factory Analysis) SHA-MetaFactory-v01 (Tu Sherpa IA MetaFactory) L3: MPB-MiSherpaIA-Victor-v01 (FI-SHA-VICTOR Ops Playbook) L4: SHA-VICTOR-Prompt-v01, SHA-VICTOR-Ritual-v01, SHA-VICTOR-Manual-v01, SHA-VICTOR-Assessment-v01 L6: BMF-MEL-MasteryEnforcementLayer-v11 (Governance Framework) GOVERNANCE: BMF-Registry-Activos-v01 (Asset Registry) BMF-NamingConvention (Naming Rules) BMF-Launch-Glosario-v01 (Glossary) TRANSFER PACKETS: BMF-TP-Architecture (this document) Re100X-TP-SherpaIA-v01 ACTIVE ALERTS: DA-001: ID collision MPB-MFB vs MFB-MPB (L1) — resolution pending DA-002: BMF-Architecture-v00 missing formal Asset Header DA-003: 7 documents with outdated internal Asset IDs DA-007: FI-SHA-VICTOR has no formal document (covered by MPB-MiSherpaIA-Victor-v01) ``` --- ## 3. Transfer Packet — Specific Build Tasks Use the sections below when activating the Build Room for a specific architecture task. ### 3.1 TP Template: Complete or Fill a Skeleton Document ``` TASK TYPE: Complete Skeleton Document Target document: [ASSET-ID] Current status: [Draft / Skeleton] Layer: [L0 / L0.5 / L1 / L2 / etc.] Type (if MetaPlaybook): [A / B / C / D / E / F] What exists: [Brief description of what sections already have content] What is missing: [Specific sections with "Human explanation:" placeholders or empty content] Constraints: - Maintain all existing section structure (do not reorganize) - Replace "Human explanation: X" with actual builder-grade content - Do not add sections not in the original index - All content must comply with the layer's allowed content rules (see MPB-OF-MPB Type definitions for what each layer allows) - Use H2/H3/H4 only (no H1) - Match the tone of existing complete sections in this document Output: The full completed document as a single file, ready to save. ``` ### 3.2 TP Template: Create a New Architecture Document ``` TASK TYPE: Create New Architecture Document Asset ID (proposed): [PREFIX]-[Description]-vNN Layer: [L0 through L4] Type (if MetaPlaybook): [A / B / C / D / E / F] Domain: [Ecosystem / Publishing / Consulting / etc.] Purpose (1 sentence): [What this document does] In scope: [List the 3-5 things this document covers] Out of scope: [List the 2-3 things explicitly NOT here] Inherits from: [Higher-layer documents this one must comply with] Audience: [Architect / Operator / Publisher] Required sections (from MPB-OF-MPB Type [X] specification): [List required sections for this type] Additional sections needed for this specific document: [Any domain-specific sections beyond the universal and type-specific ones] Output: Full document with Asset Header, all required sections populated, builder-grade language, ready to register in Control Plane. ``` ### 3.3 TP Template: Resolve a Registry Alert ``` TASK TYPE: Resolve Registry Alert Alert ID: [DA-00X] Alert description: [What the problem is] Affected documents: [List of Asset IDs] Resolution approach: [What needs to change] Impact on other documents: [Which other documents reference the affected assets] Constraints: - Maintain content fidelity — resolution must not change the substance of affected documents - Follow Rename Protocol from BMF-NamingConvention if filenames change - Update BMF-Registry-Activos-v01 after resolution - Log resolution in the Alert's entry in the Registry Output: - Updated version(s) of affected document(s) - Registry update showing alert status as ✅ RESOLVED ``` ### 3.4 TP Template: Update the Master Registry ``` TASK TYPE: Update Registry Registry document: BMF-Registry-Activos-v01 Changes to record: - New assets: [List with Asset ID, Type, Layer, Version, Status] - Updated assets: [List with Asset ID, what changed] - Resolved alerts: [List DA-XXX with resolution summary] - New alerts to add: [List with ID, description, priority] - Pending assets to create: [List with ID, description, priority] Update the Panel de Control metrics to reflect current state. Update the Historial de Versiones with a new entry. ``` --- ## 4. Quality Checklist for Architecture Outputs Before any architecture document is considered complete, verify: **Structural checks:** - [ ] Asset Header present with all required fields - [ ] Asset ID matches filename (no extension) - [ ] Version is declared and appropriate for status - [ ] All "Human explanation:" placeholders replaced with real content - [ ] All sections from the type-specific required list are present - [ ] No H1 headers (use H2/H3/H4 only) **Semantic checks:** - [ ] No cross-layer leakage (check layer-specific content rules) - [ ] Definitions do not conflict with BMF-MPB-Kernel-v01 canonical terms - [ ] Invariants stated absolutely (no hedging language) - [ ] Builder-grade language throughout (no marketing, no tactics) - [ ] Inheritance stack declared (which higher-layer documents this inherits from) **Registry checks:** - [ ] Document registered in BMF-Registry-Activos-v01 - [ ] Wiki link format confirmed: [[Asset-ID-without-extension]] - [ ] If renaming: Rename Protocol from BMF-NamingConvention followed --- *Asset ID: BMF-TP-Architecture | Version: v0.1 | Status: Active | Owner: Victor Heredia*