MyAdvisorData.ai the brand, set 09-25-26
Your hierarchy's business with Brokers Alliance, on one screen, with your own AI on top.
A command center for BGA principals: the cases your agents place through Brokers Alliance, the requirements open on them, the contracting packets and carrier appointments in motion, and the licensing picture from SureLC. Scoped to your hierarchy only. Read-only. Every number names its source and when it was last updated.
How to read this document (read this first)
Pages come in two kinds, marked by the band across the top. Green band: in the pilot today, proven with a real outside account. Gold striped band with a watermark: concept, a screen that does not exist yet. Each panel also carries three small labels:
Data · do we hold it: live partial not held
BGA access · may a principal see it: approved approved once reconciled not established out by ruling
Screen · how it is delivered: pilot proven by the connection concept
A panel is only "live for a BGA" when all three read green. Most do not yet, and they say so.
What is real behind this preview
The read-only connection behind these pages is live. On 09-25-26 at 10:45 PM ET a real claude.ai account signed in and asked all four questions against a test hierarchy; each answered with its source and as-of time.
Every figure on the following pages is illustrative: a fictional agency, fictional agents, numbers shaped like one real 40-agent hierarchy as of 09-25-26. Not typical, not a benchmark. Insureds appear by initial only, exactly as the connection returns them.
Concept screen · not live · illustrative data · BGA access to production rollups approved 09-25-26 once one real hierarchy reconciles to the dollar
CONCEPT
MyAdvisorData.ai
Northline Financial Group (fictional) · 40 agents · principal view · production as of 09-25-26 9:04 PM ET
ProductionCase deskContracting & licensingPlacement operationsAsk your assistantAccess & audit
Submitted and placed, your hierarchy only
Brandon's ask on 09-25-26: "a submitted dashboard demo version to show agents." Brokers Alliance already computes this view for its own book every two hours and groups it by Team Code. Showing a hierarchy its own rollup was approved on 09-25-26 on one condition: one real hierarchy must first reconcile to Brokers Alliance's internal view to the dollar and pass a foreign-hierarchy denial test.
data liveaccess: approved once reconciledscreen: concept
Submitted · September
33
$486,440 life premium · 558 YTD
data liveaccess: approved once reconciledscreen: concept
Placed · September
45
$385,051 placed premium · 377 YTD
data liveaccess: approved once reconciledscreen: concept
Submitted premium · YTD
$8.46M
Life $7.86M · Annuity $600K · Health $0
data liveaccess: approved once reconciledscreen: concept
Open in pipeline
118
$1.71M submitted premium, not yet decided
data liveaccess: approved once reconciledscreen: concept
Producers, September
| Agent | Sub | Sub prem | Placed | Top carrier |
|---|
| D. Okafor | 7 | $121,300 | 9 | United of Omaha |
| M. Vasiliou | 6 | $96,880 | 8 | Corebridge |
| R. Whitfield | 5 | $74,150 | 6 | F&G |
| S. Nakamura | 4 | $62,900 | 5 | North American |
| J. Brandt | 3 | $48,210 | 4 | Transamerica |
| 35 more agents | 8 | $83,000 | 13 | show all |
Source iPipeline Agency Integrator replica (Snowflake CASE_INFORMATION_VC), agents scoped by Team Code (AGENT_CODE_BRIDGE_VC) · Submitted = SUBMITDATE, Placed = PLACEDDATE with In Force, the same basis as BA's own Command Center since 09-02-26 · principal sees the whole hierarchy; downline agents get no login (access policy, 09-08-26) · not commission, not in-force values
data liveaccess: approved once reconciledscreen: concept
Carrier mix · submitted YTD
Source same replica, CARRIER_NAME · lines Life / Annuity / Health per the 06-22-26 definitions · the internal view already renders top carriers and products per book
data liveaccess: approved once reconciledscreen: concept
Where the open cases sit
9
Approved, awaiting issue
Statuses are iPipeline's own words, grouped by its status dimension. No BA scoring, no colouring by "health".
Filter verified on three real hierarchies 09-25-26 against the live production record: agents grouped once each, shared agents counted and disclosed, no duplicates. The per-hierarchy filter holds; the to-the-dollar reconcile for a real BGA is the remaining gate.
Concept screen · the answers behind it are live in the pilot by case id · illustrative data
CONCEPT
MyAdvisorData.ai
Northline Financial Group (fictional) · snapshot 09-25-26 7:00 PM ET · next refresh 9:00 PM ET · nights and weekends read live (1 to 2 min)
ProductionCase deskContracting & licensingPlacement operationsAsk your assistantAccess & audit
Open cases and what each one is waiting on
The two questions a principal asks a distributor every week, answered from the record instead of a phone call. Today the connection answers them by case id or policy number; the list view below is a screen that would read the same per-principal snapshot through a new, logged, scope-checked path. Insureds by initial only. Case notes never appear.
data liveaccess approved (case status)screen: concept · list view
Open cases · 118 · sorted by last change
| Case | Agent | Carrier · product | Insured | Status | Prem | Open reqs | Last change |
|---|
| 60412988 | D. Okafor | United of Omaha · Income Advantage IUL | W. | Awaiting requirements | $14,200 | 2 | 09-24 |
| 60411203 | M. Vasiliou | Corebridge · Max Accumulator+ III | R. | Pending decision | $9,600 | 0 | 09-24 |
| 60408871 | R. Whitfield | F&G · Pathsetter | K. | App. submitted | $7,150 | 1 | 09-23 |
| 60407540 | S. Nakamura | North American · Builder Plus IUL 4 | L. | Approved | $18,000 | 0 | 09-23 |
| 60403316 | J. Brandt | Transamerica · FFIUL | P. | Awaiting requirements | $5,400 | 3 | 09-22 |
| 60399102 | D. Okafor | Allianz · Accumulator IUL | T. | Issued · delivery req. | $24,000 | 1 | 09-19 |
| 60381777 | A. Tremblay | Mutual of Omaha · Term Life Express | G. | Unknown or incomplete | $1,180 | n/a | 08-2025 · status frozen |
The last row is deliberate: a case whose status has not moved in twelve months is shown as unknown, never as clean. A source outage or a row cap shows the same way, with its reason.
Source per-principal snapshot (Firestore caseNerveSnapshots: open cases, open requirements, appointments, packets) warmed 06:30 UTC and every 2 h weekdays 13:00 to 23:00 UTC, max age 6 h · fields: case id, agent id, APPLICATION_STATUS, STATUSDATE, CHGDATE, CARRIER_NAME, PRODUCT_NAME, POLICYNUMBER, insured last initial · never notes, SSN, medical, contact details · a screen must read it through the same scope check and ledger the connection uses, not directly
data liveaccess approvedpilot proven 09-25-26
Case 60412988 · open requirements
| Requirement | Of | Status | Requested | Follow-up |
|---|
| Paramed exam · labs | Insured | Outstanding | 09-12 | 09-26 |
| Attending physician statement · Dr. H. | Carrier | Ordered | 09-15 | 09-29 |
| Signed illustration | Agent | Received 09-18 | 09-12 | closed |
source: iPipeline replica (Snowflake)
completeness: requirements_found
replica_row_as_of: 09-24-26 8:12 PM ET
retrieved: 09-25-26 7:00 PM ET served_from: snapshot
// a case outside your hierarchy and a case that does not exist return the identical "none recorded" answer
Source CASE_REQUIREMENT_INFORMATION_VC: REQUIREMENT_OF, DESCRIPTION, REQUIREMENT_STATUS, REQUEST_DATE, FOLLOWUP_DATE, STATUS_CHANGE_DATE · this is the open_requirements question, answered end to end on 09-08-26 (Inspector) and 09-25-26 10:45 PM ET (a real claude.ai account)
Concept screen · appointments and packets are live in the pilot by agent id · SureLC panel is not in the pilot
CONCEPT
MyAdvisorData.ai
Northline Financial Group (fictional) · contracting as of 09-25-26 7:00 PM ET · SureLC as of 6:45 PM ET
ProductionCase deskContracting & licensingPlacement operationsAsk your assistantAccess & audit
Contracting, appointments, and the licensing picture
Day one for a newly contracted hierarchy is this page, not the case desk. Two panels are answered by the connection today. The third reads a system we can query but cannot yet map to your hierarchy, and it is drawn to show that gap rather than hide it.
data liveaccess approvedby the connection · pilot proven
Carrier appointments · by agent
| Agent | Carrier | Status | State |
|---|
| D. Okafor | United of Omaha | Active | TX |
| D. Okafor | Corebridge | Active | TX |
| M. Vasiliou | F&G | Pending carrier | FL |
| S. Nakamura | North American | Active | CA |
| A. Tremblay | Transamerica | Terminated 08-26 | NC |
| K. Lindqvist | Mutual of Omaha | None recorded in the replica | AZ |
Source iPipeline APPOINTMENT_INFORMATION_VC per agent per carrier, status decoded by LICENSE_APPOINTMENT_STATUS_VC · the contracting_progress question, answered from claude.ai 09-25-26 10:45 PM ET · "none recorded" means the replica holds no row, not that no appointment exists
data partialaccess approvedby the connection · pilot proven
Contracting packets · Brokers Alliance intake
| Packet | Agent | Carrier · lines | Status | Last touch |
|---|
| 218841 | K. Lindqvist | Mutual of Omaha · Life | Pending requirements | 09-24 |
| 218702 | M. Vasiliou | F&G · Life, Annuity | Pending requirements | 09-22 |
| 218455 | T. Okonkwo | Allianz · Annuity | Ready to process | 09-19 |
| 217990 | J. Brandt | Corebridge · Life | Completed | 09-11 |
Coverage note, carried on every answer: intake records name an iPipeline agent on about one in three instances, so a packet can exist that cannot be attributed to your hierarchy. The answer says so instead of showing an empty list.
Source Single Source Postgres contract_details_view, modules 44 and 45 (record id, status, carrier, product lines, created, last touch), read-only session · packets scoped by contactid = iPipeline agent id · the agency-contracts intake mirror is not used because its status field does not advance
data live (agency-wide)access: not establishednot in pilot
SureLC · licensing and contracting requests · dependency, not a feature yet
17 of 40
producers matched to your hierarchy by NPN
23
not matched · not shown · not "unlicensed"
4
matched requests at BGA stage
3
matched requests at carrier
| Producer (matched) | Licenses on file | Nearest expiry |
|---|
| D. Okafor | TX, OK, NM · Life & Health | TX · 03-31-27 |
| M. Vasiliou | FL, GA · Life | FL · 11-30-26 |
| K. Lindqvist | not matched · SureLC identity unresolved |
What blocks this panel. Brokers Alliance holds a working SureLC agency key (request stages, contracts, producers and license rows readable since 09-14-26). The join from a SureLC producer to a Team Code hierarchy is not proven: a first census on 09-14-26 matched well under half of producers by NPN and email, and SureLC's own unit is the affiliated agency, which is not the same population as your hierarchy. Until a roster reconciliation for one real BGA passes, this panel stays out of the pilot. Documents (E&O certificates, license images, W-9s) are not in the API at all.
Source SureLC REST API v2 (agency key): /appointment-requests stage PRODUCER · BGA · CARRIER · COMPLETED, /producers/licenses, /lookup/carriers · the commissions and hierarchy objects on every request row are excluded by an explicit field allowlist, not by omission
Concept screen · computed for the whole Brokers Alliance book today · never run for one hierarchy · approved for BGAs once reconciled
CONCEPT
MyAdvisorData.ai
Northline Financial Group (fictional) · trailing 12 months · as of 09-25-26 7:04 AM ET
ProductionCase deskContracting & licensingPlacement operationsAsk your assistantAccess & audit
How your submitted business moves, in operational terms
Three counts Brokers Alliance computes on its whole book every morning. For one hierarchy they are the same query with your agent list in the filter, and they have not been run that way yet. They are rates from the record with their denominators shown. They are not policy health scores, and a 40-agent book will swing month to month.
data live (whole book)access: approved once reconciledscreen: concept
Days from submit to in force
38median · on 377 cases your hierarchy placed in the trailing 12 months
P90: 71 days. Cases still open are not in this number; they are on the right.
Definition SUBMITDATE to PLACEDDATE, cases with PLACEDDATE in the trailing 12 months, the same definition Brokers Alliance uses on its own book
data live (whole book)access: approved once reconciledscreen: concept
Resolved cases that placed
68%= 412 placed ÷ (412 placed + 194 closed without placing) · cohorts submitted 12 to 36 months ago
Excludes the 118 still open. Life 66% · Annuity 84%. "Closed without placing" = Declined, Not Taken, Withdrawn, Void, Lapsed Pending.
Definition pipelineHealth.velocity pull-through, cohort window chosen so every case has had time to resolve
data live (whole book)access: approved once reconciledscreen: concept
Submitted premium on open cases aged 90+ days
$412Kon 23 of your 118 open cases · age from SUBMITDATE
Definition pipelineHealth.aging: open in-flight statuses, Shopped excluded as closed-out · this is submitted premium sitting in the pipeline, not a forecast of lost premium and not in-force exposure
out by ruling
What this page will not show
- Persistency. Brokers Alliance does not publish a persistency figure yet, because carrier in-force feeds do not cover enough of the book and lapse events reach the case system only when someone touches the case. No number here until they do.
- Policy health scores, suitability verdicts, product recommendations. The published line we do not cross (brokersalliance.com/ai/for-bga-principals, signed 09-08-26).
- Commission grids, comp, overrides, chargebacks. Grid detail stays in MyAdvisorGrids until carriers answer in writing.
- In-force values. Cash value, loans, paid-to-date do not exist in the case-management replica.
Why it is printed so nobody in a meeting can be asked for it and say yes
In the pilot today · proven with a real claude.ai account 09-25-26 10:45 PM ET · conversation below is illustrative
MyAdvisorData.ai
Connection: MyAdvisorData by Brokers Alliance · your assistant · your terms with its vendor
ProductionCase deskContracting & licensingPlacement operationsAsk your assistantAccess & audit
You bring the AI. We bring your data. We do not host the chat.
The AI layer is not a chat box we run. It is the same read-only connection, added to the Claude your office already uses. What Brokers Alliance receives is each question's request: which of the five questions, the ids in it, who asked, when. That is logged and you can read the log. Your conversation with your assistant stays with your assistant's vendor, under your terms with them.
data liveaccess approvedpilot proven · Claude
Connect in three steps
Add the connectionIn claude.ai or Claude Desktop, add Brokers Alliance as a custom connector and paste the connection address.
Sign in with your work accountGoogle Workspace or Microsoft 365. The email must be a named user on your hierarchy. Nobody shares a login.
Ask in plain EnglishFive questions today: who am I connected as, case status, open requirements, contracting progress, what has been asked.
ChatGPT: the connection speaks the same open standard and its ChatGPT sign-in address was registered on 09-25-26, but no ChatGPT account has connected yet. Say "Claude today, ChatGPT when we have proven it."
Evidence caseNerveCalls ledger, 09-25-26 10:41 to 10:45 PM ET: a claude.ai client completed sign-in and ran whoami, case_status, open_requirements and contracting_progress, all outcome ok · OAuth 2.1 with PKCE, hosted sign-in on Firebase (Google proven live; Microsoft configured and unit-tested, not yet used by a real account)
envelope = the server's real shapewording illustrative
What a session looks like · your assistant, not ours
Which of my cases are waiting on requirements older than two weeks?
Two open cases in your hierarchy have requirements requested more than 14 days ago: 60412988 (United of Omaha, insured W., paramed labs requested 09-12) and 60403316 (Transamerica, insured P., three items, oldest 09-09). source: iPipeline replica · as of 09-24-26 8:12 PM ET · completeness: requirements_found · served from snapshot
Where is K. Lindqvist's Mutual of Omaha contracting?
Packet 218841 is Pending requirements at Brokers Alliance, last touched 09-24. No carrier appointment is recorded in the replica for that carrier. source: Single Source + iPipeline replica · as of 09-25-26 7:00 PM ET · completeness: found · coverage note attached
Design rule every answer names its source, its as-of time, and one of three completeness values: found, none recorded, unknown or incomplete with a reason. A case outside your hierarchy and a nonexistent case get the identical "none recorded" answer. An empty list is never a success.
chat box: out by rulinglookup box: concept
Why there is no Brokers Alliance chat box
The signed page says "Brokers Alliance is not in the conversation." A chat window we host would put your questions on our servers and us in the middle. Two honest options were weighed:
- A · Bring your own assistant (this page). Live now with Claude.
- B · A lookup box with no AI: type a case id or policy number, get the same envelope on a screen. Buildable on the same five questions; not built; it would hold no transcript, only ids.
Natural-language search by name, phone or email stays out: it leaks across books.
Basis the access policy set 09-07 and 09-08-26 and the 09-08-26 seven-engine design review
In the pilot today · these controls run on the live connection · names below are fictional
MyAdvisorData.ai
Principal: J. Northline (fictional) · 3 named users · downline logins: off
ProductionCase deskContracting & licensingPlacement operationsAsk your assistantAccess & audit
Your hierarchy stays yours. You decide who sees it.
Permissions are enforced on the Brokers Alliance side, not by the screen and not by the assistant. A request for a broader scope is refused there, whatever asks for it. Any screen built later reads through the same scope check and the same ledger.
data liveaccess approvedby the connection · pilot proven
Named users
| User | Role | Sign-in | Status |
|---|
| J. Northline | Principal | Google Workspace | Active |
| P. Aldridge | Office · contracting | Microsoft 365 | Active |
| E. Duval | Office · case follow-up | Google Workspace | Revoked 09-19 |
Downline agent logins
Off
until the principal names them
Scope
1 hierarchy
the Team Code agent set, refreshed daily 06:30 UTC
Source caseNervePrincipals: named users per principal, one token per user hashed at rest, a single revoked flag ends every session on the next request · answers older than 48 h of ACL refresh are marked acl_stale · revocation ends future access; it cannot recall an answer already delivered
tested 09-08-26pilot proven
Fails closed, by design
- A hierarchy relationship ends, or a Team Code is retired: every answer becomes "hierarchy retired" at the next daily refresh, and the connection fails closed.
- A foreign case id and a nonexistent case id return the identical answer. The system does not confirm what exists outside your book.
- A timeout, a row cap, a source outage: the answer says unknown or incomplete with the reason. Never an empty success.
- Every SQL the server runs opens with your agent set in the filter. A projection that touches a grid or level column fails the build.
Evidence scoping test set recorded 09-08-26 (foreign id, revoked token on initialize, cap hit, retired code) · 96 automated tests on the service · Microsoft sign-in is configured and unit-tested, not yet used live
data liveaccess approvedby the connection · pilot proven
Request ledger · what has been asked
| When | User | Question | Served | Outcome |
|---|
| 09-25 6:41 PM ET | J. Northline | open_requirements · 60412988 | snapshot · 0.3 s | found |
| 09-25 6:40 PM ET | J. Northline | case_status · 60412988 | snapshot · 0.2 s | found |
| 09-25 2:02 PM ET | P. Aldridge | contracting_progress · agent 23901188 | snapshot · 0.4 s | found |
| 09-24 9:15 PM ET | P. Aldridge | case_status · 61000123 | live · 71 s | none recorded |
| 09-24 12:30 PM ET | E. Duval | initialize | n/a | rejected · revoked |
The principal sees this same ledger through the connection ("what has been asked"). Brokers Alliance holds the question class, the ids, the user, the time and the outcome. It does not hold the conversation.
Source Firestore caseNerveCalls, one row per request including rejected and unauthenticated ones, written before any byte leaves; the my_calls question reads it back per principal
Capability map · read before promising anything · verified live 09-25-26 7:45 to 10:50 PM ET
MyAdvisorData.ai
Every panel in this document traces to one cell below
What is in the pilot, what the connection answers, what is computed but unruled, what stays out
"Data we hold" and "a BGA may see it" are different questions. The columns keep them apart.
In the pilot today · proven with an outside account
- Case status by case id, or policy number + carriercase_status · claude.ai 09-25-26 10:45 PM ET
- Open requirements on a caseopen_requirements · same session
- Carrier appointments and Brokers Alliance packets per agentcontracting_progress · same session · packets carry a coverage note
- Who am I connected as; what has been askedwhoami, my_calls
- Sign in with Google; named users; downline logins off; revoke; fail closed on a retired codeMicrosoft sign-in configured, not yet used live
- Claude as the assistantChatGPT address registered 09-25-26, no account connected yet
Held per principal · no screen yet
- Open-case list, open-requirement list, appointments, packets for the hierarchycaseNerveSnapshots, warmed 06:30 UTC + every 2 h weekdays, max age 6 h
- Source, as-of, served-from and completeness on every rowthe envelope on page 3
- A screen reading it must pass the same scope check and write the same ledgerdirect reads of the document are not the product
- A no-AI lookup box (option B, page 6)concept; not built
Computed inside BA today · approved for BGAs once reconciled
- Submitted and placed counts and premium, MTD and YTD, by line, carrier, product, agent, per Team CodeCommand Center book drilldown, refreshed every 2 h · filter verified on three real hierarchies 09-25-26
- Open pipeline by iPipeline statusstatus dimension join
- Days to place, resolved-placed share, submitted premium on cases open 90+ dayspipelineHealth, whole book only; per-hierarchy not yet run
- Gate set 09-25-26: one real hierarchy reconciles to the internal view to the dollar and passes a foreign-hierarchy denial test before any principal sees a rollupthe 09-08-26 design had kept rollups out of the connection's first version
Out by ruling · or out until proven
- Commission grids, comp, overrides, chargebacks, anything moneyMyAdvisorGrids stays the grid surface
- Case notes text; search by name, phone, emailSSNs and medical; leaks across books
- Policy health scores, suitability verdicts, product recommendations; any write; alerts to downline agentsthe published line
- PersistencyBrokers Alliance does not publish its own figure yet; carrier feed coverage is the gap
- A Brokers Alliance hosted chat transcript"not in the conversation"
- Until proven: SureLC licensing and request stages per hierarchyAPI live since 09-14-26; producer-to-hierarchy join not yet proven; documents not in the API
Naming · GoDaddy availability read live 09-25-26 10:50 PM ET · nothing purchased for this document
MyAdvisorData.ai
MyAdvisorCloud is the registered mark, #7,220,484
MyAdvisor(blank): the name, what we own, what is taken
Domain facts as read on 09-25-26. Domain ownership is not trademark clearance.
Already owned by Brokers Alliance
- myadvisorcloud.com the mark · agent portal
- myadvisorgrids.com live · grids
- myadvisordata.com + myadvisordata.ai the brand · the .com reserved in 2025 for agency data delivery, the .ai added 09-25-26
- myadvisorbrain.com registered 09-25-26 5:46 PM ET
- myadvisorcrm.com / .ai, contracts, contracting, commissions, leads, metrics, suite, online held
Set 09-25-26: MyAdvisorData.ai is the brand for everything a BGA principal gets from Brokers Alliance about their own data: the read-only connection (internal codename Case Nerve, never a customer-facing name) and this screen. It says what it is, your data, and the .ai says AI-ready without claiming a Brokers Alliance AI. The brand was reserved in 2025 for exactly this, agency data delivery. Still owed: trademark review, a Cloudflare zone for the .ai, and the connection hostname (for example connect.myadvisordata.ai). "Brain" stays with RetirementBrain, LifeBrain and CRMBrain.
Taken by others
- myadvisorai.com
- myadvisor.ai
- myadvisorbook.com
- myadvisorhub.com
- myadvisordesk.com
- myadvisorinsights.com
- myadvisorcenter.com, myadvisorone.com, myadvisorx.com
Any name that needs the .ai ending or the plain "AI" suffix is gone. The open field is a noun after MyAdvisor.
Available · $12.99 first year each
- MyAdvisorNerve.com considered · pairs with the internal codename
- MyAdvisorPulse.com · MyAdvisorLens.com · MyAdvisorSignal.com
- MyAdvisorCommand.com · MyAdvisorIntel.com · MyAdvisorIQ.com
- MyAdvisorMind.com · MyAdvisorCortex.com · MyAdvisorSynapse.com
- MyAdvisorCompass.com · MyAdvisorRadar.com · MyAdvisorScope.com
- also open: core, copilot, sight, sense, vision, nexus, neural, matrix, live, hq, edge, genius, gpt, pilot, ops, orbit, prism, atlas, beacon, canvas, studio (.com)
Also open in .ai at $419.96: myadvisornerve.ai, myadvisorcloud.ai, myadvisorbook.ai. myadvisorai.io is open at $59.99.
From connection to screen · what would have to be true, in order
MyAdvisorData.ai
Nothing on this page is a date or a commitment
If a BGA says yes, this is the honest path
The server, the scoping, the sign-in and the audit exist. What does not exist is a screen, and two decisions have not been made. The order below keeps every step provable before the next one is promised.
Now · the connection
Team Code from contracting, principal name and email, Claude, one acknowledgment sentence. Brokers Alliance turns the hierarchy on in a day. A recorded 30-minute session against the BGA's own data is the demo and the test. No screen needed.
Gate · rollups for BGAs
Approved 09-25-26 on condition: the internal book drilldown, behind the connection's sign-in and scope check, reconciled to the internal view to the dollar for one real hierarchy and tested against a foreign hierarchy before any principal sees it (pages 2 and 5).
Screen · case desk and contracting
A page over the per-principal snapshot, read through the same scope check and ledger as the connection, with the completeness envelope on every row. Tested with a revoked user, a foreign case, a stale snapshot and a source outage before release.
Later · SureLC and the front door
Licensing after a roster reconciliation for one real BGA passes. Connection hostname on myadvisordata.ai. Delivered as a MyAdvisorCloud tile or a whitelabeled agency site, both of which exist as mechanisms today.
Decisions this document waits on
- Rollups for BGAs: approved 09-25-26, gated on the to-the-dollar reconcile.
- Name: MyAdvisorData.ai, set 09-25-26 (owned); trademark review still owed.
- Audience: open. This concept may be shared freely; the connection pilot itself stays by invitation.
What stays true at every step
Read-only. One hierarchy. Named users. Every request logged. Access revocable on the next request. Each answer carries its source and as-of time. Grids and case changes stay out until carriers and the case-management platform answer in writing. A named person at Brokers Alliance signs the regulated content.
What to say, and not say, in the room
Say: we run our own operation on AI you can check; your hierarchy stays yours; you bring the assistant, we bring your data. Say "Claude today." Do not say first, only, fastest or "the AI-enabled BGA"; do not name competitors as unable; do not quote counts. When asked "is this live," point to the band at the top of the page and the three labels on the panel.