verification/data-map.md

GameTide: data map

How the GameTide data connects: the systems, the shared keys that join them, the business flows that run through them, the tie-outs that prove they agree, and where every assumption and monthly note lives. The diagrams are written in Mermaid, a plain-text diagram format: GitHub draws them on this page, and Miro imports them (Insert, Diagram, Mermaid), so each diagram can become a frame on a Miro board (Miro may not draw the timeline in section 2; its table carries the same dates). The last section lays out the board.

1. The big picture

One engine builds one internal model of the company. Each system's files are an export view of that model, in that system's own field names and IDs. The warehouse adds the crosswalks and the answer key. Everything is checked every month before it is written to the release.

flowchart LR
    S["Settings and assumptions<br/>config/settings.yaml<br/>docs/assumptions.md"] --> E["GameTide engine<br/>one deterministic run<br/>Jan 2020 to Dec 2029"]
    E --> M["Internal model<br/>customers, contracts, people,<br/>ledger, cash, events"]
    M --> X["System exports<br/>24 folders, one per system,<br/>each in its own field names"]
    M --> W["Warehouse<br/>dimensions, crosswalks,<br/>ARR bridges, answer key"]
    X --> C{"Acceptance checks<br/>every month"}
    W --> C
    C -->|all pass| R["Release<br/>120 monthly folders,<br/>SQLite, Parquet"]
    M --> N["Month in review notes<br/>and events table"]
    N --> V["Verification package<br/>assumptions, policies, story bible,<br/>data dictionary, answer key, test report"]
    R --> V

2. When each system starts

A system's folder appears in the month GameTide adopts it (assumption S). Before Sage Intacct (January 2023) the books are in QuickBooks Online; the conversion journal and crosswalks join the two.

timeline
    title System adoption (folder name)
    2020 : accounting_qbo, bank, cloud_costs (Jan) : hr, payroll, equity (Mar) : engineering_time, crm (Jul)
    2021 : payments (Jan) : support (Mar) : product_usage (Jul)
    2022 : marketing, web_analytics, ads, commissions, sales_tax, recruiting (Jan)
    2023 : accounting (Sage Intacct), planning, customer_success, implementation, inventory (Jan) : software_spend (Jul)

System	Folder	Layout of	From
CRM, quotes and support cases	crm, support	Salesforce Sales Cloud and Service Cloud	July 2020 (support March 2021)
Marketing automation	marketing	Salesforce Account Engagement	January 2022
Website analytics	web_analytics	Google Analytics 4	January 2022
Ad platforms	ads	Google Ads, Meta Ads, LinkedIn Ads	January 2022
Commissions	commissions	CaptivateIQ	January 2022
Accounting	accounting_qbo, then accounting	QuickBooks Online to December 2022, then Sage Intacct	January 2020, January 2023
Payments	payments	Stripe	January 2021
Sales tax	sales_tax	Avalara	January 2022
Bank and lender	bank	A commercial bank portal and lender statement	January 2020
Planning	planning	Anaplan	January 2023
Equity	equity	Carta	March 2020
HR and payroll	hr, payroll	Rippling	March 2020
Recruiting	recruiting	Greenhouse	January 2022
Product usage	product_usage	Amplitude	July 2021
Customer success	customer_success	Gainsight	January 2023
Implementation	implementation	Kantata	January 2023
Engineering time	engineering_time	Jira with Tempo	July 2020
Cloud costs	cloud_costs	AWS Cost and Usage Report	January 2020
Hardware inventory	inventory	Sage Intacct inventory	January 2023
Software and AI spend	software_spend	Zylo	July 2023
Warehouse	warehouse	Built by the engine (no vendor)	January 2020

Product names describe the layout of the files only. GameTide is not affiliated with these companies.

3. The shared keys

Each system issues its own IDs. The warehouse crosswalks map every one of them to one master key, so any two systems can be joined. Every file also carries the record's name next to its ID, so a single file can be read without a join.

flowchart LR
    CK(("customer_key<br/>GT-C-000123"))
    CK --- SF["Salesforce Account Id<br/>001..."]
    CK --- IC["Intacct CUSTOMERID<br/>C-10123"]
    CK --- QC["QuickBooks customer Id<br/>to Dec 2022"]
    CK --- ST["Stripe customer<br/>cus_..."]
    CK --- AV["Avalara customerCode"]
    CK --- GS["Gainsight GS ID"]
    CK --- AM["Amplitude account_id"]

    EK(("employee_key<br/>GT-E-0042"))
    EK --- RW["Rippling worker id"]
    EK --- IE["Intacct EMPLOYEEID"]
    EK --- SU["Salesforce User Id<br/>005..."]
    EK --- CQ["CaptivateIQ employee"]
    EK --- CA["Carta Employee ID"]
    EK --- TE["Tempo author"]
    EK --- KU["Kantata user_id"]
    EK --- GH["Greenhouse application"]

    PK(("product_key<br/>GT-TIER-PRO"))
    PK --- P2["Salesforce Product2 Id"]
    PK --- IT["Intacct ITEMID"]

    DK(("department_code<br/>16 codes"))
    DK --- ID["Intacct DEPARTMENTID"]
    DK --- QB["QuickBooks class"]
    DK --- RD["Rippling department"]
    DK --- AN["Anaplan Departments"]

    AK(("ACCOUNTNO<br/>Intacct GL account"))
    AK --- QA["QuickBooks account<br/>crosswalk_gl_account"]
    AK --- AA["Anaplan Accounts"]

Entity	Master key	Crosswalk file
Customer	customer_key	warehouse_crosswalk_customer
Employee	employee_key	warehouse_crosswalk_employee
Product	product_key	warehouse_crosswalk_product
Department and cost center	department_code	warehouse_crosswalk_department
GL account	ACCOUNTNO	warehouse_crosswalk_gl_account
Vendor	Intacct VENDORID	warehouse_crosswalk_vendor
Contract line	Salesforce ContractLineItem Id	referenced by ARR movements and revenue recognition lines

4. Quote to cash: a customer's journey

flowchart LR
    AD["Ads<br/>spend, clicks"] --> WEB["Website<br/>sessions, form fills"]
    WEB --> MA["Marketing automation<br/>prospect, score"]
    MA --> LD["CRM lead"]
    LD --> OP["CRM opportunity<br/>stages, history"]
    OP -->|won| SC["Service contract<br/>and contract lines"]
    OP --> CM["Commissions<br/>per rep per deal"]
    SC --> INV["Invoice<br/>QuickBooks or Intacct"]
    INV --> TX["Sales tax<br/>Avalara"]
    INV --> PAY["Payment<br/>Stripe or bank"]
    PAY --> BK["Bank<br/>deposits, reconciliation"]
    INV --> DR["Deferred revenue"]
    DR --> RV["Recognized revenue<br/>GL"]
    SC --> ARR["Warehouse ARR<br/>by customer and by product"]
    SC --> IMP["Implementation project<br/>Kantata hours"]
    IMP --> RV

5. Why customers stay or leave

Causes drive outcomes: churn follows low usage and support pain; expansion follows seat growth.

flowchart LR
    US["Product usage<br/>active users, sessions"] --> HS["Customer success<br/>health score"]
    SP["Support cases<br/>volume, SLA"] --> HS
    PM["Payments<br/>late or failed"] --> HS
    HS -->|at risk| CTA["Call to action<br/>for the CSM"]
    HS --> RN{"Renewal"}
    RN -->|healthy| EX["Expansion<br/>seats, modules, tier"]
    RN -->|low usage, support pain| CH["Contraction or churn"]
    EX --> ARR["ARR movements"]
    CH --> ARR

6. People and cost

flowchart LR
    PL["Planning<br/>headcount plan"] --> RQ["Recruiting<br/>jobs, openings, offers"]
    RQ --> HR["HR<br/>workers, compensation"]
    HR --> PR["Payroll<br/>biweekly register"]
    PR --> GL["General ledger<br/>salaries, taxes, benefits"]
    HR --> EQ["Equity<br/>grants, vesting"]
    EQ -->|stock-based compensation| GL
    HR --> JT["Engineering time<br/>Jira and Tempo"]
    JT -->|capitalized software| GL
    CL["Cloud costs<br/>AWS"] --> GL
    SW["Software and AI spend<br/>Zylo"] --> GL
    VN["Vendors and bills"] --> GL
    GL --> TB["Trial balance"]
    PL -->|plan versus actual| TB

7. The tie-outs

Every month, these checks must pass before the month is written to the release. The full list with each month's result is in warehouse_test_results.

What ties	To what	Checks
Trial balance	Debits equal credits; balances roll month to month; equals GL detail	TB-01 to TB-05, QBO-01
ARR bridge	Opening plus movements equals closing for every customer; equals CRM contract lines, account ARR and the GL statistical account	ARR-01 to ARR-05
ARR by product	Foots by product; sums to the customer bridge column by column; swaps net to zero; equals CRM lines by product	ARR-06 to ARR-09
Deferred revenue and revenue	Rolls forward; recognized revenue equals the schedules	DR-01, DR-02, AK-02, AK-03
Accounts receivable	Rolls forward; rebuilt invoice by invoice; aging adds up	AR-01 to AR-03, AK-01, QBO-03
Cash	Stripe charges, payouts and fees equal the GL; bank reconciles to GL cash	CASH-01 to CASH-04, BANK-01 to BANK-03
Payroll	Register equals GL salaries, net pay, commissions, bonuses and severance	PAY-01 to PAY-07
Commissions	Payouts equal payroll; accruals and clawbacks equal the GL; accelerator follows attainment	COM-01 to COM-04
Sales tax	Tax on invoices equals the GL; rate times base; liability report; certificates	TAX-01 to TAX-05
Marketing	Ad spend equals bills; campaign costs and influence add up	ADS-01, ADS-02, CMP-01 to CMP-03, WEB-01, WEB-02
Operations	Implementation, analyst and installation revenue rebuilt from hours; capitalized labor from Tempo; SBC from Carta; cloud cost from AWS; inventory valuation	IMP-01 to IMP-03, ENG-01, EQ-01, CLD-01, INV-01 to INV-04
Customer health and usage	Health score components; Gainsight ARR equals CRM; usage within licensed seats	CS-01 to CS-03, USE-01 to USE-03, SUP-01, SUP-02
Keys	Every fact row keys to its dimensions and systems	KEY-01 to KEY-07, EQ-02, ENG-02, REC-02, PLAN-01
Answer key	Snapshots and metrics equal the source files; the allowance equals the G10 rates times the aging	AK-04 to AK-09
Story targets	Each year-end lands within tolerance of the lifecycle model, gross margin included; December health ranks the next year's churn against each segment's rate	ANN-ARR, ANN-CUST, ANN-HC, ANN-REV, ANN-OM, ANN-GM, ANN-K4
Accounting registers	Open AR invoices equal 1100; unpaid bills equal 2010; asset cost and depreciation equal their accounts; prepaids equal 1300; open accruals equal 2020; the lease schedule equals 1700, 2400 and 2410; the revenue schedule equals the recognition journal and 2200	AR-04, AR-05, AP-01, AP-02, FA-01, FA-02, PP-01, ACR-01, LEASE-01, REV-01, REV-02
Contacts, activity, quotes and forecasts	Every link resolves; accepted quotes equal the deal's products; forecast categories nest and closed ties to won deals	KEY-08, KEY-09, QUO-01, FC-01, FC-02
Active users, survey and cohorts	DAU within WAU within MAU, month-end MAU equals monthly uniques; survey invitations equal active workers; cohort counts consistent	USE-04, ENG-01, COH-01
Layout	Every file keeps the same columns in every month	COL-01

8. Where everything is documented

Nothing the engine uses is hidden. Each item below ships in the verification package with the data.

What	Where	What it holds
Assumptions	docs/assumptions.md and config/settings.yaml	Every number the engine uses, with its ID, value, reason, source and check. The settings file is the one the engine reads.
Policies	docs/policies.md	ARR bridge categories, ARR by product, revenue recognition and every metric definition
Story bible	docs/story-bible.md	What happens each year and where each planted event shows in the data
Monthly notes	month_in_review_YYYY-MM-DD.md in every month folder	ARR, ARR movements, ARR by product type, customers, revenue, cash, close date, headcount, deals, the month's events and where to look
Events table	warehouse/warehouse_events	Every planted event, system adoption, pattern and minor event, with its date, cause, the record it touches (ID and name) and its expected effect
Data dictionary	docs/data-dictionary.md	Every file: what one row means, its key, columns, links and tie-outs
Metric definitions	warehouse/warehouse_metric_definitions	Each published metric, its unit, definition and source tables
Answer key	warehouse answer-key tables and reports/answer-key-2020-2029.md	Expected values of the headline metrics for every month
Test report	warehouse/warehouse_test_results and reports/full-run-2020-2029.md	Every check, every month, expected and actual
Decisions	docs/decisions-log.md	Every decision after the baseline, with who made it

9. Laying out the Miro board

One frame per section, left to right in two rows:

Row	Frames
Top	1. The big picture; 2. When each system starts; 3. The shared keys
Bottom	4. Quote to cash; 5. Why customers stay or leave; 6. People and cost
Side	7. The tie-outs (as a table); 8. Where everything is documented (as a table)

To build it by hand: in Miro, add a frame, choose Insert, Diagram, Mermaid, and paste one diagram's text (the lines between the fences, without the word mermaid). Tables paste into a Miro table from this page.