THE STANDARD · STRATEGIC BRIEF
The Standard Is the Moat: Why the NIST Path Matters More Than the Schema
BY REAL REVEALAUG 20268 MIN READ
The SDTX technical architecture is the strong part. A v1.0 release
candidate already exists — versioned, layered, machine-readable. What it lacks is not schema.
What it lacks is a standards home, a conformity regime, and federal legibility. Those gaps are
external and institutional, which is exactly where a young standard's gaps should be.
A schema you can copy in a weekend. A governed standard with a conformity-assessment body,
a federal pilot sponsor, a 501(c) standards home, and a chain of institutional adoption you
cannot copy — because you cannot be the first organization to have governed it. That ordering
is the moat, and it is the entire strategy.
What already exists
The SDTX architecture reads in five layers, each with one job. The doctrine layer (RT-001
through RT-012) defines what a file means: feature-control-frame logic, modifier bundles,
spatial comparisons, vault-record logic. The core package layer defines what a package is:
profile-governed schemas, state-aware records, compound records, redacted derivatives. The
operational layer makes it usable: a unified validator, migration runners, workbench projects.
The interoperability layer lets it coexist: bindings to IFC/BCF, STEP/QIF, STAC/GeoPackage,
and 3D Tiles. The trust layer makes claims durable: trust envelopes, countersignatures,
verification manifests, and the v1.0 release-candidate pack. The lineage behind it is real and
incremental: v0.1 core through v0.9 reference and the v1.0 RC — twelve versions, one direction.
WHAT EXISTS → COHERENT STANDARDS-FAMILY ARCHITECTURE · MACHINE-READABLE SCHEMAS
→ LIFECYCLE + TRUST + REDACTION · CROSS-DOMAIN PROFILES · v1.0 RC
OPEN GAPS → NO FORMAL STANDARDS-BODY HOME YET
→ NO FEDERAL PILOT SPONSOR YET
→ NO CONFORMITY-ASSESSMENT SCHEME · NO ACCREDITED PATH LOCKED
THE POINT → GAPS ARE EXTERNAL AND INSTITUTIONAL · EXACTLY WHERE THEY SHOULD BE
Six phases from release candidate to moat
Between the current state and a federally legible, institutionally governed standard is a
defined sequence. What makes it credible — rather than a wish list — is that each phase has
a hard exit condition: an externally checkable fact, not an internal opinion. You do not advance
until the prior gate is objectively met.
Phase 1 stabilizes the specification: lock the v1.x core, freeze naming and package identity,
publish compatibility and deprecation policy. Exit condition: no breaking schema change without
formal version movement. Phase 2 hardens the reference implementation: one official validator,
one migration runner, one example suite. Exit condition: independent users validate and migrate
without tribal knowledge. Phase 3 defines conformity: test corpora, conformance levels, a
machine-readable evidence trail. Phase 4 establishes the standards home — a 501(c) body that
can sponsor the standard through consensus process and position it for NIST comment.
Phase 5 engages federal sponsorship: agency pilot, interoperability demonstrations, procurement
references. Phase 6 achieves the outcome: credible NIST-facing position — referenced
in federal guidance, procurement-ready, with third-party implementations.
The critical ordering: credible NIST-facing position is an outcome, not an input. It is
produced by the other phases working together — it cannot be purchased, declared, or shortcut.
A competitor who starts building a spatial standard today faces every one of those phases with
zero institutional history. Real Reveal does not.
Why the standardization path is the durable moat
The schema is defensible but copyable. The standards path is neither — because the path is
time-stamped and institutional. The SD&T priority date is April 9, 2026. The 501(c) standards
body pathway, the pilot-sponsor relationships, the conformity-assessment framework, the
government source inspection discipline built into the founder's career — none of these are
replicable by a competitor starting today, because the starting date has already passed.
The moat is not the notation. It is the chain of governed adoption that cannot be
backdated.
SD&T PRIORITY DATE → APRIL 9, 2026
ARCHITECTURE → v1.0 RELEASE CANDIDATE · FIVE LAYERS · MACHINE-READABLE
STANDARDS PATH → 501(c) BODY · NIST COMMENT VENUE · FEDERAL PILOT SPONSORSHIP
THE MOAT → GOVERNED ADOPTION THAT CANNOT BE BACKDATED
Every standard that governs something important went through this sequence — from MIL-STD-8
to ASME Y14.5 to the IFC schema. What each of those has that no competitor could later claim
is the institutional history of being first, governed, and adopted. The value is not being
right about what the standard should say. The value is being the organization that said it first,
governed it properly, and let the institutions build on top of it.