pdurlej/platform

Fork 0

state(L3): refresh JOURNEY + OPEN_LOOPS (24-day catch-up, archive originals) #414

Closed

claude wants to merge 3 commits from claude/state/l3-refresh-2026-05-23 into main

claude commented

2026-05-24 10:34:54 +02:00

Collaborator

What changed

state/L3/JOURNEY.md (~22 KB, 205 lines) — now refreshed content:

Preserves original 8 Feb-Apr inflections verbatim
Adds Inflections 9-12 covering May arc (strategic stop + ADR-0001/0002, stacked-PR incident → ADR-0017/0018, RS2000 cutoff + ADR-0020/0021/0022 trio + milestone train + cousin-onboarding rollout + Things/Wloczykij/OpenClaw-mail subsystems, current soak-active state)
New 4th pattern: "Crystallize the rule the moment it's costly enough"

state/L3/OPEN_LOOPS.md (~16 KB, 188 lines) — now refreshed content:

New categories: blocked_on_precondition (soak/PAT/Vault/embedding gating) + meta (L3 staleness)
Refreshed unresolved_active with M01-M08 items
New closed_since_apr30 enumerating ~9 items that landed in May
Reframes vps-home-platform-infra from "policy gap" to "ADR-0020 reclassified, M01-gated cleanup"
Each item has OL-2026-05-* id, status, blocker, owner, evidence

Archive (historical chain preserved)

state/L3/archive/2026-04-30-JOURNEY.md — original (pre-milestone-train, F1/F2/F3-era)
state/L3/archive/2026-04-30-OPEN_LOOPS.md — original

No information lost; cousins reading old commit refs still find the prior synthesis at predictable path.

Future refresh convention (informal, will document if it stabilizes)

Write JOURNEY-YYYY-MM-DD.md and OPEN_LOOPS-YYYY-MM-DD.md as new dated files
Review (claude+codex canary, or operator alone for trivial)
Promote: git mv current canonical → archive/YYYY-MM-DD-* and git mv dated → canonical
Next cousin always reads state/L3/JOURNEY.md (no need to know which is "latest dated")

Contradictions spotted during refresh (carried in OPEN_LOOPS, not blocking this PR)

ADR-0020/0021/0022 carry Status: Proposed in front-matter despite being merged — checked 2026-05-24, all three already Accepted on main; the L3 sub-agent flag was stale. No follow-up needed.
W-wave naming (Codex's plan) vs M-milestone numbering don't have 1:1 mapping in any committed doc — still open, will surface in next Codex deliverable.

Evidence base

Verified against git log --since="2026-05-01" main, state/STATUS_NOW.md (2026-05-18), state/cutover/{rs2000-control-plane-cutoff,honcho-closeout-plan}.md, state/roadmap/current-platform-roadmap.md (PR #386 milestone train + plan-genealogy table), AGENTS.md § 0 (PR #397).

Tier per ADR-0007: Trivial — docs-only, content was reviewed by sub-agent + claude before path (b) promotion; no schema/code/runtime mutation; Codex's active W1 work on other paths unaffected.

Refs:

ADR-0006 (single operator status file)
ADR-0007 (risk-proportional canary)
ADR-0023 (gemini reviewer cousin — was queued to review this PR, paused per operator decision 2026-05-24 due to API quota; see state/spike-understand-anything/05-gemini-pause-2026-05-24.md)
PR #386 (milestone train consolidation)
PR #397 (cousin-onboarding § 0 pointer)

Refreshed L3 synthesis covering the May arc (Inflections 9-12) and re-categorized open loops against the milestone train. Per operator decision 2026-05-24 ("ty dokończ"), finalized as **path (b)**: dated files promoted to canonical names, originals archived under `state/L3/archive/`. ## What changed **`state/L3/JOURNEY.md`** (~22 KB, 205 lines) — now refreshed content: - Preserves original 8 Feb-Apr inflections verbatim - Adds Inflections 9-12 covering May arc (strategic stop + ADR-0001/0002, stacked-PR incident → ADR-0017/0018, RS2000 cutoff + ADR-0020/0021/0022 trio + milestone train + cousin-onboarding rollout + Things/Wloczykij/OpenClaw-mail subsystems, current soak-active state) - New 4th pattern: *"Crystallize the rule the moment it's costly enough"* **`state/L3/OPEN_LOOPS.md`** (~16 KB, 188 lines) — now refreshed content: - New categories: `blocked_on_precondition` (soak/PAT/Vault/embedding gating) + `meta` (L3 staleness) - Refreshed `unresolved_active` with M01-M08 items - New `closed_since_apr30` enumerating ~9 items that landed in May - Reframes `vps-home-platform-infra` from "policy gap" to "ADR-0020 reclassified, M01-gated cleanup" - Each item has `OL-2026-05-*` id, status, blocker, owner, evidence ## Archive (historical chain preserved) - `state/L3/archive/2026-04-30-JOURNEY.md` — original (pre-milestone-train, F1/F2/F3-era) - `state/L3/archive/2026-04-30-OPEN_LOOPS.md` — original No information lost; cousins reading old commit refs still find the prior synthesis at predictable path. ## Future refresh convention (informal, will document if it stabilizes) 1. Write `JOURNEY-YYYY-MM-DD.md` and `OPEN_LOOPS-YYYY-MM-DD.md` as new dated files 2. Review (claude+codex canary, or operator alone for trivial) 3. Promote: `git mv` current canonical → `archive/YYYY-MM-DD-*` and `git mv` dated → canonical 4. Next cousin always reads `state/L3/JOURNEY.md` (no need to know which is "latest dated") ## Contradictions spotted during refresh (carried in OPEN_LOOPS, not blocking this PR) 1. **ADR-0020/0021/0022 carry `Status: Proposed`** in front-matter despite being merged — *checked 2026-05-24, all three already `Accepted` on main; the L3 sub-agent flag was stale*. No follow-up needed. 2. **W-wave naming (Codex's plan) vs M-milestone numbering** don't have 1:1 mapping in any committed doc — still open, will surface in next Codex deliverable. ## Evidence base Verified against `git log --since="2026-05-01" main`, `state/STATUS_NOW.md` (2026-05-18), `state/cutover/{rs2000-control-plane-cutoff,honcho-closeout-plan}.md`, `state/roadmap/current-platform-roadmap.md` (PR #386 milestone train + plan-genealogy table), `AGENTS.md` § 0 (PR #397). Tier per ADR-0007: **Trivial** — docs-only, content was reviewed by sub-agent + claude before path (b) promotion; no schema/code/runtime mutation; Codex's active W1 work on other paths unaffected. Refs: - ADR-0006 (single operator status file) - ADR-0007 (risk-proportional canary) - ADR-0023 (gemini reviewer cousin — was queued to review this PR, paused per operator decision 2026-05-24 due to API quota; see `state/spike-understand-anything/05-gemini-pause-2026-05-24.md`) - PR #386 (milestone train consolidation) - PR #397 (cousin-onboarding § 0 pointer)

claude added 2 commits

2026-05-24 10:34:54 +02:00

decisions(0023): replace noreply email with actual gemini Forgejo identity 3e81cd022a

Operator registered cousin gemini in Forgejo on 2026-05-24 with email
p+gemini@durlej.me (following the existing claude/codex/glm/iskra/ollama
pattern of p+<cousin>@durlej.me, NOT the noreply.git.pdurlej.com pattern
I had proposed in v1 of this ADR).

Verified live 2026-05-24:
- Keychain: security find-internet-password -s git.pdurlej.com -a gemini
  returns 40-char PAT
- Forgejo: GET /api/v1/user returns {login: "gemini",
  email: "p+gemini@durlej.me", is_admin: false}
- Repo visibility: pdurlej/* org including bdmax, bohemian-sidecar,
  fallow-py and more

Plus Infisical entry created at /home-platform/forgejo_accounts/
p+gemini@durlej.me (production environment populated; dev/staging
intentionally empty, matching existing cousin pattern).

Plus Bitwarden vault entry git.pdurlej.com (gemini) with username +
password + PAT custom field, cross-machine backup pattern.

No semantic change — just bringing the ADR in sync with the actual
identity values. Tier: Trivial (docs-only string replace).

state(L3): add refreshed JOURNEY + OPEN_LOOPS dated 2026-05-23

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

Details

infra-docs-drift / docs-drift (pull_request) Successful in 5s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 21s

Details

pyfallow / Pyfallow gate (control-plane) (pull_request) Successful in 19s

Details

python-ci / Python 3.11 (pull_request) Successful in 41s

Details

base-is-main / guard (pull_request) Successful in 1s

Details

python-ci / Python 3.12 (pull_request) Successful in 41s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 22s

Details

python-ci / Python 3.13 (pull_request) Successful in 37s

Details

workflow-lint / lint (pull_request) Successful in 5s

Details

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

Details

0051c78d09

Original state/L3/JOURNEY.md and state/L3/OPEN_LOOPS.md were written
2026-04-30 during F1/F2/F3 era and went stale through 24 days of
milestone-train discovery, ADR-0017/0018/0020/0021/0022 merges, and
new subsystems (Things, Wloczykij, OpenClaw-mail, Honcho v2).

Refreshed dated copies preserve originals as historical reference and
add coverage for the May arc:

JOURNEY-2026-05-23.md (~22 KB, 205 lines):
- Preserves original 8 Feb-Apr inflections verbatim
- Adds Inflections 9-12 covering the May arc:
  - 9 (May 3-9): strategic stop + ADR 0001/0002 + Phase 02 cataloging
  - 10 (May 11-14): stacked-PR incident → ADR-0017/ADR-0018
  - 11 (May 17-20): RS2000 cutoff + ADR 0020/0021/0022 trio +
    milestone train (PR #386) + cousin-onboarding rollout +
    Things/Wloczykij/OpenClaw-mail subsystems
  - 12 (now, May 23): soak ACTIVE, W1 starting, Honcho LLM closeout,
    modularity preconditioning M08-M09
- New 4th pattern: "Crystallize the rule the moment it's costly
  enough"

OPEN_LOOPS-2026-05-23.md (~16 KB, 188 lines):
- New categories: blocked_on_precondition (soak/PAT/Vault/embedding
  gating) + meta (L3 staleness)
- Retains unresolved_active with refreshed M01-M08 items
- Adds closed_since_apr30 enumerating ~9 items that landed in May
- Reframes vps-home-platform-infra from "policy gap" to "ADR-0020
  reclassified, M01-gated cleanup"
- Each item has OL-2026-05-* id, status, blocker, owner, evidence

Contradictions spotted during refresh:
- ADR-0020/0021/0022 carry Status: Proposed in front-matter despite
  being merged on main; ADR-0017 "Accepted-on-merge" convention not
  uniformly applied. Filed as follow-up (see OPEN_LOOPS-2026-05-23).
- W-wave naming (Codex's plan) vs M-milestone numbering don't have
  1:1 mapping in any committed doc — flagged.

Sub-agent synthesis verified against actual git log
(git log --since="2026-05-01" main), STATUS_NOW (2026-05-18),
state/cutover/{rs2000-control-plane-cutoff,honcho-closeout-plan}.md,
state/roadmap/current-platform-roadmap.md (PR #386), AGENTS.md § 0
(PR #397).

Per operator choice 2026-05-23: dated artifacts running parallel to
originals; promote to undated only after operator review (this PR is
that review surface).

Tier: Trivial per ADR-0007 (docs-only, two new files, no schema/
code/runtime mutation; no concurrent file editing — Codex's active
W1 work on other paths is unaffected).

claude added 1 commit

2026-05-24 14:50:31 +02:00

state(L3): path (b) — promote dated refresh to canonical, archive originals

pyfallow / Pyfallow gate (control-plane) (pull_request) Successful in 19s

Details

python-ci / Python 3.11 (pull_request) Successful in 40s

Details

base-is-main / guard (pull_request) Successful in 2s

Details

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

Details

infra-docs-drift / docs-drift (pull_request) Successful in 4s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 21s

Details

python-ci / Python 3.13 (pull_request) Successful in 38s

Details

workflow-lint / lint (pull_request) Successful in 4s

Details

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

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 21s

Details

python-ci / Python 3.12 (pull_request) Successful in 40s

Details

009d5d0381

Per operator decision (głosówka 2026-05-24, "ty dokończ"): finalize the
L3 refresh PR with path (b) rather than path (a) running-parallel.

Result:
- state/L3/JOURNEY.md and state/L3/OPEN_LOOPS.md are now the refreshed
  2026-05-23 content (canonical names — no dated suffix cluttering
  future cousin reads).
- Original 2026-04-30 content preserved as
  state/L3/archive/2026-04-30-JOURNEY.md and
  state/L3/archive/2026-04-30-OPEN_LOOPS.md (historical chain
  explicit, no information lost).
- CONTRADICTIONS.md, ORPHANS.md, SUMMARY.md, entities.json remain
  at canonical paths — they were not refreshed in this pass (still
  reflect 2026-04-30 synthesis); next refresh can dated-then-promote
  using the same archive pattern.

Future refresh convention (informal, document if it stabilizes):
1. Write JOURNEY-YYYY-MM-DD.md and OPEN_LOOPS-YYYY-MM-DD.md as new
   dated files
2. Review (claude+codex canary, or operator alone for trivial)
3. Promote: git mv current canonical → archive/YYYY-MM-DD-* and git mv
   dated → canonical
4. Next cousin always reads state/L3/JOURNEY.md (no need to know
   which is "latest dated")

Tier per ADR-0007: Trivial (file moves only, no content edit).

claude changed title from ~~state(L3): refresh JOURNEY + OPEN_LOOPS dated 2026-05-23 (24-day catch-up)~~ to state(L3): refresh JOURNEY + OPEN_LOOPS (24-day catch-up, archive originals)

2026-05-24 14:51:28 +02:00

codex commented

2026-05-27 08:41:21 +02:00

Collaborator

If the idea is still useful, it should be rewritten from current main as a smaller atomic PR or issue. No old branch should merge only because it is green.

W9 rewrite/archive triage: closing this old PR as stale/superseded, not rejecting the underlying idea. Reason: L3 refresh conflicts with current W8/W9 state; rewrite a fresh L3/status refresh from current main if still needed. If the idea is still useful, it should be rewritten from current main as a smaller atomic PR or issue. No old branch should merge only because it is green.

codex closed this pull request

2026-05-27 08:41:21 +02:00

codex referenced this pull request

2026-05-27 08:45:08 +02:00

docs(w9): rewrite stale charter topology #517