H3 Quality-profile sync
- Area
- H — Ecosystem glue
- Audience
- operator
- Kind
- feature
- Status
- accepted
- Maturity
- planned
- Labels
- quality, wiring, verification, stats
- Relates to
- D2
The feature in the specification · Read at
Requirements
The catalogue source MUST be an open, community-owned quality catalogue; the tool MUST NOT depend on a proprietary or closed quality source.
- locked by
- 0.20.0 open
The tool MUST wire each \arr instance via its API and reconcile it to the operator's selected custom formats and profiles declaratively.
- locked by
- 0.20.0 open
The tool MUST present a preview diff — creates, updates, and (if enabled) removals with score changes — before applying, and a dry run MUST apply nothing.
- locked by
- 0.20.0 open
After a sync, the tool MUST query the \arr API and assert that the intended custom formats and profiles exist and carry the expected scores; it MUST NOT treat an accepted write as proof.
- locked by
- 0.20.0 open
A sync whose read-back does not confirm the expected formats and scores MUST be reported as failed, even if every write returned success.
- locked by
- 0.20.0 open
The tool MUST verify each instance's reachability and accepted credential, and the catalogue source's reachability, before reconciling.
- locked by
- 0.20.0 open
The tool MUST NOT prune unmanaged custom formats unless pruning is explicitly enabled, and when enabled MUST list every item that would be removed in the preview.
- locked by
- 0.20.0 open
If the catalogue source is unreachable, the tool MUST leave the instance untouched and MUST NOT apply a partial or empty catalogue.
- locked by
- 0.20.0 open
A custom format a profile depends on MUST be created before the profile, or the unmet dependency MUST be reported; a profile MUST NOT be left referencing a missing format.
- locked by
- 0.20.0 open
Divergence caused by another tool writing the same instance MUST be reported as a conflict rather than driving a silent re-apply loop.
- locked by
- 0.20.0 open
Each \arr instance MUST be reconciled independently, so a failure on one does not block the others.
- locked by
- 0.20.0 open
The tool SHOULD be able to explain a release's score by naming the custom formats that matched and their contributions relative to the profile cutoff.
- locked by
- 0.20.0 open
Applying without an explicit preview MUST still compute and record the diff so the change is auditable.
- locked by
- 0.20.0 open
Previewing, applying, and running the read-back proof MUST each be reachable non-interactively.
- locked by
- 0.20.0 open