Blair

System Map

BlueForest Intelligence · 2026 edition · one code threads every system

Project ID
XXX-YYYY-NNN
Division + year + number · valid for every entity

The Network

Data boards at the outer stations, rides the Librarian's routes to the Registry interchange, and terminates at the Analyst. The tools express runs nonstop: no connector, straight to the middle.

Blair system map A transit-style network map. Three feeder lines of connected systems (business, comms, docs and archive) converge on the Librarian station. A tools express line bypasses the Librarian and runs directly to the Registry, the central interchange. From the Registry, the four Division lines (VID, SYS, MKT, EMP) run through the Semantic Layer station and terminate at the Analyst. Business line Comms line · phase 3 Docs & archive line Tools express ingest · dedupe · normalize unify on the Project ID express · writes natively · no connector HubSpot — deals and CRM. Connected live. HubSpotdeals · CRM Xero — invoices, the financial source of truth. Connected live. Xeroinvoices · the financial truth Streamtime — budgets and time tracking. Under construction. Streamtimebudgets · time Gmail — client threads. Planned, phase 3. Gmailthreads Calendar — meetings. Planned, phase 3. Calendarmeetings Drive — proposals and files. Planned, phase 3. Drivefiles GitHub — one repo per entity, CLAUDE.md captured on commit. Under construction. GitHubrepos · CLAUDE.md M4 agent — catalogs the NAS and archive drives. Under construction. M4 agentNAS archive BlueView — review and hosting, replaces Vimeo. In build. BlueViewreviews · hosting BlueCue — edit and motion graphics. Planned. BlueCueedit · motion gfx BlueLaunch — project genesis, mints the Project ID. Planned. BlueLaunchproject genesis · mints the code BlueStream — marketing content engine. Planned. BlueStreamcontent engine The Librarian — collects from every connected system on schedule. THE LIBRARIAN the collector · deterministic The Registry — one row per entity, keyed by the Project ID. Everything joins here. REGISTRY one row per entity · the interchange project_code Semantic layer — every table and column explained, so the data is AI-readable. SEMANTIC LAYER every column explained · AI-readable THE ANALYST end of the line · ask anything in plain English query · chat · briefings · alerts

Lines & Divisions

The four Division lines carry every coded entity out of the Registry. Two service lines feed it: the Librarian's scheduled routes and the tools express.

VID · Video productionVID-2026-030

Client delivery work, the studio's core line.

ClientQuoted $BudgetHoursInvoiced $MarginReview statusMaster location
SYS · Systems & internalSYS-2026-001

Internal tools and finance. Blair itself rides this line.

RepoTech stackOwnerMonthly costDocs summaryBuild cost
MKT · Sales & marketingMKT-2026-004

BlueForest's own campaigns, sites and marketing videos.

ChannelGoalSpendLeadsConversionsTrafficROI
EMP · PeopleEMP-2026-001

One work profile per person. Owner-private.

RoleSkillsTrainingAssessmentsPreferencesGoals
Tools expressno connector

Custom-built tools (BlueView, BlueCue, BlueLaunch, BlueStream) write natively to the store, skipping the Librarian.

Feeder linesconnectors

External systems the Librarian pulls on schedule. Dashed route = opens in a later phase.

In service — connected and syncing
Under construction — being built now
Planned — a later phase

Network Status

Traffic on the network

1,728deals (clean, coded)
14,712companies (junk-heavy)
22,328contacts (junk-heavy)
0invoices in HubSpot · Xero holds the truth

Line openings

  • P1 Business spine: HubSpot · Xero · Streamtime now boarding
  • P2 Media & archive: M4 agent · BlueView native next
  • P3 Comms line + vector search later
  • P4 Analyst surfaces: dashboards · briefings later

Depots & Works

Where Blair lives. The railway itself runs in the cloud — around the clock, no Mac required. Everything local is a workshop: useful, replaceable, never the system of record.

The running railway · cloud

supabase (postgres) · cloudflare workers · hourly crons

The live service: the central store (every ingested record, the Registry, the semantic layer) and the Librarian's pipelines. If the local drive died, Blair would keep running without noticing.

The records office · GitHub

private repo · one repo per coded entity (via BlueLaunch)

The canonical home of the source, migrations, and docs. Anyone joining the team gets the whole workshop with one git clone — no access to any personal machine needed. Entity repos mint into the BlueForest organization.

The works · M4 Studio

external drive · working copy · disposable

Where building happens. A few jobs are machine-bound by design: keychain secrets, deploy authorization, local backfills, and the NAS/archive agent (it must run where the drives are mounted). Deploys move to CI when a second builder joins.

Off-network stores · Drive

google drive · non-repo documents only

Backs up what isn't a repo — like the NotebookLM source docs, which live in Drive natively. Repo folders are excluded from file-sync: GitHub is already the offsite copy.

House rule: file-sync services never touch a .git directory — sync artifacts inside repo internals are a real corruption risk. Code and docs are backed up by pushing; documents are backed up by syncing. Never both on the same folder.