ingest

Run the ingest process after fact-checking completes: it reads findings.json, fact-check.json, investigation-log.json, and summary.json from the case directory, then creates investigation, entity, methodology, tool, and claim notes while updating all vault registries atomically.

Only findings passing the eligibility gate become claim notes: verdict verified or partially_verified, grounding confidence_cap above low, at least one source reference, and non-RLM origin. Excluded findings are logged with reasons and remain flagged in the investigation note.

Yes. New entity names and aliases are normalized and checked against the derived alias index. Collisions produce entries in entities/_merge-proposals.json for human review; ingest never merges entities automatically and proceeds with both entities separate.

A vault-level .ingest-lock prevents concurrent runs, and the journaled commit resumes or restores the exact pending operation rather than starting over. The case-local ingestion.json receipt is updated to failed while preserving its dependency digest.

Later investigations never rewrite existing claim content. Re-verification or supersession appends a dated row to the claim's Supersession History table, updates verified/verified_by frontmatter, and may promote the layer from lead to durable.