landing

Who it is for

DesignSystem — an honestly-declared PLANNED product-domain stub (owner founder, T2): a declaration, not a live domain. domains/design-system.xml:6-6

Reaves Labs Site — the site anatomy node; every page is a projection FROM it, never edited directly. domains/reaveslabs-site.xml:9-9

Lives in ~/RLL, git-tracked, brain-indexed; the pattern repeats for every product and system node. domains/reaveslabs-site.xml:16-16

GTM Model — a revenue domain node; decks, PRD sections, CRM seeds, and outreach templates project FROM it. domains/gtm-model.xml:12-12

ESSA Tier 4 (paid research institution) + FERPA/COPPA + per-state student-data-privacy agreements. Starts NOW; contract signs day-1 of funding. domains/gtm-model.xml:55-55

Who it is for for Landing page. Customer ask centers on a Landing page for GCBC. Promise and proof on the web. You get: A page a stranger gets. Raw ask: Build a Landing page for GCBC.

Detail for Who it is for: this Landing page stays locked to a Landing page. 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 Landing page appears in the working lines, not only the title.

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

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

Message & promise

Your company, compiled. Ask it anything and get the line the answer came from. domains/reaveslabs-site.xml:36-36

Reaves Labs & Learning builds products people learn with, tools we build and run, and engagements you can hire us for — across Education, Finance, AI & Engineering, and Life Skills. domains/reaveslabs-site.xml:37-37

Our franchise product is the Genesis Company Brain Compiler. Everything else here is either built with it or waiting behind it. domains/reaveslabs-site.xml:38-38

Deterministic AI. We use the components that make modern AI work — retrieval, structure, learned representations — without the sampled step that guesses. Every answer is computed and cites its source; every build is a compile, not a generation. domains/reaveslabs-site.xml:39-39

Two tracks, one adventure: Math (the prerequisite) unlocks Financial Literacy. 72 free modules, K-12, mastery proven not assumed. domains/reaveslabs-site.xml:74-74

Message & promise for Landing page. Customer ask centers on a Landing page for GCBC. Promise and proof on the web. You get: A page a stranger gets. Raw ask: Build a Landing page for GCBC.

Detail for Message & promise: this Landing page stays locked to a Landing page. 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 Landing page appears in the working lines, not only the title.

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

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

Channel & proof

Every answer names the file and line it came from; every refusal names the contract line that broke. It is a property of the architecture, so it cannot regress, and a sampled model can never offer it about itself. domains/reaveslabs-site.xml:41-41

Answers are retrieval plus verbatim citation — no inference cost and nothing to hallucinate. As token economics tighten, an answer that costs nothing to generate and cannot be invented is a lasting cost and trust advantage. domains/reaveslabs-site.xml:42-42

The frontier trades legibility for capability. We compose deterministic transforms, each inspectable, so governance and compliance are satisfied by showing the work — a requirement that only grows. domains/reaveslabs-site.xml:43-43

GCBC compiles a company's declared knowledge into its own source of truth. The value is their data, structured — data gravity and switching cost that deepen with use and cannot be reproduced by a general model. domains/reaveslabs-site.xml:44-44

Any model or computer-use agent is an optional, gated effector downstream of the contract, never on the provable path. Every frontier gain — cheaper tokens, better hands, native multimodality — plugs in as an upgrade without touching the deterministic core, so model churn never destabilises us. domains/reaveslabs-site.xml:45-45

Channel & proof for Landing page. Customer ask centers on a Landing page for GCBC. Promise and proof on the web. You get: A page a stranger gets. Raw ask: Build a Landing page for GCBC.

Detail for Channel & proof: this Landing page stays locked to a Landing page. 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 Landing page appears in the working lines, not only the title.

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

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

Cadence

2-3 tailored district emails/day once outreach opens (one district, one custom email); log every touch in the CRM node. domains/gtm-model.xml:73-73

Daily demo pass: run the full 9-12 flow start-to-finish, fix the worst break found, re-run. Stop only when two consecutive clean runs. domains/gtm-model.xml:74-74

One deck section to final per day until pitch-ready; the ask stays on ONE slide. domains/gtm-model.xml:75-75

End of each week: gauge vs facts — anything slipping gets named, not absorbed. domains/gtm-model.xml:78-78

A: deck final for Kevin+Jennifer (whole company: RA numbers + 3 sibling apps + 5yr roadmap; the ask on ONE slide). A: LLC-structure answer crisp. B: lock Cluster-A district list + verify decision-maker names. C: shortlist Tier-4 research institutions, draft scope. D: write both job specs, start sourcing. domains/gtm-model.xml:83-83

Cadence for Landing page. Customer ask centers on a Landing page for GCBC. Promise and proof on the web. You get: A page a stranger gets. Raw ask: Build a Landing page for GCBC.

Detail for Cadence: this Landing page stays locked to a Landing page. 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 Landing page appears in the working lines, not only the title.

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

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

Guardrails

Declared in the manifest as status="planned"; no live spec/state yet (honest, not a dangling ref). domains/design-system.xml:66-66

D58 measurement integrity: reported as planned, never asserted active; the denylist forbids claiming the domain operates before it is built. domains/design-system.xml:15-15

If any surface or report treats this domain as operating, flag it as a violation. If ownership of the informal duty becomes ambiguous, escalate; if authority is uncertain, route to the founder queue (D57). domains/design-system.xml:16-16

Stages are stated honestly: in development means in development. GCBC is the only product available today; nothing else on this page is for sale or claims an outcome yet. domains/reaveslabs-site.xml:274-274

verify-projection.mjs renders index.html and proves every declared section present and no undeclared top-level section[id]; product stages stay honest (demo vs coming-soon); undeclared third-party origins fail the gate. domains/reaveslabs-site.xml:18-18

Guardrails for Landing page. Customer ask centers on a Landing page for GCBC. Promise and proof on the web. You get: A page a stranger gets. Raw ask: Build a Landing page for GCBC.

Detail for Guardrails: this Landing page stays locked to a Landing page. 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 Landing page appears in the working lines, not only the title.

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

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

Bound to your ask

Founder decides whether to activate this domain or keep brand/UI inside product surfaces. domains/design-system.xml:78-78

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

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

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

Bound to your ask for Landing page. Customer ask centers on a Landing page for GCBC. Promise and proof on the web. You get: A page a stranger gets. Raw ask: Build a Landing page for GCBC.

Detail for Bound to your ask: this Landing page stays locked to a Landing page. 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 Landing page 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 Landing page for GCBC.”). Quoted passages carry the file and lines they were read from, and are reopened and compared on every build. If a Landing page 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 Landing page — who does what, by when, and what “done” looks like for this Landing page. Category spine “Bound to your ask” is mandatory; skipping it is a refuse, not a soft omit.