viduxlisted

# Vidux Vidux is a repository-owned plan/proof/resume contract. It is not a model router, scheduler, worker runtime, or provider transport. Use it when work crosses sessions, workers, releases, or interruptions and a cold reader must be able to continue without reconstructing a chat. Skip it for a factual answer or an obvious small repair that needs no durable handoff. ## Read Before acting: 1. Read repository instructions and the canonical `PLAN.md`. 2. Inspect the current revision and working tree. 3. Read only the proof named by the active row. 4. Resume `[in_progress]`; otherwise take the highest unblocked row. Never overwrite or absorb unexplained work merely to make the tree clean. ## Cycle ```text READ plan, revision, working tree, named proof ASSESS active row first; otherwise highest unblocked row ACT one bounded, reversible change VERIFY the repository's real gate CHECKPOINT result, proof, uncertainty, and one cold-resume next move ``` A row is complete only when its requested outcome exists and its named gate passes. A commit, pull request, chat message, or activity count alone is not proof. `vidux checkpoint <plan> <task> <summary> --proof <text>` is an optional helper for updating the plan and, when configured, appending a local ledger row. Completion requires explicit proof text. Changes remain uncommitted unless `--commit` is supplied. The plan remains authority; a ledger row never grants permission to push, merge, deploy, spend,