Fork: 0
OpenStack / openstack-caracal-dc-dc
Transfer to URL with SHA Find file
Newer
Older
openstack-caracal-dc-dc / docs / archive / session-ledger-rotated-20260730.md
@JANeumatrix JANeumatrix 13 hours ago 5 KB GA-R4 session close: F9 closed live, the reissue tool, P7, lib-identity
Raw Blame History

Session-ledger summaries rotated 2026-07-30 (GA-R4 rule 3 / F1)

Moved VERBATIM from docs/session-ledger.md at the 2026-07-30 (part 2) close, oldest first, to restore the 300-line cap. Only the SUMMARIES moved; each still points at its own full body. Rotated early and deliberately: the operator directed that the NEXT session proceed to the juju deployment no matter what, so it should not inherit a ledger already at the cap.

SESSION CLOSE 2026-07-27 -- STAGE-5 GROUNDING AUDIT (bounded, GA-R4)

  • Operator-directed reconciliation before Stage 5 opens; ran AUTONOMOUSLY while they were away, read-only, rulings QUEUED not adopted. Branch dc-dc-stage5-grounding-audit off main at 71519a2; 4 commits 514f0aa..de11bf4 pushed. NO stage opened or closed.
  • VERDICT: Stage 5 would NOT run error-free today and would fail early. SUBSTRATE is excellent -- all THREE tofu roots ZERO DIFF (first time in one session), 18 nodes Ready exact to D-121 C, MACs/power/statics/fabrics/interfaces all verified, both artifact paths serving, gauntlet 81 GREEN. The gap is the layer between substrate and deploy.
  • Blockers, each measured: voffice1 -- the D-128 host Stage 5 RUNS FROM -- is 105 commits behind on a retired branch, both dc1 overlays ABSENT, bundle still VR0 4-node; NO openstack client on either host (10 scripts need it); 10th controller VM UNAUTHORED + no tag, and dc1 has exactly 9 nodes for a 9-machine bundle; osd-devices=/dev/vdb but every node has only vda; per-role tags authored nowhere; ZERO IPv6 vs D-101's RULED dual-stack; and phase-01, which Step 4 delegates to "verbatim", ABORTS on dc1.
  • Gates that should have caught these cannot fail: repo-lint PASSES over ZERO files on a one-char typo; cluster_count checked nowhere so decorative HA passes; preflight ignores any sub-gate rc not in {1,2}; P3 verified ZERO of 33 channel pins (no juju on PATH). Three Stage-5 gate commands cannot execute on juju 3.6.27; four of five owed VERIFY-LIVE gates have no runbook step at all.
  • Deliverables: docs/audit/stage5-readiness-20260727.md (READ FIRST), stage5-committee-raw-20260727.md (7 lenses verbatim), queued-rulings-20260727.md -- 11 blocking + 4 standing questions, ONE exchange each, NONE adopted, stage5-live-measurement-20260727.txt, charter stage5-grounding-audit-scope-*.md.
  • 21-item DOCFIX batch LOGGED NOT EXECUTED (interlocks with unanswered rulings); next-free unchanged D 138 / DOCFIX 205 / BUNDLEFIX 053. ONE mechanical fix: G3's stale FREEZE clause, which would have blocked the remediation batch itself.
  • OWNED: ran the rack checkers locally and got a false FAIL (they pipe to the rack); read tail's exit code not the script's; waved P3's 33 warns through as expected when the CAUSE was a missing binary; called the privileged creds sweep a newly-closed item when 07-26 had already done it. All four corrected in place, not silently.
  • A SESSION-SCOPED PERMISSION BLOCK IS LIVE in the gitignored settings.local.json -- REMOVE IT. Its only durable record is scope-doc section 6. SEC 21 open, unchanged.
  • Full body: docs/archive/changelogs/changelog-20260727-stage5-grounding-audit.md. Status ONLY in CURRENT-STATE.md.

POST-CLOSE ADDENDUM 2026-07-27 -- 14 RULINGS + SKILL SWEEP (GA-R4; 07-25/07-26 precedent)

  • The STAGE-5 GROUNDING AUDIT close bookend above landed while the operator was away, by design. They then returned and worked the queued rulings. This addendum records what followed rather than re-opening that entry -- the same shape as the 2026-07-26 addendum.

  • Operator-directed full reconciliation before Stage 5; 7-lens read-only committee + live measurement, run AUTONOMOUSLY while away. Branch dc-dc-stage5-grounding-audit, ~30 commits 514f0aa..HEAD pushed. NO stage opened or closed.

  • VERDICT: Stage 5 would NOT run error-free. Substrate excellent (all THREE tofu roots ZERO DIFF, 18 nodes exact to D-121 C, gauntlet 81 GREEN); the gap is between substrate and deploy.
  • Blockers: voffice1 -- the D-128 host Stage 5 RUNS FROM -- is 105 commits stale on a branch deleted upstream; no openstack client on EITHER host; the 10th controller VM is UNAUTHORED; osd-devices points at a device no node has; per-role tags authored nowhere; ZERO IPv6 vs D-101's ruling; and phase-01, which Step 4 delegates to "verbatim", ABORTS on dc1.
  • Gates that should have caught these CANNOT FAIL: repo-lint PASSES over ZERO files on a one-char typo; cluster_count checked nowhere; preflight fails open on rc not in {1,2}; P3 verified ZERO of 33 channel pins. All ruled fixed (R15).
  • 14 RULINGS, 2 WITHDRAWN, G18 OPENED (blocking, deferred until the cloud is live). Authority = each D-number's Status block; questions+utterances in docs/audit/queued-rulings-20260727.md. Execution ALL logged-not-executed.
  • Next-free UNCHANGED: D 138 / DOCFIX 205 / BUNDLEFIX 053. SEC rows unchanged at 21.
  • Two RULED-BUT-NEVER-BUILT decisions found (D-134 bands, D-020 vault VIP), neither detectable by any gate. R8's evidence base collapsed on reading the cited bugs -- the charm's own default was the opposite of the repo's draft.
  • OWNED: three of my own premises needed correcting by measurement (R2a, R9, R14); used a 2-day dump instead of polling the apex; pushed one red-lint commit; hit the repo-lint L5 heading trap twice. All corrected on-surface, none silently.
  • Close sweep found 3 stale surfaces THIS AUDIT created (readiness doc's 13 dead NEEDS-RULING markers, "nothing is adopted" header, 6 blank utterance lines) -- all fixed.
  • SKILL SWEEP done despite no stage close (operator-directed): 3 new invariants + 4 authoring traps folded in; snapshot regenerated 1695 lines, ASCII/LF verified.
  • Session-scoped permission block REMOVED at close. Full body: docs/archive/changelogs/changelog-20260727-stage5-grounding-audit.md. Status ONLY in CURRENT-STATE.md.