Generated from
cat-harness/sdlc/processes/bean-close.bpmnbygen-processes-viz.ts— do not edit here. All processes · cat-harness processes
Close the bean
Process_BeanClose · strict · 4 step(s)
The closing half of every bean’s life: end it in a state that says why. Done work is completed and archived; unwanted work is scrapped with its reasons — never deleted — and archived; blocked work records what it waits on and goes back to todo for whoever can act. Called, never run on its own, straight before an end event of a process that called Process_BeanOpen.
A bean is never deleted. A scrapped bean stops the next agent re-entering a dead end; a deleted one leaves a sibling unable to tell abandonment from accident.
How it connects
- Called by: Drain the beans, Agent bean lifecycle, Code change and review, A refused merge-train member, Test Data Curation — Fixed Sets and Generated Recipes, Test-plan execution, Watching a pinned upstream dependency, Adopting an upstream version bump, Getting started, Authoring a document, Content Change and Review, Content lifecycle, Draft, review and publish, Editing and HCI validation, L1 document ingestion — a document to the L1 source knowledge graph, Data sharing agreement document life cycle, Authoring a paper, DIIG — from a health system bottleneck to a costed implementation plan, L2 DAK authoring
- Calls: none
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
| lane | role | what it does here |
|---|---|---|
| Agent (this session) | authoring-agent | Closes only the bean its caller opened and claimed — Process_BeanOpen already sent someone else’s to its sibling — and picks one of three recorded endings for it. |
Steps
Every one of the 4 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Complete (no unchecked todos left)Close_Complete | Agent (this session) | todo-manager | Only once nothing is unchecked, and with a summary of what changed. The engine’s resolve completes a bean only after the instanceitself has completed, or has nothing left but archive steps — whether work is done is a judgement, and a bean is not closed on someone else’s say-so. The only resolve op in the corpus (check:bean-calls). |
Scrap with reasons NEVER deleteClose_Scrap | Agent (this session) | todo-manager | status: scrapped, plus a “Reasons for Scrapping”section. This is what “disable” means here — the CLI has no disabled state; its vocabulary is draft, todo, in-progress, completed, scrapped. The agent’s own beans update; the engine has no scrap op.DELETION IS NEVER THE ANSWER, even though beans delete exists. A scrappedbean records that the work was considered and rejected, and why; a deleted one leaves a sibling session unable to tell abandonment from accident, and leaves the next agent free to re-open the same dead end. |
Archive the bean (completed or scrapped)Close_Archive | Agent (this session) | todo-manager | Move the bean, now completed or scrapped, into the archive, with a line saying which process closed it. A bean still open stays where it is with a note saying why: only a completed or scrapped bean may be archived (check:bean-archive), and only once the calling process has finished. The periodic sweep (beans archive) still archives anything this step leaves — it stays the floor, this op the exception (todo-manager § Archiving). The owner’s 2026-10-20 ruling keeps archive a per-activity op; this is that activity, shared by both terminal outcomes and by every caller. |
Record the blocker and hand backClose_RecordBlocker | Agent (this session) | bean-coordination | Blocked is not scrapped. Set --blocked-by, say in thebody what would unblock it, and return it to todo so it is visible to whoevercan act. An in-progress bean nobody is progressing reads as active work. Not archived: the work is still wanted. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Outcome?Close_Outcome | The performer’s judgement on the work the caller did, and one of three recorded endings. done: complete it only when no todo is unchecked, with a summary of what changed. not wanted: set it scrapped with a ‘Reasons for Scrapping’ section — never delete. blocked: record what it waits on with --blocked-by, say what would unblock it, and return it to todo, because an in-progress bean nobody is progressing reads as active work. The caller’s end event usually says which: an end named for success is done, one named for a refusal or a decline is not wanted, one named for an undetermined answer is blocked. | done → Complete (no unchecked todos left) not wanted → Scrap with reasons NEVER delete blocked → Record the blocker and hand back |