02 / Folder contractBrowse docs
DOCS/PREPARE02

Folder contract

What belongs in the source workspace and how the agent treats each file.

DOCUMENTEDUPDATED AUG 2026

The folder contract defines what the agent may treat as evidence, what it should ignore, and where generated files belong. A clear boundary makes the manuscript easier to audit.

One project, one folder#

Use one dedicated top-level folder per manuscript. The agent reads recursively, so nested folders are useful for grouping but do not hide content.

DO

coastal-risk-manuscript/
One research question, one evidence set.

DON’T

Desktop/
Unrelated files, secrets, and ambiguous scope.

Supported material#

MaterialTypical filesHow it is used
Research notes.md .txt .docx .pdfQuestions, rationale, methods, interpretation
Data & results.csv .tsv .xlsxReported values, tables, and traceable summaries
Figures.png .jpg .pdfArticle figures and visual evidence
References.bib .ris .pdfCitations and bibliography records
Code outputs.json .html .logReproducibility context and computed results
Journal files.cls .sty .bst .texTemplate rules in specific-template mode

What to keep out#

  • Passwords, access tokens, private keys, and credentials.
  • Personally identifying raw data that is not cleared for manuscript use.
  • Unrelated projects or duplicate archives with unclear authority.
  • Generated output from an earlier run unless it is intentionally being revised.
  • Paywalled or licensed material you are not permitted to process.

Evidence source of truth#

Files in the workspace are evidence candidates, not automatic truth. The agent should distinguish raw observations, analysis outputs, interpretations, and author instructions.