Concept

Known Business Record

The central JSON document in OCG: one business, one point in time, one hashable machine-readable shape.

A Known Business Record represents one real business at a specific point in time, with enough structure for a wallet, agent, or indexer to act without guessing.

The record carries four signals: Identity, Understanding, Proof, and Consistency. It may also carry a Solana profile, Blink references, external attestation pointers, and vendor-namespaced extensions.

It is not a database row, contract, or Solana account. It is a JSON document with a stable schema, a strict normalization pipeline, and a lowercase SHA-256 content hash.

Required surface

The required fields are schemaVersion, recordId, recordType, lifecycleStatus, identity.displayName, locations, categories, services, proof, and metadata with createdAt, updatedAt, and source.

Lifecycle status is operator intent. Readiness status is validator output. The two never mix.