Academic Repo Analyzer

Produce a concise repository understanding document plus a machine-readable Semantic Architecture Handoff v1. The handoff describes scientific roles and executable relationships, not the repository's folder layout or engineering boilerplate.

Read keywords.md only when task or framework classification is uncertain. Read references/missing-info-policy.md when evidence is sparse.

Core Principle: Narrative Priority & Non-Intrusive Extraction

1. Paper & User Narrative > Code Implementation:
   • A paper figure depicts the scientific contribution and conceptual data flow, not the full software engineering artifact.
   • Omit engineering plumbing (such as DataLoader, Trainer, Logger, ConfigParser, DeviceManager, or Optimizer setup) unless the paper specifically contributes a training algorithm or infrastructure system.
2. Fact-Checking & Parameter Grounding:
   • When a paper draft or user architecture is already present, the repo analyzer acts as a supporting fact-checker (verifying tensor dimensions, loss formulas, exact module names, and execution directions) rather than re-inventing the architecture.

Input contract