Indago Daily workflows

The four daily moves. Every bundle inherits them.

Most Indago sessions begin with one of these four shapes — long before any heavyweight Anspruchskarte or PRISMA work kicks in. Each has a native renderer with a typed payload, a chunk-resolved evidence list, and a SHA-256 over the rendered HTML. Anti-fab gated.

Ask a question. Get a cited answer.

The lightest archetype in the library — and the most-used. indago_findindago_read → cited sentence-by-sentence response with chunk_id provenance. Every load-bearing sentence cites a chunk; every cited chunk resolves to literal text.

terminal$ indago find "contrastive learning, audio-text alignment, before 2022, with code" → 8 hits · 1.1 ms $ indago report --template qa-with-citations --answer '{question, answer_body, evidence_list, uncertainty, confidence}' → renderer rewrites inline [chunk_id] markers to clickable chips → matrix_sha256=… · HTML rendered · optional journal append

Save only when needed — daily Q&A doesn't require chain-of-custody. Promote to reg-grade (audit chain) when the answer is going into a regulated context.

"Walk me through this repo."

A senior engineer joining a ten-year codebase needs the same five things: entry points, the data plane, the integration surface, the tests of record, the load-bearing decisions. The onboarding-brief renderer composes them — file:line cited — in under a minute against the indexed repo.

terminal$ indago report --template onboarding-brief --brief '{repo, persona, focus_areas, evidence_list}' → rendered: 6 sections × file:line citations → matrix_sha256=… · journal seq=…

Pairs with the Code bundle. Free Code tier covers one repo; Plus for unlimited.

"Should we do A or B?"

When the user asks a comparison question — vendor A vs B, approach X vs Y, bid vs no-bid — the decision-memo renderer composes a memo with: criteria, A's evidence, B's evidence, the comparison row, a recommendation. Every row chunk-resolved.

terminal$ indago report --template decision-memo --memo '{question, criteria, options:[A,B], evidence_list, recommendation, uncertainty}' → rendered HTML · matrix_sha256=… · journal seq=…

Pairs with Business, Legal, Procurement, Trademark — any decision that needs a citation behind the call.

"Tell me what changed."

A query that runs on a schedule against the index, and emits a digest when something new appears. Opposition windows in Trademark, new tenders in Procurement, new calls in Grants, new directives in Legal, new continuations in Patent. The watchlist-alert renderer composes the digest with a "what's new since last run" diff.

terminal$ indago report --template watchlist-alert --brief '{watched_query, since, new_hits, expiring_windows, evidence_list}' → rendered HTML · diff against last run · matrix_sha256=…

A persona is the natural carrier for a watchlist — see indago_persona and the five discovery families (funding · job · research-grant · tender · residency).

Daily → reg-grade.

When a daily-utility answer is about to be filed, submitted, or carried into a regulated process, promote to the heavier archetype that fits — anspruchskarte for patents, tm-clearance-chart for trademarks, prisma + validation-binder for systematic reviews, filing-package for any multi-jurisdiction filing. The chain-of-custody mechanism (audit chain) closes the loop.