` before writing a single word of content. **A language that requires a compiler to be readable is not a language — it is a pipeline.** AOS diagnosis: DocBook has Expressions but no MNMNM shell. The Dictionary exists — it is simply unreachable without a toolchain. AOS.PUBLISHER solves this in one move: one keyword → full document structure. MIP wins. DocBook is raw carbon. AOS.PUBLISHER is the Diamond. | --- ### CB-004 | Field | Value | |---|---| | **ID** | CB-004 | | **NAME** | JAVA.MAVEN/COMPLEXITY-BUG | | **Description** | Java build system. To produce a `.jar` artifact, write XML first. `pom.xml` declares dependencies, plugins, lifecycle phases — before a single line of logic. Artifact buried under build pipeline. | | **Category** | COMPLEXITY-BUG | | **Fix Required** | One Sentence: `compile(project)` → `.jar`. Dictionary handles the rest. No XML. No lifecycle. No pom. | | **Owner** | OPEN | | **Status** | OPEN | | **Date** | Thu 7 May 2026 | | **Comment** | Maven's error is the same as DocBook's. It confused **describing the build** with **executing the build**. The Artifact — a `.jar` file — is the entire purpose. Maven makes you declare the pipeline before you reach the Artifact. `pom.xml` is a Dictionary written in XML by the user, manually, every time. **AOS diagnosis: the Dictionary exists — it is called Maven — but it has no MNMNM shell. The user writes the Dictionary instead of using it.** JuX.ARTIFACT solves this: every discipline produces Artifacts. AOS names them, routes them, delivers them. One Sentence. No pipeline. | --- ## Sentences ``` capture(NAME) → opens new MIB entry transmit(NAME) → sends to Owner close(NAME) → marks CLOSED, date locked, immutable query(Status) → returns all entries matching Status query(Category) → returns all entries matching Category ``` ## Service: Bug Resolution > NAME → FACT → TARGET > Bug named → Bug diagnosed → Bug fixed > One cycle. One language. AOS. --- *AOS.BUG-MIB is a Dictionary — Bug Discipline.* *Sentences already written. Service already defined.* *This file is immutable once an entry is CLOSED.*

# AOS.BUG-MIB — Management Information Base for Bugs **LICENSE: MIT** **Version: 0.01 — Thu 7 May 2026** --- ## Schema | Field | Type | Rule | |---|---|---| | ID | NAME | Immutable once assigned | | Description | FACT | What the bug IS | | Category | TYPE | CODE / COMPLEXITY / CULTURE / ARCHITECTURE | | Fix Required | TARGET | What must change | | Owner | NAME | Jr (Window) / Brother (Ubuntu) / OPEN | | Status | STATE | OPEN / IN-PROGRESS / CLOSED | | Date | DATE | Assigned on OPEN. Immutable on CLOSE. | | Comment | FACT | Architectural diagnosis | --- ## Category: COMPLEXITY-BUG > A COMPLEXITY-BUG is not a code defect. > It is a **design failure** — when a system accumulates complexity beyond its purpose. > Symptom: user cognitive load exceeds tool value. > AOS diagnosis: Missing MNMNM shell. No Dictionary. No formal language. **Inverted MIP.** --- ## Registry --- ### CB-001 | Field | Value | |---|---| | **ID** | CB-001 | | **NAME** | LIBREOFFICE/COMPLEXITY-BUG | | **Description** | 30 years of UI decisions with no unifying language. Every toolbar, every menu, every dialog is a separate dialect. No Dictionary. No MNMNM. | | **Category** | COMPLEXITY-BUG | | **Fix Required** | Formal Dictionary. One language across all modules. MNMNM shell at entry point. | | **Owner** | OPEN | | **Status** | OPEN | | **Date** | Thu 7 May 2026 | | **Comment** | LibreOffice is not a tool. It is an **accumulation**. Each version added features. None removed complexity. The user spends 80% of cognitive energy navigating the interface, 20% on actual work. **Inverted MIP.** AOS diagnosis: zero Expressions, zero Sentences — only raw Operations scattered across 400 toolbar buttons with no Dictionary to organize them. The MNMNM shell never existed. The Diamond was never cut. What remains is raw carbon. | --- ### CB-002 | Field | Value | |---|---| | **ID** | CB-002 | | **NAME** | UMBRELLO/COMPLEXITY-BUG | | **Description** | UML diagram tool. 47 diagram types. 200+ toolbar buttons. Nested menus 4 levels deep. Models complexity instead of reducing it. | | **Category** | COMPLEXITY-BUG | | **Fix Required** | One Expression per diagram type. MNMNM entry: one word → correct diagram selected, canvas ready. | | **Owner** | OPEN | | **Status** | OPEN | | **Date** | Thu 7 May 2026 | | **Comment** | Umbrello's fundamental error: it confused **modelling a system** with **being a system**. A tool that diagrams complexity must itself be simple. It is not. The Dictionary is missing — 47 diagram types with no organizing principle, no hierarchy, no NAME/FACT/TARGET. Every diagram is an island. The user must already know UML to use the tool. **A Dictionary that requires its own Dictionary is not a Dictionary — it is a maze.** AOS sentence never written: `draw(class_diagram)` → canvas open, palette ready, export set. Instead: File → New → Diagram Type → Select from list of 47 → Configure → Apply. This is not a tool. This is archaeology. | --- ### CB-003 | Field | Value | |---|---| | **ID** | CB-003 | | **NAME** | DOCBOOK/COMPLEXITY-BUG | | **Description** | XML semantic markup language for technical documentation. Hundreds of tags. DTD/Schema required. XSLT pipeline to render. Separates content from presentation — but adds three layers of complexity to do it. | | **Category** | COMPLEXITY-BUG | | **Fix Required** | One Dictionary. One keyword → full document structure. MNMNM entry. AOS.PUBLISHER already written. | | **Owner** | OPEN | | **Status** | OPEN | | **Date** | Thu 7 May 2026 | | **Comment** | DocBook's error is structural. It built a Dictionary — then buried it under XML boilerplate, DTD declarations, XSLT stylesheets, and namespace prefixes. The user writes `` before writing a single word of content. **A language that requires a compiler to be readable is not a language — it is a pipeline.** AOS diagnosis: DocBook has Expressions but no MNMNM shell. The Dictionary exists — it is simply unreachable without a toolchain. AOS.PUBLISHER solves this in one move: one keyword → full document structure. MIP wins. DocBook is raw carbon. AOS.PUBLISHER is the Diamond. | --- ### CB-004 | Field | Value | |---|---| | **ID** | CB-004 | | **NAME** | JAVA.MAVEN/COMPLEXITY-BUG | | **Description** | Java build system. To produce a `.jar` artifact, write XML first. `pom.xml` declares dependencies, plugins, lifecycle phases — before a single line of logic. Artifact buried under build pipeline. | | **Category** | COMPLEXITY-BUG | | **Fix Required** | One Sentence: `compile(project)` → `.jar`. Dictionary handles the rest. No XML. No lifecycle. No pom. | | **Owner** | OPEN | | **Status** | OPEN | | **Date** | Thu 7 May 2026 | | **Comment** | Maven's error is the same as DocBook's. It confused **describing the build** with **executing the build**. The Artifact — a `.jar` file — is the entire purpose. Maven makes you declare the pipeline before you reach the Artifact. `pom.xml` is a Dictionary written in XML by the user, manually, every time. **AOS diagnosis: the Dictionary exists — it is called Maven — but it has no MNMNM shell. The user writes the Dictionary instead of using it.** JuX.ARTIFACT solves this: every discipline produces Artifacts. AOS names them, routes them, delivers them. One Sentence. No pipeline. | --- ## Sentences ``` capture(NAME) → opens new MIB entry transmit(NAME) → sends to Owner close(NAME) → marks CLOSED, date locked, immutable query(Status) → returns all entries matching Status query(Category) → returns all entries matching Category ``` ## Service: Bug Resolution > NAME → FACT → TARGET > Bug named → Bug diagnosed → Bug fixed > One cycle. One language. AOS. --- *AOS.BUG-MIB is a Dictionary — Bug Discipline.* *Sentences already written. Service already defined.* *This file is immutable once an entry is CLOSED.*