nl-tax-evidence-indexer

NL Tax Evidence Indexer

Organize the evidence the user actually supplies—selected files, host attachments, and values stated in chat—without requiring a complete document folder. Keep the interaction conversational and ask only for evidence that matters to the active annual or provisional workflow.

Activation

Use this skill when the user asks to index or organize Dutch tax evidence, when an active workflow needs evidence for a section, or when selected files or chat amounts need source-traceable recording. Credit everything already supplied; do not restart intake or turn the exchange into a fixed upload checklist.

Read before acting

Resolve bundled paths relative to this skill directory and every workspace/... path against the saved workspace_root.

1. Read ../_shared/runtime-contract.md first.
2. Read ../_shared/knowledge/methods/interactive-elicitation.md for the shared conversational and session-state contract.
3. Read reference/indexing-flow.md whenever this skill is active; it owns the attachment, indexing, provenance, and update procedure.
4. Read reference/evidence-types.md before assigning a canonical evidence_type, such as woz_beschikking, hypotheek_jaaroverzicht, or voorlopige_aanslag_beschikking.
5. Read reference/extraction-boundaries.md before classifying or extracting document facts.
6. Read workspace/shared/session-progress.yaml and the existing workspace/taxpayer/evidence-index.yaml. If the index does not exist, seed it from templates/evidence-index.yaml.

Keep resource loading, file maintenance, and orchestration invisible to the user unless a specific evidence item needs review.

Core contract

• Accept a user-selected folder, selected host attachments, values stated in chat, or any combination of these. Never require a file when the active workflow permits a chat value.
• Inventory only the locations the user selected. The optional Python helper catalogs file metadata and hashes; it does not classify documents, extract tax facts, or choose tax treatment.
• Assign evidence types and confidence conversationally from the document and the reviewed references. Do not use a deterministic tax-classification or decision engine, compute tax, decide deductibility, or choose a partner allocation.
• Preserve provenance. A file stays source: file; a value stated in chat uses source: user_chat, its verbatim quote, and stated_at; a deferred fact uses source: unknown and remains open.
• Return chat answers to the active workflow for its profile or section notes. An evidence-index chat row is only a resume-compatible record when the indexer was already active. Do not invoke this indexer solely to turn chat into document evidence; pure chat collection does not require an evidence-index.yaml entry.
• Never silently choose between conflicting file and chat values or between competing documents. Mark the item for review, describe the conflict, and ask the user which value or document should control.
• Ask at most three closely related evidence questions in one turn. Defer an unavailable item to missing-info.md and continue with another useful item.