thought-forest-note-intake

Automating note intake prevents duplicates by performing deduplication checks before creating or updating entries, then applying repository rules for tag consistency and frontmatter correctness to maintain a clean knowledge graph.

Enforcing frontmatter and tag consistency is achieved by automating the normalization of new or updated notes to align with repository standards, deciding the note role, and reusing the appropriate template.

Updating a MOC or synthesis entry when expanding an existing note is handled automatically during the intake workflow, which routes changes to related entries and prevents scope creep by guiding actions toward a single focused entry point.

You need an approved intake plan when continuing a topic, adding a new note, or expanding an existing note, ensuring the process follows the structured workflow requirements and references the intake-checklist.

You can decide a note role such as concept, synthesis, moc, or howto during the knowledge management intake process, which automatically selects and reuses the appropriate template for the chosen role.

Note intake requires routing through repository rules and AGENTS.md to enforce structural consistency, validate frontmatter correctness, and ensure new entries integrate properly with existing synthesis and MOC structures.