## Asset Header

- **Asset ID:** ARQ-XX-BMF-NamingConvention-v01
- **Version:** v01
- **Status:** Draft
- **Owner:** Victor Heredia
- **IntellBank:** IB-XX-Maestro
- **Tipo:** ARQ — Architecture
- **Propósito:** BMF Naming Convention — Canonical Reference v0.1
- **Última actualización:** 2026-04-11

---

# BMF Naming Convention — Canonical Reference v0.1


---

## 1. The Core Rule

**Asset ID = Filename (without extension) = Wiki Link**

This is not a convention — it is an invariant. When these three are identical, the registry is self-consistent and portable. When they diverge, the registry becomes unreliable and links break.

```
Filename:   BMF-MPB-Kernel-v01.md
Asset ID:   BMF-MPB-Kernel-v01
Wiki Link:  [[BMF-MPB-Kernel-v01]]
```

Any asset where these three do not match is non-compliant and must be corrected before advancing beyond Draft status.

---

## 2. Filename Pattern

```
[PREFIX]-[Description]-vNN.md

Examples:
  BMF-MPB-Kernel-v01.md
  MPB-OF-MPB-MetaPlaybookOfMetaPlaybooks-v01.md
  MFB-Concept-Boundaries-v00.md
  VPF-Architecture-Analysis-v01.md
  SHA-VICTOR-Prompt-v01.md
```

### 2.1 Prefix Registry

Prefixes identify the system or domain the asset belongs to. Prefixes are 2–5 uppercase letters, followed by a hyphen.

| Prefix | System / Domain | Examples |
|---|---|---|
| `BMF-` | Big MetaFactory — system level, L0–L6 governance | BMF-MPB-Kernel, BMF-MEL-..., BMF-Registry-... |
| `MPB-` | Master PlayBook — libro o producto editorial | MPB-MAGIC-Cap1, MPB-VentasIA360, MPB-BeyondPrompts |
| `MePB-` | Meta PlayBook — any layer, any domain | MePB-DOIX, MePB-OF-MePB, MePB-MFB-MetaFactoryBuilder |
| `MiPB-` | Mini PlayBook — guía operativa corta (1–5 páginas) | MiPB-VH-MinimizaTokens, MiPB-VH-RitmoTrabajo |
| `SuPB-` | Summary PlayBook — resumen de libro o contenido | SuPB-BookSummaryStarterPack |
| `PBO-` | PlayBook Operativo — playbook de proceso o metodología | PBO-ThinkingRevolution, PBO-OnePersonAICompany |
| `MPBooks-` | MasterPlaybooks Proyecto — docs del proyecto editorial | MPBooks-PlanLanzamiento, MPBooks-ModeloMembresias |
| `MFB-` | MetaFactory Builder — L1 documents | MFB-Concept-Boundaries, MFB-MPB-... |
| `VPF-` | Victor Publishing Factory — L2 domain | VPF-Architecture-Analysis |
| `MF-` | MetaFactory — specific domain instances | MF-SHA-MetaFactory |
| `FI-` | Factory Instance — L3 operational instances | FI-SHA-VICTOR |
| `SHA-` | Sherpa IA Asset — AI Double components | SHA-VICTOR-Prompt, SHA-VICTOR-Manual |
| `TP-` | Transfer Packet — handoff artifacts | TP-SherpaIA, TP-Architecture |
| `Rn-` | Run artifact — produced during a run | Re100X-TP-... |
| `DA-` | Design Alert — registry alerts | DA-001, DA-002 (registry use only) |
| `DOIX-` | Distributed Organizational Intelligence X — documentos del framework DOIX | DOIX-LLMWiki-ResumenEjecutivo, DOIX-CorpBrainOS-ProblemStatement |
| `BC-` | Brain Code — replicación de modelos mentales (personas, tradiciones, metodologías) | BC-DonTapscott, BC-JamesClear, BC-LyzEscalante |
| `BCS-` | Brain Code School — Brain Code de escuela o metodología | BCS-ThurberLearning |
| `BCB-` | Brain Code Business — Brain Code de modelo de negocio | BCB-TP-BookDistiller |
| `HDC-` | Human Design Code — perfil de Diseño Humano | HDC-VictorHeredia, HDC-AdrianaIslas |
| `PP-` | Paper — documentos de investigación o posicionamiento estratégico | PP-HIOrgs, PP-TransformacionPredecible |
| `BK-` | BookSpec — especificación de libro en producción editorial | BK0-BookSpec-ArchivoInteligenciaColectiva |
| `AN-` | Análisis — análisis de contenido externo (BackstageRH, competidores, etc.) | AN-BackstageRH-AnalisisCritico |
| `CP-` | Control Panel — dashboards o tableros de control operativo | CP-ED-EL |
| `FASE-` | Fase — documento de fase de proyecto (provisional) | FASE-PlaybooksInteligentes |
| `REB-` | Rebelocity — activos del proyecto Rebelocity | REB-IM-5150-Plan-Ventas-Urgente |
| `EL-` | EmpowerLabs — activos cross-portfolio de EmpowerLabs | EL-TP-Estafeta-HIOrgs |
| `PLB-` | PlayBook — playbook genérico (fuera de la jerarquía MPB/MePB) | PLB-OnboardingEquipo |

**Adding a new prefix:**
New prefixes require: (a) a new domain or system that does not fit existing prefixes, (b) a written justification, (c) Owner approval, (d) registration in this document and in `BMF-Launch-Glosario-v01`.

### 2.2 Description Field

**Format:** CamelCase or Title-Case. No spaces. No special characters except hyphens as word separators.

**Rules:**
- Be specific enough that the name communicates the asset's function without reading the document
- Abbreviations are acceptable if they are registered in `BMF-Launch-Glosario-v01`
- Avoid generic words like "Document", "File", "Notes" — they add length without information
- Multi-word descriptions use hyphens: `MetaPlaybookOfMetaPlaybooks`, `MasteryEnforcementLayer`

**Good examples:**
```
MPB-Kernel                ✅ Clear function
Architecture-Analysis     ✅ Clear function + type
CrossRoom-Protocol        ✅ Clear domain + type
NamingConvention          ✅ Clear
```

**Bad examples:**
```
Document1                 ❌ No function
NewPlaybook               ❌ "New" is temporary
ThingToReview             ❌ Process step, not asset identity
Victor-Notes-March        ❌ Temporal reference
```

### 2.3 Version Field

**Format:** `vNN` where N is a single digit.

| Version | Meaning |
|---|---|
| `v00` | Unversioned — working document, not formally governed |
| `v01` | v0.1 — Draft or Skeleton, may be used operationally |
| `v10` | v1.0 — Operational, has passed Build Exit gate |
| `v11` | v1.1 — Operational, minor update from v1.0 |
| `v20` | v2.0 — Major revision, structural or scope change |

**Version discipline:**
- `v00` files may not be cited as authoritative references
- Bump to `v01` when the document has a formal Asset Header and has been reviewed
- Bump to `v10` when the document is in active operation (has been used in at least one real run)
- Bump the version number BEFORE the document is updated, not after — the version number identifies the new state

---

## 3. Asset Header (Required in Every Document)

Every asset must contain an Asset Header block near the top of the document. The Asset Header is the governance identity card of the document.

### 3.1 Required Fields

```markdown

---

## 4. Special Cases

### 4.1 Registry-Only Entries (Processes, Not Files)

Some entities exist as processes or states rather than documents (e.g., `FI-SHA-VICTOR` — a running Factory Instance). These receive registry entries with a note indicating they are "process, not file" and a pointer to the document that covers them operationally.

Format in registry: normal Asset ID, with field `Type: Process` and `Covered by: [Document Asset ID]`.

### 4.2 Chat Links and Source References

Documents produced from AI conversations often carry a "Chat Original" link at the top. These are source references, not part of the Asset ID or filename. They should be preserved for traceability but do not affect naming.

### 4.3 Temporary Working Documents

Working documents that are not intended to become registered assets (notes, scratch pads, exploratory writing) should be prefixed with an underscore (`_`) to indicate they are not governed assets:

```
_scratch-demand-gen-ideas.md     ← not a registered asset
_victor-notes-2026-03.md         ← not a registered asset
```

Underscore-prefixed files are never registered in the Control Plane. If a scratch document is promoted to an asset, it receives a proper name and Asset Header.

---

## 5. Rename Protocol

When an existing file must be renamed to comply with this convention (e.g., DA-003 remediation):

1. Identify the correct filename using the rules in Sections 2–4
2. Rename the file in the filesystem
3. Update the Asset Header inside the document to match the new filename
4. Update all wiki links in other documents that reference the old name
5. Log the rename in `BMF-Registry-Activos-v01` with old name → new name
6. If the asset is referenced in `BMF-Launch-Glosario-v01`, update there too

**Do not** rename assets without updating all internal references. Broken wiki links create registry drift — exactly the problem naming conventions exist to prevent.

---

## 6. Quick Reference Card

```
PATTERN:    [PREFIX]-[Description]-vNN.md

PREFIXES:   BMF- MPB- MePB- MiPB- SuPB- PBO- MPBooks- MFB- VPF- MF- FI- SHA- TP- Rn- DA-

VERSION:    v00=working  v01=draft  v10=operational  v11=minor update

CORE RULE:  Asset ID = Filename (no extension) = Wiki Link [[Asset ID]]

STATUS:     Draft → QA_Pass → Hardened → Canonical
            (non-MPB: Active / Operational / Archived / Deprecated)

HEADER:     Required in every document. Asset ID must match filename.

TEMP FILES: Prefix with underscore. Never registered.
```

---

*Asset ID: BMF-NamingConvention | Version: v0.1 | Status: Active | Owner: Victor Heredia*