StarIntel Auto-Dig
Goal
Run one complete evidence-first research loop and leave a validated, traceable next frontier.
Requires web research tools and a current StarIntel Auto-Dig checkout.
Input
A root target or investigation-target document, research question, dataset, and recursion budget.
Output
A source ledger, canonical documents and relations, a research-pass, a green gate, optional remote receipts, and selected next targets.
Loop
- Read the current checkout's
AGENTS.md, reuse its canonical dataset root, and record the starting commit.
- Use
starintel-local-search to find existing records, relations, unresolved targets, conflicts, and prior passes.
- Use
starintel-osint for extensive external research and independent corroboration.
- Resolve identities and split material into exact document dtypes.
- Use
starintel-document-create for canonical documents and explicit relations.
- Add or update a
research-pass recording the question, method, findings, supporting and counterevidence IDs, unresolved target IDs, agent identity, iteration, start/end times, and coverage gaps.
- Use this skill's
scripts/verify.py --repo <auto-dig-checkout> helper for the canonical local nimble buildFast plus bin/validate-for-merge --site gate. It validates the checkout, logs the exact argument vectors, and stops on the first failed stage.
- When remote publication is part of the request, use
starintel-ingest and preserve accepted, queued, failed, and persisted states separately.
- Generate the next deterministic frontier with the Auto-Dig repository's maintained
python3 scripts/starintel.py select-targets --query '<current subject>' --limit 20 --emit-documents --output recursive-targets.jsonl operation.
- Review and import accepted target documents through the canonical batch path, then publish through the repository's branch/PR workflow when requested.
Rules
- Every conclusion traces to canonical IDs and exact sources; mission plans and selection scores are not evidence.
- Keep actors or research roles independent until synthesis so shared assumptions do not masquerade as corroboration.
- Stop recursion at the declared depth/breadth, satisfied question, exhausted credible leads, or repeated unsupported hypothesis.
- Never describe a failing, skipped, pending, stale, or unrun gate as success.
1---2name: starintel-auto-dig3description: starintel, auto-dig, osint, recursion, documents, relations, validation4---56# StarIntel Auto-Dig78## Goal910Run one complete evidence-first research loop and leave a validated, traceable next frontier.1112Requires web research tools and a current StarIntel Auto-Dig checkout.1314## Input1516A root target or investigation-target document, research question, dataset, and recursion budget.1718## Output1920A source ledger, canonical documents and relations, a `research-pass`, a green gate, optional remote receipts, and selected next targets.2122## Loop23241. Read the current checkout's `AGENTS.md`, reuse its canonical dataset root, and record the starting commit.252. Use `starintel-local-search` to find existing records, relations, unresolved targets, conflicts, and prior passes.263. Use `starintel-osint` for extensive external research and independent corroboration.274. Resolve identities and split material into exact document dtypes.285. Use `starintel-document-create` for canonical documents and explicit relations.296. Add or update a `research-pass` recording the question, method, findings, supporting and counterevidence IDs, unresolved target IDs, agent identity, iteration, start/end times, and coverage gaps.307. Use this skill's `scripts/verify.py --repo <auto-dig-checkout>` helper for the canonical local `nimble buildFast` plus `bin/validate-for-merge --site` gate. It validates the checkout, logs the exact argument vectors, and stops on the first failed stage.318. When remote publication is part of the request, use `starintel-ingest` and preserve accepted, queued, failed, and persisted states separately.329. Generate the next deterministic frontier with the Auto-Dig repository's maintained `python3 scripts/starintel.py select-targets --query '<current subject>' --limit 20 --emit-documents --output recursive-targets.jsonl` operation.3310. Review and import accepted target documents through the canonical batch path, then publish through the repository's branch/PR workflow when requested.3435## Rules3637- Every conclusion traces to canonical IDs and exact sources; mission plans and selection scores are not evidence.38- Keep actors or research roles independent until synthesis so shared assumptions do not masquerade as corroboration.39- Stop recursion at the declared depth/breadth, satisfied question, exhausted credible leads, or repeated unsupported hypothesis.40- Never describe a failing, skipped, pending, stale, or unrun gate as success.