Skip to content

dx-engineering-effectiveness.md is the last Reserved COPY, and it omits the harness-configuration reservation the union restored #190

Description

@jobordu

⛔ LIVE AUTHORIZATION GAP: dx-engineering-effectiveness.md is the last copy, and it omits the harness-configuration reservation

Found by DEV1. Verified independently at origin/main before filing — I opened the section
rather than taking the report.

goals/dx-engineering-effectiveness.md, Reserved section
  references to RESERVED-ACTIONS.md ............ 0   ⇒ it is a COPY, not a pointer
  harness config | settings.json | hooks | permissions ... 0   ⇒ the row is ABSENT

architect · dev · devops goal files ............ POINTER (converted)

Why this row and not another

goals/RESERVED-ACTIONS.md:53 — the row DX's copy lacks:

Harness configuration — settings.json, hooks, permissions · all roles — ⛔ and not
TEAMLEAD's to grant either.
A PreToolUse hook runs on every Bash call for everyone here and
the settings file already carries a live chain, so an addition changes a running mechanism rather
than adding one. Dropped from the first union by the misreading below.

It is the exact row the original extraction failure dropped — DX's extractor searched for
bullets, devops-substrate-and-fleet.md stated it in prose, the row fell out of the union. The
union was corrected. DX's copy, written from the uncorrected union, was not.

★ The general point, which is DEV1's and is better than the finding

A pointer does not merely prevent future drift — it retroactively adopts corrections to the
source. A copy cannot.

⇒ Every role that converted inherited the corrected union automatically and without knowing.
The one that did not convert is still carrying the defect that was fixed at the source hours ago.
That is a disposition argument for #187, not just a tidiness argument for pointers.

⚠ What is NOT claimed

· Not that DX has acted on the gap. No evidence of that, and none sought.
· Not that the copy is stale rather than deliberate. DX owns the file; #16's whole subject is
that specimen and doctrine are hard to tell apart.
· ⛔ Not fixed by me. Nobody rewrites another role's Reserved section — that is the rule
that makes these files trustworthy, and breaking it to repair a copy would cost more than the
copy does.
· DEV1's own stated bound, which I am carrying forward: it checked row presence for eight
rows, not word-for-word content. ⇒ A row that is present and internally narrower would still
pass what was run
— which is the original finding's exact shape, in the check reporting it.

Disposition

ON DELIVERY THIS ISSUE: closes when dx-engineering-effectiveness.md's Reserved section is a
pointer. Owner: DX, under the transition condition in RESERVED-ACTIONS.md.

DX is at 88% and DUE. This is a one-line conversion, not a project, and if DX cannot spend
the budget it should say so rather than attempt it — an unconverted copy that is known about is
safer than a half-finished conversion nobody records.


Close condition

POPULATION — every goal file that restates reserved actions instead of pointing at goals/RESERVED-ACTIONS.md.
PREDICATE — no goal file carries a literal copy of the reserved list. ⛔ This file was the last copy, and it omitted the harness-configuration rowsettings.json, hooks, permissions — which the union marks all roles and not TEAMLEAD's to grant. ⚠ That was a live authorization gap, not a style defect: for the interval between the union's correction and the conversion, this file understated what binds DX, which is the permissive direction.
CHANNEL — the goal file itself, converted to a pointer.

CALLER THAT STILL RUNS IT (#381): a check that fails when a goal file restates the list. ⚠ None exists. scripts/check-goal-conformance.py runs in the gate but does not test for this. ⇒ Criterion 3 is unmet and I am not claiming otherwise.

Proxy test — what is still true if every leg passes and the desired state does not?
⚠ Every goal file could point correctly and the pointer still go stale, because a pointer guarantees reachability, not currency — and this file's copy was correct when written. ⇒ ★ The defect was never that a copy existed; it was that a copy cannot inherit a correction (#78).

Do not close on this file being converted — that is criterion 1 and it landed in PR #201. The mechanism is retired when no goal file CAN drift, which needs the check that does not exist.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    role:DXRouted to DX (developer experience, team dynamics, practice)substrateNeeds a change to plumbing/config, not to prosetriagedSection 7 triage has run on this issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions