Navigation
Home Investors
The Case
The SaaS Problem The Graveyard The Five Levels Why Lisp
Platform
Platform Overview Deployment Migration Mainframe Path Before You Ask For Workflow Geeks
Advisory
Advisory Board Legal & Clinical
The Stack
Chandra Protocol CRC Standard GABA Standard Aegis Genera
Speak Your Domain

The General Reasoning Stack speaks all domain languages. Describe yours.

Every regulated vertical uses its own terminology for the same structural concepts. This questionnaire maps your domain’s language onto the Chandra Protocol vocabulary — producing a personality layer that allows Chandra-based systems to speak your industry’s native terms without changing the underlying attestation architecture.

Start with the glossary below. Understand what each Chandra term means before filling in your domain equivalents. Then select your domain, review the pre-filled terms, correct anything that doesn’t fit, and submit. Your mapping is recorded in the Chandra audit chain and becomes the foundation for your spoke configuration.

Chandra Term Glossary

These are the canonical terms of the Chandra Protocol. Each has a precise architectural meaning. Read them before touching the mapping table.

Structural Hierarchy
CHPInstance
A discrete deployment of the Chandra stack serving a single regulated organization or firm. The top-level container. Analogous to a database cluster — isolated, self-contained, governed.
CHPDomain
A governed partition within an Instance, corresponding to a distinct line of business, regulatory program, or operational area. The database within the cluster — a coherent scope of records and rules.
CHPHub
The governing authority within a Domain. A Hub defines the rules, roles, and scope families that apply to all Spokes beneath it. Analogous to a table schema — it declares structure and enforces conformance.
CHPSpoke
A governed entity operating under a Hub. Spokes are the primary actors — the subjects of attestation. In practice: a firm, a registered person, a system, a site, or any bounded operational unit that produces compliance records.
CHPCU Stable ID
The permanent, never-reused identifier assigned to a Spoke at registration. Every Context Unit written by or about that Spoke carries this identifier. Reusable identifiers are architecturally incompatible with Chandra’s append-only model.
CHPContext Unit (CU)
The atomic record of the Chandra system. Every write is a Context Unit — append-only, hash-chained to its predecessor, and immutable after commit. There are no updates, no deletes. The CU is what regulators examine.
Behavioral & State
CHPSpoke Suspension
A governed state in which a Spoke is prohibited from producing new Context Units. The Spoke record persists — the chain is intact — but the entity is operationally halted. Corresponds to regulatory revocation, disqualification, or curtailment.
CHPCU Write / Attestation Event
The act of committing a Context Unit to the chain. Every business event that must be provable — a filing, a transaction, a control test, a signature — is represented as a CU write. This is the moment that creates regulatory defensibility.
CHPChain Traversal / Audit
The act of reading and verifying the ordered sequence of Context Units for a Spoke or Domain. An examiner traversing the chain sees the complete, unbroken, hash-verified history of every attested event. No reconstruction required.
Net-New Chandra Concepts — No domain equivalent exists; your organization adopts these terms
NEWChain
The ordered, immutable, hash-linked sequence of all Context Units produced by or about a Spoke. The Chain is the audit record. It cannot be reordered, edited, or selectively disclosed. It either exists intact or it does not.
NEWGABA Cert
A governing attestation that binds a Spoke to a Hub under certified authority. The GABA Cert is what makes a Spoke governed rather than merely registered. It is the architectural equivalent of a license, a BAA, an ATO, or a C3PAO certification — but issued within the Chandra system itself.
NEWMarshaller
A behavioral role — not a data structure — that coordinates operations across multiple Instances or Spokes simultaneously. The Marshaller handles portfolio-level orchestration: multi-firm operations, multi-site submissions, cross-domain workflows.

Select Your Domain

Choose your regulated vertical. Pre-populated terms will flood the mapping table. Review each one and correct anything that does not match your organization’s usage. Select Other if your domain is not listed.

Select a domain above to load the mapping table.

What happens after you submit

Your personality mapping is immediately written as a Context Unit in the Chandra audit chain. On success, your permanent chain unit ID is displayed on screen — the immutable Chandra reference for this configuration record.

The General Reasoning team reviews all submissions and will contact you to discuss spoke configuration, implementation scope, and next steps.

Platform overview Chandra Protocol

General Reasoning, Inc. · Proprietary & Confidential
Audit substrate: Chandra Protocol · genreason.com/personality-mapping
Enterprise inquiries: inquiries@genreason.com
© 2026 General Reasoning, Inc. · All rights reserved