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.
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.
| Traditional DB | Chandra Term | gr-identity | Your Industry Term |
|---|
| Concept | Closest industry resonance | Acknowledged | Internal nickname (optional) |
|---|---|---|---|
| Chain | Ordered immutable CU sequence — the audit record. Similar to: | ||
| GABA Cert | Governing attestation binding Spoke to Hub. Closest analog: | ||
| Marshaller | Portfolio-level orchestration role. May resemble: |
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.
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.
Tell us about the systems your organization runs today. This helps General Reasoning scope the integration path and give you an honest picture of what onboarding actually involves. Skip this step if you’re starting fresh or prefer to discuss it directly.
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.