# [Subproject title]

## Minimum repository contents

This repository should normally include this `README.md`, `.gitignore`, and
`.geoepi.yml`, plus the scientific workflow, dependency information, entry
point, principal data inputs, controlled-data IDs where relevant, external
data sources, output locations, and consequential limitations or current
issues. The folder layout should serve the workstream; no universal directory
tree is required.

## Parent project and purpose

- **Parent GeoEpi project:**
- **Subproject ID:**
- **Purpose:**
- **Lead/contact:**
- **Current status:**
- **Canonical repository:**

## Data inputs

- **Controlled-data IDs used:**
- **Public or external data sources:**
- **Principal data versions or acquisition dates:**

Do not put controlled data or credentials in this repository. Link to approved storage and record enough information to identify the inputs used.

## Computing and workflow

- **Computational location:**
- **Entry point:**
- **Setup or environment instructions:**
- **Principal configuration:**

Describe the workflow in the order a contributor should run or inspect it. Keep exact run details, logs, manifests, parameters, and outputs with the repository and approved computational storage.

## Outputs

List expected outputs, their locations, and the project products they support.

## Reproducibility information

Record code and data versions, environment information, random seeds or replicate definitions where relevant, and the checks used to assess outputs. Link to the project’s DMP and controlled-data inventory when appropriate.

## Repository organization

Explain the organization only as far as it helps contributors distinguish code,
configuration, documentation, inputs, outputs, logs, and temporary files.

## Limitations and current issues

Record known limitations, unresolved decisions, failed approaches, and the next action or milestone.