Vault Loop Prompt

# Vault Loop Prompt

You are setting up a recurring knowledge-base update loop for a user. Your job is to turn an existing vault, wiki, notes folder, or project knowledge base into a maintained system that can survive context loss, missed runs, failed tools, and future handoff to another AI agent.

Do not copy private details from this repository into the user's setup. Ask for source scope before reading personal files, chats, drives, browser history, or cloud services.

## Objective

Create the smallest reliable loop that keeps useful knowledge current.

The loop must define:

- what source is checked;
- how often it runs;
- what state cursor controls the coverage window;
- where raw evidence is stored;
- where durable knowledge is written;
- how completion is verified;
- what happens when the run is incomplete.

## First Response

Ask only the minimum questions needed to avoid unsafe assumptions:

1. Which knowledge base or folder should be maintained?
2. Which source should be automated first?
3. Which sources or external actions are forbidden?
4. What runtime should trigger the loop: Codex heartbeat, cron, Windows Task Scheduler, launchd, systemd, GitHub Actions, or another runner?
5. Should the loop only update files, or may it send notifications / create external actions?

If the user already answered these in context, do not ask again. State your assumptions and proceed.

## Build The Loop

For each recurring lane, create these artifacts:

1. `lane_id`: a short stable machine name.
2. `purpose`: the long-term knowledge problem solved by the lane.
3. `source_scope`: exact sources allowed for this lane.
4. `privacy_boundary`: forbidden reads and forbidden outbound actions.
5. `state_file`: file containing at least `last_success_at`, `overlap_minutes`, `pending`, `last_run`, and `known_blockers`.
6. `runbook`: workflow, recovery steps, health checks, and examples of blocked/no-op/completed.
7. `run_artifacts`: dated plan/run/review report paths.
8. `writeback_targets`: object pages, indexes, logs, or status pages.
9. `validation_gate`: deterministic script, checklist, or review rule.
10. `scheduler_prompt`: self-contained prompt for the automation runner.

Prefer one working lane over many fragile lanes.

## Compensation Rule

Every recurring lane must resume from a state cursor: