Document review-base policy compliance (#134) (#460) Add a "Review-base policy compliance" section to How-the-Review-Model-Works, GitHub-PR-Review-Guide, and Local-Code-Review-Guide describing the merged #134 shared invariant: repository-relative, fail-closed, HEAD never substituted, stacked-PR-aware, one blocking P0 before implementation findings. Links to the canonical shared/policies/review-base-policy.md rather than restating it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Document the finding-placement mental model (#388) Adds an "Evidence location, symptom location, and fix/action location" section to How-the-Review-Model-Works.md, right after candidate-finding validation and before the existing shared-cause consolidation section (renamed "Where a validated finding is anchored across several sites" to distinguish single-finding placement from multi-site consolidation). Covers the evidence/symptom/finding distinction and its shorthand, causal ownership, contract ownership, locality preservation during context expansion, semantic honesty over false precision, and that GitHub-inline availability never redefines semantic ownership, with three worked examples (cause vs. symptom, the precedent trap, the nearest-line trap). Links the canonical contract in shared/templates/finding.md's "Deriving the fix/action location" section rather than restating it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add a common Wiki Page Map to every page for navigation Appends an identical, compact "Wiki Page Map" table (Page / What it covers) to the end of all 22 existing Wiki pages, so a reader landing on any single page can see every other page and its purpose without returning to Home first. No _Sidebar.md or _Footer.md exists in this wiki, so there is no native shared-rendering mechanism that would place identical content inside every page's own body; the table is duplicated intentionally (kept small, one heading, one table) rather than introducing a partial or page-specific navigation aid. No substantive content, technical claims, or existing links were changed — this is a pure addition at the end of each page. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Synchronize Wiki with root-cause consolidation, verdict-consistency, and confidence model Closes the three bounded gaps identified by the Wiki-vs-implementation research (Findings 1-3): - How-the-Review-Model-Works.md: explains that a validated finding is anchored at its causal/root-defect location, that shared-cause manifestations are consolidated with an affected-locations list, and that uncertain/thematic-only cases stay separate. Links shared/policies/root-cause-consolidation.md. - Severity-and-Decision-Model.md: explains the read-only verdict-consistency comparator that re-verifies the about-to-render/ publish signal against the mechanically-derived decision and withholds on mismatch. Links shared/policies/verdict-consistency.md. - Feature-GitHub-Publication-and-Authorization.md: one sentence noting ACTIVE publication's pre-submit event is covered by that same check. - Feature-Runtime-Validation-Evidence.md: expands the single-sentence confidence rollup into a table of the 5 closed values, clarifies it reflects both runtime-validation state and context provenance, and restates that confidence never changes finding identity, severity, or decision. Links docs/finding-confidence/finding-confidence-model.md. No new pages, no unrelated prose changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Document candidate-finding validation mental model (#384) Adds a "From an observation to a candidate to a finding" section to How-the-Review-Model-Works.md covering the observation-first gate, semantic-role validation, evidence/contract grounding (including non-Jira technically-grounded blocking findings), causal/regression proof discipline, the disconfirmation pass, and the finding-validity vs. blocking-justification-validity separation, with four worked examples. Links to the canonical design record in docs/candidate-finding-validation/ rather than restating it. Also registers that doc in Repository-Documentation-Map.md's design-records row. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sync Wiki with the implemented Adaptive Specialist Depth architecture (#268) Adds a Specialist-Depth Review page documenting the final Tier 3 architecture (base reasoning -> materially implicated concern -> evidence-driven specialist-depth decision -> 0..N deepening capabilities -> one unified review) and the five capabilities that actually landed (Security, Distributed Systems, Database/Migration, Performance, Dependency/Supply-Chain), grounded in shared/policies/specialist-depth.md and review-scope.md. Wires it into Home, How the Review Model Works, Architecture Overview, the Repository Documentation Map, Review Context and Existing Evidence (explicit-focus additive-only), the Local Code Review guide (capability provenance field), the AI Code Review Landscape positioning section, and the FAQ. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
docs: establish code review project wiki Add the initial GitHub Wiki: 14 explanatory/navigational pages covering onboarding, Skill selection, the review model, architecture, per-Skill guides, review context/evidence, severity/decision model, packaging, a dated AI code-review landscape analysis, the development workflow, an FAQ, and a repository documentation ownership map. All content links out to canonical repository files rather than duplicating policy text. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>