Skip to content

Brand onboarding — partly built, and more than we remembered

Onboarding is everything that should happen when a brand enters the system: get its basic facts, find its official links, understand its products and features, find and capture its brand guidelines, and route it into ongoing collection. Checked against the code and the live database on 17 August 2026 — two big pieces exist that we spoke about as unbuilt.

What exists today

CapabilityStatusWhat it does
Entity enrichmentbuiltpulls a brand's basic facts — founding year, headquarters, industry, ticker, website, logo — from public sources, with a person-level pass for founders and executives that stages uncertain matches for review
Brand-guidelines pipelinebuilt, and it has runa five-stage path — discover the guidelines online, scrape them, store the images, structure the sections with a model, seed them into the database. Ninety-four guideline sections across twelve brands are live from it
Entity auto-createbuilta brand mentioned in analyzed content gets an entity row and a sector tag automatically
Products & features harvestmissingproduct data today is a byproduct of per-piece analysis; nothing deliberately walks a brand's site to build its product and feature map
"Onboard this brand" routing stepmissingthe ruled onboarding step — decide what a newly-added brand needs and kick it off — does not exist; each piece above is triggered by hand

What a build would decide first

  • The order of operations — enrichment, then links, then guidelines, then products, then collection: one orchestrated run, or independent steps a person triggers?
  • Verification — the guidelines pipeline captures what it finds; the ruled bar ("find it, scrape it, verify it") needs a review surface before seeded sections are treated as truth.
  • Where product discovery writes — the products layer has two connected homes; the harvest must respect the ruled shape rather than invent a third.

Where to look next

Atlas — the BrandTrackers domain model. Source: git markdown, drift-checked against the live DB.