Skip to content

elevator becomes elevation — 6.1 settled the name, the tree never received it #679

Open

Description

@David-Noble-at-work

Epic: #520
Plan: docs/plans/elevation-provider-rename.md
Design: 6.1-privilege-elevation.md

6.1-privilege-elevation.md:8 records the name as settled: "Provider elevation.Provider in package
elevation (pkg/op/provider/elevation)." The tree never received it.

  • the package, directory, and package clause are still elevator
  • the package doc comment still calls the name provisional, contradicting 6.1
  • 6.1-privilege-elevation.status.md still carries an unchecked box: "Name the provider — elevator are working
    names"
  • 6.1's body cites pkg/op/provider/elevator/broker.go:14 and :53 — paths that break on rename
  • 3.5-provider-catalog.md lists it as a provider with role planned, though it has no gen/, no inventory
    entry, and zero importers

52 elevator references across 22 files — 10 Go, 42 documentation. No type is named Elevator; the rename is
package-level only.

The stub stays. It is the scaffold step 38's design builds on. It remains unannounced by design; the catalog
row moves under a "Designed, not announced" heading carrying no role.

Not in scope: renaming Config / EnvironmentConfig / TokenProviderConfig. 6.1 still carries "Settle the
full config shape," and step 38's open questions 1-4 are unresolved. The package name is settled; the config shape
is not.

Metadata

Metadata

Labels

Area:ArchitectureSystem architecture and designEpic:ElevationPolicyThe elevation policy epicPriority:P2Scheduled, not urgentSeverity:LowCosmetic, or a defect nobody is hittingchoreMaintenance work on the repo: build, CI, tooling, process

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions