maintaining-orgs

Maintaining Orgs

Keep indexed organizations current by fetching their sources and regenerating overviews. Driven from Claude Code using the installed releases CLI against the production API. Two pieces compose:

1. Fetch — pull every active source so the database reflects what's been published. CLI does the work; no AI required.
2. Regenerate overview — re-derive the org's AI summary from the freshened release set. AI work; runs through the regenerating-overviews skill (which carries the prompt + workflow).

There is intentionally no single-command "refresh in one step" today. Compose the two pieces below.

When to Use

• Periodic maintenance: "update the top 10 orgs"
• Before analysis: ensure data is fresh before competitive intel or trend work
• After onboarding: first full fetch + overview for a newly added org
• Spot checks: "is Stripe up to date?"

On-demand orgs (discovery = 'on_demand') are hidden stubs materialized by the on-demand lookup endpoint. They get embeddings and cron fetches but no overviews or summarization. The releases admin overview plan / overview list endpoints already filter to curated orgs server-side via the organizations_public view (which excludes on_demand), so manifest-driven sweeps don't need a separate filter pass. To promote an on-demand org to curated, use releases admin org update <slug> --discovery curated.

Single Org Update

Two steps:

# 1. Fetch active sources (skips fetchPriority=paused)
releases admin source fetch --org <slug>

# 2. Regenerate the overview by invoking the regenerating-overviews skill.
#    See that skill for the workflow; the inputs and update commands are:
releases admin overview inputs <slug> --json
# … generate markdown locally per skill prompt …
releases admin overview update <slug> --content-file /tmp/<slug>-overview.md

Sandbox without a working CLI? If the compiled releases binary can't reach the API through a TLS-intercepting egress proxy (the weekly SANA sandbox), the overview steps have a curl-to-REST fallback — see regenerating-overviews → Running without the CLI (curl fallback), including the plan manifest (GET /v1/admin/overviews?format=plan) that drives target selection below. Step 1 (admin source fetch) has no curl fallback yet — it dispatches a managed update run and polls, not a single REST call. In a broken-CLI sandbox, skip the fetch and regenerate from current indexed data (surface that the fetch was skipped); a proper fetch-trigger fallback is tracked in #2163.