fomo-kernel

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.

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 current prices and market context — so verify once rather than mid-answer.

The response is the contract

The payload is the authority for portfolio facts. External research is optional and relevance-driven; when used, keep it sourced and separate from engine facts.

• evaluation.consequence — the book before and after the trade, and the delta: weights, largest position, top three, sector and AI share, cash. Also disclosures, and the holdings the numbers were measured without.
• evaluation.rule_collisions — the user's own rules this trade touches, each with the rule_effect naming how it moves.
• challenge — this call's must_state (facts the answer owes, with anchors), may_state (owed on no call — state one only when it decides this call), machine_state (machines only, never rendered), rule_effects (must_convey / must_not_convey per rule), quote_verbatim (the user's own words, never relabeled as an outside source), unchecked (never enumerated), and case_required.
• disclosures_display — each disclosure as a sentence in the user's language. Use it as an end-block line rather than translating a key.
• prior_decision — present only when the user already resolved one earlier consideration of this same ticker: their own stored words, and what they reported doing about it, never proof they did it. Use prior_decision only when it changes the current lead judgment, evidence requirement, process action, or a decision-changing question; otherwise ignore it.