# Fictional source-preparation checklist and redaction guide

This is a free, fully fictional Saltworks give-first resource. Do not send files or contract material. No intake path is open.

## Prepare one narrow source bundle per agreement

- Add a plain agreement label and fictional vendor label.
- Include only the pages or excerpts that may govern term, renewal, notice period, notice method, notice recipient, amendments, or document precedence.
- Label each source with a stable source identifier and section or page reference.
- Place amendments next to the agreement they may change.
- Mark duplicates explicitly. A duplicate does not become a new agreement.
- Mark unreadable pages instead of assuming their content.
- Record the current internal owner if one exists, or use `owner_missing`.

## Redact before any future reviewed transfer

Remove unrelated client records, employee records, credentials, secrets, payment details, bank information, government identifiers, regulated personal or health data, and privileged legal advice. Keep only the minimum agreement language needed to assess term, renewal, notice, recipient, method, and dates.

## Check source quality

- Searchable text is preferred, but image excerpts must remain readable at normal size.
- Keep the full clause context when an exception or definition changes the meaning.
- Do not crop signatures, dates, headings, or section identifiers that establish lineage.
- If two sources disagree, include both and mark the conflict.
- If a field is absent, record `not found`. Do not infer a notice route or operational date from habit.

## Current boundary

Saltworks has not accepted a secure source-intake or deletion workflow for this offer. This checklist does not open one. Independent Product, Finance, privacy, and implementation review must return before any source transfer is considered.