ticker-analysislisted

# Ticker analysis ## Orient through the interface - Work from the repository root; the root constitution holds the bootstrap and capability-catalog commands. Before invoking a capability for the first time, read only its `describe` output or that leaf command's `--help`. - Decide whether the request is prospective, active-position, re-entry, or comparison. Collect only evidence that can change that decision. - Treat a virtual or fixed-evidence prompt as a closed world: use only its supplied evidence, never an unrelated fixture, live ticker, or web number. If a Primary Base duration, depth, or all-time-high trigger is not supplied, keep it missing; do not infer it. ## Prospective entry - Qualify first. Do not research a story, inspect valuation, or deepen the setup before the low-cost technical gate earns it. - On a known gate failure, stop and name the exact failed evidence. On an incomplete one, resolve only the named gap -- a chart for `needs_chart` -- and never infer a pass. - Declaring a plane's state is an assertion, and only a gate licenses one. A band or marker below its range is review evidence: typing it into `--fundamentals-state` or `--setup-state` turns a measurement that reports into a verdict that decides, and the reducer takes it because a caller's word is always allowed to be more cautious. Where no gate failed and the other planes are unmeasured, the ticker is INCOMPLETE -- a route you can rule out on its own terms is not the ticker's verdict. - If eligib