engineering-standardlisted

# Engineering Standard **Requirement:** apply this standard when the task matches its scope. Full progressive-disclosure body: [references/full-standard.md](references/full-standard.md). Rule IDs: [references/binding-predicates.md](references/binding-predicates.md). For code structure or architecture migration, also read: - [Capability-first architecture](references/capability-first-architecture.md) - [Architecture pattern applicability](references/architecture-pattern-applicability.md) - [Language mappings](references/capability-first-language-mappings.md) - [Executable-shape examples](references/capability-first-examples.md) When creating a project, adding a package, or upgrading a runtime, framework, SDK, generator, plugin, or library, use `dependency-version-selection`. Query the authoritative live release source; never select a version from model memory, a stale template, or an old example. When invariants span a broad generated state or input space, read [Generative verification](references/generative-verification.md). When exact expected outputs are unavailable but relations or independent implementations can falsify behavior, read [Oracle-free verification](references/oracle-free-verification.md). When a test, gate, alert, validator, or recovery control claims to catch a failure, read [Control-effectiveness verification](references/control-effectiveness.md). When diagnosing or fixing a defect, changing observable behavior, or refactoring behavior whose curr