Check the user's running component versions against known facts. Versions are compared LOCALLY — only project slugs are sent to the ratatosk server, running versions never leave this process. Returns, per component, the facts from releases NEWER than the running version (the upgrade path). Default is a briefing: summary counts, critical/high facts in action_required, one line each for the rest, and the same advisory fixed on several release branches collapsed into one entry. Use detail:"full" for every fact verbatim (capped at 50 per component with relevant_facts_omitted — narrow with severity_min or target_version), target_version to limit to one upgrade hop, severity_min to filter. Components with zero facts carry tracked:true|false — tracked:false means the project is NOT covered by ratatosk, so the absence of facts is no-coverage, not safety. In brief mode, facts sharing one quoted sentence are merged with their ids listed together. Drill down with get_release or facts_by_entity.

Reverse index: every fact touching one exact identifier — a CVE id, CRD, feature gate, flag, metric, config field, or dependency. Case-insensitive. Call this when you have a specific identifier (e.g. from a manifest or advisory) and want to know what changed around it.

One reviewed release: envelope (coverage, assessment, source URL) plus all its facts. facts=[] with coverage=full_reviewed means the release was read and is routine — auditable silence. Omit version for the latest reviewed release of the project. Set include_raw for the original release note body (raw_notes); when the review is not the full story (coverage insufficient, or zero facts) raw_notes is included automatically.

Incremental feed of release facts (typed, entity-level changes: security fixes, removals, deprecations, renames, defaults) for CNCF/cloud-native projects. Ordered by fact_id ascending; poll with since=. Call this to survey recent actionable changes, optionally filtered by project/type/severity.

Every project ratatosk tracks: slug (the canonical id all other tools take), name, tier (graduated|incubating), category, analyzed_releases. Small response, no arguments — call this FIRST when you are unsure of a slug instead of guessing (a wrong slug shows up as tracked:false in check_stack).