{
  "format": "vercy-enterprise-profile-candidate/v1",
  "contourId": "EM-LND-13",
  "name": "Enterprise Data Landscape and Analytical Lineage View",
  "decision": "PROFILE",
  "newRuntimeId": false,
  "bases": [
    "WM-DAT-001",
    "WM-DAT-005",
    "WM-DAT-006",
    "WM-DAT-008",
    "WM-DAT-004",
    "WM-MAT-008",
    "WM-XCT-003",
    "WM-ACT-036",
    "WM-KNW-007"
  ],
  "conditionalDependencies": [
    {
      "ref": "WM-REC-002",
      "condition": "Report / Statement publication specification becomes available"
    },
    {
      "ref": "EM-DAT-05 Metric Definition",
      "condition": "Registry identifier is allocated"
    },
    {
      "ref": "WM-DAT-006 completeness perimeter",
      "condition": "Perimeter edition and scope semantics are reconciled"
    }
  ],
  "mastershipMapping": {
    "catalogRecord,dataProduct": "WM-DAT-008",
    "dataset,datasetVersion,distribution": "WM-DAT-001",
    "schema,contractVersion": "WM-DAT-004",
    "pipelineDefinition,deployment": "WM-DAT-005",
    "lineageAssertion": "WM-DAT-006",
    "observation": "WM-MAT-008",
    "reportDefinition,reportIssue": "WM-REC-002 (conditional)",
    "study": "WM-ACT-036",
    "finding,claim": "WM-KNW-007",
    "projectionShape": "WM-XCT-003",
    "metricDefinition": "EM-DAT-05 (unassigned)"
  },
  "unownedFamilies": [
    "pipeline run and task attempt",
    "analysis method definition"
  ],
  "constraints": [
    "Data Landscape is an issued-at, version-pinned snapshot projection and Analytical Lineage View is a WM-DAT-006 profile; neither mints subject identity.",
    "A published projection uses an existing WM-DAT-008 Data Product identity; a reusable handle owns no lineage edge.",
    "Issued-at and as-of are distinct required pins; issued-at binds an immutable observed set.",
    "Definitions remain disjoint from observations, issues, runs, studies and claims; corrections and retries append successors and never amend released artifacts in place.",
    "Every lineage edge records type, granularity, capture method, producer, confidence and evidence; both endpoints are version- or partition-addressed.",
    "Inference-derived edges use captureMethod inferred and cannot establish absence, comparability or direct derivation.",
    "Impact results contain four labelled sets: affected definitions, affected issues or runs, affected findings or claims, and unresolved coverage; flat unclassified results are invalid.",
    "Comparability reconciles formula or method, unit and code-system version, population, dimensions and null policy using comparable, comparable-with-restatement or non-comparable; a missing verdict defaults to non-comparable.",
    "A report issue pins definition versions, parameters, period, cutoff, as-of, issued-at, input versions or partitions and digests, and run reference.",
    "A live dashboard is citable only through a frozen successor report issue.",
    "Missing edges mean unobserved unless a closed, scoped, time-bounded, edition-pinned completeness perimeter covers the issued projection's exact observed set.",
    "Freshness evaluates schema, classification, cohort or privacy, and snapshot states relative to issued-at.",
    "Run success proves neither quality, freshness, publication, acceptance nor fitness.",
    "A superseded WM-XCT-003 crosswalk marks the issued projection stale; mappings are never silently re-resolved.",
    "Unknown, zero, not-applicable, missing and suppressed remain distinct gap classes.",
    "Dependent findings and conclusions must retain stale-input and incomplete-input markers and are never rewritten.",
    "Findings retain scope, assumptions, defeaters and evidence; association never auto-promotes to causation.",
    "The issued projection pins source-rights policy version and fingerprint; policy re-evaluation creates a successor and never mutates the issue.",
    "Withheld segments remain marked withheld and require cohort or privacy controls against recovery by differencing.",
    "Metric-facing validation is gated on EM-DAT-05 registry allocation; report validation is gated on WM-REC-002 publication; perimeter absence validation is gated on reconciled WM-DAT-006 perimeter semantics."
  ],
  "holds": [
    "Metric Definition remains identifier-unassigned under EM-DAT-05.",
    "WM-REC-002 is conditional and has no published specification.",
    "WM-DAT-006 completeness-perimeter semantics and source-version divergences require reconciliation.",
    "Pipeline run or task-attempt and analysis-method mastership are not covered by the resolved bases.",
    "All target bases remain non-canonical reviewable drafts and relation rows remain candidate."
  ]
}