Skip to content
PatchArc

The six review sections

How each section of the deterministic review is derived from evidence, and what each one can and cannot tell a reviewer in 0.2.0.

validated against patcharc 0.2.0 · 2026-08-22

patcharc stop computes a review from the recorded evidence and writes it to evidence/summary/review.json inside the capsule. No model is involved, so the same Arc always produces the same review.

1. Goal

The string you passed to patcharc start, or Untitled Arc. Also the capsule title.

2. What changed

Counts of commits, files, and scopes, plus the list of changed files with status and line counts. Derived from the commits the observer recorded and git diff-tree per commit.

3. Affected scopes

One summary per scope that was touched: the commits and files in it, additions and deletions, and a severity band (major at 500+ changed lines, moderate at 100+, minor otherwise). Scopes with no changes are omitted. See Monorepo scopes.

4. Verification

Aggregated test results: passed, failed, skipped. In 0.2.0 nothing parses test output, so this section reads zero across the board. If test results matter for your review, put them in a note (patcharc note "vitest: 212 passed") until test parsing ships.

5. Phases

Commits sorted by author time and split into thirds, labelled Phase 1, Foundation, Phase 2, Implementation, Phase 3, Verification and cleanup. A single-commit Arc has one phase, Single change. If commit rewrites were observed, a Superseded approaches phase is appended. The labels are positional, not inferred from content; they are a reading aid, not a claim about intent.

6. Decisions and remaining risk

Every patcharc decision and patcharc risk you recorded, with timestamps, followed by notes. This is the section reviewers thank you for; it only exists if you wrote it down during the work.

Evidence ids

Each review entry carries evidence ids (commit_a1b2c3d, file_apps_web_src_…) that point at files inside the capsule, so a claim in the review can be traced to the commit or patch that supports it.

Reading the review

$ unzip -p .patcharc/capsules/arc_8f2c1d4a9b.parc evidence/summary/review.json | jq '{goal, decisions, risks}'

patcharc serve exposes the same JSON at http://127.0.0.1:7777/api/capsule?file=<absolute path> after verifying the capsule; the browsable viewer for it is planned. The ArcLink page in 0.2.0 shows the published capsule record, not this full review.