Architecture rejected ideas

One page per rejected idea (won't do) — a cross-cutting standard, an enforcer, or a third-party tool we chose not to adopt. Check here before proposing one; never re-argue a decided idea.

• Migration chain guard — db:gen is the only producer of a snapshot, so a linearity test only catches an already-banned hand-edit
• Spec frameworks — the proposal/as-built/validator loop already exists here, and the docs suite checks more than a spec CLI does
• PDF viewer consolidation — the full viewer's product is search, virtual scrolling and ARIA, which the stop list refuses twice over
• Monorepo task runners — Turborepo-style per-package cache keys, for a package build measured in seconds and a third content-hash cache beside two that already exist
• Nuxt build cache — experimental.buildCache invalidates on the same commits the app build's content-hash marker already does, and trades that marker's key for one that cannot say when it is wrong
• TypeScript build info cache — the only version that saves anything rests on the compiler's own invalidation rather than a hash of its inputs
• No confirm for undoable deletes — two kinds of delete is a rule a reader learns by losing something, and only "every delete asks" is one a lint rule can hold
• Published package metadata — engines, repository.directory and a LICENSE file are claims no gate here can hold honest, and one of them cannot even be shared by symlink