Finance OS
Foundation phase

Gravity Finance OS

Standalone close workspace for publisher economics, source reconciliation, contract terms, credits, and audit-ready finance operations.

Publisher spend
$482.6K

Nov-Apr discovery scope

Event-level verification required
House spend
$344.3K

Classified from discovery rules

Classifier basis tracked
Credit-funded spend
$47.3K

Needs grant-class waterfall

Policy split required
Paid-brand spend
$91.0K

Stripe-backed operating view

Stripe/QBO reconciliation lane
Month-close operating path
First build establishes the primitives, then calculations can be layered on safely.
1
Source sync health
2
Entity alias review
3
Contract term approval
4
Event-level spend verification
5
Credit funding waterfall
6
Publisher calculation run
7
Cash and QBO reconciliation
8
Exception review and close lock
Readiness
7 of 8 sources have configured credentials or validated discovery data.

Stripe

Operational advertiser billing/payment objects

Configured

QuickBooks sandbox

Sandbox accounting, customers, vendors, and chart of accounts

Configured

Google Drive

Publisher agreement folder inventory and text extraction

Configured

Plaid sandbox

Bank transaction integration development lane

Missing

Rho CSV

Manual cash transaction CSV fallback import

Configured

Finance Supabase

Dedicated Finance OS raw records, entity review, audit events, exceptions, and close state

Configured

Gravity prod database

Canonical entities, credits, billing state, and event-level spend joins

Configured

Redshift

Historical event-level spend verification

Configured
Foundation scope
This PR intentionally builds the safe substrate before calculations or source-system mutations.
PrimitivePurposeIncluded now
Source sync runsTrack read-only ingestion attempts, cursors, row counts, freshness, and failures
Yes
Raw source recordsImmutable payload/hash store for Stripe, QBO, Gravity, Drive, Rho/Plaid
SQL blueprint
Finance entitiesCanonical finance identity layer independent of source naming
SQL blueprint
Alias approvalsHuman-reviewed mapping from Rho/Drive/XLSX/QBO/Stripe/Gravity
SQL blueprint
Audit eventsRecord every future override, approval, calculation rerun, and close lock
SQL blueprint
Source-first

Every source record gets a run ID, hash, cursor, and source trace before it can affect finance outputs.

Audit-ready

Aliases, overrides, contract approvals, and close locks are explicit finance events, never silent mutations.

Accounting-aware

Stripe, QBO, Rho/Plaid, credits, and Gravity spend each have clearly separated source-authority roles.