## Asset Header

- **Asset ID:** MePB-BMF-MetaFactoryBuilder-v01
- **Version:** v01
- **Status:** Draft
- **Owner:** Victor Heredia
- **IntellBank:** IB-XX-Maestro
- **Tipo:** MePB — MetaPlaybook
- **Propósito:** Mpb-mfb — Meta Factory Builder Meta Playbook (skeleton V0
- **Última actualización:** 2026-04-11

---

# Mpb-mfb — Meta Factory Builder Meta Playbook (skeleton V0

## 

Chat original: [https://chatgpt.com/g/g-p-692b375798388191b4858e1c523a638d-metafactory-lab/c/69646e5c-a42c-8329-9976-5a88ec23754f](https://chatgpt.com/g/g-p-692b375798388191b4858e1c523a638d-metafactory-lab/c/69646e5c-a42c-8329-9976-5a88ec23754f)   
Chat público: [https://chatgpt.com/share/69794b0e-43c4-8004-a08c-3f1ca06a0312](https://chatgpt.com/share/69794b0e-43c4-8004-a08c-3f1ca06a0312) 

## **0\. Human Introduction and Index**

### **0.1 Human Introduction**

This MetaPlaybook defines the **MetaFactory Builder** as an enforceable build system for creating **Domain MetaFactories** and their governing **Type D (L2) Domain MetaFactory MetaPlaybooks**.

It exists to prevent domain drift by making it deterministic:

* what a Domain MetaFactory MetaPlaybook must contain  
* what it is forbidden to contain  
* how Domain MetaFactories delegate to Factory Builders  
* how QA and promotion work at the MetaFactory layer

This is builder-grade documentation. It defines **protocols, required sections, and validation tables** — not execution steps.

### **0.2 Index**

1. Orientation  
2. Canonical Definitions (MetaFactory Builder Context)  
3. Scope and Boundaries  
4. Build Lifecycle (Type D Production)  
5. Required Sections for Type D (L2)  
6. Delegation Contracts (to Factory Builder)  
7. QA Hard Gate (Machine-Readable)  
8. Promotion and Release  
9. Control Plane Integration  
10. Anti-Patterns  
11. Appendices

---

## **Asset Header**

### **Asset ID**

MPB-MFB-MetaFactoryBuilder-v01

### **Canonical Role (DA-001 Resolution)**

**This document is the Type C Builder MetaPlaybook for the MetaFactory Builder layer (L1).**
It defines the governance structure and QA gates for CREATING Domain MetaFactory MetaPlaybooks (Type D, L2).
It does NOT contain operational how-to guidance for running a MetaFactory build process.

**Companion document:** `MFB-MPB-MetaFactoryBuilder-v01` is the operational runbook —
it contains the design phases (Thinking/Design/Build/Operate), Blueprint templates, and replication standards.
These two documents are complementary, not duplicates. MPB-MFB governs WHAT Type D must contain;
MFB-MPB guides HOW to design and build a MetaFactory.

---

### **Title**

MetaFactory Builder MetaPlaybook — Domain MetaFactories (Type D) Creation System

### **Version**

v0.1

### **Status**

Draft (Skeleton)

### **Owner**

Victor Heredia

### **Project Class**

BIG METAFACTORY (L1.x)

### **Purpose**

Provide a repeatable, auditable system to create **Domain MetaFactory MetaPlaybooks (Type D, L2)** that comply with:

* Big MetaFactory Kernel (L0)  
* MetaPlaybook of MetaPlaybooks (L0.5)  
* MetaPlaybook Builder (L1)  
* MetaFactory Builder — Concept & Boundaries (v0.1)

### **Scope**

**In scope**

* Required sections and constraints for Type D (L2)  
* Delegation boundaries from L2 → L1 Factory Builders  
* QA gates and promotion discipline for Domain MetaFactories  
* Control Plane hooks specific to Domain MetaFactories

**Out of scope**

* Building specific factory instances (Factory Builder)  
* Running factories day-to-day (Ops MetaPlaybooks)  
* Producing market-facing assets (Production MetaPlaybooks)  
* Tooling implementation (agents, automation, code)

### **Non-Negotiables**

* Builder-grade language only (no marketing)  
* Station archetypes, not steps  
* Explicit inheritance declaration  
* Delegation is mandatory (no hidden assumptions)  
* QA can fail (PASS / FAIL)  
* Everything is versioned and auditable  
* Use H2/H3/H4 only (no H1)

---

## **1\. Orientation**

### **1.1 Why This MetaPlaybook Exists**

Factory Builders can produce factories, but without a MetaFactory layer the domain will fragment. This MetaPlaybook ensures every domain builds factories under the same structural rules.

### **1.2 Relationship to Other Authorities**

* Inherits from Kernel (L0)  
* Must comply with MPB-OF-MPB (L0.5)  
* Must be compatible with MPB-BUILDER (L1)  
* Implements MetaFactory Builder — Concept & Boundaries (v0.1)

If conflicts exist, higher-layer authority wins.

---

## **2\. Canonical Definitions (MetaFactory Builder Context)**

### **2.1 Domain MetaFactory**

A governed family of factories within a single domain, defined by shared station archetypes, artifacts, modules, and constraints.

### **2.2 Type D MetaPlaybook (L2)**

A constitutional blueprint for a Domain MetaFactory. It defines architecture, registries, and boundaries — not operations.

### **2.3 Delegation Contract**

A declared interface where L2 defines what must exist, and L1 Factory Builders define how it is instantiated.

---

## **3\. Scope and Boundaries**

### **3.1 What This MetaPlaybook Governs**

* Structure of Type D MetaPlaybooks  
* Domain station archetypes  
* Domain artifact and module registries  
* Delegation to Factory Builders  
* QA and promotion

### **3.2 Hard Boundaries (Forbidden Content)**

A Type D MetaPlaybook may not include:

* Step-by-step procedures  
* Prompts or tactical instructions  
* Run cadence, WIP rules, defect handling (Ops)  
* Packaging / launch / marketing narratives (Production)

Any such content triggers FAIL.

---

## **4\. Build Lifecycle (Type D Production)**

### **4.1 Lifecycle Stages**

1. Intent Declaration  
2. Domain Declaration  
3. Skeleton Instantiation (Type D)  
4. Station Archetype Mapping  
5. Registry Completion (modules, templates, artifacts)  
6. Delegation Contracts to Factory Builder  
7. QA Hard Gate  
8. Promotion

### **4.2 Mandatory Declaration Fields**

* Domain  
* Type \= D  
* Layer \= L2  
* Audience  
* Risk level  
* Inheritance stack

---

## **5\. Required Sections for Type D (L2)**

### **5.1 Type D Required Sections (Canonical)**

A Type D MetaPlaybook must contain:

1. Asset Header  
2. Purpose and Domain Scope  
3. Inheritance Declaration  
4. Station Architecture (Archetypes)  
5. Artifact Registry (Domain)  
6. Module Registry (Domain)  
7. Template Registry (References)  
8. Delegation Contracts (to L1)  
9. QA Model (Domain extensions)  
10. Control Plane Hooks  
11. Boundaries and Out-of-Scope

### **5.2 Required Station Archetype Fields**

For each station:

* Station name  
* Purpose  
* Required inputs  
* Required outputs  
* Interfaces (schemas)  
* Delegation target (Factory Builder / Ops / Production)

---

## **6\. Delegation Contracts (to Factory Builder)**

### **6.1 Delegation Principle**

L2 declares *what must exist*.  
L1 declares *how it is instantiated*.

### **6.2 Minimum Delegation Artifacts**

Each Type D MetaPlaybook must output delegation contracts that include:

* Station → Factory Builder mapping  
* Required artifact schemas per station  
* Template references (IDs \+ versions)

---

## **7\. QA Hard Gate (Machine-Readable)**

### **7.1 Structural QA**

| CHECK\_ID | CATEGORY | RULE | RESULT |
| ----- | ----- | ----- | ----- |
| D-S-01 | Structure | Type declared as D and Layer as L2 | PASS / FAIL |
| D-S-02 | Structure | All Type D required sections present | PASS / FAIL |
| D-S-03 | Structure | All stations include required fields | PASS / FAIL |
| D-S-04 | Structure | Registries present (artifact/module/template) | PASS / FAIL |

### **7.2 Semantic QA**

| CHECK\_ID | CATEGORY | RULE | RESULT |
| ----- | ----- | ----- | ----- |
| D-M-01 | Semantics | No cross-layer leakage (ops/prod steps) | PASS / FAIL |
| D-M-02 | Semantics | No prompts or tactics included | PASS / FAIL |
| D-M-03 | Semantics | Explicit inheritance stack declared | PASS / FAIL |
| D-M-04 | Semantics | Delegation contracts present and explicit | PASS / FAIL |

### **7.3 Promotion Gate**

* Any FAIL blocks promotion.  
* No overrides at this level.

---

## **8\. Promotion and Release**

### **8.1 Promotion States**

Draft → QA\_Pass → Hardened → Canonical

### **8.2 Release Requirements**

* Version bump  
* ChangeLog entry  
* Registry update in Control Plane

---

## **9\. Control Plane Integration**

### **9.1 Domain MetaFactory Registry (Required Fields)**

* MetaFactory ID  
* Domain  
* Type (D)  
* Layer (L2)  
* Version  
* Status  
* Owner  
* QA status  
* Upstream dependencies

### **9.2 ChangeLog Policy**

* Every change has: reason, scope, impact, version

---

## **10\. Anti-Patterns**

### **10.1 Domain Drift**

Ad-hoc additions without registry and delegation.

### **10.2 Hidden Procedures**

Embedding steps inside L2 documents.

### **10.3 Template Embedding**

Copying templates into the Type D instead of referencing them.

---

## **11\. Appendices**

### **11.1 Type D Skeleton Template (Paste-Ready)**

(Use the required sections list in §5.1 as the skeleton outline.)

### **11.2 Example Delegation Contract (Format)**

* Station:  
* Factory Builder Target:  
* Required Inputs:  
* Required Outputs:  
* Template References:

### **11.3 Open Questions (Reserved)**

* Risk classification mapping per domain  
* Standard station naming conventions