Reconcile the spec with the settled config and broker models #521

Activity

1. David-Noble-at-work

   self-assigned this

   on Aug 18, 2026
2. David-Noble-at-work

   added

   featureDeliverable unit within an epicDeliverable unit within an epic

   Epic:ElevationPolicyThe elevation policy epicThe elevation policy epic

   on Aug 18, 2026
3. David-Noble-at-work commented on Oct 2, 2026

   

   David-Noble-at-work

   on Oct 2, 2026

   Last edited by David-Noble-at-work

   ContributorAuthor

   More actions

   Placed on #916 as lane 34, in PR C, after lane 33 (named roots, #597)

   The owner, 2026-10-02: "So add the elevation design to your schedule. It's time to bite the bullet." Earlier the same day: "The elevation spec is a draft that requires deep research when we're ready to execute."

   What brought it here: lane 7's VM run (#926) reached its System-scope adoption. Adopting a root-owned file under /etc needs root, nothing in writ elevates, and pkg/op/provider/elevator is a stub whose Elevate always answers not implemented. Running writ under sudo does not substitute. Measured on danoble-ud24-1: sudo's secure_path leaves writ off root's PATH, env_reset clears the XDG_* variables, and HOME is /root; and pkg/xdg resolves the home directory from the account by design, so root's writ uses root's home, configuration and store. Read from the code, not run: forcing the user's XDG_* directories onto it would write the lifetime and receipts root-owned and 0600 (cmd/internal/cli/lifetime.go writes 0o600) into the user's store, which the user's next unprivileged run could not read or replace.

   So the design begins with deep research, then this feature's tasks (#522-#525) reconcile 6.1 with the settled configuration and broker models. Writ's System scope is one consumer the design must answer: one record, with the user's writ elevating only the operations that need root, as 6.1 frames it, or root running its own writ for System. It follows lane 33 because named roots decides what a root is, and elevation how a run reaches System's. Until then, tests against System are skipped: "For now: skip tests against system."
4. David-Noble-at-work

   added a commit that references this issue on Oct 2, 2026

   docs(plan): lane 7 closes, its VM run recorded and its tests against …

   ...

   e2a75b2