4.3 KiB
| id | type | title | domain | repo | status | owner | topic_slug | flavor | created | updated | related | origin | origin_ref | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CUST-WP-0075 | workplan | Use the dependency graph to shrink the blocked set and route human gates to decisions | infotech | the-custodian | active | the-custodian | custodian | planning | 2026-10-03 | 2026-10-03 |
|
analysis | the-custodian/docs/evidence/2026-10-03-dependency-graph-triage/README.md |
Use the dependency graph to shrink the blocked set
Why
CUST-WP-0072 and CUST-WP-0074 built the facility: flavor, workplan
and task depends_on, needs_human, blocked_on, wait_until,
decision_id, indexed by C-20 and checked by C-39/C-40/C-41. Nobody has
yet read the resulting graph. On 2026-10-03 the open set is 108
workplans (100 blocked) with 232 wait tasks. The security concepts
(credential custody, attended OpenBao provisioning, identity, access
engine) are the dominant blockers, and every one of their 69 human gates
is free text: zero carry a decision_id, so Bernd has no single list to
resolve and C-40 rule 4 never fires.
This workplan uses the graph in three ways: clear what the graph says is
already satisfied, correct what the graph says is mis-statused, and
collapse the human gates into a handful of hub decisions that one
attended session can resolve. Evidence and scripts:
docs/evidence/2026-10-03-dependency-graph-triage/.
Rules: owner repos are edited directly (Bernd's 2026-09-30 direction on
CUST-WP-0074-T06), one commit per repo, synced by fix-consistency;
no hub writes except recording and resolving decisions; residual-flavor
workplans are left alone except to finish one whose tasks are all done.
Capture the graph and publish the triage
id: CUST-WP-0075-T01
status: done
priority: high
File-view and hub-view scans committed under
docs/evidence/2026-10-03-dependency-graph-triage/ with the headline
numbers in its README. Done 2026-10-03.
Clear satisfied waits and correct mis-statused workplans
id: CUST-WP-0075-T02
status: progress
priority: high
Graph says satisfied (every depends_on target terminal):
ACTIVITY-WP-0032-T05, COORDINATION-WP-0004-T02, TD-WP-0003-T07,
USER-WP-0027-T04, USER-WP-0028-T03, RCLK-WP-0005-T04 (keeps its
blocked_on), RAPPS-WP-0014-T03 and MARKITECT-WP-0002-T07 (keep
their human gate; drop the satisfied depends_on).
Mis-statused: UPC-WP-0002/0003/0004 blocked without a wait task;
MARKITECT-WP-0002 and RBT-WP-0006 active while every open task
waits; ACTIVITY-WP-0042 proposed with three unqualified waits;
RAIL-FAB-WP-0031 blocked with all tasks done; FLUID-WP-0007 carries
the non-canonical status done; NK-WP-0011 depends on
NK-WP-0003/0004/0006, which no file carries.
Done when each owner repo is committed and synced and a re-run of the
file scan lists none of the above.
Route the human gates to decisions
id: CUST-WP-0075-T03
status: todo
priority: high
Cluster the 69 needs_human waits by the person's actual act (one
attended OpenBao provisioning window, one ArgoCD go-ahead, one Telegram
operator session, Vergabe two-user acceptance, trust-root design, and
so on). For each cluster record one hub decision whose description lists
the task ids, then set decision_id on those tasks in the owner files.
Done when every needs_human wait in a non-residual open workplan
carries a decision_id and Bernd has one ranked decision list.
Record the security-infrastructure lessons
id: CUST-WP-0075-T04
status: todo
priority: medium
Write history/20261003-security-gate-packets.md: what the graph shows
about how credential, identity and access work gets blocked, and the
improvements that make it easier to maintain and extend (decision-linked
gates, batched attended windows, delegated-applier scope, catalog lanes
as the unit of provisioning). Proposals only; no canon change here.
Monitor: keep repo and hub in step
id: CUST-WP-0075-T05
status: progress
priority: medium
After every slice: commit, statehub fix-consistency for each touched
repo, one progress event on this workplan, and the headline numbers
appended below so progress is visible from the hub.
Progress log
- 2026-10-03 start: 108 open / 100 blocked / 232 wait / 69 human gates /
0 with
decision_id.