Goal

Use ProofKit as a shared contract between humans and AI agents so repository state survives across sessions and handoffs.

1. Start every change with a named workflow

Open or resume a change with:

proofkit run <change-name> --root .

This keeps everyone aligned on the same folder, same artifact set, and same current phase.

2. Give agents a repository contract

Instead of vague prompts, give explicit rules:

• run proofkit run <change-name> --root . before each handoff
• follow the current phase reported by ProofKit
• update the relevant artifact for that phase
• record the phase transition when the artifact is actually complete
• use proofkit verify --command for any success claim that depends on execution

3. Recommended phase ownership

• Proposal and delta spec: product/engineering intent
• Design: architecture and tradeoffs
• Tasks: execution checklist
• Verify: real commands and evidence
• Archive: only when artifacts, state, and execution evidence agree

4. Handoff pattern