ADR 0004 — Classify a surfaced component rather than leaving it unknown

ga · floor-software-engineer

Decision

Classify a surfaced component rather than leaving it unknown

Why

An unclassified component is treated as chrome, and chrome is dropped. The vocabulary's own header says so; the gate exists to make that a decision instead of a silent loss.

Measured

MultiFileExample WRAPS a fenced code block, so treating it as chrome takes the example with it. Four names, one hundred occurrences: byRole unknown went 100 to 0.

Inputs and outputs

This decision declares none. Every name in this section, when present, resolves against the capability vocabulary or the floor registry -- a typo fails the generator rather than rendering.

Where it is