brief-compliance-check

# Brief Compliance Check > Given a PDF brief and a LaTeX submission, report exactly what is met, missing, or over-limit. > **Report-only — never modifies files.** ## Output Path Per `rules/review-artefact-routing.md` (auto-loads in research projects (path-scoped to `paper-*/` and `paper/`)): - **Source slug:** `brief-compliance-check` - **Write reports to:** `reviews/<paper-slug>/brief-compliance-check/<YYYY-MM-DD-HHMM>.md` inside the project, where `<paper-slug>` is the paper directory name (e.g., `paper-jtp`, `paper-philtech`). Path is relative to the research project root, not the Task-Management repo. - **Never** at project root (`./CRITIC-REPORT.md`-style filenames are forbidden — pre-rule layout). - **Idempotency:** if today's file exists, append a same-day descriptor (`{date}-revision.md`, `{date}-r2.md`, `{date}-pre-submission.md`) — never overwrite. - **Index update:** if `reviews/INDEX.md` exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise `review-recap` will rebuild the index next time it runs. - **Infrastructure repos** (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there. ## When to Use - "Do we meet the requirements of the brief?" - "Check my submission before I submit" - Any coursework or report with per-task deliverables and word limits - Argument: `[brief.pdf] [submission/]` or auto-detect from context ## Defaults | Setting | Default | |---------|------...