Worked example

The ten stages carry one worked example: Meridian Engineering, a fictional mid-size AEC firm. This page shows the result — the same slice expressed as live data across all four layers.

# Layer 1 — grounding (per-source repo; compact names under its NamingContracts)
wh:pub/us.environmental.epa-npdes/DmrRecord/nc/NC0071234/001/00610/2025-06
    { reportedValueNumeric: 7.3, unitCode: "19", statisticCode: "30",
      sourceArtifact -> SourceArtifact/epa-npdes-dmr@v7 }
SourceArtifact/epa-npdes-dmr@v7
    { source -> Source/epa-npdes, semanticSha256: "ab12...",
      mediaType: "application/x-ndjson",
      originalUrl: "https://echo.epa.gov/...",
      durableUri: "https://artifacts.warmhub.dev/semantic/sha256/ab12...",
      acceptedAt: "2025-07-15T12:00:00Z",
      canonicalizationPolicy: "epa-npdes-dmr-canonical-jsonl/v1" }

# Layer 2 — identity (curated repo, identity namespace)
wh:pub/us.infrastructure/Facility/identity/epa-frs/110012345678
Arc/identity/rel/epa-npdes-NC0071234--epa-frs-110012345678   # named per predicate recipe
RefersToFacility/identity/epa-npdes/NC0071234
    about Arc/identity/rel/epa-npdes-NC0071234--epa-frs-110012345678
    { resolutionMethod: "epa-frs-program-link", evidenceWrefs: [...] }

# Layer 3 — domain (same repo, water namespace)
Measurement/water/nc/NC0071234/001/ammonia-nitrogen/2025-06
    { parameter: Parameter/water/ammonia-nitrogen, value: 7.3,
      unit: Unit/water/mg-per-l, statistic: Statistic/water/monthly-average,
      derivedFrom: <grounded record wref>, transformationPolicy: "dmr-norm/v3" }
PerformancePattern/water/millbrook-ammonia-warm-season-2022-2025
    about Facility/identity/epa-frs/110012345678
    { patternClass: recurring-warm-season-elevation, methodVersion: "1.0", evidenceWrefs: [...] }

# Layer 4 — beliefs (a public prediction; a private decision composing it)
wh:pub/us.infrastructure/RegulatoryPressureAssessment/water/millbrook-2026
    { summary: "public evidence indicates treatment-upgrade pressure within 24 months",
      evaluationAsOf: ..., evidenceWrefs: [PerformancePattern/..., ...] }
wh:meridian/intelligence/WarrantsOutreach/town-of-millbrook/2026Q3
    about wh:pub/us.infrastructure/Organization/identity/nc/town-of-millbrook
    { evidenceWrefs: [ FitsICP/..., HasRelevantCapability/...,          # private beliefs
        wh:pub/us.infrastructure/RegulatoryPressureAssessment/water/millbrook-2026 ] }

A skeptical reader starts at WarrantsOutreach and walks, wref by wref, to a pinned EPA semantic-snapshot version and hash on one side and Meridian’s own capability model on the other. That traversal existing, being cheap, and never being fabricated is what this whole method is for.