Repository navigation
Close cycle 02 — two accepted, one never started, and neither criterion moved - #27
Merged
Merged
Conversation
…on moved `closed` / `shipped`, ended 2026-09-23, on day 3 of a 21-day appetite. Not `completed`, because that would claim every deliverable was accepted and D1 was not; not the circuit breaker either, because the end date was 19 days away. D2 and D3 accepted (#20, #26). D1 — five private invitations — deferred for the second cycle running: nobody has been asked, and the cost is five messages and fourteen days of waiting. The closure records the sentence it owed in advance, and one it did not: both engineering deliverables landed in three days, so this cycle did not repeat cycle 01's shape — it repeated the other half. The deliverable that was somebody else's calendar did not move, and 19 days of appetite are unspent because the appetite was sized for work cycle 01 had already done. It also records what the cycle cost, measured: six adversarial rounds and six confirmation runs on one read-only module, eleven real defects, five refusals. Three defects the author introduced in later rounds; three refusals over a sentence in a decision record rather than over code. And the transferable lesson, which belongs to cycle 03 rather than to this closure: a class-level statement ends the sequence, a per-instance clause produces one refusal per round. **The charter is corrected, not changed.** PDR-0003 was merged in #24 with the charter's own "Success criteria" section left as it was: it still stated the twenty-members-at-day-30 count that the PDR replaced, while the open questions three screens below announced the revision. A closure that must say which criteria moved cannot be written against a section the decider had already superseded. The five phase-1 pilot criteria are now written where the criteria live, with the arithmetic that removed the count, and the commission criterion is where PDR-0003 put it — behind the phase-2 gate. One thing came out of that and belongs to the decider: PDR-0003 moved the commission criterion "with a later date" and **named no date**. I have not invented one. It is recorded in the charter's open questions as owed, because a viability criterion without a deadline is a criterion that cannot fail. `handover.md` is rewritten for the next session: nothing in flight, cycle 03 to frame around `copying`, the framework upgrade owed at this boundary, and the operational lessons that cost this cycle time — a push dismisses an approval while a description edit does not, T4 makes any commit reprint the whole sheet, and a delegated verifier has no session identifier of its own. `nstack fitness` compliant, plan included. Agent-Session: 4151570f-613e-475f-ba3f-b465b35d9a83 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
9 of 15 tasks
napkinstack-admin
approved these changes
Sep 23, 2026
12 of 17 tasks
This was referenced Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close cycle 02 — two accepted, one never started, and neither criterion moved
Module
None. This pull request changes no module:
docs/project/only.Deliverable
Out of cycle: closing the cycle. A pull request that changes no module beyond its description is
not delivery work, and this one closes the cycle itself.
What it changes
Cycle 02 is closed —
closed/shipped, ended 2026-09-23, on day 3 of a 21-day appetite.D3's state becomes
accepted, joining D2. D1 staysdeferred.shippedrather thancompleted:completedwould claim every deliverable was accepted, and D1was not. Nor is this the circuit breaker — the end date was 19 days away. The cycle closed early
because everything it could do with engineering was done, and what is left is not engineering.
The closure says four things it owes:
verdicts with the exit codes ordered by severity and a ceiling that refuses to answer past 30×
(D3 — three verdicts, so the headline cannot say yes to a trader the answer is warning about #26). And, outside the deliverables, ADR-0002, ADR-0003, PDR-0002 with four amendments,
PDR-0003 and
handover.md.copyingmodule, which does not exist. The fifth —screening's predictions confronted withreality — is the only one this cycle touched, and only by making it possible: the module now
states a fee burden, a refused share and a reproducible share precisely enough to be wrong.
Nothing has confronted them with a member's fills, because no member has any.
built a tool for choosing traders with no evidence that any member wants to copy one, and that
was a decision rather than an oversight. It was offered one week on D1 alone and chose three
weeks on everything. It did not repeat cycle 01 — both engineering deliverables landed, in
three days. It repeated the other half: the deliverable that was somebody else's calendar did
not move, and 19 days of appetite are unspent because the appetite was sized for work cycle 01
had already done.
read-only module: eleven real defects, five refusals, every refusal correct. Three defects the
author introduced in later rounds inside changes nobody asked for; three refusals over a
sentence in a decision record rather than over code. With the transferable lesson, which
belongs to cycle 03: a class-level statement ends the sequence, a per-instance clause produces
one refusal per round.
The charter is corrected, not changed
PDR-0003 was merged in #24 with the charter's own "Success criteria" section left as it was. It
still stated the twenty-members-at-day-30 count that the PDR replaced, while the open questions
three screens below announced the revision as done. A closure that must say which criteria moved
cannot honestly be written against a section the decider had already superseded.
So the five phase-1 pilot criteria are now written where the criteria live — faithful copying, zero
key incident, revocation exercised, 60% continuing past day 14, and
screening's predictionsconfronted with reality — with the arithmetic that removed the count: five invitations return
refuted 47% of the time while the product is exactly as good as forecast. The commission
criterion is where PDR-0003 put it, behind the phase-2 gate.
This applies an accepted decision. It makes no new one, and the charter still changes only through
a PDR (
docs/os/06-decisions.md§4).One thing is owed by the decider, and I have not invented it. PDR-0003 moved the commission
criterion to phase 2 "with a later date" and named no date. The old before 2027-03-21 is not
restated as though it had survived. It is recorded in the charter's open questions, because a
viability criterion without a deadline is a criterion that cannot fail.
handover.mdRewritten for the next session: nothing in flight,
mainat8277dca, cycle 03 to frame aroundcopying, the framework upgrade owed at this boundary, and the operational lessons that cost thiscycle time — a push dismisses an approval while a description edit does not; T4 makes any commit,
including a documentation-only one, reprint the whole test sheet; a delegated verifier has no
session identifier of its own.
It also corrects a mistake made while writing it: the hook citing "ADR-0004" cites NapkinStack's
ADR-0004, which this project's
docs/adr/0001names and explains. It is not a missing decision, andthe handover now says so rather than sending the next session looking for it.
Oracle
contents are the template's four questions, and the cycle's framing promised one sentence in
advance
nstack fitnessrefuses a closed cycle withno
outcomeand noended_on(C6), and refuses an unknown deliverable state (C4)nstack fitnessexit 0, plan compliantKind of oracle: fitness function
Review budget
Contracts
Definition of Done
nstack fitnessexit 0, read on its own exit statusnstack check screeningstill 0 on this branchmainTest sheet
Not required: this pull request changes no module beyond its description
(
docs/os/05-workflow.md§7).Summary
DONE
Cycle 02 closed,
shipped, with its closure written to the template's four questions. D3 markedaccepted. The charter's success criteria brought into line with PDR-0003, which #24 had left
half-applied.
handover.mdrewritten for the next session.VERIFIED
nstack fitnessexit 0 and plan compliant, read on its own exit status. The closure's figures comefrom the merged pull requests and from the confirmation runs recorded in #26, not from memory.
ASSUMED
That closing early is what the decider wants, rather than spending the remaining 19 days on D1
inside this cycle. The alternative was available and is named in the closure; closing is what lets
cycle 03 be accepted, since only one cycle may be accepted at a time.
NOT VERIFIED
Nothing in this pull request is testable beyond the fitness function. Whether the closure's reading
of the cycle is right is the decider's call, which is what this review is.
RISKS
The closure is blunt about the project's position on purpose. If it is wrong, it is wrong in
writing and can be argued with — which is better than the alternative. And the phase-2 date stays
open: the project currently has a viability criterion that cannot fail.
Signals to report
The signal. PDR-0003 revised a success criterion, and the charter's criteria section kept the
old one for a day, with the same file announcing the revision three screens below. Nothing
mechanical noticed.
nstack fitnessalready reads both files; a PDR that says it replaces acriterion could be required to name which one, and the criterion could be required to name the PDR
that last changed it. Otherwise the only thing standing between an accepted decision and a stale
charter is somebody reading both on the same afternoon.