Skip to content
THE LOCAL DISTRIBUTIONDistribution, governed

The Local Distribution

Distribution, governed.

One record. Reviewed decisions about where it may appear.

OperationalEvery part described here functions in the current system today. Nothing is sent to outside platforms.

Architecture role

The governed process that determines where approved local information may appear across The Local Grid's connections and Local Surfaces.

Publication lifecycle

  1. Eligible
  2. Reviewed
  3. Published
  4. Measured

Featured lifecycle

  1. Eligible
  2. Requested
  3. Approved
  4. Active

How it works today

  1. 1Eligible is not published

    An eligibility check says which surfaces a record may appear on, with a reason for each. Eligibility alone never makes anything appear. Nothing publishes automatically.

  2. 2Reviewed decisions

    Publication is a separate, reviewed decision. Every publication keeps a recorded reason for why it exists.

  3. 3Rules between surfaces

    An approved item may also appear on related surfaces only where a rule allows it, and only within its own country.

  4. 4Controlled wider reach

    Appearing across a wider area than a business's own places requires an independent review.

  5. 5Featured placement

    Featured placement follows its own approval lifecycle, decided by someone other than the person requesting it.

  6. 6Publication history

    Every change to a publication is written to a history that is preserved and cannot be edited.

  7. 7Measured by surface

    Owners see where they are published, why they appear there, and recorded interactions broken down by surface, privately.

One record is shown on more surfaces only when a reviewed decision allows it. It is never copied. This page explains the process; it is not another database, grid or surface.

Where it sits

  • The Local Grid

    Grid is the connections. Distribution is the reviewed decisions about where information may appear across them.

  • The Local Surfaces

    Surfaces are where approved information appears. Distribution decides whether it may.

  • The Local Visibility

    Visibility is the resulting opportunity to be discovered. Distribution never guarantees it.

Still developing

What exists today, and what does not

  • No automatic syndication to outside platforms — records are not copied, pushed or sent anywhere.
  • No automatic sharing to outside platforms or social networks.
  • No guaranteed placement — Distribution does not guarantee visibility.
  • No visibility score.

Architecture and supporting roles

The operating progression

  1. Infrastructure
  2. Database
  3. Graph
  4. Grid
  5. Distribution
  6. Surfaces
  7. Visibility
  8. Experiences

One system

  • Core is the front door.
  • Infrastructure explains the architecture.
  • Platform provides the shared capabilities.
  • Registry identifies it.
  • Database describes it.
  • Graph connects it.
  • Grid is the connected network.
  • Distribution decides where it may appear.
  • Surfaces present it.
  • Navigator moves people through it by Place × Experience.
  • Visibility is the outcome: being found.
  • Start and Search help people discover it.
  • Business tools help owners act on it.

TheLocalCore.com is the system front door. These pages explain parts of the same system; they are not separate applications or separate databases.