Pass Log

Use this skill at a pass boundary: after a loop has loaded state, acted, checked the result, and must record what happened. One pass gets one entry. Do not summarize from vibes; record only evidence that exists.

This skill uses the K3 artifacts:

• spec/pass-log-format-v0.md
• templates/contracts/pass-log.template.md
• spec/task-contract-v0.md when the pass belongs to a task contract

Entry rules

Append the fields in this order:

1. ## Pass N — <UTC start> → <UTC end>
2. run
3. state read
4. did
5. check
6. evidence
7. state written
8. verdict
9. next / escalation
10. autonomy

The verdict must be one of continue, done, blocked, exhausted, or interrupted. Only continue is non-terminal. A blocked entry must include the specific question being escalated.

Checks succeed or go green; do not write "the pass passed."

Steps

1. Re-read the contract, manifest, checklist, or previous pass entry that defines the run.
2. Identify the next pass number from the log. If the file is new, start at Pass 1 and include a title, Contract: or Source:, and Format: spec/pass-log-format-v0.md.
3. Record only durable state that was actually read or written: file paths, checklist counts, prior verdicts, commits, reports, artifacts.
4. Record the check exactly enough that a stranger can rerun or inspect it. Include command exit status, CI URL, diff, artifact path, or pending if evidence has not landed yet.
5. Choose the verdict from the evidence, not optimism.
6. Write the autonomy line as: acted alone or needs approval: <what> · confidence low|medium|high · risk low|medium|high.

Output

Return the log path, pass number, verdict, evidence pointer, and any next action. If evidence is missing, say what is missing instead of inventing it.