What a compliance obligation is
Every regulated deliverable, a safety narrative, a CSR section, a health-authority response, traces back to a specific requirement in a specific guideline: ICH E3, a PSUR module, an internal SOP. Most tools treat that link as tribal knowledge, held in a reviewer's head or a checklist nobody updates. We built Altio COG™ to hold it as data instead.
How the graph works
The Compliance Obligation Graph encodes what a framework requires, as structured nodes: guideline, section, required content, applicable data. Today it holds 2,173 obligation nodes. When Altio drafts a deliverable, it is not generating prose and hoping it matches the template, it is walking the graph, pulling the passage that satisfies each obligation, and citing where that passage came from.
Why it extends
The same mechanism that runs a signal assessment against pharmacovigilance guidance runs a Clinical Study Report section against ICH E3, because both are the same operation: match obligation to evidence. Encode a new domain's requirements once, into the graph, and the obligation engine already knows how to hold it accountable. That is the bet behind COG, patent pending, and it is why we do not rebuild the platform every time we add a domain.