docs: distinguish deferred tasks from blocked work

This commit is contained in:
tegwick 2026-08-19 20:42:39 +02:00
parent 8cde3af88c
commit 1122543e17
2 changed files with 14 additions and 14 deletions

View file

@ -9,8 +9,8 @@
| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | ORGREF-WP-0001 | backlog | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T01 | wait | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T02 | wait | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T03 | wait | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T04 | wait | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T05 | wait | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T01 | todo | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T02 | todo | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T03 | todo | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T04 | todo | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |
| task | ORGREF-WP-0001-T05 | todo | — | workplans/ORGREF-WP-0001-foundation-and-entry-gate.md |

View file

@ -4,7 +4,7 @@ type: workplan
title: "Foundation, blast-radius inventory, and execution entry gate"
domain: infotech
repo: prj-forgejo-org-refactor
status: active
status: backlog
owner: codex
topic_slug: railiance
created: "2026-08-11"
@ -29,9 +29,9 @@ This workplan exists so the finding and its evidence are not lost, and so the
condition for starting is written down and checkable rather than a judgement
call made from memory months later.
All tasks remain `wait` while the project-wide deferral stands. An operator may
reopen T01/T02 to `todo` before the full execution gate because they are
read-only; T03 onward still requires all four gate conditions.
All tasks remain `todo` (not started) while the project-wide deferral stands.
An operator may move T01/T02 to `progress` before the full execution gate
because they are read-only; T03 onward still requires all four gate conditions.
## Entry gate — do not start T03 onward until all four hold
@ -70,7 +70,7 @@ It must not:
```task
id: ORGREF-WP-0001-T01
status: wait
status: todo
priority: high
state_hub_task_id: "c027b40f-f25a-403f-8d83-e29044bab20a"
```
@ -89,7 +89,7 @@ forgejo.coulomb.social/coulomb/core-hub` in `railiance-apps/charts/core-hub/valu
```task
id: ORGREF-WP-0001-T02
status: wait
status: todo
priority: high
state_hub_task_id: "90d6a61e-b715-4073-aa3e-e92340c78dc8"
```
@ -112,7 +112,7 @@ archival policy.
```task
id: ORGREF-WP-0001-T03
status: wait
status: todo
priority: high
state_hub_task_id: "2e458360-3035-47e8-a0c5-33e2249ffaa0"
```
@ -127,7 +127,7 @@ time.
```task
id: ORGREF-WP-0001-T04
status: wait
status: todo
priority: high
state_hub_task_id: "32030788-ed92-492f-920d-5b9a51663fc0"
```
@ -138,7 +138,7 @@ record. This closes the entry gate.
```task
id: ORGREF-WP-0001-T05
status: wait
status: todo
priority: medium
state_hub_task_id: "4f5d510a-c52b-42d4-9a84-ecf432ce4866"
```