Legal Obligation Register — Documentation

Register and operationalise legal and regulatory obligations from source instruments through controls, evidence, verification, compliance assessment, exceptions and corrective actions — a single defensible line of sight from what the law requires to how the organisation proves it complies.

In this section

• 00_OVERVIEW — what the application is for, the operating chain, and the five functional areas.
• 01_QUICK_REFERENCE — the menu map, all 18 models, the status vocabularies, and the demo data story.
• 02_SYSTEM_DIAGRAM — an interactive entity map (hub tables, per-area tabs and a curated top-level flow).

The application in one paragraph

A LegalInstrument (Act, regulation, licence, permit, contract) and its Provisions are the source. Each obligation drawn from a provision becomes a governed LegalObligation — typed, risk-rated, owned by a BusinessUnit, with a frequency and due rule — and, where recurring, spawns dated ObligationOccurrences. Controls are mapped to obligations (ObligationControl), EvidenceRequirements define what must be kept, and EvidenceItems are the actual records. VerificationPlans/Verifications test control effectiveness; ComplianceAssessments record assurance status. Where something fails, an Exception is raised with CorrectiveActions; ObligationReviews keep interpretations current, InstrumentChanges flag source amendments, and Communications log correspondence — all under the framework's audit trail and soft-delete.