quaid-ingest

Idempotent markdown ingestion uses exact-byte hashing to identify source documents, ensuring re-ingesting the same files produces structured brain pages without generating unnecessary duplicates. You can ingest single files or directory batches while maintaining a clean knowledge base.

Idempotent document syncing ensures repeated batch ingestion of source files yields the same canonical brain pages without redundant data. You need it when importing directories into a knowledge base to prevent duplicate entries during live syncing or re-imports.

You can trigger a force re-ingest of frontmatter-aware markdown files to overwrite existing brain pages and regenerate canonical content. This vault-backed syncing action bypasses exact-byte duplicate checks to update your knowledge base with modified source documents.

Yes, Quaid ingest requires frontmatter support in ingested markdown to properly generate structured brain pages and manage namespaces. This frontmatter-aware process ensures documents are correctly categorized during single-file or batch ingestion into the knowledge base.

Managing namespaces during raw source document ingestion involves using Quaid's built-in wings management to organize canonical brain pages. This structured approach ensures ingested markdown files are correctly partitioned within the knowledge base during batch operations or live syncing.

Duplicate brain pages during batch ingest re-syncs indicate the exact-byte hashing mechanism was bypassed or the force re-ingest option was used. Proper idempotent syncing uses byte-level hashing to prevent these duplicates unless an explicit overwrite is required.