git:20260731.44b6d5d to git:20260830.c2263a9

2 added, 2 removed. Audit A to A.

# Mathodology Agent Guide

Mathodology is an Agent Skills pack purpose-built for math modeling contests (MCM/ICM, CUMCM, Huashu Cup, M3, HiMCM/MidMCM, IMMC/IM2C, and similar), targeting award-level submissions end to end. This repository is skills-only. The current GitHub tree intentionally contains no application source, CI, deployment, generated contracts, datasets, package manifests, lockfiles, or build outputs.

Project skills for AI coding tools live in `.claude/skills/`.

- The root `.mcp.json` registers the keyless `search` MCP server (free-search-mcp) and enables its staged `download` tool. `mathodology-evidence-search` combines that server with built-in `WebSearch` by default, so a clone has dual-source evidence discovery with no per-user setup.

+ The root `.mcp.json` registers the keyless `search` MCP server (free-search-mcp) and enables its staged `download` tool. `mathodology-evidence-search` combines that server — its two-level category routing and its `paper_graph` prior-art/retraction check included — with built-in `WebSearch` by default, so a clone has dual-source evidence discovery with no per-user setup.

Claude Code project subagents live in `.claude/agents/`.

Claude Code workflow templates live in `.claude/workflows/`.

Before non-trivial work, load the relevant skill:

- `mathodology-whole-project` for full skills-repository orientation, backup, transfer, restore, and Codex or Claude Code orchestration.

- `mathodology-project-orientation` for the current skills-only layout, retained files, deletion policy, and repository boundary checks.

- `mathodology-award-gates` for award-run gate schemas (structured handoff/gate/scorecard/decision_memo), the severity ladder, judge-panel thresholds, iteration budgets, run layout, the blind seat protocol, and the shipped figure/PDF QA and run-block linting scripts.

- - `mathodology-evidence-search` for external evidence work: combined built-in `WebSearch` and `search` MCP discovery by default, category routing to literature and dataset databases, source reconciliation, citation verification, reproducible downloads, and explicit single-source degradation.

+ - `mathodology-evidence-search` for external evidence work: combined built-in `WebSearch` and `search` MCP discovery by default, two-level category routing across literature, dataset, news, finance, code, forum, and image sources, source reconciliation, citation verification with a `paper_graph` prior-art/retraction check, reproducible downloads, and explicit single-source degradation.

- `mathodology-agent-pipeline` for archived knowledge about the former Python agent pipeline and the new award-level phase workflow.

- `mathodology-gateway-api` for archived knowledge about the former Rust gateway and API.

- `mathodology-web-ui` for archived knowledge about the former Vue web UI.

- `mathodology-dev-test-release` for skills-only validation and archived dev, test, deploy, packaging, and release guidance.

- `mathodology-skill-authoring` for adding or updating `SKILL.md` files and `agents/openai.yaml` metadata.

For Claude Code, prefer `.claude/workflows/mathodology-award-submission.md` with the `mathodology-*` project subagents. The `mathodology-lead` agent runs as the main thread and dispatches the specialists; at Phase 7 it dispatches three independent blind `mathodology-award-judge` seats in parallel and aggregates their scorecards against the numeric tier thresholds in `mathodology-award-gates`. If the contest is M3, HiMCM/MidMCM, IMMC/IM2C, leaderboard/data-science, operations/policy/business-case, or short-sprint style, also load `.claude/workflows/mathodology-contest-variants.md` and apply the matching adapter.

For Codex, run the 9-phase workflow in multi-agents mode from `docs/WORKFLOWS.md`: dispatch independent agents per phase, synthesize, then gate with an independent critic before continuing. In Phase 0, classify the contest type and apply the matching workflow adapter from `docs/WORKFLOWS.md`. Ask the user only for contest-critical details that would change requirements, data access, model choice, compute budget, or final submission constraints; otherwise record conservative assumptions and continue phase by phase. Every phase artifact must have a specialist handoff and an independent critic gate before it can feed the next phase.

Do not reintroduce non-skills project files unless the user explicitly changes the repository strategy. If historical application code is needed, inspect Git history in a separate branch or worktree instead of adding it back to `main`.