choosing-technologylisted

# Choosing technology and vendors Use this workflow before recommending: - a SaaS or managed service; - a library, framework, build tool, local executable, or self-hosted service; - a proprietary local tool; - a replacement for an incumbent dependency; - a plugin, hook, CI component, credential handler, native artifact, Wasm artifact, or prebuilt binary. Candidates may be named during discovery. The prohibition is recommending a winner before every applicable gate is complete. Walk every applicable section. Mark a non-applicable gate with its reason; do not silently skip it. Hard-gate failure removes a candidate. Soft evidence affects score only after every surviving finalist receives equal-depth validation. ## Required deliverables A completed selection produces: - a candidate ledger; - evidence records for every gate and score; - a completed vet report when the substantial-evaluation threshold is crossed; - hard-gate outcomes; - score calculations and sensitivity results; - pros and cons for every ranked finalist; - a fully sorted ranking with the reason for each adjacent ordering; - a recommendation or an explicit no-recommendation result; - a decision document only after adoption is separately authorized. Documentation, reports, and Markdown artifacts belong directly in the main worktree. Product code, dependencies, configuration, builds, installations, and experimental mutations remain outside an evaluation request. ## Lifecycle Use these st