whitepaper

Claim

Authority Matrix — the L2 STRUCTURE layer of governance: boundary files cap spend per agent; this node says WHO decides WHAT. domains/authority-matrix.xml:6-6

This matrix states which outward claims GCBC may make and what proves each one, so that no claim reaches a buyer without a proof that a reviewer can run for themselves. domains/authority-matrix.xml:295-295

The authority for GCBC's outward claims is the claims ledger and its proofs, not marketing copy; counsel owns the wording of terms, privacy and student data, and the founder owns rulings. domains/authority-matrix.xml:300-300

Claim for Whitepaper. Customer ask centers on a Whitepaper for GCBC. Deep sourced research write-up. You get: A paper a skeptic can check. Raw ask: Build a Whitepaper for GCBC.

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

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

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

Evidence & spans

Every decision routes per its class; no agent invokes the founder directly; zero autonomous denylist actions; founder needed only at defined triggers. domains/authority-matrix.xml:18-18

The GCBC legal claims ledger measured nine of fifteen rows met on 2026-09-24, run by check-ledger against the live page, with the remaining rows owned by counsel or awaiting a founder ruling rather than hidden. domains/authority-matrix.xml:281-281

The claim gate is proven to fail: with three green controls in place, removing a renewal notice, changing a renewal amount, removing the cancel line or stripping the review terms each makes the page check exit one. domains/authority-matrix.xml:282-282

The review incentive on the page carries its endorsement terms, stating that a negative review earns the same discount as a positive one and asking reviewers to disclose the discount, and property P23 verifies it. domains/authority-matrix.xml:283-283

Every answer on the GCBC board comes from what the page publishes, quoted whole with the file and the line it came from, and anything the published corpus cannot answer is refused rather than composed. domains/authority-matrix.xml:284-284

The cancellation method is stated beside the prices on the live page in one sentence a customer can act on, and property P22 verifies in a real browser that the cancel line is present and not empty. domains/authority-matrix.xml:296-296

On 2026-09-24 the built GCBC page held all twenty-two of its declared properties in a real browser, including that every comparison-table cell equals the entitlement or manifest value it is drawn from. domains/authority-matrix.xml:297-297

A counsel facts packet is generated from the nodes, not typed: it lists the recurring terms exactly as Stripe bills them, the trial and cancel lines, where data goes on each door, and the student-data answer. domains/authority-matrix.xml:298-298

Evidence & spans for Whitepaper. Customer ask centers on a Whitepaper for GCBC. Deep sourced research write-up. You get: A paper a skeptic can check. Raw ask: Build a Whitepaper for GCBC.

Detail for Evidence & spans: this Whitepaper stays locked to a Whitepaper 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 Whitepaper for appears in the working lines, not only the title.

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

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

Audience

RLL receives only the buyer's name and email address through Stripe checkout, and that is the only customer data an RLL server records; everything a customer ingests stays on their own machine or browser. domains/authority-matrix.xml:288-288

An accessibility conformance statement is published on the page because the WCAG 2.1 AA checks pass at both the desktop and phone viewports, and public-sector buyers ask for that statement. domains/authority-matrix.xml:289-289

Audience for Whitepaper. Customer ask centers on a Whitepaper for GCBC. Deep sourced research write-up. You get: A paper a skeptic can check. Raw ask: Build a Whitepaper for GCBC.

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

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

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

Reuse path

Every objective claim on the page is backed by a receipt a reviewer can run, every recurring charge is disclosed before billing, and every incentive for a review carries its endorsement terms. domains/authority-matrix.xml:290-290

A claim is trusted only after its checker has been shown to fail on a planted defect of exactly the kind it guards, because a check that has never failed has measured nothing at all. domains/authority-matrix.xml:291-291

Reuse path for Whitepaper. Customer ask centers on a Whitepaper for GCBC. Deep sourced research write-up. You get: A paper a skeptic can check. Raw ask: Build a Whitepaper for GCBC.

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

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

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

Limits

The reaveslabs.ai terms of service were last updated on April 1, 2026 and do not name GCBC or describe renewal, so the terms gap remains open and belongs to counsel, not to the page copy. domains/authority-matrix.xml:285-285

Each customer controls its own data and RLL never receives it; on 2026-09-24 every hosted GCBC server endpoint returned 404, and uploaded files, indexes and questions stayed in the customer's browser tab. domains/authority-matrix.xml:286-286

Forbidden marketing claims are screened on every build of the page, and the generator refuses to write a page that contains any of the nine forbidden claims declared in the claims register node. domains/authority-matrix.xml:287-287

Figures measured on RLL's own installation are not yet labeled as such on the page, so a reader could take them for what they will receive; that row stays open until the clause is added. domains/authority-matrix.xml:299-299

Limits for Whitepaper. Customer ask centers on a Whitepaper for GCBC. Deep sourced research write-up. You get: A paper a skeptic can check. Raw ask: Build a Whitepaper for GCBC.

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

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

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

Bound to your ask

For a per-organization license, an organization means the people the license holder names, up to the user limit of the plan, as the founder ruled on 2026-09-24 in the session record. domains/authority-matrix.xml:292-292

The Individual, Professional and Elite plans carry user limits of three, twenty-five and unlimited users, enforced by the signed license rather than by a sentence on the page, and a license cannot raise its own limit. domains/authority-matrix.xml:293-293

On 2026-09-24 the claim gate falsifier passed three green controls and caught four planted defects, exiting one on each, and it exited three when asked for a property that does not exist. domains/authority-matrix.xml:294-294

Bound to your ask for Whitepaper. Customer ask centers on a Whitepaper for GCBC. Deep sourced research write-up. You get: A paper a skeptic can check. Raw ask: Build a Whitepaper for GCBC.

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