Skip to main content
Classification: supporting evidence. This worksheet is not a production import schema or a request to design a software module. Use it when a source has inputs or operations supplied separately to agree where each one comes from, what it owns, how it joins, and who operates it. Do not complete this worksheet for inventory that simply passes through to an external sales agent unless Scope3 will separately operate a capability for that inventory. Customers may complete the table over time. They do not need to send every stream together, author a manifest, or calculate a file digest.

​
Blank worksheets

Complete the input map first. Use one row per input and inventory scope; split a row when the authority or stable-key mapping changes. An answer may be a provider API, file, named person, or a combination. 1. Map the input and its authority 2. Assign owners and close open questions Then record the operating commitment for every independently arriving stream or human step. The inputs do not need the same cadence, grace period, or failure effect. 3. Record timing and failure effects 4. Agree recovery and escalation Use one of these values in Current handling:
  • Production parser or integration — name the exact current contract.
  • Manual pilot step — name the person, work item, expected response, and durable evidence.
  • Supporting evidence — reviewed material that is not ingested.
  • Gap — no acceptable production or manual path; state whether advisory, capability-blocking, or pilot-blocking.

​
Completed fictional example

The fictional rows demonstrate one source boundary with several providers and human owners. They do not claim that these systems, schedules, or service levels exist for a real publisher.