Stale obligations
Rules change. Canon packs not updated create documents valid last year but not today. Operations running on stale obligations carry undetected exposure at every transaction.
Public Intel
Governed regulatory canon.
The obligations your vertical runs on, always current.
PUBLIC INTEL // CANON RECORD
Reviewed
SourceTTB · eCFR Title 27
ObligationCOLA before distribution
Citation27 CFR § 4.50
JurisdictionFederal — US
EffectiveCurrent
Review stateReviewed
Used byVinlio — Label Room
Regulatory obligations that aren't tracked become liabilities.
In regulated businesses, the gap between what the rules say and what operations assume the rules say is where compliance failures live.
No citation chain
Obligations without source citations and effective dates are unauditable. When a regulator or auditor asks why a document was produced the way it was, there is no defensible answer without a traceable citation.
No review state
No one knows which obligations have been reviewed, which are pending, and which are in dispute. Without review state tracked in the system, compliance posture is an assumption, not a fact.
Source → Obligation → Binding → Review → Canon pack.
Public Intel structures regulatory obligations from source through binding so every document and workflow in your vertical has a governed foundation to stand on.
Governed obligation
What a governed obligation looks like.
Every obligation in Public Intel carries a full provenance chain: the source authority, the specific citation, the jurisdiction it applies in, the review state, and the verticals it binds. No floating rules — every obligation is traceable from source to operation.
Obligations are not static records. They carry review tasks, effective-date tracking, and binding state so the canon reflects the current legal environment — not a snapshot from whenever someone last updated a spreadsheet.
Canonical Obligation
Source
TTB / eCFR Title 27
Jurisdiction
Federal — United States
Obligation
Label approval required before commercial distribution (COLA)
Citation
27 CFR § 4.50
Effective date
Current
Review state
Reviewed
Used by
Vinlio — Label Room, Vinlio — Compliance Cockpit
Healthcare — PPECC
Official sources. Source-backed operational awareness.
PPECC operators run on a dense stack of state agency rules, billing manuals, and regulatory updates. Public Intel ingests official HHSC sources, TMHP billing manuals, and state regulatory publications — and structures each obligation with a full citation chain before it touches any operation.
Official HHSC sources, TMHP billing manuals, and regulatory updates — turned into source-backed operational awareness for PPECC operators. No floating rules. No stale guidance. Every obligation traces to an authoritative source and carries a jurisdiction, effective date, and review state.
This is the foundation that powers PPEC Finder on Harbor — the public-facing directory of PPEC providers backed by the same governed canon.
Canonical Obligation — Texas PPECC
Source
HHSC LTCR · 26 TAC Ch. 550
Obligation
QAPI program required
Citation
26 TAC §550.1002
Jurisdiction
Texas — PPECC
Effective date
October 16, 2024
Review state
In review
Used by
Harbor — PPEC Operations
Canon packs for every vertical.
Regulatory obligations are grouped into canon packs scoped to each operating domain. Each pack carries the full citation chain for the vertical it governs.
Wine Canon Pack
- TTB permittees
- COLA registry (Certificate of Label Approval)
- eCFR Title 27 — Alcohol, Tobacco, Firearms
- AVA resources
- Formulas Online
Healthcare Canon Pack
- HIPAA obligations
- State licensing requirements
- Payer credentialing requirements
- Clinical documentation standards
- FL PPEC — AHCA + Medicaid rules (live)
- TX PPECC — HHSC LTCR + TMHP billing (in review)
Financial Canon Pack
- Mortgage and financial-services compliance obligations
- Licensing and disclosure requirements by jurisdiction
- Audit and record-retention obligations
Canon registry — jurisdiction status
| Canon | Jurisdiction | Source categories | Status | Used by |
|---|---|---|---|---|
| FL PPEC | Florida | AHCA provider regs, FL Medicaid billing, PPEC licensure rules | Live | Harbor — PPEC Operations |
| TX PPECC | Texas | HHSC LTCR rules, TMHP PPECC billing manual, 26 TAC Ch. 550 regulations | In review | Harbor — PPEC Operations |
| Wine / TTB | Federal — US | TTB permittees, COLA registry, eCFR Title 27, AVA resources, Formulas Online | Live | Vinlio — Label Room |
Intelligence layer
Public Intel keeps the canon fresh. DocRadar moves the work.
Public Intel is the governed source of obligation truth. It defines what the rules are, where they come from, which jurisdictions they apply in, and what review state they carry.
DocRadar compares extracted document fields against the obligations defined in Public Intel. When a document field diverges from the canon — wrong citation, outdated version, missing disclosure — DocRadar flags it for human review before the document is committed.
The two modules are designed to operate together: Public Intel provides the obligation truth; DocRadar operationalizes it against real document flows.
Intelligence Layer
Active
Public Intel
Canon source
DocRadar
Comparison engine
Citation chain
Auditable
Human confirm
Required
1
Document intake
2
Extract fields
3
Compare to canon
4
Human confirm
5
Commit + audit
Governed canon. Operational clarity.
Public Intel structures the regulatory obligations your vertical runs on. Talk to Aegis about bringing governed canon to your operations.