From 3378bce1c34c8cd6894ba898647ac5bee2793820 Mon Sep 17 00:00:00 2001 From: whosbax Date: Wed, 23 Sep 2026 22:47:01 +0200 Subject: [PATCH] =?UTF-8?q?Accept=20cycle=2003=20=E2=80=94=20the=20clock?= =?UTF-8?q?=20starts=202026-09-24,=20and=20the=20key=20is=20the=20first=20?= =?UTF-8?q?critical=20code?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `status: accepted`. Three weeks, 2026-09-24 to 2026-10-15, the dates as framed: acceptance lands the day before the start, so nothing moves. The order the framework asks for was kept and is now in the record: cycle 02 closed (#27), the framework taken to v0.6.1 at the boundary (#29), and only then this. Accepting a cycle under a framework version the project had not yet recorded would have meant a cycle judged by something the repository did not declare. `handover.md` is brought forward to this state: cycle 03 accepted and running, `copying` still nonexistent and created by the first task, the framework in step, and four steps in order — D1 first because it is day one for the third time, then the module's scaffold in its own pull request, then D2 and D3 sequentially because both are `copying`. Three things the next session would otherwise pay for again are written down: - **Look at D1 on day three**, not at the end. If the five messages have not gone out by 2026-09-27, this cycle is repeating both of its predecessors, and the framer's note says so before anyone can argue about it. - **`nstack doctor` exits non-zero on 0 gaps** when no token can read the GitHub settings. Read the gap count, not the exit code — the 13 `NOT VERIFIED` lines are the rule working, not a failure: what cannot be read is never reported as guarded. - **`nstack update` branches from the current HEAD without saying so.** #29 had to be replanted because HEAD was on a feature branch. Check out `main` first. `nstack fitness` compliant: one accepted cycle at a time holds, cycle 02 being closed on `main`. Agent-Session: 4151570f-613e-475f-ba3f-b465b35d9a83 Co-Authored-By: Claude Opus 5 (1M context) --- .../cycles/03-a-key-given-and-taken-back.md | 2 +- docs/project/handover.md | 44 ++++++++++++------- 2 files changed, 28 insertions(+), 18 deletions(-) diff --git a/docs/project/cycles/03-a-key-given-and-taken-back.md b/docs/project/cycles/03-a-key-given-and-taken-back.md index 3acff88..0bfc099 100644 --- a/docs/project/cycles/03-a-key-given-and-taken-back.md +++ b/docs/project/cycles/03-a-key-given-and-taken-back.md @@ -1,6 +1,6 @@ --- goal: "Find out whether anyone wants this, and make the key a member hands flet safe to give and safe to take back" -status: proposed +status: accepted appetite_weeks: 3 start: 2026-09-24 end: 2026-10-15 diff --git a/docs/project/handover.md b/docs/project/handover.md index 8e2d137..280275d 100644 --- a/docs/project/handover.md +++ b/docs/project/handover.md @@ -24,28 +24,38 @@ closure of cycle 02 says it at more length. | | | |---|---| -| `main` | `8277dca` — D2 (#20), ADR-0002 (#22), the pilot FAQ and declared demand (#23), PDR-0003 and the revised criterion (#24), ADR-0003 and this file (#25), D3 (#26) | -| In flight | **nothing.** No open pull request, no branch awaiting a sheet | +| `main` | D3 (#26), cycle 02's closure and the charter correction (#27), cycle 03's framing (#28), NapkinStack v0.6.1 (#29) | +| **Cycle 03** | **accepted, running 2026-09-24 to 2026-10-15.** D1 a spike, D2 and D3 on `copying` | | `screening` | 81 tests, `nstack check` 0, `nstack fitness` compliant, verified on `main` | +| `copying` | **does not exist yet.** It is created by the first task below | +| Framework | v0.6.1, project and CLI in step | -Older branches are merged or superseded and can be ignored. `nstack doctor` reports compliant. +Older branches are merged or superseded and can be ignored. `nstack fitness` is compliant and +`nstack doctor` reports **0 gaps**; its 13 `NOT VERIFIED` lines are the GitHub settings, which need +a token to read — *what cannot be read is never reported as guarded*. `doctor` exits non-zero in +that state, so read the gap count, not the exit code. ## Next, in order -1. **Frame cycle 03 around the `copying` module** — the closure of cycle 02 says where the framing - starts. It is `critical`. Two things are not negotiable and they are tests, not process: the - agent key can place orders and nothing else, and revocation works. Two commitments from - `pilot-faq.md` are framed *with* the module, not around it: the notice shown **before** a member - acts, and revocation as a first-class path. Framing is `playbooks/framing.md`, with the decider; - a cycle is `proposed` until the decider accepts it in its own pull request. -2. **D1 on day one, for the third time.** Five private messages and a fourteen-day clock. It has - been deferred by two cycles, it gates every phase-1 criterion in the charter, and the - alternative is building a `critical` module for a demand nobody has observed. -3. **Upgrade NapkinStack at this cycle boundary, before cycle 03 is accepted.** 0.6.1 exists; the - project is recorded at 0.6.0. Sequence, and only in this order: `uv tool install napkinstack - --force`, then `nstack update` (it makes the branch `nstack/update-vX.Y.Z`), then `nstack - doctor`. Upgrading the CLI without `nstack update` turns doctor's L1 red. **The framework moved - 0.3.0 to 0.6.1 in three days: re-check at every boundary rather than when someone remembers.** +1. **D1, and it is day one.** Five private messages, sent within three days, read at day 14. + Deferred by two cycles, in the cycle for the third time, and it gates every phase-1 criterion in + the charter. **The framer's note says to look on day three, not at the end:** if the messages + have not gone out by 2026-09-27, this cycle is already repeating both of its predecessors. +2. **Scaffold the module:** `nstack new-module copying NapkinStack/maintainers critical`, declared + `user_facing` — a member sees what it does. Its own pull request, as `screening` had. +3. **D2, then D3**, sequentially: both are `copying`, and it is one pull request per module. D2 is + the key a member gives and takes back; D3 is the notice shown before they act. Read the cycle + for what the criteria are built to refuse — every one of them names **the venue** as the thing + that answers, never our own state. +4. **`critical` means adversarial verification without a cap** (ADR-0003), unlike `screening`'s one + round. Hold that line when it is inconvenient; the reason is in *What this project has learned + about itself* below. + +**Owed at the next boundary, not before:** check NapkinStack again. It moved 0.3.0 to 0.6.1 in +three days. Sequence, and only in this order: `uv tool install "napkinstack==X.Y.Z" +--with-executables-from pre-commit`, then `nstack update`, then `nstack doctor`. Upgrading the CLI +without `nstack update` turns doctor's L1 red. **And `nstack update` branches from the current HEAD +without saying so** — check out `main` first, or expect to replant the branch, as #29 had to. ## Decisions taken, and where they live