## Asset Header

- **Asset ID:** DC-XX-BMF-Concept-Boundaries-v00
- **Version:** v00
- **Status:** Draft
- **Owner:** Victor Heredia
- **IntellBank:** IB-XX-Maestro
- **Tipo:** DC — Document Canónico
- **Propósito:** MetaFactory Builder — Concept & Boundaries
- **Última actualización:** 2026-04-11

---

# MetaFactory Builder — Concept & Boundaries

Chat original: [https://chatgpt.com/c/69646e5c-a42c-8329-9976-5a88ec23754f](https://chatgpt.com/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)                                                                                        
### **Status**

Draft (Foundational)
## **1\. Canonical Definition**

The **MetaFactory Builder** is the system-level builder responsible for **designing, constraining, and validating Domain MetaFactories**.

It does **not** build factories. It builds the **conditions under which factories can be built** within a domain.

In practical terms, the MetaFactory Builder produces:

* Domain-level factory archetypes  
* Station archetypes (not steps)  
* Mandatory sections for Domain MetaFactory MetaPlaybooks (Type D)  
* Delegation contracts to Factory Builders

It operates **above Factory Builders and below the Big MetaFactory Builder**.

---

## **2\. Primary Responsibility**

The MetaFactory Builder answers one question only:

**“What does it mean to build factories in this domain?”**

Examples:

* What stations must *every* AI Publishing factory have?  
* What artifacts must exist across all factories in a domain?  
* What is structurally forbidden at the domain level?

It does not answer:

* How work is executed day-to-day  
* How content is produced  
* How teams operate factories  
  ---

  ## **3\. Position in the Builder Hierarchy**

The MetaFactory Builder sits at a distinct abstraction layer:

* **Big MetaFactory Builder** → defines global factory laws and kernel invariants  
* **MetaFactory Builder** → defines domain-level factory architecture  
* **Factory Builder** → instantiates concrete factory templates and pipelines

This separation is mandatory to prevent domain-specific logic from contaminating global systems.

---

## **4\. What the MetaFactory Builder CAN Do**

The MetaFactory Builder is explicitly allowed to:

* Define **station archetypes** (names, purposes, required inputs/outputs)  
* Define **module categories** (e.g., QA, Insight, Control)  
* Specify **mandatory artifacts** at the domain level  
* Enforce **required sections** for Type D MetaPlaybooks  
* Declare **delegation boundaries** to Factory Builders

All outputs must be **builder-grade and abstract**.

---

## **5\. What the MetaFactory Builder CANNOT Do (Hard Boundaries)**

The MetaFactory Builder may **never**:

* Define step-by-step workflows  
* Include prompts, instructions, or tactics  
* Operate factories or define run cadence  
* Produce market-facing or execution-facing content  
* Redefine MetaPlaybook taxonomy or inheritance rules

Violations invalidate the asset.

---

## **6\. Relationship to MetaPlaybooks**

The MetaFactory Builder does **not** replace MetaPlaybooks.

Instead, it **governs the creation of Domain MetaFactory MetaPlaybooks (Type D)** by:

* Constraining their structure  
* Defining required sections  
* Enforcing delegation and abstraction discipline

It is enforced through the **MetaFactory Builder MetaPlaybook (Type C)**.

---

## **7\. Authority and Non-Override Rule**

The MetaFactory Builder:

* Inherits from the Big MetaFactory Kernel  
* Is constrained by the MetaPlaybook of MetaPlaybooks  
* **Cannot override taxonomy, layers, or kernel invariants**

If a conflict exists:

* Kernel (L0) wins  
* Taxonomy (L0.5) wins  
* MetaFactory Builder must comply  
  ---

  ## **8\. Out of Scope**

Explicitly out of scope:

* Factory execution  
* Ops governance  
* Production playbooks  
* Team instructions  
* Tooling implementation

Those belong to lower layers.

---

## **9\. Validation Signal**

This definition is considered valid if:

* It can be reused across unrelated domains (Publishing, HR, Consulting)  
* It produces consistent Type D MetaPlaybooks  
* It prevents domain-level drift

If not, it must be revised before proceeding.

---

## **10\. Next Step (Locked)**

Upon approval, proceed to:

**Create the MetaFactory Builder MetaPlaybook (Skeleton v0.1)**

This will formalize enforcement and QA for this layer.