Genesis Company Brain Compiler

How it works

Press play to see how it works, then read the promise.

How GCBC works — click play

Transcript: what the film says, scene by scene

AI tools hand you answers with no source, no date, and no way to know if the ground moved under them. A source changes, a claim goes stale, and nobody notices until a customer, an auditor or a regulator does.
GCBC is the provenance layer. It sits under any model and proves where every answer comes from: cited, contradicted, or no source.
It is for anyone who has to stand behind what they ship. For example: the solo operator with messy files who wants to sell something real, the business that needs audit built in, and the investor or team that needs a citation behind every line.
Here are two ways to use it.
First, GCBC on its own. No AI model, no developer, just your files.
Download GCBC, drag it into Applications and open it. A welcome page opens in your browser, served by GCBC on your own computer.
Paste the license key from your email and click Activate. Then answer eight short questions about your company.
Click Add documents and choose your company’s folder. Here it is Larkspur Dental, a practice GCBC has never seen. GCBC reads every file in that folder.
Ask a question in plain words. The answer is the passage from your own file, quoted word for word, with the file name and the line numbers.
Ask something your files do not cover, and GCBC says so plainly instead of guessing.
Build a document, such as a sales proposal, from what your files say. You describe it in your own words.
Every passage the proposal uses carries its file and lines, so anyone can check it.
Every question, build and refusal is written to an audit trail on your computer. Each entry is chained to the one before it, so any edit shows.
Now the second way: GCBC connected to the AI app you already use, such as Claude Desktop or Cursor.
Run one command in GCBC’s folder. It prints a short entry. Paste it once into your AI app’s settings. It holds no password and no key.
Your AI app now has GCBC’s tools. The one that matters here is verify_answer: it checks every sentence of an answer against your files.
Claude answers a question about Larkspur. GCBC checks it: this sentence is right, so it comes back cited, with the file and the line.
Here Claude got the number wrong. GCBC marks it contradicted and shows the line that holds the real figure: 35 dollars, not 25.
Here Claude made something up. GCBC finds nothing in your files that says it, and says so.
Both ways, every answer points to its source or says it can’t.
Build any of 60 kinds of deliverable from your own material, each one cited. GCBC re-checks your sources on a schedule and shows what changed; nothing in your library changes without your click. Your documents stay on your computer.
Start with the 90-day Beta for 99 dollars. Individual is 299 dollars a month for up to 3 users on your own documents. Professional adds 25 users and the vetted 18-domain library; Elite adds unlimited users and the investor pack.
GCBC. Ship with proof that what left your door is still true.

How it works, and why you can check it

Five drawings from the filing, in plain language. Each one is a promise you can test against your own material.

Show the five drawings that explain the outcome

One way in

However you ask — typing a request or handing over documents — everything passes the same checkpoint. There is no side door and no shortcut.

It reads, it does not invent

The only part that could make something up is walled off to understanding your material. What you receive is built by rules, not guessed.

Nothing is built until it is understood

A request is accepted only when it is both complete and clear. If it is neither, you get a refusal naming what was missing, not a plausible guess.

It knows what complete looks like

Your documents are measured against a standard that was written down in advance, so it can show you what a full company should have and what yours is missing.

Your data stays yours

The licensed copy runs on your machine, and the engine underneath can be swapped without losing a single one of these guarantees — no cloud dependency, no lock-in. Hosted Command at gcbc.reaveslabs.ai is the same compiler in a workspace we run for you.

Get in

Ninety days. Ninety-nine dollars. Or try Mini free.

How your material gets in

The app does all of this with buttons. If you prefer Terminal, run these three commands in GCBC’s folder (cd /Applications/GCBC.app/Contents/Resources). Your documents stay on your machine — there is nothing to upload and no account to make.

Show how your material gets in

./runtime/darwin-arm64/bin/node gcbc.mjs activate <your license key>The license key from your email. It is checked against a public key inside the app, so the software never asks us for permission to run.
./runtime/darwin-arm64/bin/node gcbc.mjs ingest ~/Documents/workPoint it at a folder. It reads what is there and indexes it in place. Nothing is copied to us; there is no upload step because there is nowhere to upload to.
./runtime/darwin-arm64/bin/node gcbc.mjs serveOpens your board in your browser, served by GCBC on this computer only. On an Intel Mac use runtime/darwin-x64 in each command. After that there is no account and no service to sign up for, and everything works with the network off; the one request GCBC makes on its own is a once-a-day check for signed updates.

What it builds from your folder

Not a pile of search results. Your documents are placed into eighteen areas a company actually has, and those areas are wired to each other.

A document lands in an area by the words it contains — a file talking about roadmap, priority and direction lands in Founder Intent & Strategy. You can see which, and move it.
The eighteen areas carry thirty-five declared relationships between them — strategy directs governance, governance constrains product. That is what "knows how it relates" means here: a stated link, not a guess.
So you can see which areas bear on a question before you trust the answer — a pricing claim sits next to the governance rules that bind it. Today the links are declared and shown to you; reading across them is yours to do, not something the software does for you.

Ingestion is a desktop step, because that is where your documents are. The board itself is a web page — once it is serving, you can open it from your phone on the same network.

Chat and meetings

Three things in one place: ask the published knowledge and get a verbatim passage with file and line — or a refusal; message a person or team; open a meeting:<id> room with zero-dependency WebRTC (media peer-to-peer; only signalling touches the server).

Ask it anything

Ask, and it answers with the line it came from.

This is the product, running here in your browser. There is no model of any kind and nothing is sent anywhere: the page ships an index of what we publish, finds the passage that answers you, and quotes it verbatim with the file and the lines it came from. If nothing covers your question, it says so rather than composing something.

Show the full-corpus chat

Ask a question about the product, the pricing, the proof, or how it works.

Verbatim, with the file and the line span. Same question, same answer, every time. The index loads once, and after that asking costs no network call at all — measured in a real browser: twenty-two questions, one request.

Which one are you?

The new business owner

You are building a company and starting to hire. A drive full of work with no order to it, and nothing you can hand someone on their first day.

To turn what you already have into something you can hand a new starter.

Individual

Compile the operating notes and the first-day handbook you have never had time to write, out of the drive you already have — every line pointing at the file it came from, and rebuilt the same way each time it changes. Ask across it as you go. Room for 3 users — the first people through the door.

The solo professional

You work for yourself, and what you send out carries your name. Years of client work, proposals and research in folders only you can navigate.

Every claim you put in front of a client to be one you can show the source for.

Individual

Compile the proposal, the report, the case study — and every claim in it points at the line in your own material that produced it. Build it again next quarter and it comes out identical. Nothing is invented: where the material is not there, it refuses rather than filling the gap.

The fifteen-year company

You are ten to forty people, fifteen years in. Share drives nobody has audited, and knowledge that lives in a handful of heads.

To use what the company already knows, before the people who know it leave.

Professional

Your own material blended with the whole vetted library, company building and the sciences, and access for everyone who needs it.

The thirty-year regulated company

You are thirty years in, regulated, and everything you publish gets examined. Provenance obligations on every claim that leaves the building.

A trail behind every outbound statement, and a stale source to stop the work rather than ship under your name.

Elite

An expired source in a regulated domain refuses the build by name. The regulated library walls (coming), the quarterly digest, and a named contact instead of a form.

The developer

You build software, and you want what it says to be checkable. Your own documentation, release notes and specs, and code that makes claims about them.

To give your code the file and lines behind a claim, or a clear refusal.

Individual

From your own code, on your own Mac, ask GCBC over its local HTTP API or its MCP server and get back the file, the lines and the exact quote behind a claim, or a refusal that names its law.

The team that connects an LLM to DRE

Your team already works with an LLM. Answers that sound right, with nothing to check them against.

Every answer the LLM gives to cite your own files, or to refuse.

Professional

Connect the LLM your team already uses to DRE, over MCP, so its answers quote your files by name and line or decline.

Ask

your material goes in, and every answer carries the line it came from

First mile — learn your corpus

Drop a folder → ask one question → see a cite or a refuse → pick one hole to declare.

Organize

Organize is the Ask surface — same as Home A, and since 2026-09-23 the top nav carries it under the name ASK. The two words name one surface; the nav uses the one a first-time reader understands without being told. Scope chips, example chips, the question bar, and the promise: if it is not in your material, it says so.

Refuse

When the answer is not in scope, GCBC refuses instead of guessing. That is the product promise on Organize and across cite paths.

Upload / ingest

Bring files into Sources so Ask and Build can cite them. Unregistered files stay out of compiles.

Master your data

Don’t just own your data. Master your data. Own means files on your hardware. Master means doctrines declared, conflicts named, and judgment compiled you can prove. Cite teaches the corpus; refuse is the syllabus; declare the hole in Build.

Chat and meetings

From Home open Chat and meetings (C). Message a person or team. Schedule a meeting, invite by email, start with camera when ready.

Meetings

Inside Chat and meetings: set title and time, invite emails, schedule, then Start meeting. Local and far peer panes prove the media path when permissions allow.

Scopes — what a question is allowed to reach

Every question runs inside one scope, chosen with the scope chips above the ask bar: My files, Company or Investor pack. My files limits answers to your own ingested material — drafts, notes, private working files — and a refuse there means it is not in your personal ingest. Company limits answers to shared company knowledge; new hires should start here after they are added as a user, not on an empty My files corpus. Investor pack limits answers to the investor slice — briefs, legal, metrics, strategy — and is LOCKED on Individual and Professional and for team members: the chip shows it locked, choosing it refuses, and the app itself refuses its passages. On Elite the license holder reaches it. The separation is deliberate: an intern in Company scope cannot pull fundraising material by accident.

Technical requirements

What it needs, and what it does not

Show what it needs from you, and what it does not

A Mac or a Windows PC, and a folder.

It runs on your machine

A Mac (Apple silicon or Intel) or a Windows PC. Everything it needs is inside the download, so there is nothing else to install. After that there is no account and no service to sign up for.

It never needs the network

Activation, indexing and every answer happen offline. Your license is verified by signature against a key packaged beside it, so the software never asks us for permission to run. Once a day it downloads our public, signed update and revocation list; that request carries no account, key, file or answer.

You do not need to write code

You point it at a folder and you ask it things. Nothing is built until you ask for it, and nothing reaches a customer until you send it yourself.

If you do write code: the declaration behind every request is plain XML, and on Professional and up you can add your own kinds of deliverable without waiting on an engineer. That door is open. You never have to walk through it.

What arrives when you buy

A license key by email, and this. Open the zip: GCBC for Mac, GCBC for Windows and a one-page Start Here. Double-click GCBC, paste the key from your email on the welcome page, add a folder, and it answers from your own documents with the line it came from — offline, on your machine.

gcbc-1.0.0.zip · 132.1 MB · Node included, nothing to install · sha256 26459d7ba3f8ee48…

Space needed: about 500 MB free to download and unzip. Once installed, about 250 MB on a Mac or 130 MB on Windows, plus about 4 MB for every 1 MB of documents you add.

Join the beta waitlist. Testers are invited in small groups to try the whole product for a limited time.

Tested on an Apple-silicon Mac. On an Intel Mac or a Windows PC, follow these steps.

Start on an Intel Mac

The same GCBC app runs on a Mac with an Intel processor; there is nothing separate to download.

Double-click the zip you downloaded and drag GCBC (GCBC.app) into your Applications folder.
Double-click GCBC. Its launcher (GCBC.app/Contents/MacOS/GCBC) asks the Mac whether it has Apple silicon and, on an Intel Mac, starts the Intel runtime built into the app (GCBC.app/Contents/Resources/runtime/darwin-x64/bin/node). The first time, your Mac may ask you to confirm that you want to open an app you downloaded.
Your browser opens the GCBC welcome page. Paste the license key from your GCBC email and click Activate; the key is checked on this computer against the public key inside the app (GCBC.app/Contents/Resources/gcbc-license-public.pem).
Answer the setup questions (the app carries them in GCBC.app/Contents/Resources/setup-questions.json), then click Add documents… on the board and choose a folder.
Command line (optional), in Terminal: cd /Applications/GCBC.app/Contents/Resources, then ./runtime/darwin-x64/bin/node gcbc.mjs kinds to list what it can build.

Start on Windows

Right-click the zip you downloaded and choose Extract All… (running GCBC from inside the zip does not work). You get GCBC for Windows, GCBC.app (the Mac app; a Windows PC ignores it) and Start Here.pdf.
Open the GCBC for Windows folder and double-click GCBC.bat. If SmartScreen shows “Windows protected your PC”, click More info → Run anyway. It starts the Windows runtime inside the folder (app\runtime\win-x64\node.exe).
Your browser opens the welcome page at http://127.0.0.1:8787/. Paste the license key from your GCBC email and click Activate; the key is checked against the public key inside the folder (app\gcbc-license-public.pem).
Keep the black window titled GCBC (from GCBC.bat) open while you use GCBC; closing it stops GCBC. Double-click GCBC.bat again to reopen; if GCBC is already running, your browser simply comes back to it.
Command line (optional), in the GCBC for Windows\app folder: runtime\win-x64\node.exe gcbc.mjs kinds lists what it can build.

What you actually do

Four things, and only the first one takes a morning.

Everything after setup is picking from lists and deciding what is good enough to ship.

Show the four steps, with times

01 · once

Answer eight questions

Who you are, your domain, what you want first, where it ships, what rules apply to you, what you already have, and how you want to be told things.

about twenty minutes

02 · once

Bring your material in

Drop in documents, slides, spreadsheets and scans. Each is read and shown to you before anything is indexed. You approve, then it is answerable.

as long as your drive takes

03 · every day

Ask, or ask for something built

Pick a domain and a kind from the list. An answer comes back as a line from your own material. A build comes back as a finished set of files.

seconds

04 · when you choose

Decide what leaves the building

Nothing is built until you ask for it. There is no background process, no schedule and no watcher — between your commands the instance does nothing at all, so there is no queue of documents to police and nothing to switch off.

your call, always

Build and prove

One declaration through stations, including refuse. Proof is the receipt: the same declaration compiles to the same bytes, and a violated contract produces no artifact.

The compile line

One declaration, all the way through

Advance it station by station. The same declaration is carried the whole way, and you can see what each step does to it - including the step where it refuses.

Show the six-station compile line

Run it clean

A scale model of the mechanism, drawn from the real one. The live compiler below runs the hashing for real, in your browser.

The declaration, at this station

receipt

Pick what to build.

The 60 kinds in 10 categories, each built from a declaration and its cited passages, or refused by name.

Win the deal

Sales and founders closing revenue

Sales proposal · Deck · Discovery brief · Mutual action plan · Objection sheet · Business case

Find customers

Marketing that stays on message

Positioning · Customer profile · Campaign · Content series · Brand kit · Landing page

Decide what to build

Product decisions before code

Problem brief · Product scope · Roadmap · Experiment writeup · Launch checklist · Do-nothing case

Ship a product

Working software customers can use

Installable app · Phone app · Game · Course outline · Library API · Demo

Keep it shippable

Engineering and ops that hold

Architecture note · Test plan · Runbook · Trust boundary · Checker · Fixture

Run the money

Finance and operating reality

Financial model · Unit economics · Runway · Pricing sheet · Board pack · Operating plan

Underwrite the bet

Investors and capital allocation

Investment memo · Valuation bridge · Diligence index · Returns scenarios · Portfolio fit · Projection

Prove it to people

Trust, talent, inventory

Whitepaper · Investor update · Case study · Delivery handoff · Hiring shortlist · Asset register

Live better

Habits, money, and time you can keep

Habit plan · Friction map · If-then plan · Streak log · Personal budget · Week calendar

Go and play

Travel and sports you can execute

Trip plan · Pack list · Training plan · Game plan · Recovery plan · Season goals

Show every kind and whether it is buildable now

Sales proposalOffer answered to a buyer’s needs.Buildable now DeckShort company story for a meeting.Buildable now Discovery briefWhat the call taught you.Buildable now Mutual action planShared path to close.Buildable now Objection sheetAnswers to repeat pushbacks.Buildable now Business caseTheir ROI math.Buildable now PositioningWho it’s for and not for.Buildable now Customer profileWhich buyer, why now.Buildable now CampaignOffer + channel + creative + measure.Buildable now Content seriesRepeatable posts or emails.Buildable now Brand kitVoice, proof points, visual rules.Buildable now Landing pagePromise and proof on the web.Buildable now Problem briefWho hurts; how we’ll know it’s fixed.Buildable now Product scopeIn, out, done-when.Buildable now RoadmapNow / next / later with reasons.Buildable now Experiment writeupHypothesis, metric, result.Buildable now Launch checklistMessage, price, support, day-one metric.Buildable now Do-nothing caseIf we don’t ship.Buildable now Installable appLink-install app that works offline.Buildable now Phone appSame product on a phone.Buildable now GameLevels, score, a standard.Buildable now Course outlineModules/lessons mapped to a standard.Buildable now Library APICalls a developer uses, with examples.Buildable now DemoShort clickable walkthrough.Buildable now Architecture noteWhat talks to what.Buildable now Test planMust-pass and must-fail cases.Buildable now RunbookDeploy, rollback, who to page.Buildable now Trust boundaryWhere data enters and may leave.Buildable now CheckerOne rule that can fail automatically.Buildable now FixtureKnown good and bad examples.Buildable now Financial modelP&L, balance sheet, cash flow that tie.Buildable now Unit economicsCAC, LTV, payback, margin by segment.Buildable now RunwayCash left under the real plan.Buildable now Pricing sheetTiers, discounts, margin after delivery.Buildable now Board packPlan vs actual and decisions needed.Buildable now Operating planQuarter priorities, owners, dates.Buildable now Investment memoThesis, risks, what kills it.Buildable now Valuation bridgeHow the price was derived.Buildable now Diligence indexProven vs asserted in the data room.Buildable now Returns scenariosBase / down / up with ownership.Buildable now Portfolio fitWhy this sits with the other bets.Buildable now ProjectionOne claim tied to one source — or refuse.Buildable now WhitepaperDeep sourced research write-up.Buildable now Investor updateWhat changed for people who funded you.Buildable now Case studyOne customer win with proof.Buildable now Delivery handoffWhat was sold, for who builds it.Buildable now Hiring shortlistRanked candidates with evidence.Buildable now Asset registerWhat you own/use and its status.Buildable now Habit planOne behavior with cue, routine, reward.Buildable now Friction mapWhat makes good hard and bad easy.Buildable now If-then planWhen X happens, I do Y.Buildable now Streak logWhat broke the chain and what restarted it.Buildable now Personal budgetMoney in, money out, one rule.Buildable now Week calendarTime blocks for what matters.Buildable now Trip planWhere, when, budget, must-dos.Buildable now Pack listWhat to bring, nothing forgotten.Buildable now Training planSessions toward a race or season goal.Buildable now Game planHow you’ll play this match or event.Buildable now Recovery planSleep, food, rest after load.Buildable now Season goalsWhat a good season means in numbers.Buildable now

Infrastructure vs. architecture.

Infrastructure is the engine you run your company on. Architecture is how that engine is built. GCBC is the infrastructure — point your documents at it and it becomes the system your company answers and builds from. Its architecture is why you can trust it: every fact is declared, every answer is tied to its source, and every product is compiled, not made up. Change the architecture — the declarations — and everything downstream changes with it, in seconds. It is also why privacy here is a property of the design, not a setting you toggle.

Integrity at scale

GCBC turns what you already know into finished, sellable products — apps, courses, reports, entire product lines — across 60 kinds of deliverable. Each one shows up complete for where it’s headed: the right content, the regulations already built in, packaged and ready for the App Store, your website, or wherever you earn. Nothing goes out until it’s proven, so every single thing you put your name on is something you can stand behind. Build from what you know, prove every word of it, and ship it anywhere — that’s integrity at scale.

Show what integrity at scale means here

Nothing goes out until it is proven, so everything you put your name on is something you can stand behind. That is the whole promise, and it is narrow on purpose — here is the proof, and here is what is not proven.

Build from what you know

A local, two-part compiler. It ANSWERS questions from your own corpus with the file and line the answer came from, and it BUILDS finished artifacts by compiling declared XML nodes. One board renders both.

Prove every word of it

Every claim is bound to a source before it can be stored, and every step is hashed into a chain you can verify after the fact.

Ship it anywhere

The deliverable knows its destination, so you do not have to remember what that destination demands.

Why we built it

The knowing was never the problem

This began in a classroom. One person with twenty years of material that no software could turn into anything sellable, and no engineer to hand it to. Every tool on offer answered with a model that writes confidently and cannot show you where a single sentence came from. For work that carries your name, that is not an answer.

Show why it was built

You already know the thing

Domain expertise is not the bottleneck. Turning it into something finished, correct for where it is going, and safe to put your name on is the bottleneck. That work is structural, repetitive, and exactly what a compiler is for.

You cannot ship what you cannot source

An answer you cannot trace is a liability the moment someone asks. Every answer here is a verbatim line out of your own corpus with the file and the line number, or an honest refusal. There is no third outcome.

Same input, same product, every time

A tool that produces something slightly different each run cannot be audited, cannot be corrected once, and cannot be trusted at volume. The transform is deterministic over its input, so a fix is permanent and a rebuild is a check.

Your material never leaves

A regulated buyer cannot send a corpus to someone else’s cloud, and most experts should not want to. It runs on your hardware, bound to loopback. We scanned this installation from its own network and every part of the compiler refused the connection.

It refuses rather than guess

A violated contract does not produce a worse product. It produces no product, and names the line that broke. That is the difference between a tool that helps you work and a tool you can stand behind.

None of the mechanisms here are novel on their own. Declaration-driven codegen, mutation testing and air-gapped deployment are all ordinary. What is unusual is applying them to the thing that produces your work, and then publishing what they measure about us.

Who it is for, and when it matters

Show who it is for, and when it matters

Who

Organizations that must be able to show where an answer came from — regulated buyers, school districts, enterprise engineering and compliance teams. If nobody ever asks you to justify an output, you do not need this.

When

When an answer has to survive a review: an audit, a procurement questionnaire, a board packet, a safety case, a public-records request. The cost of "we think the model said so" arrives later, all at once.

Where it runs

On your own hardware if you want it there. The compiler does not require a model to run, and the answer path makes no model call at all.

Is there an AI in this?

Not the kind you are thinking of. Nothing here predicts or invents text. Every answer is a passage lifted out of your own files and shown with the line it came from — or a refusal. That is why the same question gives the same answer every time.

Break it yourself

Four stages. Break any one and watch what does not get made.

Press run and each stage does its work in order. Then break one. It will not warn you and carry on — it stops, says which line it could not prove, and everything after it produces nothing at all.

Ready.

Input

Reads what you declared and works out what it means

—

Build

Checks every claim against the source it names

—

Generate

Composes the deliverable from your material

—

Project

Renders it for its destination, byte for byte

—

Press run.

The hashing is real and runs in your browser. It is one kind in one page, so it is a scale model of the compiler and is labeled as one.

What you actually own

Your instance, your machine, your corpus

Most software you buy is an account on someone else's computer. This is not that. You license a compiler, you run it on your own hardware, and your material never leaves it. What follows is what that means in practice, including the parts that are inconvenient for us.

Show what running it on your own machine means

You hold a license, not an account

One license, bound to one email address. The instance verifies it by signature against a key packaged beside it, so it works with the network off and it keeps working if we are unreachable. It never asks us for permission to run; its once-a-day update check carries no account, key, file or answer.

You give your team access by email

The license holder grants access to colleagues by address, up to their tier's user limit, and the instance recognizes exactly those people. Your own address does not count against the limit. Nobody creates an account with us to be added, because there is nothing of yours on our side to attach an account to.

Your documents never reach us

Indexing, retrieval and every answer happen on your machine. Nothing is uploaded to us and nothing syncs in the background: files come in when you add them, and a connector pulls only after you press Connect, with your own sign-in, straight from that service to your computer. We have zero read access to your corpus by architecture rather than by policy, which is the difference between a promise and an arrangement where breaking the promise is not possible.

Updates arrive as signed patches you choose to apply

New kinds, new sources, refreshed doctrines and fixes are announced by email and downloaded when you want them. Every patch is signed and verified locally before it is applied, and an unsigned or altered patch is refused rather than warned about. That update channel is what the annual license and its maintenance pay for.

If you stop paying, what you have keeps working

You keep the instance you have and the corpus you built. What lapses is the update channel: no new kinds, no refreshed sources, no fixes. We cannot switch off software we cannot reach, and we would not design it so we could.

Every one of those five is exercised by a check that can fail: the license is verified offline, a forged one is refused, the user limit is proven by trying to exceed it. With no connector turned on, GCBC’s only network request is the once-a-day download of our public, signed update and revocation list; it carries no account, key, file or answer, and every build is tested for that. A connector you turn on talks only to the service you connected, using your own sign-in.

What it actually makes

Graded before it is shown.

Each kind is graded in a real browser against its declared floor of words, sections and sourced citations. The menu above opens every kind that clears it.

Show what qualifies an artifact to appear here

60 kinds carry a declared floor: at least 700 words, 6 sections and 6 sourced figures with the file and line each came from. The menu above opens every kind that clears it, and a photograph appears here once one is taken of that artifact.

Start the 90-day beta — $99 Ask on Command — cite the file and line, or refuse

Measured by check-kind-depth --registry gcbc-customer-60 against domains/gcbc-kind-build-specs-60.xml; the page refuses to build if any other count renders.

How sources work

A citation is the line, not a summary of it

Every answer this system gives is a passage lifted whole from a document you can open. Nothing is paraphrased, nothing is blended, and nothing is written. That is a mechanical property rather than a promise, so here is exactly how it is enforced.

Show how a citation is resolved

Sources are declared, never crawled

A document enters the corpus because a declaration names it. Nothing arrives by discovery, so no one has to wonder later where a claim came from or whether something wandered in. What makes a source authoritative here is that a person put it in the declaration and signed for it.

Every passage carries its file and its lines

A passage is stored with the document it came from and the exact line span it occupies. That span is what a citation shows you, so checking a quote means opening the file at those lines rather than trusting a label.

The quote is reopened and compared at build time

On every build, each passage is read back out of its source file at its span and compared byte for byte with what the index holds. If one character has drifted the build stops. A quote that cannot be reproduced from the file is not allowed to be quotable.

A superseded source stops being citable

Editing a document re-indexes it, and the passages that no longer exist stop being reachable in the same build. Nothing keeps quoting a paragraph that was deleted, because the index is rebuilt from the documents rather than accumulated alongside them.

Out of scope is answered by refusing

If nothing in the corpus answers a question closely enough to quote, the system declines instead of writing something plausible. The refusal is the feature: it is what makes the answers you do get worth something.

The public knowledge base behind the chat on this page holds 531 passages across 2 documents, and every one of them was reopened and compared when this page was built. Your own instance works the same way over your own documents, and we never see either.

The domains

Every place your expertise already lives.

These are not features of ours. They are the parts of a company, and your material already sits in some of them. Pick the one a request belongs to and the system knows which rules apply, which sources are in scope, and who may see the result.

35 declared connections between the 18 domains. Choose one to see everything a request landing there can legitimately reach.

Nothing selected. Every line is a declared route between two domains.

D1Founder Intent & Strategy

Where the company is going and why, so every other domain has something to check itself against.

D2Governance & Law

Who may do what, which rules bind you, and what the system refuses on your behalf.

D3Product Development

How a thing actually gets built, from a declaration to a finished artifact.

D4Product Management

What is being worked on now, what is blocked, and what ships next.

D5Product Registry & Assets

The one list of what exists, so no two parts of the company count differently.

D6Demo & Experience Systems

How the work is shown to someone who has never seen it before.

D7Brand & Identity

What it is called, how it looks, and the rules that keep it consistent.

D8Narration & Communication

How the company explains itself, in its own voice, to whoever is listening.

D9Revenue Engine

How money is actually made: what is sold, to whom, at what price.

D10Trading & Financial Intelligence

The money itself — what came in, what went out, what is owed and when.

D11Marketing & Distribution

How people find out this exists.

D12Sales & Conversion

How someone who found you becomes someone who bought.

D13Learning & Knowledge Systems

Everything the company knows, indexed so a question has an answer with a source.

D14Agent Workforce & HR

Who does the work, human or otherwise, and what they are accountable for.

D15MCP Automation & Orchestration

How work gets routed and run without someone remembering to start it.

D16Infrastructure & Local Intelligence

What it all runs on, and what stays inside the building.

D17Memory Systems

What the company remembers, so a decision made once does not have to be made again.

D18RLL City (Simulation & Emergence)

Where the whole system is tested at scale before it meets a customer. This one is ours rather than yours — it is how we shake the engine out, and it is listed so you are not left guessing which of the eighteen is not about you.

The machine, running

Watch it build one. Then watch it refuse.

Two compiles of the same declaration. The second has one source removed — a single emptied attribute — and that is the whole difference. Nothing here is animated for effect: both traces were recorded from real runs when this page was built.

Show it build one, then refuse one

762 files and 103 MB indexed in 1.46 seconds — 21,751 passages, nothing leaving the machine. Measured on a real desktop, not estimated; every file it could not read was named with the reason.

The declaration is complete

Six stages, and a finished paper at the end of them.

01
parse11 nodes
02
resolve0 errs · 0 assumed
03
enforceconforming
04
consult0 doctrine(s) — kind not governed by any binding
05
render1440 b
06
assemble3051 b

artifact: 3,051 bytes

One claim has lost its source

It stops where the evidence ran out. It does not produce a worse paper — it produces nothing, and names the line.

01
parse11 nodes
02
resolve0 errs · 0 assumed
03
enforce1 violation(s)
04
consult0 doctrine(s) — kind not governed by any binding

Never reached: render, assemblefigure at line 7:5 — wanted a sourced figure

artifact: 0 bytes

Recorded from two real compiles of the same sample. The break is one attribute emptied, which is the smallest edit that removes the evidence behind a claim.

Your business, not a demo business

Pick the one closest to yours.

Nothing below was written for these businesses. Each one answered the same ten questions any owner answers, and the compiler decided the rest — which areas of obligation open, which sources apply, and which tier actually reaches the material. Switch between them and watch the answer change.

Show the worked examples by industry

These eight are drawn from the US small-business distribution rather than chosen for recognition: professional services is the largest category at 4.53 million firms, then construction at 3.62 million, transportation at 3.39 million and real estate at 3.33 million. Three of them trip a regulated wall, which is the part worth watching.

Every fact you borrow has a shelf life — what “freshness” means here

A law’s wording does not change. A national statistic is replaced every year. A price moves every week. Quote a two-year-old number as if it were current and you have put your name on something that stopped being true — and nothing in the document warns you.

Freshness is us doing that check for you. Every source in your library carries the date we last confirmed it, and how fast that kind of fact goes out of date. Every time you build something, we subtract one from the other and tell you where it stands.

static: Settled material. We re-look every five years in case something replaced it.
periodic: Updated on a schedule. If it is more than fifteen months old, its next edition is out and we have not looked.
volatile: Moves constantly. Older than three months and we would not put your name on it.

fresh We checked it recently enough. Use it.
stale We have not looked lately, and its replacement may already be out. You can still use it, and now you know to look.
expired Do not build on this. We will not let it into your library either — the build stops rather than handing you a number we would not stand behind.

What this does not mean: we are not re-reading the internet while you work. Nothing leaves your machine. The dates travel with the library, and the arithmetic happens where you are.

Accounting practiceMarketing consultancyRoofing contractorLocal trucking companyProperty managementMedical officeRestaurantTaekwondo school

Accounting practice

Reaches this on Elite Professional, scientific and technical services — the largest category, 4.53M firms

Why this one needs EliteThis business touches regulated material. The compiler will not hand it back on a lower tier — it refuses and names the wall, here and inside the instance, decided by the same function. The wall here is financial advice.

What this owner said

6 owner answers · ids P3, P4, P5, P6, P7, P8

What opened

employment
financial advice
financial conduct
personal data
premises
professional licensing

Sources behind it

SourceAuthorityFreshness · verified

plainlanguage.gov — the Federal Plain Language Guidelines periodic · 2026-09-07
The Chicago Manual of Style periodic · 2026-09-07
The Associated Press Stylebook periodic · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07
Common Core State Standards static · 2026-09-27
Anderson and Krathwohl, the revised Bloom taxonomy static · 2026-09-07
Council for Economic Education — National Standards for Personal Financial Literacy periodic · 2026-09-07
WHO — Who we are (mandate, membership and governance) periodic · 2026-09-29
NLM PubMed — About PubMed (content and provenance) periodic · 2026-09-29
NIST — Fundamental Physical Constants (CODATA recommended values) periodic · 2026-09-29
CERN — Who we are (mission, governance and founding) static · 2026-09-29
Particle Data Group — Review of Particle Physics (home) periodic · 2026-09-29
IPCC — About the Intergovernmental Panel on Climate Change periodic · 2026-09-29
EPA — Our Mission and What We Do periodic · 2026-09-29
EIA — About the U.S. Energy Information Administration volatile · 2026-09-29
NCBI — Our Mission static · 2026-09-29
NHGRI — About the National Human Genome Research Institute static · 2026-09-29
ASM — About the American Society for Microbiology static · 2026-09-29
NIMH — About the National Institute of Mental Health periodic · 2026-09-29
WHO — International Classification of Diseases (ICD-11) periodic · 2026-09-29
NIH Toolbox — About the neurobehavioral assessment system static · 2026-09-29
NIST — Chemistry WebBook (Standard Reference Database 69) periodic · 2026-09-29
wwPDB — Worldwide Protein Data Bank archive of 3D structures periodic · 2026-09-29
RCSB PDB — US data center for the Protein Data Bank archive periodic · 2026-09-29
NIST/SEMATECH — e-Handbook of Statistical Methods, What is EDA static · 2026-09-29
ASA — Ethical Guidelines for Statistical Practice periodic · 2026-09-29
Crossref — About the DOI registration agency periodic · 2026-09-29
FAO — About the Food and Agriculture Organization periodic · 2026-09-29
Codex Alimentarius — About Codex, joint FAO/WHO food standards periodic · 2026-09-29
USDA NASS — About the National Agricultural Statistics Service periodic · 2026-09-29

Marketing consultancy

Reaches this on Professional Professional, scientific and technical services

What this owner said

5 owner answers · ids P3, P6, P7, P8, P10

What opened

claims substantiation
employment
financial conduct
personal data
premises

Sources behind it

SourceAuthorityFreshness · verified

plainlanguage.gov — the Federal Plain Language Guidelines periodic · 2026-09-07
The Chicago Manual of Style periodic · 2026-09-07
The Associated Press Stylebook periodic · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07

Roofing contractor

Reaches this on Professional Construction — 3.62M firms

What this owner said

6 owner answers · ids P3, P5, P6, P7, P8, P10

What opened

claims substantiation
employment
financial conduct
personal data
premises
professional licensing

Sources behind it

SourceAuthorityFreshness · verified

plainlanguage.gov — the Federal Plain Language Guidelines periodic · 2026-09-07
The Chicago Manual of Style periodic · 2026-09-07
The Associated Press Stylebook periodic · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07
Common Core State Standards static · 2026-09-27
Anderson and Krathwohl, the revised Bloom taxonomy static · 2026-09-07
Council for Economic Education — National Standards for Personal Financial Literacy periodic · 2026-09-07
WHO — Who we are (mandate, membership and governance) periodic · 2026-09-29
NLM PubMed — About PubMed (content and provenance) periodic · 2026-09-29
NIST — Fundamental Physical Constants (CODATA recommended values) periodic · 2026-09-29
CERN — Who we are (mission, governance and founding) static · 2026-09-29
Particle Data Group — Review of Particle Physics (home) periodic · 2026-09-29
IPCC — About the Intergovernmental Panel on Climate Change periodic · 2026-09-29
EPA — Our Mission and What We Do periodic · 2026-09-29
EIA — About the U.S. Energy Information Administration volatile · 2026-09-29
NCBI — Our Mission static · 2026-09-29
NHGRI — About the National Human Genome Research Institute static · 2026-09-29
ASM — About the American Society for Microbiology static · 2026-09-29
NIMH — About the National Institute of Mental Health periodic · 2026-09-29
WHO — International Classification of Diseases (ICD-11) periodic · 2026-09-29
NIH Toolbox — About the neurobehavioral assessment system static · 2026-09-29
NIST — Chemistry WebBook (Standard Reference Database 69) periodic · 2026-09-29
wwPDB — Worldwide Protein Data Bank archive of 3D structures periodic · 2026-09-29
RCSB PDB — US data center for the Protein Data Bank archive periodic · 2026-09-29
NIST/SEMATECH — e-Handbook of Statistical Methods, What is EDA static · 2026-09-29
ASA — Ethical Guidelines for Statistical Practice periodic · 2026-09-29
Crossref — About the DOI registration agency periodic · 2026-09-29
FAO — About the Food and Agriculture Organization periodic · 2026-09-29
Codex Alimentarius — About Codex, joint FAO/WHO food standards periodic · 2026-09-29
USDA NASS — About the National Agricultural Statistics Service periodic · 2026-09-29

Local trucking company

Reaches this on Professional Transportation and warehousing — 3.39M firms

What this owner said

6 owner answers · ids P3, P5, P6, P7, P8, P9

What opened

cross jurisdiction
employment
financial conduct
personal data
premises
professional licensing

Sources behind it

SourceAuthorityFreshness · verified

W3C WCAG 2.2 — contrast and non-text contrast periodic · 2026-09-07
ISO 12647 — graphic technology process control static · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07
FTC guidance on advertising substantiation periodic · 2026-09-07
MEDDIC and Challenger qualification frameworks static · 2026-09-07

Property management

Reaches this on Professional Real estate, rental and leasing — 3.33M firms

What this owner said

5 owner answers · ids P3, P5, P6, P7, P8

What opened

employment
financial conduct
personal data
premises
professional licensing

Sources behind it

SourceAuthorityFreshness · verified

plainlanguage.gov — the Federal Plain Language Guidelines periodic · 2026-09-07
The Chicago Manual of Style periodic · 2026-09-07
The Associated Press Stylebook periodic · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07

Medical office

Reaches this on Elite Health care and social assistance

What this owner said

6 owner answers · ids P1, P3, P5, P6, P7, P8

What opened

employment
financial conduct
health records
personal data
premises
professional licensing

Sources behind it

SourceAuthorityFreshness · verified

plainlanguage.gov — the Federal Plain Language Guidelines periodic · 2026-09-07
The Chicago Manual of Style periodic · 2026-09-07
The Associated Press Stylebook periodic · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07
Common Core State Standards static · 2026-09-27
Anderson and Krathwohl, the revised Bloom taxonomy static · 2026-09-07
Council for Economic Education — National Standards for Personal Financial Literacy periodic · 2026-09-07
WHO — Who we are (mandate, membership and governance) periodic · 2026-09-29
NLM PubMed — About PubMed (content and provenance) periodic · 2026-09-29
NIST — Fundamental Physical Constants (CODATA recommended values) periodic · 2026-09-29
CERN — Who we are (mission, governance and founding) static · 2026-09-29
Particle Data Group — Review of Particle Physics (home) periodic · 2026-09-29
IPCC — About the Intergovernmental Panel on Climate Change periodic · 2026-09-29
EPA — Our Mission and What We Do periodic · 2026-09-29
EIA — About the U.S. Energy Information Administration volatile · 2026-09-29
NCBI — Our Mission static · 2026-09-29
NHGRI — About the National Human Genome Research Institute static · 2026-09-29
ASM — About the American Society for Microbiology static · 2026-09-29
NIMH — About the National Institute of Mental Health periodic · 2026-09-29
WHO — International Classification of Diseases (ICD-11) periodic · 2026-09-29
NIH Toolbox — About the neurobehavioral assessment system static · 2026-09-29
NIST — Chemistry WebBook (Standard Reference Database 69) periodic · 2026-09-29
wwPDB — Worldwide Protein Data Bank archive of 3D structures periodic · 2026-09-29
RCSB PDB — US data center for the Protein Data Bank archive periodic · 2026-09-29
NIST/SEMATECH — e-Handbook of Statistical Methods, What is EDA static · 2026-09-29
ASA — Ethical Guidelines for Statistical Practice periodic · 2026-09-29
Crossref — About the DOI registration agency periodic · 2026-09-29
FAO — About the Food and Agriculture Organization periodic · 2026-09-29
Codex Alimentarius — About Codex, joint FAO/WHO food standards periodic · 2026-09-29
USDA NASS — About the National Agricultural Statistics Service periodic · 2026-09-29

Restaurant

Reaches this on Professional Accommodation and food services

What this owner said

4 owner answers · ids P3, P6, P7, P8

What opened

employment
financial conduct
personal data
premises

Sources behind it

SourceAuthorityFreshness · verified

W3C WCAG 2.2 — contrast and non-text contrast periodic · 2026-09-07
ISO 12647 — graphic technology process control static · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07

Taekwondo school

Reaches this on Elite Educational services

What this owner said

5 owner answers · ids P2, P3, P6, P7, P8

What opened

employment
financial conduct
minors
personal data
premises

Sources behind it

SourceAuthorityFreshness · verified

W3C WCAG 2.2 — contrast and non-text contrast periodic · 2026-09-07
ISO 12647 — graphic technology process control static · 2026-09-07
FTC Endorsement Guides periodic · 2026-09-07
CAN-SPAM Act compliance guide, FTC periodic · 2026-09-07
FTC guidance on advertising substantiation periodic · 2026-09-07
MEDDIC and Challenger qualification frameworks static · 2026-09-07

Computed at build time by the same composition and entitlement functions the product runs. No industry content is authored anywhere; the business name is a label that selects nothing.

Made by the compiler

The first catalog, still compiled.

These 15 worked examples come from the retired first catalog and are compiled on every build as a regression check. They are not the catalog on sale; the catalog and its state are in the menu above.

Show the compiled examples

Ask on Command with your own material — cite or refuse Start the 90-day beta — $99

1 refused to emit

The compiler enforces one identity law on everything it makes: colors from the palette, sizes on the type scale, spacing on the ladder, components from the library. These kinds break it, so the compiler will not ship them. We would rather show you that than a hand-made sample.

Installable appcompiled 5769 bytes, then REFUSED its own conformance setE6 layout — no max-width

Compiled at build time from the kind registry the product ships. Where a kind refuses, the refusal and the checks it failed are shown rather than replaced with something hand-made.

The deliverables

Each one arrives complete for where it is going.

A kind knows what its destination expects — the shape a district wants in a proposal, the layout a phone screen needs, the standards a curriculum is built against. You do not have to remember any of it.

Show every kind and what it arrives complete for

Need another? On Professional and up you declare it yourself, and it compiles through the same engine as these.

The sandbox

It builds when you ask. Nothing before that.

In the sandbox you pick a kind, edit its declaration if you want, and compile it. You see whether it conforms, what it would produce and a preview.

Nothing in the sandbox ships. It writes nothing, so What shipped does not change; only a Build you run makes a deliverable. You are the only door.

A sandbox preview is a draft, not a deliverable. Check it the way you would check anything that goes out under your name.

How you check what it did

The customer's request is shown back to them as the transform received it. A request that is silently rewritten before compiling cannot be checked against its result.

Every source the transform drew on is named to the customer, with the file and line it was read from. A count of sources is not a naming of them.

Each claim in the result points at the source that produced it. Showing the answer and the source list separately satisfies neither: the customer must be able to ask "where did THIS line come from" and get one answer.

When the material is not there, the transform REFUSES and names what is missing. A refusal is a step in the derivation, not an error to be hidden, and it is the only honest alternative to inventing the middle step.

The surface presents a derivation, never a recommendation. The distinction is load-bearing: "here is how this answer was derived, step by step" is a record of what the customer's own material says; "you should do X" is advice, and this product does not give it.

Build

declare it, compile it, prove it — and nothing ships until you say so

Build and prove

Open Build (B). Work Sources → Doctrine → Sandbox, then compile a deliverable. Nothing ships until you say so. Every build leaves a receipt you can check.

Sources

Registered material the compiler may cite. Open from Build or Home L. Your files and plan library domains live here.

Doctrine

Under Build, Doctrine is the numbered list of settled rules the compiler treats as true. Every refusal names the rule it traces to, and you can declare a rule of your own; it is kept on this computer and numbered after the others. It sits with Sources and Sandbox as proof behind a deliverable.

Sandbox

Under Build: try safely. The Sandbox compiles a kind from its declaration, which you can edit there, and shows whether it conforms, what it would emit and a preview. Nothing is written, so What shipped does not change; a Build is what ships. Pair it with Sources and Doctrine for proof.

System health

Under Build: what this copy holds right now, counted from the files on this computer each time it loads — whether the record of every action is intact, how many passages and files are indexed, what is on disk, the rules in force and your plan. It reports on the machine, not on your documents, so reading it tells nobody anything about your material.

Rebuild check

Compile the same declaration twice and compare the bytes. A deliverable that cannot be rebuilt identically cannot be re-derived from its sources later, which is the whole claim — so the check runs on the artifact you are about to ship, not on a sample.

Search GCBC

The sticky top search is for finding Command surfaces and copy quickly. It does not replace Ask from sources.

Ask inside Build

Builders checking understanding mid-compile path: a quick cite-or-refuse against the ingested corpus, after ingest and before or after sandbox tries. Type a check question at BUILD → Ask step; get a cite or a refuse. It is the same promise as the Ask pillar, available without leaving the build.

What shipped

Builders tracking real outputs: the artifacts that actually compiled onto disk from a Build. A sandbox compile writes nothing, so it never appears here. Open BUILD → What shipped and open an artifact by kind or id when present. A compile that produced nothing appears nowhere — the list is what exists, not what was attempted.

Grow · user limits, library, access

What grows when your plan does

Add members by email up to your tier's user limit, and unlock library reach with your plan. Grow is user limits, library and access.

Individual

3 users · builds from your own documents

Professional

25 users · 18 library domains

Elite

Unlimited users · 18 library domains

The license holder grants access to colleagues by address, up to the tier's user limit. The user is the person, and access is revoked from the same place it was granted.

Work waits on a named approver. Pending decisions sit in one place with who can approve them, and nothing ships until that person says so.

Moving up a tier changes what the software reaches, not what it promises: user limits and library reach grow with the plan, and the compiler itself is never metered.

Upgrade. Move to a higher ratified tier (Individual → Professional → Elite) using live Stripe price ids from gcbc-offer.xml

Grow

user limits, library reach and approvals — then the proof, and what it costs to grow into

Members / user limits

Home row T (Add members) opens Grow’s user-limit path. Invite by email up to your tier's user limit; the limit for each tier is read from the license and shown on Your plan, never typed here (founder t591u — Beta treated as Elite full system view, unlimited users).

Users and snapshot

Under Grow: who currently has access, and a point-in-time snapshot of what the company brain looked like on a date. A user sees the snapshot for their own scope, which is how a new joiner reads history without being handed the whole corpus.

Saved summaries

An answer you keep. A summary is saved with the sources it was built from, so reopening it later shows the same cites rather than recomputing against material that has since moved. Saved summaries carry the scope they were made in and travel no further.

What a member can reach

A user reaches the scope its license holder granted and nothing beyond it. There is no dump of a company's private material to a member who was not granted it, and no cross-company reach at all: ask something outside your scope and it refuses by name rather than answering from material you were never given.

Plan (tiers)

Your plan (P): Individual, Professional, Elite — user limits and library grow with the plan. Copy and CTAs come from offer plan-* properties. Checkout only when Stripe is bound.

Outward claims and refusals

For anyone writing marketing or sales copy, before publishing a landing page or a pitch: the allowed external claims and the forbidden ones, as two lists. Read them and do not ship a forbidden line. The register is the same one the build gates read, so a claim that would be refused in a deliverable is refused in a headline.

What each plan reaches

The same six facts for every plan, read from the entitlement the product enforces rather than written here.

Every plan starts with a 7-day free trial. No card is collected until it converts, and you can cancel inside the trial without being charged. After that it renews automatically at the price shown until you cancel.

What you get	Individual	Professional	Elite
Deliverable kinds	All 60	All 60	All 60
Kinds you can run from the command line	60 of 60	60 of 60	60 of 60
Vetted library	Your own documents	18 domains · 18 with vetted sources today	18 domains · 18 with vetted sources today
Library shelves	none — builds from your own documents	company-building + science	company-building + science
Why that shelf	Nothing is vetted for you, so nothing can be stale on your behalf.	Founder 2026-09-27 16:09 PT: "Actually give professional that too" — the full shelf, as Elite.	Elite pays for the full shelf plus currency that cannot be overruled by a deadline.
User limit	3	25	Unlimited
Source freshness	Manual stamps	Manual stamps	Enforced on every build
Written digest	Not included	Not included	Quarterly
Named contact	Not included	Not included	[email protected]

The board

The whole system on one surface, and it explains itself.

Each tab teaches its own mechanism and carries the working half beneath it. Nothing here is a number you cannot chase — every figure names the instrument that produced it.

Show every surface on the board

chat

Your team, in the same place the work is proven

ask

A line from your own material, with its file and line

sources

What came in, and what was built from it

doctrines

Your rules, consulted before anything is built

chain

Every build linked to the one before it

bloom

The seat a model may sit in, and the switch that empties it

sandbox

Build freely; nothing ships without you

upload

Bring material in; you approve before it indexes

generate

The files this build produced, each openable

prod

Everything you sell, on every surface

signal

What the market asks for, matched to what you ship

invest

Market numbers, each derived from a cited source

system

Everything running, live

checks

Seventy gates that explain themselves

Proof, and what each number does not mean

Why believe any of this? Every figure below carries the file and line it was measured in, and the sentence that says what it does not mean.

Show the seven figures, and what each one does not mean

Same declaration in, same bytes out

The same request, run five separate times from a cold start, produced an identical result every time - not similar, identical to the byte.

What this does not mean: It means the BUILD is repeatable. It does not mean every screen looks the same on every visit: a page showing live status reads that status when you open it, and it will have moved on. Anyone claiming every response is always identical is overstating it.

measured indocs/GCBC-DETERMINISM-AND-PORTS.txt:9-18

Your information stays on your machine

We scanned this installation from the surrounding office network. Every part of the compiler refused the connection - it answers only on the machine it runs on. The one service that did answer is our own local code storage, which is not part of the product.

What this does not mean: Measured on one installation, on one date. It describes how this deployment behaves, not a promise about how yours will be configured.

measured indocs/GCBC-DETERMINISM-AND-PORTS.txt:38-53

Answers come back instantly

A typical question comes back in about seven thousandths of a second. The board's own screens draw in under two thousandths. Measured ten times each.

What this does not mean: These are measurements, not a service level. We have not committed to a speed in a contract, and we will not present a number we merely observed as one we owe you.

measured indocs/GCBC-GRADE.txt:53-59

Every answer shows you where it came from

2,496 documents indexed, with every passage keeping the file it came from and the exact lines within it. That is what lets any answer show you its own source rather than asking you to trust it.

What this does not mean: Measured 2026-09-01. The index is re-checked before this figure is quoted, because a number about a corpus goes stale the moment the corpus changes.

Fourteen surfaces are self-contained

We walked every file behind each of the board’s fourteen surfaces and resolved every relative import. Not one reaches outside its own folder. Fourteen of fourteen.

What this does not mean: This proves the source is self-contained. It does not prove that any surface boots on its own, which is a stronger claim this test does not make. And the fourteen are the board’s tabs, not fourteen separate products — the earlier wording said both of those things and neither was measured.

measured indocs/GCBC-PROVABILITY.txt:12-20

154 of 487 checks have been made to fail on purpose

We deliberately broke seventy of our own checks to find out which ones would notice. Eleven caught it. Fifty-nine did not, and we are publishing the list.

What this does not mean: This is the worst number we have and it is here on purpose. We refuse to combine it with a second, friendlier measurement to produce a bigger one - our own review calls that combined figure far too generous. The measurement also needs a quiet machine; under load it has read low.

measured inHANDOFF-GCBC-2026-09-01.md:16

'We do not know' is an answer, not a zero

When the system has never seen something, it says so. It never reports 'nothing found' as though it were a measured zero, and a check that could not run is never recorded as one that passed.

What this does not mean: This is a discipline, not a feature you switch on. Its value is that a gap in what we know reaches you as a gap, rather than as a confident answer.

measured indocs/GCBC-DUE-DILIGENCE-PACKET.txt:138-149

For investors

An AI infrastructure engine

GCBC is a compiler that converts domain expertise into provable, sellable deliverables across 60 output kinds (10 categories) and eighteen domains. The moat isn’t the output — it’s that every claim is traceable and every build is reproducible, so the same input yields the same verified product every time, with no model and no human in the assembly path. That turns expertise into an asset that ships at software margins instead of services hours. We call it integrity at scale — and it’s the one thing a raw language model structurally cannot promise.

Show the investor framing

Serving needs no model

The answer path and the build path make no model call, so the cost of the ten-thousandth deliverable is the cost of the first: file reads and a transform.

Same declaration, same bytes

Five separate processes, one hash. The transform is deterministic over its input.

The gates are tested like silicon

154 of 487 checks have been made to fail on purpose, on record. A gate that has never failed is not a gate.

We publish our own worst number

Ask for the diligence packet and you get the internal grades, the open holes and the measurements behind them — before you ask twice.

Request the diligence packet

Beta

90 days for $99

Run the whole product on your own machine for 90 days for one payment of $99. Not a trial of a cut-down version and not a demo: the same compiler as Elite — all 60 kinds, full system view, unlimited users, the same refusals. One payment, 90 days, no renewal and nothing to cancel. This one does not renew. It is a single payment for 90 days, and there is nothing to cancel.

Tell us what you think of it and get 20% off any plan

Leave a review or a comment about the product during the beta and we take 20% off whichever plan you go on to buy, at every level. You get the same 20% whether the review is positive or negative — we are buying the opinion, not a good one. If you post it anywhere public, please say that you received a discount for writing it.

Start the 90-day beta — $99

4 ways to own it

One product, 3 plans. Licensed per person for Individual and per organization for Professional and Elite. Billed monthly.

Beta

$99 / one payment · 90 days · no renewal

The whole product for 90 days.

Buy the Beta on Gumroad — $99

Sold and delivered by Gumroad. Your receipt and download stay in your Gumroad library.

Individual

$299 / per month

Build from what you already have.

You have a folder — or a drive, or a decade — of work that has never been usable by anything. Individual turns it into something you can build from.

Ask across everything you have written and get the answer with the file and line it came fromdocs/GCBC-DUE-DILIGENCE-PACKET.txt:15-16
On a local Gumroad instance: runs offline on your own hardware, bound to loopback. On hosted Command (gcbc.reaveslabs.ai): the same cite-or-refuse compiler in your workspace — not a claim that the browser tab never uses the networkdocs/GCBC-DETERMINISM-AND-PORTS.txt:38-53
Same request, same file: a recorded compile replays byte for byte
Runs with no model at all — every answer is arithmetic over an index on your own machine, which is why the same question returns the same passage every timedocs/GCBC-DETERMINISM-AND-PORTS.txt:38-53
Regulated walls open when obligation predicates answer yes (health-records / minors / financial-advice walls in domains/gcbc-obligations.xml) — library count remains 0

Not in this plan. The vetted source library, blending it with your documents, and adding your own sources to it. Individual builds from YOUR material. Library membership stays zero (FOUNDER t709u).

Subscriptions open here soon. Checkout for this plan is not switched on yet, so this button does nothing today. The Beta below is on sale now.

Most complete

Professional

$2,499 / per month

Never build from an empty shelf.

Everything in Individual, plus the thing that changes what you can build: a curated library of pre-vetted sources, dated and organized by domain, ready on day one.

All 60 deliverable kinds — decks, briefings, reports, curriculum, checkers, architecture documents and the rest
The whole vetted source library, company building and the sciences across eighteen domains — every entry carries its authority tier and its freshness class
Blend your material with the library in one deliverable, and see at a glance which facts came from which
Add your own sources into your library, permanently

Not in this plan. The regulated domains stay walled, automatic freshness, the Investor pack, and the direct line.

Subscriptions open here soon. Checkout for this plan is not switched on yet, so this button does nothing today. The Beta below is on sale now.

Elite

$4,999 / per month

Current, without being asked.

Everything in Professional, plus the full library, the regulated domains, and a service layer that keeps it all fresh without you filing a ticket.

All eighteen library domains, not half
The regulated domains — student privacy and finance, where getting provenance wrong has consequences
Every source is re-checked against its freshness window on every build — fresh, stale or expired — and a library carrying an expired source will not ship at all
A quarterly written digest of what moved in your domains, delivered rather than requested, and a one-page currency statement on demand
Priority build queue, early access to new deliverable types, and a named contact rather than a form — Reaves Labs Elite Support (the Reaves Labs Elite team) at [email protected]; one accountable company team for digest/re-verify and the priority queue, not a personal founder cell

Not in this plan. Nothing in the catalog. Elite is the whole library and the service layer (digest + priority queue are MUST-PROVE under t538u — not deleted).

Subscriptions open here soon. Checkout for this plan is not switched on yet, so this button does nothing today. The Beta below is on sale now.

Already a member? Manage your membership

To cancel, email [email protected] from the address on the license and it stops at the end of the period you have paid for. No call, no retention script.

For help, email [email protected]. To cancel, email [email protected] from the address on the license. Read the terms at https://reaveslabs.ai/terms.html.

Every price on this page quotes a founder ratification dated 2026-09-03 and is recorded in the offer node it is read from. No price originates on this page.

What GCBC fixes for you

The new business owner

The solo professional

The fifteen-year company

The thirty-year regulated company

The developer

The team that connects an LLM to DRE

Plans and prices

Individual

Professional

Elite

Download and first run, click by click

Connect your LLM to DRE

What each tool does

Everything you can do in GCBC

Cite-or-refuse Ask

Scope: My files

Scope: Company

Scope: Investor pack

Prompt chips

Ingest (Desktop, folder, or file)

Connectors (every plan)

Connectors coming next

What stays on this computer

Corpus teaching after refuse

Answer verification

Your LLM, connected to DRE (MCP)

Chat

Encrypted sending

Meetings

Sources

Doctrine

Sandbox

Ingest (in Build)

Ask inside Build

Compile (sixty kinds / ten categories)

Prove

What shipped

System health

Index fingerprints and replayable receipts

Security hash chain

Connector safety and download checks (S7 and S6)

Rebuild-check quotes

Four-quadrant proving ground

Vetted library / Blend / Add sources

Regulated domains + freshness

Add members / user limits

Library reach

Your company

Approvals

Your plan

Investor pack

Quarterly digest

Priority queue and named contact

Outward claims and refusals

Chat (from Grow)

Get in / access

Ask

Founder Intent & Strategy

Search & HOW TO

Which plans your needs leave standing

How it works

How it works, and why you can check it

One way in

It reads, it does not invent

Nothing is built until it is understood

It knows what complete looks like

Your data stays yours

Get in

How your material gets in

What it builds from your folder

Chat and meetings

Ask, and it answers with the line it came from.

Which one are you?

The new business owner

The solo professional

The fifteen-year company

The thirty-year regulated company

The developer