Skip to content
AIGP

RFC-038: Domain of Concern Registry — AIGP Dialects as First-Class Artifacts — 7. Subscription and Governance Integration

AIGP Specification › RFC-038: Domain of Concern Registry — AIGP Dialects as First-Class Artifacts › 7. Subscription and Governance Integration

← 6. Registry Operations · Section index · 8. Local Profile Override →

7. Subscription and Governance Integration

7.1 Subscription as Governance Contract

A dialect subscription is not advisory. It is a governance contract. When an application subscribes to autonomous_systems@2.1.0, it declares:

“My artifacts will be evaluated against this observation apparatus. I accept that my evidence must meet its admissibility floors, my variables must be populated from declared extraction methods, and my verdicts will be rendered by observers meeting its accreditation requirements.”

This subscription is recorded in the application’s AIGP governance registration (RFC-010 §3.1 REGISTER) and enforced at runtime.

7.2 Subscription Verification at CHECK Time

At pre-invocation CHECK time, the governance authority verifies:

  1. The application has an active dialect subscription
  2. The subscribed dialect version is not deprecated (or deprecation is acknowledged)
  3. The application’s evidence infrastructure can satisfy the dialect’s minimum admissibility floor
  4. The application’s observer configuration meets the dialect’s accreditation requirements

A CHECK that fails subscription verification produces a governance warning (REPORT mode) or block (ENFORCE mode).

7.3 Subscription Verification at VERIFY Time

At post-hoc VERIFY time (RFC-032), the evaluation loop verifies:

  1. The populated Mediation Vector matches the subscribed dialect’s variable schema
  2. All variables are populated from admissible evidence (per the dialect’s floors)
  3. Gap computation used the dialect’s declared gap operators
  4. Thresholds applied are at least as strict as the dialect’s defaults (Local Profile may tighten, never weaken)

A VERIFY that detects dialect violation produces a VIOLATION verdict class — distinct from a concern MISMATCH. The artifact didn’t merely fail a concern check; it violated its declared observation contract.

7.4 Multi-Dialect Subscription

An application MAY subscribe to multiple dialects simultaneously when its artifacts span multiple Domains of Concern:

{
  "app_id": "clinical-decision-support-v2",
  "dialect_subscriptions": [
    { "dialect_id": "regulated_advice_under_uncertainty", "version": "^1.2.0" },
    { "dialect_id": "risk_escalation_and_triage", "version": "^1.0.0" }
  ]
}

Each artifact declares which dialect(s) apply to its evaluation. An artifact MAY be evaluated against multiple dialects if its concern classes span multiple domains.

← 6. Registry Operations · Section index · 8. Local Profile Override →