RFC-038: Domain of Concern Registry — AIGP Dialects as First-Class Artifacts — 6. Registry Operations

AIGP Specification › RFC-038: Domain of Concern Registry — AIGP Dialects as First-Class Artifacts › 6. Registry Operations

← 5. Versioning Model · Section index · 7. Subscription and Governance Integration →

6. Registry Operations

6.1 Publish

A publisher submits a dialect bundle to the registry. The registry validates structural completeness before accepting:

Structural Completeness Checks:

Check	Validates
All variables have required fields (§10 of RFC-035)	Measurement validity
All variables declare gap_operator compatible with scale	Stevens constraint
All variables declare evidence_source and min_admissibility_level	Evidence grounding
All variables declare extraction_method	Reproducibility
At least one concern_class is declared	Domain binding
Observer modes are non-empty	Verdict capability
Default thresholds exist for all gaps of all variables	Calculability
Hard stops reference valid variables and gap types	Integrity
MANIFEST dependencies are satisfiable	Compatibility
Bundle hash matches declared hash	Tamper detection

A dialect that fails any check is rejected with a structured error indicating which completeness criterion failed.

6.2 Resolve

A consumer requests a specific dialect version or a compatible range:

GET /registry/dialects/autonomous_systems@2.1.0
GET /registry/dialects/autonomous_systems@^2.0.0    # semver range
GET /registry/dialects/autonomous_systems@latest

Resolution returns the complete bundle or a signed reference to it.

6.3 Discover

A consumer queries the registry by concern class, mediation domain, or constraint pattern:

GET /registry/dialects?concern_class=unauthorized_autonomous_action
GET /registry/dialects?mediation_domain=autonomous_systems
GET /registry/dialects?constraint_pattern=authority,reversibility

Discovery returns a list of matching dialect manifests (not full bundles).

A governed application declares its dialect subscription:

{
  "app_id": "drone-control-v3",
  "dialect_subscription": {
    "dialect_id": "autonomous_systems",
    "version_constraint": "^2.1.0",
    "local_profile_override": "military-recon-profile-v1",
    "subscription_mode": "pin",
    "notify_on": ["major", "minor", "deprecation"]
  }
}

Subscription modes:

Mode	Behavior
`pin`	Locked to exact version; manual upgrade only
`patch`	Auto-accept patch updates; manual for minor/major
`minor`	Auto-accept minor updates; manual for major
`latest`	Always resolve to latest stable (NOT RECOMMENDED for production)

6.5 Validate

A consumer submits a populated Mediation Vector for validation against a dialect version:

POST /registry/dialects/autonomous_systems@2.1.0/validate
Body: { mediation_vector: [...] }

Validation checks:

All required variables present
All variable values within declared ranges
All evidence sources meet minimum admissibility levels
All gap operators match declared scales
No inadmissible aggregation attempted

Returns a structured validation report, not a verdict. The registry validates structure, not truth.

6.6 Diff

A consumer requests the structural difference between two dialect versions:

GET /registry/dialects/autonomous_systems/diff?from=2.0.0&to=2.1.0

Returns a structured changeset: added variables, removed variables, changed thresholds, new hard stops, modified observer requirements.