AtlasWhat BrandTrackers knows, in plain language

What Atlas is ​

BrandTrackers is a library of brand and marketing work — companies, the content they make, the campaigns they run, and the labels that describe all of it. Over time, the logic of how these pieces fit together has lived in scattered documents and in people's heads, and it kept getting re-explained.

Atlas is the one place that logic lives. It describes each part of the domain in plain words, says how the parts connect, and points to the exact data behind each claim. Read it before making a big decision about how the product is structured.

The four families ​

Everything we track falls into one of four groups, and this is how they hang together:

Click a box to read that pillar. Three of the four families are written; the last follows the same shape.

• Entities — the things in the world we follow: companies, people, songs, and artists. Read it →
• Groupings — the containers that gather work together: campaigns, brand-identity collections, projects, events and seasons. Read it →
• Content and moments — the actual creative pieces (posts, videos, pages) and the individual beats inside them. Content → · Moments →
• Concepts — the labels we classify against: industry, audience, channel, creative discipline. (being written)

Each pillar follows the same pattern you'll see in Entities: what it is, in plain language; how it connects; a real worked example generated from live rows; and where to look for everything else.

Four surfaces, and why they are separate ​

A page here answers exactly one kind of question. A document that mixes them makes you decide, sentence by sentence, whether you are reading a rule, a measurement, a defect, or a musing — and that is a tax every reader pays forever.

One rule follows from it: a model page contains no unresolved question and no bare number. If something is undecided it lives in open questions. If it is a count it is generated into the state of the data. If it is a place where the system contradicts the model, it is a check on the conformance report — not a paragraph that quietly goes stale and that nobody remembers to delete once it is fixed.

That is what makes a model page reviewable. It can only be wrong about meaning, which is the one thing reading it can actually catch.

How to use this ​

• Reading to understand the domain? Start with the pillars above.
• About to build something? Read the model page, then the conformance report — it tells you which parts of the model the system currently honours.
• Reviewing? Go to open questions. That is the agenda.
• Curious how it is made? The internal notes hold the build plan, research, and status. They're working documents — not the domain model — and they're labelled that way.