Effective: 2026-07-16
BR-02 makes entity-profile v1 the only production contract in the VizAI Business Registry.
| Concern | Supported value |
|---|---|
| Profile path | registry/<entity-slug>/profile.json |
| Schema | schema/entity-profile-v1.0.schema.json |
| Authoritative verifier | python -m registry_verify |
| Index generator | tools/build_indexes.py |
| Generated distribution | index/ |
| CI | .github/workflows/validate-registry.yml |
The following production models were deleted:
data/verified/data/community/data/enterprise/registry/<country>/<region>/<city>/<id>.jsonschema/business-profile-v1.0.jsonschema/discovery-profile-v1.0.jsonschema/registry-entry.schema.jsontools/validate_registry.pytools/validation/validate-profile.pytools/validation/validate-entity-profile.pytools/validation/check-registry-duplicates.pytools/automation/generate-indexes.pytools/automation/generate-profile.pyTheir final source remains available in Git history. They must not be restored as production paths.
| Retired field/model | Canonical replacement |
|---|---|
registryId |
entitySlug |
top-level domain |
businessIdentifier.primaryDomain |
top-level name |
businessIdentifier.commonName |
top-level industry |
category |
top-level services |
profile.services |
geo location object |
profile.country plus profile.locations[] |
description / offerings |
approved facts under profile |
storage or service tier |
no public replacement |
verified |
claimed_verified when business-approved |
community |
unclaimed_observed unless a stronger state is established |
pending |
verification_pending |
disputed is the canonical state for a material public factual dispute.
Consumers should stop enumerating tier directories and instead:
index/by-domain.json for exact domain lookup;index/ for discovery;registry/<entity-slug>/profile.json; andverification.status rather than a service tier as the trust signal.No runtime redirect is possible for removed raw GitHub file paths. This migration note and Git history are the compatibility record.