The governed infrastructure for every Chandra deployment.

chandrahub.net is the trust anchor for the Chandra ecosystem. Every governed deployment connects here. Every GABA cert traces here. Every examiner inquiry starts here.


What chandrahub is.

Chandra is an open protocol for append-only, hash-chained, attributed audit records. A single organization running Chandra is a tree. chandrahub.net is the forest — the governed federation of every Chandra deployment that has established a trust relationship here.

Every deployment in the forest holds a GABA cert issued against chandrahub.net as the forest authority. That cert is the cryptographic link between a specific deployment's audit trail and the trust infrastructure of the broader ecosystem. When an examiner asks to verify an audit record, the chain of verification terminates here.

The audit trail doesn't end at your organization. It traces to here.

Find what you need.

For regulators
Examiner Reference
Verify GABA certs, read CUs, trace audit opinions to work papers. No prior Chandra knowledge required.
For auditors
Auditing with Chandra
SSAE 18 engagement types, governed work papers, opinion issuance, chain of custody.
For organizations
Being Audited
What your audit trail contains, how to produce evidence for examiners, retention policies by standard.

How the forest works.

Every governed Chandra deployment is structured as a hierarchy: context units aggregate into spokes, spokes aggregate into hubs, hubs aggregate into domains, domains aggregate into instances, and instances connect to the forest. chandrahub.net is the forest root.

A deployment joins the forest by producing a GABA cert — a Governed AI Boundary Attestation — that declares the deployment's governance posture, permitted agent tiers, compliance profile, and forest membership. That cert is issued by gr-identity, attested by General Reasoning, and recorded as an immutable context unit on the forest chain. Membership cannot be backdated or edited.

The result is a verifiable chain of custody from any individual audit record in any deployment all the way to the forest authority. Regulators and examiners can follow that chain without access to the underlying deployment infrastructure.

One column addition per auditable table. Everything else is governed infrastructure.

Connecting your deployment.

External organizations integrate with the Chandra audit infrastructure through gr-identity, General Reasoning's identity and governance platform. The integration requires one column addition per auditable database table. No schema redesign. No audit middleware. No separate compliance system.

Every write your application makes appends a context unit to the corresponding Chandra spoke. The spoke is the auditable record for that object instance. The hub is the auditable collection for that table. The domain is the auditable universe for your organization. The chain is the compliance record.

Examiner reference Integration guide

General Reasoning, Inc. · Birmingham, Alabama · 2026
Enterprise inquiries: inquiries@genreason.com
Page integrity: Pending chandrapassport deployment — CU verification active post-launch.