> ## Documentation Index
> Fetch the complete documentation index at: https://saydo-5cd0e3d7.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# /wiki-ingest

> Interactively add a single file to your wiki with guided emphasis and review.

`/wiki-ingest` is the interactive, single-file alternative to `/wiki-compile`. Use it when you've added one important new file and want to walk through how it fits into your wiki — what to emphasize, which topics it touches, and what changes.

## Command

```bash theme={null}
/wiki-ingest path/to/file.md
```

If you omit the file path, you'll be prompted to specify one. The file must be a `.md` file. If it lives outside your configured source directories, you'll get a warning but can proceed.

## When to use ingest vs compile

| Use `/wiki-ingest` when…                      | Use `/wiki-compile` when…                     |
| --------------------------------------------- | --------------------------------------------- |
| You've added one notable new file             | You've added or changed many files            |
| You want to guide what gets emphasized        | You want batch processing without interaction |
| You're reviewing a new document as you add it | You want incremental or full recompilation    |

## Interactive flow

<Steps>
  <Step title="Read the file">
    The command reads the full source file and presents 3–5 bullet points summarizing the key takeaways.
  </Step>

  <Step title="Guide emphasis">
    You're asked:

    > "Anything you want me to emphasize or de-emphasize when updating the wiki?"

    This is the interactive step where you steer what matters. Your input shapes how the content is integrated — for example, "focus on the experiment results, not the backstory" or "this contradicts what we decided in March, flag that."

    The command waits for your response before continuing.
  </Step>

  <Step title="Classify into topics">
    The command reads `schema.md` to understand your existing topics, then determines which ones this file belongs to (a single file can touch multiple topics).

    If the file introduces a genuinely new topic, the command will propose creating it.

    You'll see:

    > "This file touches these topics: \[list]. I'll update each one. Sound right?"

    Confirm before the command proceeds.
  </Step>

  <Step title="Update topic articles">
    For each affected topic, the command:

    * Reads the current article
    * Integrates the new source's information into the relevant sections, following your emphasis guidance
    * Updates coverage indicators (source counts may move a section from `low` to `medium`, for example)
    * Adds the new source to the Sources section
    * Writes the updated article

    If a new topic was approved, a fresh article is created using your configured `article_sections`.
  </Step>

  <Step title="Update schema, index, and state">
    After updating articles, the command:

    * Adds any new topic to `schema.md` with an evolution log entry
    * Regenerates `INDEX.md` with updated source counts and dates
    * Appends an ingest entry to `compile-log.md`
  </Step>

  <Step title="Review the summary">
    You'll see a summary of what changed:

    ```
    Ingested: meetings/2026-04-07-standup.md

    Topics updated:
    - retention: added experiment results from standup discussion
    - onboarding: updated status on Day 1 flow rollout

    New topics created: none

    Tip: Run /wiki-lint to check for new cross-references or contradictions.
    ```
  </Step>
</Steps>

## Flags

| Flag      | Effect                                                                                        |
| --------- | --------------------------------------------------------------------------------------------- |
| *(none)*  | Full interactive flow with discussion and confirmation prompts                                |
| `--quiet` | Skips the interactive discussion steps (steps 2–3) and auto-classifies. Useful for scripting. |