## Asset Header

- **Asset ID:** MAP-XX-BMF-BuilderHierarchy-v00
- **Version:** v00
- **Status:** Draft
- **Owner:** Victor Heredia
- **IntellBank:** IB-XX-Maestro
- **Tipo:** MAP — Mapa
- **Propósito:** Builder Hierarchy — Canonical Map (v0)
- **Última actualización:** 2026-04-11

---

# Builder Hierarchy — Canonical Map (v0)

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**

Canonical Reference (Foundational)

---

## **1\. Purpose of This Map**

This document defines the **authoritative builder hierarchy** for the Big MetaFactory ecosystem.

Its purpose is to:

* Eliminate ambiguity between builder layers  
* Prevent responsibility overlap  
* Serve as a single reference for governance, QA, and AI enforcement

This is not explanatory prose. It is a **structural truth table**.

---

## **2\. Canonical Builder Stack (Top → Bottom)**

BIG METAFACTORY (System Constitution)  
│  
├─ Big MetaFactory Kernel (L0)  
│    • Global laws, invariants, interfaces  
│  
├─ Big MetaFactory Builder (L0.8)  
│    • How MetaFactories are designed as a class  
│    • Global factory patterns and constraints  
│  
├─ MetaFactory Builder (L1)  
│    • Domain-level factory architecture  
│    • Defines what it means to build factories in a domain  
│  
├─ Domain MetaFactories (L2)  
│    • One per domain (AI Publishing, HR, Consulting, etc.)  
│    • Governed by Type D MetaPlaybooks  
│  
├─ Factory Builders (L1 / L2 boundary)  
│    • Instantiate concrete factory templates  
│    • Translate domain rules into buildable systems  
│  
├─ Factories (Instances)  
│    • Operational pipelines producing outputs  
│  
└─ Outputs / Assets  
     • Books, playbooks, diagnostics, reports, products

---

## **3\. Responsibility Separation (Non-Negotiable)**

### **Big MetaFactory Builder**

* Defines **how MetaFactories themselves are created**  
* Never touches domains

  ### **MetaFactory Builder**

* Defines **domain constraints and architecture**  
* Never builds factories

  ### **Factory Builder**

* Builds **actual factories**  
* Never defines domain laws

Any overlap is a design error.

---

## **4\. MetaPlaybook Alignment**

| Layer | Builder / Entity | Governing MetaPlaybook |
| ----- | ----- | ----- |
| L0 | Kernel | Kernel MetaPlaybook |
| L0.5 | Taxonomy | MetaPlaybook of MetaPlaybooks |
| L1 | MetaPlaybook Builder | MPB-BUILDER |
| L1 | MetaFactory Builder | MPB-MFB |
| L2 | Domain MetaFactory | Type D MetaPlaybook |
| L3 | Operations | Ops MetaPlaybook |
| L4 | Production | Production MetaPlaybook |

---

## **5\. Validation Rule**

This hierarchy is valid if:

* A new domain (e.g. HR) can be added without modifying upper layers  
* Factories can be rebuilt without redefining domain architecture  
* AI agents can determine authority by layer alone

If not, the hierarchy must be revised.

---

## **6\. Usage Rule**

This map must be referenced whenever:

* A new MetaPlaybook is proposed  
* A builder is created or modified  
* A conflict or overlap is detected

No exceptions.