curator

name: curator type: workflow description: Ingests a URL or file into an Obsidian vault. Use when the user says "curator", "curator-ingest", or provides a URL or local file path to add to ~/Obsidian/MahVault. Do NOT use for personal zettels — those are human-only.

Curator

Drives loom to ingest a URL or local file into the Obsidian vault. The job of the orchestrator is to drive $CURATOR ingest/next/complete, dispatch agent tasks, run the human gate. Loom owns task ordering, predicate evaluation, schema validation, and persistence.

Dependencies

• loom — DAG execution library
• tiling — pane layout and activity tracking
• editor — used by the human gate to show the rendered report

Parameters

• url-or-path (required): http(s) URL or local file path to ingest into the Obsidian vault.

Workflow

Step 1: Ingest

1. Set tiling activity, capture the parameter and build layout:

   CUR_INPUT="<url-or-path>"
   CUR_TARGET=$(basename "$CUR_INPUT")
   
   CUR_SKILLS=~/.kiro/skills
   CURATOR=$CUR_SKILLS/home/curator/scripts/curator.sh
   LOOM=$CUR_SKILLS/home/loom/scripts/loom.sh
   TILING=$CUR_SKILLS/home/tiling/scripts/run-ttm.sh
   EDITOR=$CUR_SKILLS/home/editor/scripts/run-editor.sh
   
   $TILING activity set "curator($CUR_TARGET): Ingest"
   eval "$($TILING layout build)"
   

2. Ingest:

   CUR_WD=$($CURATOR ingest "$CUR_INPUT")
   

3. If ingest fails: NEEDS_CONTEXT.

Step 2: Drive the loop

$TILING activity set "curator($CUR_TARGET): Drive the loop"

Loop until done:

1. Run $CURATOR next "$CUR_WD". Parse the YAML response.

2. If done: true → break.

3. If stuck: true → BLOCKED.

4. Otherwise, for each ready[].id:

   • If the task kind == human → drive the human gate (see helper).
   • If the task kind == agent → dispatch the sub-agent (see helper).

   After the chosen branch returns, run $CURATOR complete "$CUR_WD" <id>.

Dispatch independent agent ids in the same batch in parallel; human tasks always run serially.

When stepping into a per-task action, refresh the activity to include the current task id so the user can see progress:

$TILING activity set "curator($CUR_TARGET): <task-id>"

$TILING activity set "curator($CUR_TARGET): Done"

Helper: Dispatch agent task

$CURATOR next yields ready agent tasks with their prompt_path already rendered. For each id, dispatch via the subagent MCP tool with role: trusted (grants file-read/write access).

The sub-agent's prompt_template should instruct it to fs_read the prompt_path and follow it. The agent writes its output to the output_path (also in the next response). After dispatch returns, call $CURATOR complete "$CUR_WD" "<id>".

Dispatch independent ids in parallel via the subagent stages array with no depends_on.

Helper: Drive human gate

Human tasks are conversational. The orchestrator reads the rendered prompt at prompt_path, follows its instructions, captures the user's decision into output_path against the task's output_schema via loom's output writer, then calls $CURATOR complete "$CUR_WD" "<id>".

For the vault-gate task (the sole human task), the rendered prompt is the ingest report. Show it in the editor:

$EDITOR show file "<prompt_path>"

STOP and wait for the user. They may edit or rm files in $CUR_WD/global/vault-replica/; replica state at apply time is the authoritative decision. When the user signals proceed or abort, capture the decision via the loom writer:

$LOOM output init "$CUR_WD" --task vault-gate
$LOOM output add  "$CUR_WD" --task vault-gate \
    --set 'proceed=true'   # or false

Then mark the task complete:

$CURATOR complete "$CUR_WD" vault-gate

strip-dead-links and apply-replica are gated on proceed == true via loom's when: predicates — false skips both.

Rules

1. Source binary files and *.assets/ folders are immutable — they are copied verbatim from source so any edit loses fidelity.
2. Atomic page filenames use natural item names (no kebab-casing) so [[Item Name]] wikilinks resolve directly.
3. A failed task aborts the entire run. Loom's next() raises RunAborted; the orchestrator emits a run-level error. Do not try to recover by re-running the failed task; report status and stop.
4. Spawn sub-agents only for tasks where loom yields kind == agent; run all orchestrator bash, file reads, and human-gate work inline.

Completion

Determine the final status by aggregating judge verdicts:

$CURATOR status "$CUR_WD"

Loom workdirs live under /tmp/curator/<YYYY-MM-DD>/<slug>/ — ephemeral by design. Re-running ingest "<url-or-path>" wipes the workdir and starts fresh; previous runs are not auto-resumed.