RFC-038: Domain of Concern Registry — AIGP Dialects as First-Class Artifacts — 3. Core Definitions
AIGP Specification › RFC-038: Domain of Concern Registry — AIGP Dialects as First-Class Artifacts › 3. Core Definitions
← 2. Motivation · Section index · 4. Dialect Structure →
3. Core Definitions
3.1 Dialect
A dialect is the complete, versioned, distributable instantiation of an AIGP concern observation apparatus for a specific Domain of Concern. It bundles:
- A Domain of Concern declaration (RFC-034)
- A Mediation Observation Model with all variables fully declared (RFC-035)
- Calculation semantics binding (RFC-036)
- Observer accreditation requirements (RFC-037)
- A default Local Profile (thresholds, admissibility floors, hard stops)
- Extension points for organizational specialization
A dialect is immutable once published. Changes produce a new version.
3.2 Dialect Registry
A Dialect Registry is an authoritative, queryable store of published dialect versions. It provides:
- Discovery (what dialects exist for my concern class?)
- Resolution (give me dialect
autonomous_systems@2.1.0) - Validation (is this dialect structurally complete?)
- Lineage (what changed between versions?)
- Subscription (notify me when a new version is published)
3.3 Local Profile Override
A Local Profile Override is an organization-specific customization layer applied on top of a subscribed dialect version. It may tighten thresholds, raise admissibility floors, add hard stops, or restrict observer modes — but it MUST NOT weaken the dialect’s minimum requirements.
3.4 Dialect Subscription
A Dialect Subscription is a governed application’s binding declaration that it will be evaluated against a specific dialect version (or compatible range). The subscription is recorded in the application’s governance contract and enforced at runtime.