Data requirements

A smaller, documented input makes the service safer and easier to audit.

The normal starting point is ten representative signed agreements through an agreed secure exchange. Nothing operational should be sent through the public website.

Accepted profile

Fields the working schema is designed around.

  • agreement token
  • counterparty
  • business owner
  • effective date
  • term
  • renewal rule
  • notice window
  • source page

The field list is a planning profile, not a request to email data. The exact schema and secure exchange are agreed in writing after fit review.

Explicit exclusions

Data and authority we do not need.

No legal advice, redlining, autonomous interpretation, signature workflow, privilege guarantee, or claim that AI review replaces counsel.

Credentials, unrestricted system access, and unrequested free text are never part of the published plan.

Data lifecycle

Five visible handling stages.

  1. 01

    Agree

    Write down the permitted fields, purpose, owner, transfer, retention, and deletion rule.

  2. 02

    Prepare

    The buyer exports and normalizes only the agreed minimum input.

  3. 03

    Validate

    Schema failures and unknown values are rejected without inference.

  4. 04

    Deliver

    Portable outputs carry definitions, exceptions, and confirmation states.

  5. 05

    Delete

    Working data follows the written retention rule; the buyer keeps the final pack.

Field glossary

Shared definitions prevent expensive rework.

Source page
The page where the reported field appears in the supplied agreement.
Confirmation state
Unreviewed, confirmed, corrected, or legal review required.
Notice window
A reported contractual period requiring authorized interpretation.
Register steward
The person accountable for maintaining the structured record.
Ambiguity
A field that cannot be safely recorded without human interpretation.
Portable export
A tabular copy that avoids repository lock-in.

A useful first conversation

Check the data boundary before discussing a plan.

Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.