General Reasoning

Industry Configurator genreason.com
1
Industry
2
Levels
3
Map Terms
4
Workflows
5
Current Systems
6
Submit

Select your industry

Choose your vertical. Pre-populated terminology floods the mapping table in Step 2 — review and correct anything that doesn't fit your organization's usage.

The General Reasoning stack can be configured for virtually any industry. Selecting your vertical pre-loads terminology, workflows, and governance patterns — reducing initial system setup from weeks to minutes.

Review logical industry Levels

Based on your industry, this is the logical Level/Hub/Spoke spine the personality file will emit. Physical Chandra Instances are not chosen here; Spine Editor computes them later from CRC inputs.

Logical spine only — physical packing deferred The Configurator emits logical Levels, Hubs, Spokes, forms, and event/CU templates. Spine Editor later applies CRC isolation-surface sizing to decide how many physical Instances are needed and how whole Levels are packed into them.
ISS — Isolation Surface Score Each tier shows an ISS derived from the formula 100 × Cost(S*) / Cost(T) — how close this environment's typical principal population is to its own cost-optimal surface size. A score of 100 means the environment is already at the minimum-cost partition. Lower scores mean the surface is wider than optimal, carrying more risk-adjusted cost than a well-partitioned deployment of the same scale would require.
75–100 · Efficient Near-optimal surface size 40–74 · Suboptimal Wider than optimal, manageable 15–39 · Overextended Significant excess surface 1–14 · Critical Surface far exceeds optimal — consolidation needed

Map your terms

Pre-populated terms are filled for your industry. Correct anything that doesn't match your organization's usage. Open the Term Reference if you need Chandra concept definitions.

Chandra is an immutable, append-only attestation chain with its own precise native vocabulary. It can surface your industry’s terms instead — so audit records, workflow gates, and examiner reports read in language your organization already uses.
Structural Hierarchy
CHPInstance
A discrete deployment of the Chandra stack serving a single regulated organization or firm. The top-level container — isolated, self-contained, governed.
CHPDomain
A governed partition within an Instance, corresponding to a distinct line of business, regulatory program, or operational area.
CHPHub
The governing authority within a Domain. Defines the rules, roles, and scope families that apply to all Spokes beneath it.
CHPSpoke
A governed entity operating under a Hub — the primary actors and 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.
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. 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 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.
CHPChain Traversal / Audit
Reading and verifying the ordered sequence of Context Units for a Spoke or Domain. An examiner sees the complete, unbroken, hash-verified history of every attested event.
Net-New Chandra Concepts — No industry equivalent; 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.
NEWGABA Cert
A governing attestation that binds a Spoke to a Hub under certified authority — the architectural equivalent of a license, a BAA, an ATO, or a C3PAO certification, issued within the Chandra system.
NEWMarshaller
A behavioral role that coordinates operations across multiple Instances or Spokes simultaneously. Handles portfolio-level orchestration: multi-firm operations, multi-site submissions, cross-domain workflows.
Part A — Term Mapping
Traditional DBChandra Termgr-identityYour Industry Term
Part B — Net-New Chandra Concepts — Acknowledgment & Optional Internal Nickname
ConceptClosest industry resonanceAcknowledgedInternal nickname (optional)
ChainOrdered immutable CU sequence — the audit record. Similar to:
GABA CertGoverning attestation binding Spoke to Hub. Closest analog:
MarshallerPortfolio-level orchestration role. May resemble:

Describe your processes

Every industry runs on governed sequences — approvals, submissions, reviews, attestations that happen in order and leave a record. DXMachine builds those sequences as governed workflows on top of the Chandra chain. Check what applies, customize steps, add your own.

Each workflow becomes a governed value stream in DXMachine — every gate transition writes a Chandra CU. Pre-populated workflows are known patterns for your industry. Check the ones that apply, edit steps to match your process, and add any that aren’t listed. ISS (Isolation Surface Score) on each workflow reflects how well-contained that workflow is as an isolation surface, based on its distinct actor count and the privilege level implied by its outputs. 100 = optimally partitioned. Thresholds: 75–100 Efficient 40–74 Suboptimal 15–39 Overextended 1–14 Critical. Workflow ISS is informational only and does not affect your submission.
Draft saved locally
Add a workflow specific to your organization

Optional. Applies to any industry. Declares the guiding principles your hub is subject to and configures examiner access for a third-party governance review — COSO GP1–12.

Current systems, ETL, and data quality — optional

Tell us about the systems your organization runs today, and whether the source data is clean enough to govern as-is. This helps General Reasoning scope the integration path, identify duplicate-record risk, and determine whether data cleansing, deduplication, or entity-resolution review should be included in onboarding.

Optional — but useful. Every organization starts somewhere. The General Reasoning stack is designed to ingest from existing systems, but migration is not just a transport problem. Where source data contains duplicate people, inconsistent identifiers, missing SSNs, conflicting addresses, stale records, or spreadsheet-era workarounds, onboarding may include governed data cleansing before records are loaded into Chandra and DXMachine. Remediation decisions can themselves be written to the Chandra chain: rule version, match confidence, merge decision, reviewer override, and exception status.
Primary compliance or records system (optional)
Data quality / duplicate-risk profile (optional)

Some implementations require more than extraction and loading. If records are incomplete, duplicated, or inconsistently identified, General Reasoning can include a governed cleansing and deduplication phase before import.

Additional context (optional)

Submit your configuration

The industry vocabulary and governed workflows you've mapped are directly importable into DXMachine. Your instance can be configured within hours of submission. This submission is written as a Context Unit in the Chandra audit chain.

Your submission is written as an immutable Context Unit in the Chandra chain the moment it is received — a permanent, hash-chained record that this configuration was declared by your organization. General Reasoning uses it to provision your spoke within hours.
Contact details
Audit record. This submission is written as a Context Unit in the Chandra Protocol audit chain — append-only and hash-chained. Your mapping receives a permanent chain unit reference. By submitting, you confirm these mappings reflect your organization's operational usage and that you are authorized to make this declaration on its behalf.
Chain unit reference returned on submission.
General Reasoning follows up within 10 business days.
Generated personality JSON
General Reasoning, Inc. · Chandra Protocol · inquiries@genreason.com

© 2026 General Reasoning, Inc. · All rights reserved