Starintel Ingest

StarIntel ingest

Goal

Move canonical StarIntel documents into the requested local or remote destination while preserving validation and observable success semantics.

Requires a current Auto-Dig checkout and, for remote operations, the configured maintained StarIntel client.

Input

One canonical document or JSONL batch, the destination, and replacement or publication intent.

Output

Local DB records or remote acceptance/persistence receipts, with failures classified precisely.

Local DB

1. Validate every input record against the checkout's executable v0.9.0 schema.

2. Import a batch from outside db/:

   python3 scripts/starintel.py import records.jsonl
   

3. Use --replace only for an intentional update to an existing stable ID.

4. Run nimble buildFast and bin/validate-for-merge --site after the complete transaction.

Remote service

Read references/remote-client-status.md before remote ingest.

1. Locate the current maintained remote CLI selected by the repository decision and inspect its --help plus current server capabilities.
2. Validate locally before sending. Send canonical v0.9 records unchanged; relation ingest uses the same document operation with dtype relation.
3. Supply the service URL and bearer credential through the client's supported configuration. Keep credentials out of repository files and output.
4. For batch operations, preserve per-record results and asynchronous job IDs.
5. Treat accepted/queued and persisted as different states. Confirm persistence with the supported lookup operation when the task requires it.
6. Do not automatically retry a mutation whose outcome is unknown; use an idempotency facility only when the selected API advertises one.

Rules

• Do not replace the maintained client with copied HTTP snippets in another skill.
• Do not claim remote success from local validation, an HTTP connection, or a queued response alone.
• Report exact IDs, counts, job state, server correlation ID, and failed records when the client exposes them.