The USG Resolver is a minimal, read-only HTTP service that resolves canonical Universal Sports Graph (USG) identifiers into authoritative registry records.
It provides a thin query surface over the USG Reference Registry for inspection, experimentation, and integration testing. The resolver introduces no business logic, authorization, inference, or opinionated behavior.
This repository contains a reference implementation, not a production service.
The resolver exists to demonstrate that USG identifiers are queryable and inspectable, not merely described in documentation.
Its role is to:
- expose deterministic ID → record resolution,
- allow third parties to inspect real registry objects,
- validate referential integrity across the protocol stack.
The resolver is intended for researchers, engineers, and evaluators assessing the USG protocol, not for end-user or production consumption.
It is intentionally small in scope and deliberately constrained.
The resolver is:
- Read-only — no writes, mutations, or state changes
- Reference-only — not production-hardened
- Registry-backed — loads a pinned snapshot of the USG Reference Registry at startup
- Logic-free — no joins, inference, scoring, or interpretation
- Non-operational — no uptime guarantees, SLAs, or support commitments
The resolver is not a second source of truth.
It is a thin interface over the registry.
The resolver does not:
- expand or curate datasets
- perform access control or rights enforcement
- model business logic or commercial terms
- provide SDKs, client libraries, or UI
- define adoption paths or roadmaps
Any such work would occur in separate projects.
- Resolver version:
v0.1 - Registry snapshot:
usg-registry@0.1.1 - Intended use: inspection, verification, and protocol evaluation
This is the intended stopping point for the resolver at this phase.
The Universal Sports Graph (USG) is a protocol framework for representing sports rights, events, entities, and entitlements in interoperable form.
This resolver exists solely to make the protocol inspectable as infrastructure, not just specification.