Skip to content

Add manifest table for idempotent ingestion #14

Description

@sid-ak

Category: Ingestion & Data Management
Priority: Low
Phase: Phase 2 (Ingestion + CLI)

Problem
Idempotent ingestion is asserted but the mechanism is unstated; a naive full-scan to detect changes doesn't scale across hundreds of files.

Solution
Maintain a manifest table (file path, content hash, ingest timestamp, chunk count) in Postgres; only parse/embed files with a changed or missing hash.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions