governance: decide whether a Bustfile runner is wanted (old bust.ncl referenced nonexistent ../_base.ncl) #81

Activity

1. hyperpolymath

   added

   choreRoutine maintenance with no behaviour changeRoutine maintenance with no behaviour change

   cicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatesCI/CD: workflows, actions, lockfiles, pins, runners, release gates

   governancePolicy, rulesets, standards, compliance, and their enforcementPolicy, rulesets, standards, compliance, and their enforcement

   on Aug 27, 2026
2. hyperpolymath

   added a commit that references this issue on Sep 26, 2026

   fix: resolve repository issues, port Lean FilesystemCNO, and unify Co…

   ...

   b7c780f
3. hyperpolymath

   added

   priority:p3Low - nice to haveLow - nice to have

   scope:repoConfined to this repositoryConfined to this repository

   status:needs-rulingAwaiting an owner decisionAwaiting an owner decision

   on Sep 30, 2026
4. hyperpolymath commented on Sep 30, 2026

   

   hyperpolymath

   on Sep 30, 2026

   OwnerAuthor

   More actions

   RULING D187 (2026-09-30T14:23Z) · scope: repo · basis: applied-unless-struck (D113; owner approved the full table, none struck)

   Drop the Bustfile runner (disabled, references a nonexistent _base.ncl) unless a concrete need appears.

   surface: hyperpolymath/standards#787 (comment)

   The open question in this issue is answered by the ruling above; future agents should act on it rather than re-ask.
5. hyperpolymath

   removed

   status:needs-rulingAwaiting an owner decisionAwaiting an owner decision

   on Sep 30, 2026