llmwiki:ingest

LLM Wiki: Ingest

Process new source files and integrate their knowledge into the wiki.

Step 1: Identify New and Modified Sources

The wiki tracks every ingested file via an MD5 manifest at wiki/.manifest.json. Format:

{
  "docs/research/cross-platform-tech-stacks-2026.md": {
    "md5": "a1b2c3d4e5f6...",
    "ingested": "2026-04-06",
    "wiki_pages": ["sources/cross-platform-tech-stacks-2026.md", "entities/expo.md"]
  }
}

Detection logic

If the user provided a specific path as an argument, ingest only that file/folder (skip detection, force re-ingest).

Otherwise:

1. Read wiki/.manifest.json (create empty {} if it doesn't exist).
2. Scan these directories for markdown (and other readable) files:
   • raw/ (recursively, skip raw/attachments/)
   • docs/ (recursively)
   • notes/ (recursively)
3. For each file found, compute its MD5 hash:

   md5 -q <file>
   

4. Compare against the manifest:
   • New: file path not in manifest → queue for ingest
   • Modified: file path in manifest but MD5 differs → queue for re-ingest (update existing wiki pages)
   • Unchanged: file path in manifest and MD5 matches → skip
   • Deleted: file path in manifest but no longer on disk → flag for user attention (don't auto-delete wiki pages)

If no new or modified files are found, report "Nothing new to ingest" and exit.

Present the list of files to ingest, grouped by status (new/modified/deleted), and ask the user for confirmation before proceeding.

Re-ingesting modified files

When a previously ingested file has changed:

• Read the wiki_pages list from the manifest to find all wiki pages that were created/updated from this source
• Re-read the source and update those wiki pages with the new content
• Preserve information from OTHER sources on those pages — only update the parts that came from the modified source
• Note in the log that this was a re-ingest due to source modification

Step 2: Read the Wiki State

Before processing sources:

1. Read wiki/index.md to understand existing pages and structure.
2. Optionally use qmd to search for relevant existing pages that might need updating.

Step 3: Process Each Source

For each new source file, in order:

3a. Read and Analyze

• Read the full source file
• If the file references images in raw/attachments/, read key images for additional context
• Identify: key entities (people, companies, tools, technologies), core concepts, claims/data points, relationships

3b. Create Source Summary

Write a summary page in wiki/sources/:

---
title: "Source Title"
type: source
tags: [relevant, tags]
sources: [relative/path/to/original.md]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# Source Title

**Source:** `relative/path/to/original.md`
**Ingested:** YYYY-MM-DD

## Summary
2-4 paragraph summary of key content.

## Key Takeaways
- Bullet points of the most important facts, claims, or insights

## Entities Mentioned
- [[Entity Name]] — brief note on how it appears in this source

## Related Concepts
- [[Concept Name]] — brief note on relevance

## Raw Notes
Any additional details, quotes, or data worth preserving.

3c. Create or Update Entity Pages

For each significant entity mentioned in the source:

• If wiki/entities/<entity>.md exists: update it — add new information from this source, update the sources list in frontmatter, add updated date, ensure cross-references are correct.
• If it doesn't exist: create it with information from this source. Add wikilinks to related entities and concepts.

Entity page template:

---
title: Entity Name
type: entity
tags: [relevant, tags]
sources: [source1.md, source2.md]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# Entity Name

Brief description of what this entity is.

## Details
Key information aggregated from all sources.

## Mentions
- Mentioned in [[Source Summary]] — context

3d. Create or Update Concept Pages

Same logic as entities, but for concepts/topics. Place in wiki/concepts/.

Concept page template:

---
title: Concept Name
type: concept
tags: [relevant, tags]
sources: [source1.md, source2.md]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# Concept Name

Definition and explanation of the concept.

## Key Points
Information aggregated from all sources.

## Related Concepts
- [[Other Concept]] — relationship description

## Sources
- [[Source Summary]] — what this source says about the concept

3e. Update Cross-References

After creating/updating pages for a source:

• Check all pages that were created or updated
• Ensure bidirectional wikilinks exist (if A links to B, B should link to A)
• Add links to the source summary from all entity/concept pages it touches

Step 4: Update Index

Rebuild wiki/index.md:

• Read all .md files in wiki/ subdirectories
• Group by type (entity, concept, source, comparison, synthesis)
• For each page, list: - [[Page Title]] — one-line description (read from frontmatter or first paragraph)
• Sort alphabetically within each group

Step 5: Update Manifest

After processing each source file, update wiki/.manifest.json:

# Compute MD5 for the ingested file
md5 -q <file>

Update the manifest entry:

{
  "relative/path/to/file.md": {
    "md5": "<current md5 hash>",
    "ingested": "YYYY-MM-DD",
    "wiki_pages": ["sources/page.md", "entities/entity.md", "concepts/concept.md"]
  }
}

The wiki_pages array lists all wiki pages that were created or updated from this source. This is used by future re-ingests to know which pages to update when the source changes.

Read the existing manifest, merge in the new/updated entries, and write it back. Use the Bash tool to read/write JSON if needed.

Step 6: Update Log

Append to wiki/log.md:

## [YYYY-MM-DD] ingest | filename.md
- Source: relative/path/to/file.md
- Status: new | modified (previous hash: abc123)
- Pages created: list of new pages
- Pages updated: list of updated pages
- New entities: count
- New concepts: count

Step 7: Reindex qmd

If qmd is available:

qmd update

Step 8: Report

Print a summary for the user:

• Files ingested
• Pages created (with links)
• Pages updated (with what changed)
• Any contradictions or notable findings between new and existing content

Important Notes

• Never modify source files in raw/, docs/, or notes/. They are immutable.
• Flag contradictions. If new source data conflicts with existing wiki claims, note the contradiction on both pages and mention it in the report.
• Be thorough but concise. Source summaries should capture all key information but not be longer than necessary.
• Use parallel subagents when ingesting multiple files to speed up processing.
• When updating existing pages, preserve information from previous sources. Add, don't replace.