# Fictional MSP vendor renewal map field dictionary

This dictionary belongs to a free, fully fictional Saltworks resource. It does not describe customer work or a proven Saltworks service.

## Identity and lineage

- `row_id`: Stable fictional row identifier used to connect the map, calendar, and draft.
- `fictional_state`: Must be `fictional_example` for every row in this give-first set.
- `fictional_vendor`: Invented vendor label. No real vendor or customer identity belongs in this asset.
- `agreement_label`: Invented agreement identifier used consistently across sources and outputs.
- `source_reference`: Buyer-readable source label and section reference. A row without an accessible source reference is incomplete.

## Renewal and notice facts

- `commencement_date`: Date the supplied source says service begins, or `not found`.
- `initial_term`: Initial period directly stated in the supplied source, or `not found`.
- `candidate_term_end`: Source-stated term end or a date derived from a source-stated commencement date and initial term. This is not silently treated as a renewal date.
- `candidate_term_end_calculation_inputs`: Reproducible source inputs, operation, and result when candidate term end is derived. Use `not applicable` when the field is direct or not found.
- `renewal_date`: Renewal date directly stated in the supplied source, or `not found`.
- `renewal_term`: Renewal period directly stated in the supplied source, or `not found`.
- `notice_period`: Exact period stated in the supplied source, a visible conflict, or `not found`.
- `last_safe_notice_date`: Calculated date only when the controlling renewal date and notice period are established. Otherwise `not found`.
- `last_safe_notice_date_calculation_inputs`: Reproducible source inputs, operation, and result for a derived last-safe-notice date. Use `not applicable` when no calculation exists.
- `notice_method`: Method stated in the supplied source, a visible conflict, or `not found`.
- `notice_recipient`: Recipient stated in the supplied source, a visible conflict, or `not found`. The buyer must verify the operational recipient before use.

## Evidence and confirmation

- Each operational field has its own adjacent `*_evidence_state`. A row-level label may not stand in for field-level truth.
- Every `*_evidence_state`: Exactly one of `directly_stated_in_supplied_source`, `derived_from_supplied_dates_and_stated_period`, `conflicting_sources`, or `not_found`.
- A `not found` field must use `not_found`. A derived field must expose its source inputs and operation where a calculation is required.
- `buyer_confirmation_state`: Exactly one of `buyer_confirmed`, `buyer_must_check`, or `not_found`.
- `calendar_date`: A date admitted to the calendar preview only when the fictional row is `buyer_confirmed`.
- `calendar_eligible`: `yes` only for a buyer-confirmed fictional date with a source reference and owner state. Otherwise `no`.

## Ownership and action

- `owner_state`: Exactly one of `owner_assigned` or `owner_missing`.
- `owner_label`: Fictional owner label when assigned, or `not assigned`.
- `next_action`: Bounded next check. It does not direct a vendor action or claim an outcome.

## Honest limits

This map does not provide legal interpretation. Every operational date, notice method, recipient, document-precedence question, and owner must be confirmed by the buyer before use. An unknown remains `not found`; a conflict remains `conflicting_sources`.