Skip to content

docs(memory): the four lifecycle decisions a port lost, as pointers #892

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wenzowski wants to merge 1 commit into
base: main
Choose a base branch
from
+28 −1
Draft

docs(memory): the four lifecycle decisions a port lost, as pointers #892

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .serena/memories/core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,8 @@ Read on demand, never all of them.
- `mem:workflow/agent-fanout` — spawning a subagent, or running more than one
session against this repo.
- `mem:workflow/landing-loop` — landing a branch; before "repairing" `land`, the
lease, the CI wait or their suites.
lease, the CI wait or their suites; porting a lifecycle (a trap, a lock, a
reaper) out of a retired program.
- `mem:workflow/sonar-scope` — Sonar refuses your branch; reading or changing
`sonar-gate`; a Sonar verdict looks wrong on a SHA; before treating a `final`
failure as trunk's, or a check-run's annotations as the whole finding list.
Expand Down
26 changes: 26 additions & 0 deletions .serena/memories/workflow/landing-loop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,32 @@ means it is a different change wearing the same subject.
The cheap answer is to redo the amend on the clean pushed commit. It costs one
gate run and cannot borrow anything.

## Porting a lifecycle: four owner decisions, each a pointer

Recovered from PR #848's session (2026-09-06), where a port carried every STEP
of `land.sh` and dropped its LIFECYCLE with every gate green. Each rule lives
on its row; this section is the pointer, not the argument.

- **Crash-only is the architecture** (CLOUD-1558). The lock and the reaper
exist because the container crashes and leaves zombies. Recovery is the NEXT
instance's job on entry — reap, then reclaim, then register — and `Drop`,
`trap` and in-process unwinding are never the mechanism.
- **Read the retired program line by line** (CLOUD-1559). Every line is a
measured decision; each gets `carried`/`changed`/`withdrawn`/`lost`. The
losses cluster in trap handlers and top-of-file guards, which no test title
covers. The audit's remainder is CLOUD-1561.
- **No gate but a commit-message gate distinguishes committed from dirty**
(CLOUD-1565). `verify` runs over a dirty tree with a content-keyed receipt;
`tree-clean` gates the push only. Commit early, push to the draft, rewrite
draft history freely; the Stop arm is CLOUD-1503's `commit-or-discard`.
- **One PR is an efficiency, not a commandment** (CLOUD-1566). A two-merge
dependency is a correctness reason for a second PR, claimed in the Ready
block's `blockers`, never in a PR body alone.

The composition itself is a declared list with a durable compensation per step
(CLOUD-1556 carries the Pkl default and its schema; CLOUD-1564 `Push`'s row),
and the sleep policy that the raced wait needs is CLOUD-1557.

## Rollout posture

Every mechanism here fails open on a clone that predates it, so none of them
Expand Down