Skip to main content

Review And Evidence

Agent-assisted work is only useful when the evidence is clear. Lumie separates reviewer findings, checker signals, Verify-phase evidence, and mandatory human ownership so that agent output cannot silently become approval.

The review routing source of truth is .codex/routing/review-matrix.md.

Capability Classes​

CapabilityPhaseMeaning
human-owner:*ReviewMandatory human owner coverage
reviewer-agent:*ReviewSpecialist reviewer evidence
checker-agent:*ReviewAdvisory or policy checker evidence
verify-evidence:*CheckVerification evidence, not Review coverage

Always union every matching base surface and overlay row, then dedupe identical capability tokens. A reviewer agent, checker agent, hook, or Verify-evidence row never replaces a required human-owner row.

Product Documentation Coverage​

Changes under lumie-document/** require human-owner:document-owner and reviewer-agent:lumie-doc-reviewer.

Add more coverage when the diff changes these surfaces:

ChangeAdd
Sidebar root, _category_.json, page placement, or locale structurereviewer-agent:lumie-doc-structure-reviewer
Korean localization coveragereviewer-agent:lumie-doc-i18n-reviewer

This means a Docusaurus tab split needs English doc review, structure review, and Korean i18n review. It still needs document-owner coverage before commit readiness can be considered complete.

Reading Reviewer Output​

Reviewer output should be treated as evidence:

  • severity-ranked findings identify concrete risks or defects;
  • No findings means the reviewer did not find issues in the assigned scope;
  • no reviewer result approves a commit;
  • stale reviewer evidence must be refreshed when follow-up edits invalidate the reviewed scope;
  • contradictory reviewer evidence must be resolved before Report or commit.

No findings is valuable, but it is not a proof that the entire system is correct. It is a scoped signal from one reviewer role.

Commit Readiness​

Commit readiness is owned by .codex/routing/commit-policy.md. The close gate expects staged-scope evidence, including:

  • exact staged files from git diff --cached --name-only;
  • passing commit-readiness checker output for the target repo;
  • matching work-log evidence;
  • Review evidence for the staged scope, including required human-owner:* rows;
  • Verify evidence for the staged scope or selector-defined no_run evidence;
  • Docs Sync evidence when the staged scope affects public docs, developer docs, routing docs, workflow policy, or documentation structure;
  • a commit message that satisfies .codex/routing/commit-conventions.md.

Commit readiness does not rebuild reviewer routing, rerun broad verification, or run Docs Sync from scratch. The evidence must already exist and match the staged scope.

Verification​

Use these source files to verify review routing:

sed -n '1,150p' .codex/routing/review-matrix.md
sed -n '1,120p' .codex/routing/repos/document.md
sed -n '1,120p' .codex/routing/commit-policy.md

Expected success signal: the matrix shows capability classes and product-doc rows, the document route shows the doc specialist routing, and the commit policy shows the staged-scope evidence contract.