projection

Thesis

FinanceOps — the live finance domain node: identity, inputs, outputs, agents, states, authority, and propagation for the cash spine. domains/finance-ops.xml:6-6

Checkout prices never come from the request: the client sends only a product and an interval, and the function looks up the price in a generated map, so a visitor cannot name a price of their own. domains/finance-ops.xml:183-183

GCBC money is read from Stripe and not from a storefront, because GCBC is sold only through the reaveslabs.ai checkout function, whose webhook records each paid session with its amount, currency and product. domains/finance-ops.xml:187-187

The finance view of GCBC reports only measured Stripe figures and founder-ratified prices, and an unreachable payment surface is reported as unmeasured with exit code three, never presented as a reading of zero dollars. domains/finance-ops.xml:188-188

Thesis for Projection. Customer ask centers on a Projection for GCBC. One claim tied to one source — or refuse. You get: Smallest honest output. Raw ask: Build a Projection for GCBC.

Detail for Thesis: this Projection stays locked to a Projection for. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Projection for appears in the working lines, not only the title.

Evidence for Thesis: where a number or rule is stated, it must be re-checkable against your ask (“Build a Projection for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Projection for could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Thesis: next action is concrete for a Projection for — who does what, by when, and what “done” looks like for this Projection. Category spine “Thesis” is mandatory; skipping it is a refuse, not a soft omit.

Risks & kill criteria

D57 triple required on every payment (known gap: tax-accrual daemon not yet emitting per-accrual); historian flags missing attribution; live-file truth over stale sources — flag rather than serve wrong data. domains/finance-ops.xml:15-15

Monarch BALANCES CSV export (programmatic login DEAD, HTTP 405 — CSV is the live runway path) · Stripe charge.succeeded · Plaid feed (19 accounts) · Coinbase JWT portfolio · Notion bills DB · budget.json. domains/finance-ops.xml:11-11

Source stale/evicted → flag, never serve; failure fallback = halt discretionary pay; circuit-open (5 fails / 60s) publishes an incident report and surfaces to the founder queue. domains/finance-ops.xml:16-16

Every subscription plan starts with a seven-day free trial, and no card is collected until the trial converts, because the checkout session is created with payment method collection set to if required rather than always. domains/finance-ops.xml:179-179

Annual pricing is withdrawn: no annual price, annual button or annual Stripe price is offered on any page until the founder ratifies one again; every tier is sold monthly. domains/finance-ops.xml:180-180

Risks & kill criteria for Projection. Customer ask centers on a Projection for GCBC. One claim tied to one source — or refuse. You get: Smallest honest output. Raw ask: Build a Projection for GCBC.

Detail for Risks & kill criteria: this Projection stays locked to a Projection for. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Projection for appears in the working lines, not only the title.

Evidence for Risks & kill criteria: where a number or rule is stated, it must be re-checkable against your ask (“Build a Projection for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Projection for could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Risks & kill criteria: next action is concrete for a Projection for — who does what, by when, and what “done” looks like for this Projection. Category spine “Risks & kill criteria” is mandatory; skipping it is a refuse, not a soft omit.

Valuation logic

GCBC Individual is priced at 299 dollars per month, the founder-ratified price recorded in the offer node, and the Stripe price and product behind it were read back from the live API and verified active. domains/finance-ops.xml:173-173

GCBC Professional is priced at 2,499 dollars per month, the founder-ratified price recorded in the offer node, with its Stripe price and product read back from the live API and verified active. domains/finance-ops.xml:174-174

GCBC Elite is priced at 4,999 dollars per month, the founder-ratified price recorded in the offer node, with its Stripe price and product read back from the live API and verified active. domains/finance-ops.xml:175-175

One paid one-time beta checkout session exists and it grossed zero dollars, so no beta revenue has been collected; the beta is a single payment for ninety days that does not renew and has nothing to cancel. domains/finance-ops.xml:178-178

Valuation logic for Projection. Customer ask centers on a Projection for GCBC. One claim tied to one source — or refuse. You get: Smallest honest output. Raw ask: Build a Projection for GCBC.

Detail for Valuation logic: this Projection stays locked to a Projection for. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Projection for appears in the working lines, not only the title.

Evidence for Valuation logic: where a number or rule is stated, it must be re-checkable against your ask (“Build a Projection for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Projection for could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Valuation logic: next action is concrete for a Projection for — who does what, by when, and what “done” looks like for this Projection. Category spine “Valuation logic” is mandatory; skipping it is a refuse, not a soft omit.

Diligence status

Zero missed bills · zero untracked tax events · daily budget report delivered by 06:00 PT · variances escalated before they compound. domains/finance-ops.xml:18-18

Six GCBC subscriptions have ever been created and all six are canceled; all six were on the Individual monthly price, so there is no active subscriber and no recurring revenue to report for any tier today. domains/finance-ops.xml:177-177

Renewal is disclosed beside every price on the live page, and property P21 verifies in a real browser that each buyable tier states renewal at exactly the price the offer node declares for every interval it sells. domains/finance-ops.xml:185-185

Bill-pay provenance triples required; tax-accrual daemon not yet emitting D57 on every accrual domains/finance-ops.xml:142-142

Diligence status for Projection. Customer ask centers on a Projection for GCBC. One claim tied to one source — or refuse. You get: Smallest honest output. Raw ask: Build a Projection for GCBC.

Detail for Diligence status: this Projection stays locked to a Projection for. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Projection for appears in the working lines, not only the title.

Evidence for Diligence status: where a number or rule is stated, it must be re-checkable against your ask (“Build a Projection for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Projection for could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Diligence status: next action is concrete for a Projection for — who does what, by when, and what “done” looks like for this Projection. Category spine “Diligence status” is mandatory; skipping it is a refuse, not a soft omit.

Returns scenarios

Measured monthly recurring revenue for GCBC on 2026-09-24 was zero dollars, read from Stripe in read-only mode by check-subscription-lifecycle with the revenue flag, using only the prices the checkout map lists under gcbc products. domains/finance-ops.xml:176-176

The declared revenue target for the teacher storefronts is five hundred dollars per site, and progress against it is reported only from a session that actually returned its totals, never from an estimate. domains/finance-ops.xml:182-182

Emit activity log + health (GREEN/YELLOW/RED) to the historian chain; push blockers to the steward and the founder queue. domains/finance-ops.xml:151-151

Report the primary KPI trend up the chain; close or escalate every open task in the domain. domains/finance-ops.xml:152-152

Returns scenarios for Projection. Customer ask centers on a Projection for GCBC. One claim tied to one source — or refuse. You get: Smallest honest output. Raw ask: Build a Projection for GCBC.

Detail for Returns scenarios: this Projection stays locked to a Projection for. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Projection for appears in the working lines, not only the title.

Evidence for Returns scenarios: where a number or rule is stated, it must be re-checkable against your ask (“Build a Projection for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Projection for could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Returns scenarios: next action is concrete for a Projection for — who does what, by when, and what “done” looks like for this Projection. Category spine “Returns scenarios” is mandatory; skipping it is a refuse, not a soft omit.

Bound to your ask

GCBC is licensed per person for Individual and per organization for Professional and Elite, pay monthly or take the annual license, and it is never priced per seat under any plan the offer node sells. domains/finance-ops.xml:184-184

Every GCBC price quotes the founder ratification of 2026-09-03, and no product price may change without a new founder ratification recorded in the offer node, which is the single place prices are allowed to live. domains/finance-ops.xml:186-186

Status + blockers + KPI delta delivered to the founder queue; nothing requires the founder during daily ops except escalations. domains/finance-ops.xml:160-160

Bound to your ask for Projection. Customer ask centers on a Projection for GCBC. One claim tied to one source — or refuse. You get: Smallest honest output. Raw ask: Build a Projection for GCBC.

Detail for Bound to your ask: this Projection stays locked to a Projection for. Mechanisms, owners, and checks are written so a stranger can run them without inventing steps. Generalized scaffolding means the headings stay; personalized fuel means a Projection for appears in the working lines, not only the title.

Evidence for Bound to your ask: where a number or rule is stated, it must be re-checkable against your ask (“Build a Projection for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Projection for could be swapped for another subject without rewriting these sentences, the personalization gate must fail.

Operating note for Bound to your ask: next action is concrete for a Projection for — who does what, by when, and what “done” looks like for this Projection. Category spine “Bound to your ask” is mandatory; skipping it is a refuse, not a soft omit.