Generated from processes/process/bean-triage.bpmn by gen-processes-viz.ts — do not edit here. All processes

Assured AI programme: triage a bean

Process_AAI_BeanTriage · strict · 2 step(s)

Decide what an open bean is to the programme. Beans are how work is done, in whichever repository does it; programme issues are how the programme sees it. A bean gets an issue when it delivers part of an epic, changes a date, creates or clears a cross-workstream dependency, or needs a human review or decision. Otherwise it stays a bean. The issue is the record of the link, by a hidden line in its body, <!-- bean: owner/repo/id -->; nothing in the bean’s repository is written.

How it connects

• Called by: Assured AI programme: act on bean drift
• Calls: Assured AI programme: propose a new or changed epic
• Presented on: no docs page section shows this diagram

Lanes — who acts

lane	role	what it does here
Workstream lead	workstream-lead	Decides what a bean is to the programme, and keeps the issue that carries it current. An agent may act in this lane and propose; the lead decides.
PM & Architecture Integration	pm-architecture-integration	Owns epics: accepts, amends or declines a proposal (req:aai-linking#LINK-07).

Steps

Every one of the 2 step(s) is documented.

step	lane	skill / sub-process	what it does
Propose an epic Call_Propose	PM & Architecture Integration	calls Assured AI programme: propose a new or changed epic	There is none: propose one (the epic-proposal process); the issue goes under it.
Open the issue with its bean line A_Issue	Workstream lead	—	Under the epic or proposal, as a sub-issue: its type:, ws: and stage: labels, a Programme fields table, and one <!-- bean: owner/repo/id --> line per bean it carries. A decision or a dependency is a type:decision or type:dependency issue instead (req:aai-dependencies#DEP-02).

Decisions

Every one of the 2 decision(s) is documented.

decision	what decides it	branches
Does the programme need to see it? GW_Matters	Answered by the rule: does it deliver part of an epic, change a date, create or clear a cross-workstream dependency, or need a human review or decision? no covers a step under a bean an issue already carries, and work outside the programme.	no → Stays a bean: decision recorded yes → Is there an epic or proposal for it?
Is there an epic or proposal for it? GW_Epic	Answered from the board’s Workstreams page: does an open epic or epic proposal of its workstream cover it?	yes → Open the issue with its bean line no → Propose an epic