Maintain structured, auditable research documentation for the scope-and-evidence-review stage, with logs, evidence tables, and canonical background analysis. Use when gathering findings, drafting background research analysis, keeping claim-to-source traceability, or turning scattered notes into a coherent pre-experiment analysis artifact.
Keep the research traceable. Documentation is not optional once evidence starts accumulating.
Convert raw findings into durable background-analysis artifacts that preserve provenance, uncertainty, and decision context before experimentation starts.
Use or update these files under research/ as needed:
active-plan.mdresearch_log.mdevidence_table.mdanalysis/analysis_report.mdInitialize them from the templates in assets/ when they do not exist.
For experiment-specific artifacts, use:
experiment-log for run recordsresults-analysis for experiment comparison sections in the shared analysis reportverification-protocol for claim verification logsresults-report for the final report after the experimentation stageresearch_log.md:
evidence_table.md for every claim that matters.analysis/analysis_report.md, using the canonical shared schema.analysis/analysis_report.md as the main background-research artifact that experimentation will later extend.research/analysis/history/YYYY-MM-DD_<slug>/ before editing the live interpretation:
analysis_report.mdstats_appendix.mdfigure_catalog.mdEvery important claim should capture:
For benchmark or evaluation claims, capture:
research/analysis/history/ before replacing the live analysis bundle.analysis_report.md should keep a short Revision Status block and a compact Revision History table once material reframes exist.Table N. ....pending rather than inventing experiment content.assets/research-log-template.md.assets/evidence-table-template.md.assets/analysis-report-template.md.references/source-hierarchy.md when deciding source quality.