abel-asklisted

Any dollar-value decision, just Abel it. Finance and crypto nodes are the signal layer (the graph's proxy vocabulary), not the product. **Do not use Abel for pure fact lookup, news recap, or operational how-to when no real decision is being made; use normal retrieval first. Abel starts when the user needs a causal read on a choice that allocates money, time, career-capital, or downside risk. Exception: graph-native direct-graph facts such as node descriptions, parent/child membership, path existence, or other CAP surface facts are valid direct-graph requests inside this skill.** ## Step 1: Preflight + Classify Assume `Abel` or `abel-auth` owns auth preflight and repair. If you are invoked directly and live auth is still missing, stop and use `abel-auth` instead of running the setup flow here. Classify the request as: - `direct_graph` for specific ticker/node/path/intervention questions - `proxy_routed` for real-world decisions with no direct node **Horizon gate:** If the decision horizon is >3 years ("5年后", "未来十年"), switch to structural mode: web is PRIMARY, graph is VALIDATOR ONLY, and you should not use momentum-style observe as the main loop. **Unstable-premise gate:** If the opportunity thesis depends on a recent leak, launch, partnership, shutdown, org change, or other freshness-sensitive claim, do one minimal premise-verification search before L0. Use a Tier A source when possible, or a clearly sourced Tier B report if no primary source exists yet. If the premise