JuX.ARTIFACT

AOS — Adequate Operating System · Formal Concept
NAME / FACT / TARGET
NAME: JuX.ARTIFACT
FACT: The formal packaged output of an AOS Operation. Every discipline produces Artifacts. AOS names them directly. No pipeline required.
TARGET: Artifact delivered. One Sentence. One move.

The Pattern — Every Discipline, Same Problem

Discipline Tool Artifact Pipeline Cost
Software Java JAR / WAR / EAR Maven + Gradle + pom.xml + lifecycle
Modeling UML Diagram set / Model Umbrello + 47 types + export config
Documentation DocBook Rendered document XML + DTD + XSLT + stylesheet
AOS MNMNM Operation output NAME / FACT / TARGET
execute(Expression, Dictionary) → Artifact
compile(project) → .jar
draw(class_diagram) → .model
render(document) → .pdf
// One Sentence per Artifact. No pipeline. No pom.xml. No DTD. No XSLT.

COMPLEXITY-BUG Registry — Artifact Pipeline Bugs

CB-002 UMBRELLO/COMPLEXITY-BUG OPEN
UML diagram tool. 47 diagram types. 200+ toolbar buttons. Nested menus 4 levels deep. Models complexity instead of reducing it.
"A Dictionary that requires its own Dictionary is not a Dictionary — it is a maze."
CB-003 DOCBOOK/COMPLEXITY-BUG OPEN
XML semantic markup for technical documentation. DTD + XSLT + namespace prefixes before a single word of content.
"A language that requires a compiler to be readable is not a language — it is a pipeline."
CB-004 JAVA.MAVEN/COMPLEXITY-BUG OPEN
Java build system. Write pom.xml — XML, dependencies, lifecycle phases — before a single line of logic. The Artifact buried under the pipeline.
"The user writes the Dictionary instead of using it."
The universal pattern
Every discipline has Artifacts.
Every discipline buried them under a pipeline.
AOS exposes the Artifact directly.