Task Record and Completion Receipt Schema

Task record and completion receipt

Shape for the task record (operating-contract §3 step 3) and the completion receipt (rule 10). Keep both short; a small fix needs a few lines. Records live in the PR description, the TODO entry or a local run journal. Export to Brain only durable decisions, findings, results, commitments or handoffs — never full prompts or transcripts.

Task record

task: owner/repo#123            # or a short slug when no issue exists
work_type: fix | feature | docs | research | content | ops
goal: one sentence
non_goals: [ ... ]
evidence: [path/or/url#section, ...]
acceptance: [ verifiable criteria ]
verification: [ commands or checks planned ]
authorization: what the owner explicitly allowed (branch, push, PR, publish ...)
brain_impact: [ affected notes ] | none-expected

Completion receipt

task: owner/repo#123
result: implemented; awaiting owner review | blocked: <reason> | no change needed
evidence:
  tests: [ command -> outcome ]          # include what did NOT run
  review: tool, scope, revision, result | pending
brain: [ updated notes ] | no durable knowledge change
tracker: TODO entry state
pointers: { branch: ..., commit: ..., pr: ... }
limitations: [ ... ]
next: next eligible action, or the decision needed

Status words are literal: “implemented” is not “deployed”, “PR open” is not “shipped”, “draft” is not “published”. Do not collapse decision, implementation, deployment, verification and marketing state into one “done” value.

Handoff (before context or quota runs out)

Issue, branch/worktree, base and current revision, changed files, checks run, review state, Brain/TODO disposition, exact next action. Resume from it and revalidate only evidence that changed.