Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 75 additions & 0 deletions docs/audits/metadata-closure-retirement-2026-11-13.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
# Retirement of the last hand-listed metadata check

Reviewed revision `a5e8bf7ee4f29ba14826df1ce363bef13fbe2963`. This is the review
record supplied to the Engine's `maintain_evidence` operation for the retirement
below. It records what was checked before the retirement; it is not a coverage
attestation.

## Decision

On 2026-11-13 the repository owner decided to retire
`release-maintenance-policy/metadata-closure` and accepted that the coverage
certificates it invalidates are reissued afterwards, each after its own review.
Fifty-five sibling checks were retired on 2026-11-12; this one was held back
only because of that certificate effect.

## What is retired

| Item | Disposition |
| --- | --- |
| Check `release-maintenance-policy/metadata-closure` | Retired. It ran `metadata_graph` over a hand-typed list of 12 module paths. |
| Suite `release-maintenance-policy` | Retired by the Engine because it has no other check. |
| Registry entry for that suite | Removed with the suite. |
| Catalogue node `release-maintenance-policy` (`enforcement-suite`) | Removed with the suite. |

The suite required `release-reference-closure`, which stays registered with its
own checks. No registered suite requires `release-maintenance-policy`.

## Why the check is redundant

The check `canonical-corpus-metadata/canonical-corpus` validates every member of
`evaluation/standards-effectiveness/canonical-module-corpus.toml` through the same
`validate_module_metadata` call the retired check used.

- All 12 listed paths are among the 74 corpus members.
- Mutation test on a scratch copy of the reviewed revision: four defects
(a `Requires` target that does not exist, a removed `Level` line, a wrong
`Canonical owner` path, a `Specializes` target that does not exist) were
introduced one at a time into each of the 12 modules, 48 mutations in all.
The retired check failed 48 times. The whole-corpus check failed the same 48
times with the same diagnostic code each time. No defect was reported by the
retired check alone.

The retired check therefore could not fail for a reason the whole-corpus check
does not also report.

## Graph and certificate effect

- The removed node is neither the source nor the consumer of any policy-impact
relationship, and no relationship names `suite:release-maintenance-policy` as
its evidence owner. No relationship is removed or re-owned.
- The node catalogue digest is part of every coverage requirement. Removing a
node changes all 53 requirement IDs, so the 16 certificates that were current
at the reviewed revision become stale. The 8 certificates that were already
stale stay stale.
- Stale certificates are left in place (`prune_stale_certificates` is `false`).
A stale certificate is ignored when coverage is read; its policy unit reports
`review-required` until a new certificate is published for it.

## Counts

| | Before | After |
| --- | ---: | ---: |
| Registered suites | 24 | 23 |
| Checks | 67 | 66 |
| Catalogue nodes | 122 | 121 |
| Certificates current / stale | 16 / 8 | 0 / 24 |

## Engine operation

`maintain_evidence` with this file as evidence, first with `apply: false` and
then with `apply: true`. Plan: `retire_checks` naming the one check; no suite,
input, description, relationship or consumer entries;
`replacement_evidence_owner` `review:consumer` (unused, because no relationship
names the retired suite). The Engine's candidate verification passed with 23
suites and 66 checks.
88 changes: 4 additions & 84 deletions evaluation/standards-effectiveness/generated/suite-inputs.json
Original file line number Diff line number Diff line change
Expand Up @@ -128,11 +128,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-links",
"role": "link-target",
Expand Down Expand Up @@ -1486,7 +1481,7 @@
]
},
{
"digest": "sha256:fc176982992241069f3bbb40173fd7176e10d5c9fdc1373a16c88647819ad7c4",
"digest": "sha256:9d3ec990d2ee5a74bf1bb71db3619a3fa5c90288b5c5b809f2219efa22343062",
"path": "evaluation/standards-effectiveness/policy-impact-node-catalog.toml",
"state": "present",
"uses": [
Expand Down Expand Up @@ -2158,7 +2153,7 @@
]
},
{
"digest": "sha256:af8f30134a34385b211429c7d325b9f0c233839ec8d49aee03f882f67aa69ca5",
"digest": "sha256:8634e8ae372621d80260a6006743ad8bdfe4a87cc5eccc944610448663862748",
"path": "evaluation/standards-effectiveness/suite-registry.toml",
"state": "present",
"uses": [
Expand Down Expand Up @@ -2277,18 +2272,6 @@
}
]
},
{
"digest": "sha256:61760956e55a27d2333794a36514cdabf23ca2d73722a6f71c00fb7ffda53ea8",
"path": "evaluation/standards-effectiveness/suites/release-maintenance-policy.toml",
"state": "present",
"uses": [
{
"check": "current-structure",
"role": "registered-policy-impact",
"suite": "policy-semantic-impact"
}
]
},
{
"digest": "sha256:7fea2ba620f744cee21fbd96edfff1fe2f88f43ce5d277a2edf4e0a3e979e9f7",
"path": "evaluation/standards-effectiveness/suites/release-reference-closure.toml",
Expand Down Expand Up @@ -8054,11 +8037,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -8263,11 +8241,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -8375,11 +8348,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -8437,11 +8405,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -8499,11 +8462,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -9886,11 +9844,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "legacy-index-destinations",
"role": "target",
Expand Down Expand Up @@ -10008,11 +9961,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -10264,11 +10212,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -10416,11 +10359,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -10483,11 +10421,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -10550,11 +10483,6 @@
"role": "canonical-policy-impact",
"suite": "policy-semantic-impact"
},
{
"check": "metadata-closure",
"role": "metadata",
"suite": "release-maintenance-policy"
},
{
"check": "root-router-routes",
"role": "link-target",
Expand Down Expand Up @@ -10589,11 +10517,11 @@
}
],
"registry": {
"digest": "sha256:af8f30134a34385b211429c7d325b9f0c233839ec8d49aee03f882f67aa69ca5",
"digest": "sha256:8634e8ae372621d80260a6006743ad8bdfe4a87cc5eccc944610448663862748",
"path": "evaluation/standards-effectiveness/suite-registry.toml"
},
"repository_index": {
"digest": "sha256:ae3843ae7d58b01dbbd6efb662286d52e4fc9c70f9c5e14bde04c0544d9b7d17",
"digest": "sha256:c2a56690ade32430a01832b2459f02feed2569f9d015abe1d08a10349ab23d36",
"uses": [
{
"check": "python-package-contract",
Expand Down Expand Up @@ -10664,14 +10592,6 @@
"path": "evaluation/standards-effectiveness/suites/release-reference-closure.toml",
"requires": []
},
{
"digest": "sha256:61760956e55a27d2333794a36514cdabf23ca2d73722a6f71c00fb7ffda53ea8",
"id": "release-maintenance-policy",
"path": "evaluation/standards-effectiveness/suites/release-maintenance-policy.toml",
"requires": [
"release-reference-closure"
]
},
{
"digest": "sha256:63cca2ceac227aacccf33a964801a645bb4083719e5011a46a313308f2628026",
"id": "s1-routing",
Expand Down
491 changes: 490 additions & 1 deletion evaluation/standards-effectiveness/policy-impact-node-catalog.toml

Large diffs are not rendered by default.

5 changes: 0 additions & 5 deletions evaluation/standards-effectiveness/suite-registry.toml
Original file line number Diff line number Diff line change
Expand Up @@ -50,11 +50,6 @@ id = "release-reference-closure"
path = "evaluation/standards-effectiveness/suites/release-reference-closure.toml"
requires = []

[[suites]]
id = "release-maintenance-policy"
path = "evaluation/standards-effectiveness/suites/release-maintenance-policy.toml"
requires = ["release-reference-closure"]

[[suites]]
id = "s1-routing"
path = "evaluation/standards-effectiveness/suites/s1-routing.toml"
Expand Down

This file was deleted.

Loading