Selection

We start with frequent operational records used across small service businesses. The first collection follows the quote-to-cash workflow. We intentionally exclude contracts, tax filings, employment notices, medical records, identity verification, and other documents where jurisdiction or expert advice is central.

Field design

Each field must support a real handoff, calculation, audit trail, or retrieval need. We minimize free-form text where a date, status, number, or bounded option is clearer. Sensitive account, identity, credential, payment-card, and health fields are excluded.

Validation and output

Required fields, email syntax, and number formats are checked consistently in the browser and through the public validation endpoint. Human files and agent payloads identify the template version used. Computed line-item totals use the values supplied by the user; users remain responsible for reviewing tax treatment and final amounts.

Review status

Version 1.0.0 of the initial registry was checked on August 14, 2026 for clarity, internal field consistency, privacy minimization, and output behavior. That is an editorial and product-quality review—not legal, accounting, tax, payroll, or industry certification.

Changes

Corrections and non-breaking wording improvements increment the patch version. Field additions that preserve compatibility increment the minor version. Breaking schema changes require a major version. Current schemas are exposed through the API so automated users can pin and compare versions.

Report an issue

If a field is ambiguous, an output is inconsistent, or a form encourages unnecessary data collection, send the form name, version, and a concise description. Do not include private client data in the report.