Optional, bring-your-own-key (TYPESAFE_API_KEY) judgment layer on top of the deterministic scoring:
readybase context <file> --rerank jev— reorder context by relevance to your taskreadybase guard-advise <file>— is this file security-sensitive? (auth, payments, secrets, crypto)readybase escalation prioritize— rank the open escalation queue by urgency
readybase setup . wires the security-advisory check into a PostToolUse hook automatically once TYPESAFE_API_KEY is set, and removes it again symmetrically if you unset the key and re-run setup. Advisory only: nothing here blocks an edit or changes a guard verdict. See the README's Guard section.
Everything else stays exactly as deterministic and network-free as before; this is the one explicit, opt-in exception.