# To-Do Records

This directory stores actionable follow-up documents for migration checks, parity investigations, release gates, and similar project work that should not be lost in chat history.

## File Naming

Use one Markdown file per work item:

```text
YYYY-MM-DD-short-topic.md
```

Examples:

```text
2026-06-24-nexuscrm-salesforce-staging-parity.md
2026-06-25-revenue-source-cutover.md
```

## Document Structure

Each to-do document should use this structure:

```markdown
# Title

- Status:
- Priority:
- Owner:
- Created:
- Last updated:
- Related branch:
- Related PR:

## Objective

What decision, migration, or fix this item is meant to drive.

## Scope

What was checked or will be changed. Include explicit exclusions.

## Evidence

Commands, generated artifacts, source tables, row counts, key coverage, schema diffs, or links to reports.

## Findings

Observed facts, grouped by impact. Keep findings evidence-based.

## Required Follow-Ups

Actionable tasks that must be completed before this item can close.

## Acceptance Criteria

Concrete checks that prove the work is done.

## Notes

Useful context, assumptions, or caveats that do not belong in the sections above.
```

## Status Values

- `Open`: work remains and has not been started.
- `In progress`: someone is actively working on it.
- `Blocked`: work cannot move without an upstream change or decision.
- `Ready for verification`: implementation is complete and needs validation.
- `Closed`: acceptance criteria are met.

## Priority Values

- `P0`: blocks cutover, release, or production correctness.
- `P1`: material correctness issue that should be fixed before cutover.
- `P2`: useful cleanup or follow-up that does not block cutover.
- `P3`: informational or opportunistic work.