Obligation Engine
Deadlines are not a calendar problem. The ones that cost money are only visible when lease terms, permit status and production volumes are read together — which is exactly the join no single system of record can make.
Sum of modeled value at risk if each item lapses unremedied.
Lapse would sever acreage, void a permit or trigger a royalty claim.
Invisible to any one system — required joining two or more domains.
The engine will not assert these until the well identity resolves.
Recurring filing. Roughly 3353 line items in this cycle, assembled by the package agent and released by a named filer.
Deadline corpus: recurring statutory cadence, machine-checkable.
Volume domain: line items derived from the allocation layer and traced to a measurement point.
Gate: assembled to submission-ready; a named person releases the filing.
- Due
- Aug 17, 2026
- Exposure
- $177k
It does not file anything
A cleared obligation is a claim that evidence exists. The filing itself goes through the Filing Desk under a named human, because agency Rules of Use bind submissions to an identified person.
It does not guess through an identity break
Where the well identity is unresolved, the item is surfaced but the exposure figure is withheld from rollups until a human merges or separates the records.
It does not interpret the lease
Continuation language is read and cited, not construed. Where the clause is ambiguous the item routes to counsel rather than resolving itself.