0 passed0 failed

Evidence State And Review Artifacts

Review state and evidence state are separate transitions.

Map keys: rule.reviewable-artifacts, rule.evidence-gaps, rule.packet-freshness, rule.vocabulary-consistency, rule.agent-human-resumability. Evidence path: deterministic. Evidence status: open gap. Next action: keep review-result application, evidence validation, stable maps, Markdown reports, and HTML/status views tied to packet freshness. Terms covered here: evidence refs, possible evidence, satisfied evidence, review labels, source-bound review feedback, review-feedback packet, review-feedback summary, review-learning evidence, status summary, canonical claim map, Markdown report, HTML view, stale packet, drift handling.

Maintainer Promise

Reviewer agreement can update wording, audience, evidence route, readiness, and next action, but a claim becomes satisfied only when a direct or verified evidence ref supports it; readable reports stay generated from packets and never become independent truth sources.

Subclaims

  • Review-result application updates labels, evidence route, readiness, and next action without flipping evidence status by itself.
  • A claim becomes satisfied only when a direct or verified evidence ref supports it; possible evidence and review agreement alone do not satisfy.
  • cautilus.review_feedback.v1 preserves the source review reference separately from normalized proposal, method, disposition, and note fields, and does not make the source review itself a satisfied evidence ref.
  • cautilus.review_feedback_summary.v1 summarizes explicitly selected review-feedback packets by method family and disposition, but does not claim active-run packet discovery.
  • discover claims validate exits non-zero when packet shape or evidence refs are invalid.
  • Stale packet state stays visible in discover claims status, doctor status, and rendered reports rather than masked behind cached labels.

Evidence

  • internal/runtime/claim_discovery_test.go TestApplyClaimReviewResultRejectsSatisfiedWithoutVerifiedEvidence enforces the satisfied-evidence boundary in discover claims apply-review.
  • internal/runtime/claim_discovery_test.go TestApplyClaimReviewResultAllowsStaleToRevokeSatisfiedEvidence and TestBuildClaimValidationReportValidatesEvidenceRefs cover stale-state propagation upstream.
  • scripts/agent-runtime/render-claim-status-report.test.mjs covers the renderer side so stale Markdown / HTML / status views surface stale state instead of masking it.
  • The dev/skill review-prepare-flow and reviewer-launch-flow audit fixtures under fixtures/eval/dev/skill/ exercise the application path end-to-end.
  • internal/app/cli_smoke_test.go TestCLIReviewFeedbackBuildEmitsSourceBoundLearningPacket, TestCLIReviewFeedbackBuildRejectsTestStatusDisposition, TestCLIReviewFeedbackBuildRejectsMissingReviewedProposal, and TestCLIReviewFeedbackBuildAllowsMissingCriticalWithoutProposal cover the source-bound review-learning packet boundary.
  • internal/app/cli_smoke_test.go TestCLIReviewFeedbackSummarizeCountsDispositionsByMethodFamily and TestCLIReviewFeedbackSummarizeRejectsNonFeedbackPacket cover selected-packet review-learning summaries.