Data model

Beacon publishes one object per grain. Every value on an object carries a name, a type, a method, an audience ceiling, and an availability mark for each door it can travel through.

​

Objects

​

Doors

A value reaches you through up to four doors. Three carry values today.

​

Naming

The beacon_ prefix marks a value written into a tool Beacon does not own. Inside Beacon’s own model the name is bare. One value carries both spellings, applied by the door and never stored twice.

​

Method

Two words describe how a value is produced.

• Measured — computed by a fixed formula. The same inputs return the same value.
• Modelled — a composite. A modelled value lands in a tool Beacon does not own as a band, never as a point number.

​

Availability

Financial values are available by default on the read interface and MCP tools under a reader grant, and off by default on the CRM door. A property written into your CRM leaves Beacon’s access log: the tool’s own permissions govern who reads it from that point, and Beacon can no longer record who read it.

​

Audience ceiling

Every value carries one of three ceilings — operational, leadership-only, board-grade. Above operational the CRM door is off by default and switching it on requires the opt-in above. The ceiling is not a block.

​

Constraints

• as_of accompanies every value on every door.
• Raw user-event data never leaves Beacon on any door. Usage is published at account grain only, as usage_trend, active_users and last_active_date.
• A published name is permanent. A rename ships as a redirect, and a value is deprecated in the next version rather than removed from a published one.

​

Related