Scope

Back to The Value Path

Scope

Scope governs exactly which entities, datasets, systems, relationships, and boundaries belong to the data-quality problem.

SCO-01 · SCOPE-01 — Define the Universe by Authoritative Identity. Establish the in-scope universe as the complete set of authoritative entity identifiers required by the task, not merely the records currently present in a local system.

SCO-02 · SCOPE-02 — Derive the Universe from Current Evidence. Build the entity universe from a current authoritative source and preserve valid identifiers even when they do not conform to the dominant length, format, or pattern.

SCO-03 · SCOPE-03 — Enumerate the Target Data Objects. Explicitly name the datasets, tables, collections, histories, or other objects covered by the task. Treat anything not enumerated as outside scope unless subsequently authorized.

SCO-04 · SCOPE-04 — Maintain One Master Roster Entry per Authoritative Entity. Prevent accidental duplication or omission by enforcing the declared master-row cardinality against the authoritative identifier universe.

SCO-05 · SCOPE-05 — Stage Scope in Dependency Order. Establish authoritative identities first, validated routes second, and full entity data and dependent histories only after those prerequisites are sound.

SCO-06 · SCOPE-06 — Never Lose a Valid In-Scope Entity. An awkward identifier, missing attribute, routing failure, parse failure, or exceptional shape is not permission to remove a valid entity from the required universe.

SCO-07 · SCOPE-07 — Isolate Unrelated Systems and Data. Do not touch unrelated databases, tables, datasets, interfaces, tasks, files, applications, or resources during investigation or correction.

SCO-08 · SCOPE-08 — Distinguish Canonical Routes from Observation Routes. When both matter, store the canonical entity route separately from the exact source route from which a particular observation was obtained.

SCO-09 · SCOPE-09 — Do Not Infer Correctness from Processing Order. The order in which records are discovered, processed, or committed does not establish whether their values are correct.SCO-10 · SCOPE-10 — Never Change Scope for Convenience. Do not silently narrow difficult cases out of the task or expand into adjacent systems merely because doing so simplifies execution.

The 3 Dimensions of Describing Time

1) Origin

Question: Does this unit exist without humans, or only because humans define and maintain it?
Values: Independent / Declared

2) Basis

Question: Is this unit defined by how much time passes, or by what role it plays?
Values: Counted / Assigned

3) Edge

Question: Does this unit have a practical endpoint, or is it open-ended in use?
Values: Finite / Indefinite

STRUCTURAL FORM

Time:  -----------------------------→
              ↑
         Moment (point)

Scope:      [──────────────]
             ↑          ↑
          Start      End

Time is infinite and directional.
Moment is anchored and atomic.
Scope is Perceived and bounded.