Build with Project Z7
Create resolvers, resources and services that preserve the Z7 identity and provenance contracts.
Resolver
Normalize a number and return structured profile, status and provenance information.
Manifest
Use versioned owner-authorized metadata and discoverable service endpoints.
Resource layer
Add search, communication, commerce or specialist functions without redefining the identity.
Error semantics
Distinguish unavailable, invalid, stale, disputed and unsupported states.
Conformance
Use stable schemas, reference vectors and reproducible interoperability tests.
Extensions
Request explicit permissions and expose the origin of extension-generated information.
Resolver responsibilities
A resolver should normalize input deterministically, retrieve the correct state, verify status and freshness, follow versioned references and return structured provenance. The resource may then add its own presentation and services without changing the underlying identifier.
Stable errors are part of the contract
Clients need predictable distinctions between invalid input, no matching profile, available number, suspended state, stale data, unsupported version and temporary resolver failure. An implementation should not convert every failure into an empty result.
Conformance before branding
Compatibility claims should be backed by reference fixtures, versioned schemas and reproducible tests. Resources may differ visually and commercially while remaining interoperable at the resolution and authority boundaries.