stella notify — Command Guide

Audience: operators who send and inspect Stella Ops notifications, and who set up DORA information-sharing feeds.

stella notify submits and reads notification messages through the Notify API, and prepares the local setup document for a DORA Article 45 information-sharing feed. It never leaks template content and honors offline mode against cached snapshots only.

Commands

stella notify send --channel <email|chat|webhook> --template <id> --data <file>
stella notify list --status <pending|sent|failed> [--output json|table] [--offline]
stella notify get --id <messageId> [--offline]
stella notify setup-dora-feed --tenant <tenant> --url <taxii-url> --collection-id <id> --generated-at <utc> [--output <file>]

Flags (common)

--offline: only allowed when notification queue snapshots are cached; otherwise exit code 5.
--tenant: scope to tenant; enforced by server RLS.
--output: json/ndjson/table.

Inputs/outputs

Inputs: Notify API; optional cached queue snapshots when offline.
Outputs: message metadata, status, delivery results; no template content leaks.
Exit codes follow output and exit codes; 4 for not found, 5 for an offline violation.

stella notify setup-dora-feed writes a disabled local setup document for a DORA Article 45 information-sharing feed. It does not create a live TAXII route or send to the subscriber. Operators review the generated dora-info-sharing-feed-setup-v1 JSON, bind approval and secret references, then use stella export dora-info-sharing for the offline signed handoff until live delivery-ledger wiring is available.

Determinism rules

Listings sorted by created time then id; timestamps UTC.
No retries triggered by the CLI; it only submits/reads.

Offline/air-gap notes

Sending in offline mode is disallowed (exit code 5); only listing cached snapshots is permitted.
Templates must be preloaded; no remote fetches when --offline.

stella export dora-info-sharing — the offline signed handoff that follows setup-dora-feed.
Output and exit codes