Saltworks: MSP vendor renewal map

How to read it

Four states, not one confident-looking answer.

A useful map should make its limits visible. Every operational field carries its own evidence state, alongside the row's source reference, confirmation state, and owner state. An unknown stays unknown, and only a buyer-confirmed fictional date appears in the calendar preview.

01

Directly stated

The supplied source names the fact without calculation.

02

Derived

A date follows from supplied dates and a stated period, so the buyer still checks it.

03

Conflicting

Two supplied sources disagree. The map exposes the conflict and does not choose.

04

Not found

The source does not answer the field. No date or notice route is guessed.

Fictional source set

Three invented agreements with three different evidence problems.

Every vendor, clause, date, person, and agreement below is fictional. These excerpts exist only to demonstrate source lineage and uncertainty handling.

Source-001 · § 3.2 Fictional

Northstar Compute Cooperative

Managed infrastructure agreement NC-01

“The initial term ends 31 March 2027 and renews for successive twelve-month terms unless Buyer gives at least 60 calendar days written notice before term end.”

Read the fictional source excerpt

Source-002 · § 1.1 Fictional

Cedar Desk Systems

Order form CS-02

“Services commence 15 August 2026. The initial service term is twelve months.” The source is silent on renewal, notice period, method, and recipient.

Read the fictional source excerpt

Source-003 · §§ 4.4 and A-2 Fictional

Harbourline Networks

Framework and addendum HN-03

The framework says 90 days. A later addendum says 30 days but does not state whether it replaces the framework. No renewal date appears.

Read the fictional source excerpt

Fictional map

Every field is useful only when its evidence state travels with it.

The table is a visual preview of the downloadable CSV asset. Dates are ISO-formatted to reduce ambiguity. “Buyer confirmed” is itself fictional here and demonstrates the required state, not an actual buyer action.

Fictional source-to-map example. No customer or live agreement data is present.
Agreement	Source reference	Field-level renewal and notice evidence	Confirmation	Owner and next action
Northstar Compute CooperativeNC-01 · fictional	Source-001 § 3.2 and § 4.1	Commencement datenot foundNot found Initial termnot foundNot found Candidate term end2027-03-31Directly stated Renewal date2027-03-31Directly stated Renewal term12 monthsDirectly stated Notice period60 calendar daysDirectly stated Last safe notice date2027-01-30Derived2027-03-31 minus 60 calendar days equals 2027-01-30. Notice methodportal and registered postDirectly stated Notice recipientContract Administration recipient requiring buyer verificationDirectly stated	Buyer confirmed Fictional confirmation for example purposes.	Owner assignedMorgan Lee, fictional Review the fictional notice draft and recipient.
Cedar Desk SystemsCS-02 · fictional	Source-002 § 1.1	Commencement date2026-08-15Directly stated Initial term12 monthsDirectly stated Candidate term end2027-08-15Derived2026-08-15 plus 12 calendar months equals 2027-08-15. This is not a renewal date. Renewal datenot foundNot found Renewal termnot foundNot found Notice periodnot foundNot found Last safe notice datenot foundNot found Notice methodnot foundNot found Notice recipientnot foundNot found	Buyer must check Excluded from the calendar preview.	Owner missingAssign an owner, then obtain the controlling renewal source.
Harbourline NetworksHN-03 · fictional	Source-003 §§ 4.4 and A-2	Commencement datenot foundNot found Initial termnot foundNot found Candidate term endnot foundNot found Renewal datenot foundNot found Renewal termnot foundNot found Notice period90 calendar days or 30 calendar daysConflicting sources Last safe notice datenot foundNot found Notice methodregistered postDirectly stated Notice recipientnot foundNot found	Buyer must check No operational date is inferred.	Owner assignedPriya Shah, fictional Resolve document precedence with qualified counsel.

Give-first set

The format includes the prep and review work around the map.

These downloadable assets are fully fictional and contain no intake path. They demonstrate the minimum evidence vocabulary, preparation guidance, calendar restraint, and review posture expected from the proposed output.

Field dictionary

Every column has a job and an allowed state.

Field-level evidence states distinguish direct source fact, derivation, conflict, and absence. Confirmation and owner states stay separate.

Read the fictional field dictionary

Source preparation

Redact first and keep the batch narrow.

The checklist identifies useful clauses, prohibited inputs, source labels, duplicate handling, and readability checks. Do not send files; intake is closed.

Read the fictional preparation checklist

Calendar preview

Only a confirmed fictional date with its field evidence enters the ICS file.

2027-01-30
[Fictional] Northstar Compute
Last safe notice date
Derived: 2027-03-31 minus 60 calendar days
Source-001 § 3.2 · buyer confirmed · owner assigned

The derived Cedar date and the conflicting Harbourline notice periods are deliberately absent.

Open the fictional ICS preview

Notice draft

A draft for review, never an action.

Fictional example
For buyer and legal review
Do not send

Agreement: NC-01
Source: Source-001 §§ 3.2 and 4.1

The fictional draft uses a buyer-confirmed date and source reference. It does not identify a real recipient and makes no outcome promise.

Read the fictional notice draft

Current gate

A format candidate, not an operating service.

Saltworks uses AI to prepare candidate fields, source links, calculations, and draft outputs. A separate independent review checks source links, field classifications, calculations, and file completeness. That independent review is not represented as human review.

Buyer confirmation is required for every operational date, notice method, recipient, owner, and action before use. This resource is not legal advice and does not claim a customer result.

The paid pilot and intake remain closed. This resource does not prove service delivery, support, deletion, checkout, demand, transaction, money-in, or profit.