pdurlej/platform

Fork 0

ops: ADR-0009 bounded L-1.5 baseline closure via 7-point spot-check #170

Closed

claude wants to merge 1 commit from claude-orchestrator/phase-01-bounded-closure into main

claude commented

2026-05-11 02:02:39 +02:00

Collaborator

What

ADR-0009 adopts a bounded 7-point spot-check as the canonical close for L-1.5 baseline sign-off, replacing the routine 21-check recovery/verify-baseline.sh re-run. Full 21-check remains available for deep audit.

Closes (when merged): unblocks BLOCKERS_FOR_OPERATOR.md §1 via the bounded procedure.

Files (4)

File	Change	Purpose
`decisions/0009-bounded-l-1-5-closure.md`	NEW	The ADR itself
`scripts/baseline-spot-check.sh`	NEW (executable)	The 7-point check; runs in <30s; structured Markdown report to stdout
`state/reports/L-1.5-spot-check-2026-05-11.md`	NEW	Seed report (auto-run during PR creation); 5/7 PASS, 2/7 FAIL with operator-triage analysis
`BLOCKERS_FOR_OPERATOR.md`	EDIT (§1 only)	References bounded procedure as canonical close

The 7 checks

Manifest count — find modules -name module.yaml \| wc -l returns 81–120
Schema validation — platformctl validate all exits 0
Baseline replicas — ≥2 of 3 host replicas reachable + sized
Sacred paths defined — policies/sacred-paths.yaml OR PLATFORM_CHARTER.md reference
Foundational ADR set — ADRs 0001–0005 present
AGENTS.md identity-isolation — Conventions section + Identity-isolation subsection
Sunset queue tracked — ≥1 module with lifecycle: sunset

Reasoning per check is in ADR-0009 §The 7 checks table.

Live findings from seed report (2026-05-11)

The bounded check already caught two real driftsy that the full 21-check would have caught but operator hasn't yet routinely re-run:

Check 1 FAIL: 80 manifests on disk vs INDEX.md claim of 81. 3 triage options (A/B/C) documented in seed report.
Check 3 FAIL: only 1/3 baseline replicas reachable from M1 via BatchMode SSH. Likely path-different on rs2000/vps1000 OR auth-flaky in BatchMode. 3 triage options documented.

5/7 PASS otherwise. These two findings likely overlap with operator's recalled "znając życie coś było blokerem, nie spełniało one-day-rule i poszedłem dalej" — surfacing drift without forcing full 21-check redo. Per ADR-0009 design intent.

Sign-off procedure (after this PR merges)

cd ~/Developer/iskra-platform-2026-04-30
bash scripts/baseline-spot-check.sh > state/reports/L-1.5-spot-check-$(date -u +%Y-%m-%d).md
# review report (single screen)
# if all 7 green → amend BLOCKERS §1 with:
#   **Closed YYYY-MM-DD via bounded spot-check (ADR-0009, report ...)**

What this PR DOES

✅ Defines the bounded 7-point spot-check ADR with reasoning per check.
✅ Ships the executable script (bash -n clean, lives test produced output in 0.06s).
✅ Seeds a report with auto-run output for operator review.
✅ Updates BLOCKERS §1 to reference the bounded procedure as canonical.

What this PR DOES NOT

Does NOT itself sign off L-1.5 — operator decides after running the spot-check.
Does NOT replace recovery/verify-baseline.sh (retained for deep audit, yearly, incidents).
Does NOT auto-fix the 2 surfaced failures (triage requires operator).
Does NOT touch any runtime path, sacred path, or module manifest.

Acceptance criteria

ADR-0009 has Status: Proposed.
Script is executable, bash -n clean, runs in <30s on the actual repo (verified: 5/7 PASS).
Seed report is valid Markdown with operator-triage analysis for the 2 failures.
BLOCKERS §1 amended (legacy 21-check procedure retained for deep audit).
3+3 canary fires on risk/process (touches decisions/).
Operator runs script + makes triage decisions for the 2 failures.

Rollback

git revert 4e2325f
git push origin main

Single commit, 3 net-new files + 1 edit. Reverting is clean.

Refs

GPT-5.5 Pro oracle review 2026-05-11 §4 OPEN DECISIONS (L-1.5): "Sign it after a bounded spot-check, not a full re-audit. Operator verification cost should be one focused pass. Do not personally redo 21/21 checks. That defeats the point of the platform."
BLOCKERS_FOR_OPERATOR.md §1 (existing blocker; this PR amends).
INDEX.md (original L-1.5 spec, 2026-04-30; predates 6 weeks of platform evolution).
Companion: PR #168 (governance ADRs) and PR #169 (job bundle foundation).

Codex effort needed

Review + merge. After merge, operator runs the script + makes 2 triage calls. ~30 min of operator attention is the realistic close-out cost (vs. multi-hour for full 21-check re-do).

Role: orchestrator / drafter (claude)
Lane: ops / bounded closure
Next: operator decision on Check 1 + Check 3 triage options → re-run script → sign off.

## What ADR-0009 adopts a **bounded 7-point spot-check** as the canonical close for L-1.5 baseline sign-off, replacing the routine 21-check `recovery/verify-baseline.sh` re-run. Full 21-check remains available for deep audit. Closes (when merged): unblocks `BLOCKERS_FOR_OPERATOR.md` §1 via the bounded procedure. ## Files (4) | File | Change | Purpose | |------|--------|---------| | `decisions/0009-bounded-l-1-5-closure.md` | NEW | The ADR itself | | `scripts/baseline-spot-check.sh` | NEW (executable) | The 7-point check; runs in <30s; structured Markdown report to stdout | | `state/reports/L-1.5-spot-check-2026-05-11.md` | NEW | Seed report (auto-run during PR creation); 5/7 PASS, 2/7 FAIL with operator-triage analysis | | `BLOCKERS_FOR_OPERATOR.md` | EDIT (§1 only) | References bounded procedure as canonical close | ## The 7 checks 1. **Manifest count** — `find modules -name module.yaml \| wc -l` returns 81–120 2. **Schema validation** — `platformctl validate all` exits 0 3. **Baseline replicas** — ≥2 of 3 host replicas reachable + sized 4. **Sacred paths defined** — `policies/sacred-paths.yaml` OR `PLATFORM_CHARTER.md` reference 5. **Foundational ADR set** — ADRs 0001–0005 present 6. **AGENTS.md identity-isolation** — Conventions section + Identity-isolation subsection 7. **Sunset queue tracked** — ≥1 module with `lifecycle: sunset` Reasoning per check is in ADR-0009 §The 7 checks table. ## Live findings from seed report (2026-05-11) The bounded check **already caught two real driftsy** that the full 21-check would have caught but operator hasn't yet routinely re-run: - **Check 1 FAIL**: 80 manifests on disk vs INDEX.md claim of 81. 3 triage options (A/B/C) documented in seed report. - **Check 3 FAIL**: only 1/3 baseline replicas reachable from M1 via BatchMode SSH. Likely path-different on rs2000/vps1000 OR auth-flaky in BatchMode. 3 triage options documented. 5/7 PASS otherwise. These two findings likely overlap with operator's recalled *"znając życie coś było blokerem, nie spełniało one-day-rule i poszedłem dalej"* — surfacing drift without forcing full 21-check redo. Per ADR-0009 design intent. ## Sign-off procedure (after this PR merges) ```bash cd ~/Developer/iskra-platform-2026-04-30 bash scripts/baseline-spot-check.sh > state/reports/L-1.5-spot-check-$(date -u +%Y-%m-%d).md # review report (single screen) # if all 7 green → amend BLOCKERS §1 with: # **Closed YYYY-MM-DD via bounded spot-check (ADR-0009, report ...)** ``` ## What this PR DOES - ✅ Defines the bounded 7-point spot-check ADR with reasoning per check. - ✅ Ships the executable script (`bash -n` clean, lives test produced output in 0.06s). - ✅ Seeds a report with auto-run output for operator review. - ✅ Updates BLOCKERS §1 to reference the bounded procedure as canonical. ## What this PR DOES NOT - Does NOT itself sign off L-1.5 — operator decides after running the spot-check. - Does NOT replace `recovery/verify-baseline.sh` (retained for deep audit, yearly, incidents). - Does NOT auto-fix the 2 surfaced failures (triage requires operator). - Does NOT touch any runtime path, sacred path, or module manifest. ## Acceptance criteria - [x] ADR-0009 has Status: Proposed. - [x] Script is executable, `bash -n` clean, runs in <30s on the actual repo (verified: 5/7 PASS). - [x] Seed report is valid Markdown with operator-triage analysis for the 2 failures. - [x] BLOCKERS §1 amended (legacy 21-check procedure retained for deep audit). - [ ] 3+3 canary fires on `risk/process` (touches `decisions/`). - [ ] Operator runs script + makes triage decisions for the 2 failures. ## Rollback ``` git revert 4e2325f git push origin main ``` Single commit, 3 net-new files + 1 edit. Reverting is clean. ## Refs - GPT-5.5 Pro oracle review 2026-05-11 §4 OPEN DECISIONS (L-1.5): *"Sign it after a bounded spot-check, not a full re-audit. Operator verification cost should be one focused pass. Do not personally redo 21/21 checks. That defeats the point of the platform."* - `BLOCKERS_FOR_OPERATOR.md` §1 (existing blocker; this PR amends). - `INDEX.md` (original L-1.5 spec, 2026-04-30; predates 6 weeks of platform evolution). - Companion: PR #168 (governance ADRs) and PR #169 (job bundle foundation). ## Codex effort needed **Review + merge.** After merge, operator runs the script + makes 2 triage calls. ~30 min of operator attention is the realistic close-out cost (vs. multi-hour for full 21-check re-do). --- **Role:** orchestrator / drafter (claude) **Lane:** ops / bounded closure **Next:** operator decision on Check 1 + Check 3 triage options → re-run script → sign off.

claude added 1 commit

2026-05-11 02:02:39 +02:00

ops: ADR-0009 bounded L-1.5 baseline closure via 7-point spot-check

canary-required / collect-diff (pull_request) Successful in 3s

Details

canary-required / canary (pull_request) Successful in 11s

Details

4e2325f580

Replaces routine 21-check verify-baseline.sh re-run with a 7-point bounded
spot-check that operator can complete in <5 min. Full 21-check remains
available for deep audit (incident response, yearly, structural change).

What ships

- decisions/0009-bounded-l-1-5-closure.md — the ADR
- scripts/baseline-spot-check.sh — executable, runs in <30s, exits 0 on
  all-green, structured Markdown report to stdout
- state/reports/L-1.5-spot-check-2026-05-11.md — seed report (run during
  PR creation); 5/7 PASS, 2/7 FAIL with operator-triage analysis
- BLOCKERS_FOR_OPERATOR.md §1 amended to reference bounded procedure

The 7 checks

1. Manifest count (>=81, <=120)
2. Schema validation (platformctl validate all exits 0)
3. Baseline replica presence (>=2 of 3 hosts)
4. Sacred paths defined (policies/sacred-paths.yaml OR PLATFORM_CHARTER.md
   reference)
5. Foundational ADR set complete (0001-0005)
6. AGENTS.md identity-isolation section present
7. Sunset queue tracked (>=1 module with lifecycle: sunset)

Live findings from seed report (2026-05-11T00:00:51Z)

- 5/7 PASS
- Check 1 FAIL: 80 manifests on disk vs INDEX.md claim of 81. Operator
  triage options A/B/C documented in seed report.
- Check 3 FAIL: 1/3 baseline replicas reachable via BatchMode SSH (M1 only;
  rs2000 and vps1000 either path-different or auth-flaky in BatchMode).
  Operator triage options A/B/C documented.

These two findings likely overlap with operator's recalled "coś było
blokerem, nie spełniało one-day-rule i poszedłem dalej" — surfacing drift
without forcing full 21-check redo. Per ADR-0009 design intent.

What this PR DOES NOT

- Does NOT itself sign off L-1.5 (operator decides after seeing the
  bounded report)
- Does NOT replace recovery/verify-baseline.sh (retained for deep audit)
- Does NOT auto-fix the 2 surfaced failures (triage requires operator)
- Does NOT touch any runtime path

Refs

- GPT-5.5 Pro oracle review 2026-05-11 §4 OPEN DECISIONS (L-1.5):
  "Sign it after a bounded spot-check, not a full re-audit. Do not
  personally redo 21/21 checks. That defeats the point of the platform."
- BLOCKERS_FOR_OPERATOR.md §1 (existing blocker, updated by this PR)
- INDEX.md (original L-1.5 specification, predates 6-week platform
  evolution)

**Role:** orchestrator / drafter (claude)

claude referenced this pull request

2026-05-11 02:10:47 +02:00

feat(phase-07): scope-lock Cousin Layer + Local Admin + Attention Dispatcher (design only) #171

claude referenced this pull request

2026-05-11 02:15:26 +02:00

ops: ADR-0013 4th replica = Synology + encrypted Dropbox combo (closes BLOCKERS §2) #172

claude referenced this pull request

2026-05-11 02:19:14 +02:00

ops: ADR-0014 Phase 06 prune Q2-2026 additional sunset candidates + silverbullet migration spec #173

claude referenced this pull request

2026-05-11 02:23:14 +02:00

docs(hermes): canonical 7-deliverable bundle templates (Phase 07 §G + GPT §7) #174

claude referenced this pull request from a commit

2026-05-11 02:24:55 +02:00

state/reports: WAKEUP_BRIEF for operator after overnight session 2026-05-11

claude referenced this pull request

2026-05-11 02:25:31 +02:00

state/reports: WAKEUP_BRIEF for operator after overnight session 2026-05-11 #175

codex commented

2026-05-24 07:59:20 +02:00

Collaborator

Fork A triage (codex): closing as superseded/stale.

This was a Phase/L-1.5 baseline closure artifact. The current roadmap explicitly treats Phase 01/freeze and the F-series migration waves as historical execution records; active closeout now lives in Milestone 01 and ADR-0020. This PR also edits BLOCKERS_FOR_OPERATOR.md, which is no longer an allowed operator-status surface under ADR-0006/current AGENTS rules.

Do not merge as-is; if any baseline spot-check value remains, rewrite it as a current Milestone 01/02 issue or small PR.

Fork A triage (codex): closing as superseded/stale. This was a Phase/L-1.5 baseline closure artifact. The current roadmap explicitly treats Phase 01/freeze and the F-series migration waves as historical execution records; active closeout now lives in Milestone 01 and ADR-0020. This PR also edits `BLOCKERS_FOR_OPERATOR.md`, which is no longer an allowed operator-status surface under ADR-0006/current AGENTS rules. Do not merge as-is; if any baseline spot-check value remains, rewrite it as a current Milestone 01/02 issue or small PR.

codex closed this pull request

2026-05-24 07:59:21 +02:00