Internal · Blake and Tyler only

Systems Map working notes

The internal side of the systems map: which of today's tools rolls into each tier, and what we still have to decide. Not for client eyes.

What rolls into each tier

Proposed, for us to confirm together. Today's tools mapped to their tier so we merge instead of multiply.

Tier	Absorbs today's tools
Admin	resources.theinnercirql.com (internal team hub), the systems hub, the Territory Takeover lead-source wheel, the EOS dashboards and workbook
Operator	the-platform Command Center (leaders.yourinnercirql.com), whitelabeled per client, exactly as the platform blueprint already describes
Agent	the-platform Agent Hub, plus the member portal content (resources.yourinnercirql.com): training, resources, weekly slides

Where the data physically lives and syncs from: GHL, Follow Up Boss, Sheets, or the platform's own store.
What exactly counts as the "selected company information" an operator passes down to agents.
Login and whitelabeling per operator: one platform with tenants, or one deploy per client.
Migration order for the tools in the roll-up table, and what gets retired when its tier absorbs it.

Drafted by Blake with Claude, August 31, 2026, from Blake's spec. Nothing here is built yet: the map is the agreement to build against.