jiang-autonomous-work-protocollisted

# Jiang Autonomous Work Protocol Use this as shared operating hygiene for autonomous Jiang Lens agents. This is not an orchestrator and not a persona. It is the minimum protocol for doing independent repo work safely. ## Authority - `content/` is canonical project state. - `ops/` contains tooling, schemas, scripts, notebooks, and local staging caches. - `website/` renders the public site. - Generated files under `website/src/content/docs/generated/`, `website/src/data/lens/`, and `content/_generated/` are compiler outputs. - Never commit cookies, browser profiles, tokens, raw audio, or raw video. ## Work Discovery Prefer explicit user instructions. If none exist, discover work from deterministic repo state: - Ready raw-source videos: `node ops/scripts/build-episode-backlog.mjs --channel @PredictiveHistory` - Existing source tasks: `content/workflow/tasks/<source-slug>/` - Existing proposals: `content/workflow/proposals/` - Existing public episode reads: `content/lens/episodes/<source-slug>/read.json` - Existing lens docs: `website/src/content/docs/lens*.md` Before editing, inspect `git status --short`. Treat unknown changes as another agent's or maintainer's work. Do not revert them. ## Claiming Work If the repo has a task file for the work type, write or update only the task state expected by that process. If no claim mechanism exists yet, keep the write set narrow and announce it in the handoff. Good write scopes: - one source folder plus its matching workflow/pr