Skip to main content

Codex Review Routing

Lumie routes work by owner surface. Repo cards identify the affected product repo and its local rules. The review matrix decides the concrete human-owner, reviewer-agent, checker-agent, and Verify-evidence coverage after the actual diff is known.

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

Repo Cards

Repo cards under .codex/routing/repos/*.md are the first routing stop for product repo work.

Repo surfaceRepo card
Frontend.codex/routing/repos/frontend.md
Backend.codex/routing/repos/backend.md
Worker.codex/routing/repos/worker.md
Infra.codex/routing/repos/infra.md
Product docs.codex/routing/repos/document.md

For product docs, the document repo card points to lumie-document/AGENTS.md, .codex/knowledge/document/DOC_GEN_RULES.md, the document sidebar map, the closest analog page, and the relevant writer, reviewer, structure, and localization specialists.

Capability Classes

The review matrix uses four 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 Routing

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

The document route also identifies writer roles:

AgentRole
lumie-doc-authorWrites English source-of-truth Docusaurus docs in lumie-document/docusaurus/docs/**
lumie-doc-reviewerReviews English source docs against code reality, Docusaurus rules, sidebar mapping, and link hygiene
lumie-doc-structure-authorMaintains Docusaurus structure: sidebar roots, _category_.json, page placement, locale structure, and sidebar-map alignment
lumie-doc-structure-reviewerReviews Docusaurus structure and placement
lumie-doc-translatorTranslates English source docs into complete Korean localized docs
lumie-doc-i18n-reviewerReviews Korean localization parity, frontmatter, links, and MDX hygiene

For ordinary additions under development/, the Docusaurus sidebar is autogenerated. Page placement is controlled by markdown frontmatter, so adding flat peer pages usually does not require sidebars.js or _category_.json edits.

Control-Plane Routing

.codex changes use different ownership from product docs.

SurfaceRequired coverage
.codex/**/*.md and AGENTS.mdhuman-owner:workspace-owner, checker-agent:codex-md-linter, checker-agent:anti-pattern-tripwire, checker-agent:lumie-risk-scorer
.codex/** except Markdownhuman-owner:workspace-owner, checker-agent:anti-pattern-tripwire, checker-agent:lumie-risk-scorer
Hook-chain integrity, permission boundaries, workflow guardrails, or commit guardrailsAdd checker-agent:security-tripwire
Architecture or policy changesAdd reviewer-agent:lumie-architect

These rows do not apply just because product docs describe .codex; they apply when .codex files themselves change.

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.