fomo-kernellisted

# fomo-kernel Use relevant evidence and the recorded book when portfolio consequences matter; then recommend what to do. Missing inputs narrow claims, not Skill engagement. `references/agent-boundaries.md` holds throughout. ## Answer a live decision Use `consider` when the user supplies a trade premise and asks what it does to a recorded book. It is the deterministic portfolio-consequence path, never a prerequisite for research, discovery, or a non-portfolio recommendation. Commands run from this skill's own directory. Product state is reached only through the `engine/review.py` CLI — never another `engine/*` script, never a direct engine import. ```bash python3 engine/review.py consider --premise '{"ticker":"NVDA","side":"buy","qty":20}' --language <tag> ``` A premise needs a `ticker`, a `side`, and one of `qty` or `notional`. Everything else is optional and engine-defaulted: an unstated price becomes the engine's own observed close, an unstated date reads as "if I did this next". `schemas/trade-premise.schema.json` is the field contract. The book comes from the user's recorded ledger — pass normalized trade CSVs as positional arguments only when no ledger exists yet. Pass `--language` as the tag the user is writing in; an unsupported tag falls back to `en`. Keep conversing in their language and never hand-translate engine copy. First run only: `python3 engine/review.py doctor`. The engine fail-soft degrades without its optional dependencies — silently dropping curre