One Business Record

Can a single structured Business Record become the source for multiple digital experiences?

If a business has one structured, claimable record carrying provenance and freshness per field, that record can feed listings, profile pages, publishing surfaces and machine responses without being re-entered each time.

Hypothesis — not a conclusion

Today the same business fact is duplicated across dozens of surfaces with no shared source. A record layer would give a business one place to control its own authoritative information.

1. Business entity
   ↓
2. Structured record
   ↓
3. Claim
   ↓
4. Verify
   ↓
5. Distribute
   ↓
6. Human + machine surfaces

• OneBusinessRecord.com ↗
• BusinessRecordOS.com ↗

• —That a minimum record schema can describe most local businesses
• —That per-field provenance and timestamps stay maintainable
• —That one record can render correctly across at least three different surfaces
• —That owners are willing to claim and maintain a record

Field-level provenance makes the record noticeably larger and raises real questions about who is permitted to edit what.

Testing has not yet produced documented results.

• Businesses are unwilling to claim or maintain a record
• Surfaces prefer their own data over a shared record
• Maintenance cost per record exceeds its value

• What is the smallest set of fields worth verifying first?
• Who arbitrates when the owner and an external source disagree?
• How often does a record need to be re-confirmed to stay trusted?

Define a minimum record schema and render the same record across a listing, a profile page and a machine response.