Framework Mapping
Use this after or alongside repo-audit to decide how a proposal fits the current codebase.
Procedure
- Read
AGENTS.mdand, when useful,../company-workflow/references/workflow.md. - Inspect the relevant entrypoint, config, model package, dataset, engine, and metric code.
- Identify the closest existing backend or preserved baseline.
- Decide whether the proposal needs:
- config/spec only
- a thin utility wrapper
- a copied variant package
- a new runtime adapter
- rejection as unsupported
- Call out missing artifacts, unsupported assumptions, and validation requirements.
- Route to
experiment-design,experiment-feasibility,paper-intake, or implementation.
Output
- backend mapping note
- preserved baseline / copied variant recommendation
- exact files likely involved
- minimal validation path
- caveats and next owner
Guardrails
- Preserve existing backend paths unless evidence shows a thinner path is impossible.
- Do not mutate preserved baselines for new experiments.
- Distinguish current repo behavior from proposed behavior.