For auditors

Auditing with Chandra

Chandra provides the governed work paper infrastructure for attestation engagements. Every audit act — from engagement acceptance through opinion issuance — is recorded as an immutable, attributed context unit on the engagement spoke. The chain of work papers is permanent and independently verifiable.


Engagement types and SSAE 18 mapping

Chandra-based engagements map directly to SSAE 18 engagement types. The engagement type declared at acceptance determines the structure of the engagement spoke and the form of the opinion CU.

SSAE 18 AT-C Section 205 Agreed-Upon Procedures engagement_type: agreed_upon_procedures Opinion CU: practitioner findings, not conclusion SSAE 18 AT-C Section 315 Examination engagement_type: examination Opinion CU: positive assurance conclusion SSAE 18 AT-C Section 320 Review engagement_type: review Opinion CU: negative assurance conclusion

Auditor independence

When General Reasoning engages as the auditor on a Chandra-based engagement, standard independence requirements apply under SSAE 18 and applicable AICPA standards. The engagement spoke is independent of the auditee's Chandra infrastructure. The auditee cannot write to, read, or modify the engagement spoke.

For third-party auditors using Chandra as their work paper platform, the engagement spoke is provisioned under the auditor's tenant, not the auditee's tenant. The auditee's records are read-only from the engagement perspective — the auditor reads CUs from the auditee's spokes as evidence, but does not write to them.


The engagement spoke

Every engagement is anchored to a dedicated engagement spoke. All audit work is recorded as CUs on this spoke in chronological order. The spoke cannot be deleted, archived, or modified. It grows from acceptance to opinion and then closes.

CU types in an engagement spoke

acceptance Engagement acceptance — scope, standard, parties planning Planning CUs — risk assessment, materiality, procedure design procedure One CU per audit procedure performed References evidence CU ids from auditee chain finding One CU per identified exception or observation severity: observation / deficiency / material_weakness References procedure and evidence CU ids management_response Auditee management response to findings opinion Terminal CU — the audit opinion References all finding CU ids Immutable once written

Writing the acceptance CU

POST https://chandrahub.net/api/v1/engagement/create { "engagement_type": "examination", "auditee_tenant_id": "acme-uuid", "standard": "soc2_type_ii", "scope_declaration": "...", "retention_days": 365 }

Returns the engagement id and the genesis CU id for the engagement spoke. All subsequent engagement CUs reference this engagement id.


Recording audit procedures

Each audit procedure performed is recorded as a procedure CU. The procedure CU references the evidence CU ids from the auditee's chain that were examined in performing the procedure. This creates a direct, verifiable link from the work performed to the specific records examined.

POST https://chandrahub.net/api/v1/engagement/{id}/procedure { "procedure_description": "Inspected user access provisioning records", "evidence_cu_ids": ["cu-uuid-1", "cu-uuid-2", "cu-uuid-3"], "period_start": 1720000000, "period_end": 1748000000, "result": "no_exception" }

Recording findings

Each identified exception or observation is recorded as a finding CU referencing the procedure and evidence CUs that support it.

POST https://chandrahub.net/api/v1/engagement/{id}/finding { "finding_type": "deficiency", "severity": "medium", "description": "...", "procedure_cu_id": "cu-uuid", "evidence_cu_ids": ["cu-uuid-4", "cu-uuid-5"] }

Issuing the opinion

The opinion CU is the terminal record on the engagement spoke. Once written, it cannot be modified. If a revised opinion is required, a new engagement must be opened referencing the superseded engagement.

POST https://chandrahub.net/api/v1/engagement/{id}/opinion { "opinion_text": "...", "finding_cu_ids": ["cu-uuid-6", "cu-uuid-7"], "conclusion": "unmodified" }

The response includes the opinion CU id. This is the id provided to the auditee and to any relying parties as the reference for the issued opinion.


Chain of custody

The Chandra engagement spoke is the complete chain of custody for the audit work papers. From the acceptance CU through the opinion CU, every act by every auditor is recorded, attributed, and timestamped. The chain is independently verifiable by regulators, auditees, and relying parties through chandrahub.net.

No separate work paper management system is required. The engagement spoke is the work paper file. The opinion CU is the signed deliverable. The lineage is the audit trail of the audit.

The engagement spoke is the work paper file. The opinion CU is the signed deliverable.
Examiner reference Engagement inquiries

Chandrahub.net · General Reasoning, Inc. · Birmingham, Alabama · 2026
Examiner Reference · Compliance · Contact
Page integrity: Pending chandrapassport deployment — CU verification active post-launch.