Anti-patterns

INDEX.md §O is the canonical "do not do this again" list. Every entry on it is a mistake that has actually been made at least once.

The list

Treating Blueprint as a chip — Blueprint is a layer, not a chip. Don't add it to chip rows.
Treating Settings as a chip — Settings is a sub-layout. It lives in the dock's Zone 4 (shortcuts), not in a chip row.
Treating Origin as a chip — Origin is a sovereign workspace, not a chip. It has its own workspace-id.
Putting workspace switcher in dock — Workspace switcher lives in the top bar. The dock is for cross-workspace entries (Zone 3) and pinned apps (Zone 2).
Using 3-over-1 as layout id — The correct id is horizontal. Don't use 3-over-1 (it was a typo that stuck for a while).
Using "vibe" / "coder" as workspace names — Use vibescope / vibecoder (the full word). "vibe" alone is the AI assistant's name; "coder" alone is ambiguous.
Putting horizontal chips in the side-column — Pact says side-column chips are vertical, max 3. Horizontal chips go in the chip row.
Forgetting GZ-1 protocol when modifying GOLD files — GOLD files (pact/platform/INDEX.md, pact/governance/dna/*) require the GZ-1 protocol. Skipping the protocol is a violation.
Editing docs/*.js directly instead of pact/scripts/avidcreation.js — The index is auto-generated. Hand-edits get overwritten on the next build.

Before adding a new chip, layout, or workspace, ask:

If any of these is "I don't know," look it up before acting.

The list grows by real mistake. When a Mavis (or operator) catches a violation, the violation gets added to INDEX.md §O and reflected here.

The list is append-only. Don't remove entries — even if a rule is later relaxed, the historical violation is still real.

doctrine/chip-system.md — the chip rules that anti-patterns most often violate
doctrine/pact-lookup.md — how to look up the canonical rule
pact/platform/INDEX.md §O — the source of truth