Closure: the design record states the sealed contract

Feature: #625 · Phase 5 of sealed-provider-resources.md.

The 3.5.x per-provider design docs drop any language describing the resource as a struct; each records the sealed shape.
4-resource-management.md records what the seal buys: the resource model's guarantees — claims are true when made, identity is the catalog key, a string is a key never a constructor, the graph carries complete intent — now rest on the compiler rather than on convention, because a resource cannot be produced outside its provider.
Status files follow.

Superseded by #647. Re-filed after phase-1 investigation changed the feature's shape — see the rewritten plan.

Three things moved:

This issue's enabling fact was false. pkg/op/provider/<p>/gen is a distinct package from the provider (same package name, different import path), so a gen file can never name an unexported type. Ruling 4 (2026-08-24) gives the URI fragment to the interface instead of the struct, which makes the gen files correct as-is.
The work splits in two parts, so the goal is actually reached: part 1 seals the eight single-resource providers, part 2 converts file's four variants. The original left file a permanent exception in a new direction.
Phases regroup by risk rather than footprint — the four Unpacker implementers share one silent failure mode and are proved together.

Navigation Menu