Close three workplans whose file status never caught up to reality

INFD-WP-0001-T08 (walking skeleton), INFD-WP-0002-T03/T04 (compact
sitting human binds and their file-level feedback), and
INFD-WP-0004-T02/T04 (list action request/admit-and-rollout) were all
still marked wait/progress despite being satisfied days ago -- some as
far back as 2026-09-14/21. Discovered while reviewing this repo's open
work at session close. All three workplans are now finished.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 169987@bnt-lap001
Assistant-Session: 322ef1ef-9048-4021-8570-b6d6f6347999
This commit is contained in:
tegwick 2026-09-27 21:41:40 +02:00
parent 4c2325ac76
commit 0f97b1e1b2
3 changed files with 44 additions and 11 deletions

View file

@ -4,12 +4,12 @@ type: workplan
title: "Founding specs and approver-UI ownership"
domain: infotech
repo: informed-decision
status: active
status: finished
flavor: planning
owner: claude
topic_slug: netkingdom
created: "2026-09-09"
updated: "2026-09-11"
updated: "2026-09-27"
reviewed_at: "2026-09-09"
reviewed_against_commit: "ee2cca5"
reviewed_note: >-
@ -441,7 +441,7 @@ issuer, so it is not this repository's to decide alone.
```task
id: INFD-WP-0001-T08
status: progress
status: done
priority: medium
state_hub_task_id: "b5c1d329-9580-5672-9640-2930cbbb729a"
@ -466,6 +466,15 @@ act is permitted.
Gated externally on `approval-engine` `APPROVAL-WP-0002-T01` reaching `done` and
on the service being deployed with an origin this surface can reach.
**Done, discovered stale 2026-09-27:** every acceptance condition is now met
live against the deployed engine. Platform-root approved `infd-20260927-b01`
through this surface today (and other memos before it); `return`/`discuss`
distinct from `decline` and highlight-acknowledgment gating are implemented
and covered by the test suite (`tests/test_review_controller.py`); no code
path here evaluates permission (`policy.py`/`review.py` consume flex-auth's
decision only). This was the last open task in `INFD-WP-0001`; the workplan
is finished.
2026-09-10 — **domain core built and tested; the live proof remains gated.**
`approval-engine` `APPROVAL-WP-0002-T01` is still `progress` and the namespace
has no pods, so the end-to-end proof against a deployed engine cannot run. Built

View file

@ -4,14 +4,14 @@ type: workplan
title: "Compact sign-off batches for credentials and decisions"
domain: infotech
repo: informed-decision
status: active
status: finished
owner: grok
topic_slug: netkingdom
flavor: planning
depends_on:
- INFD-WP-0001
created: "2026-09-14"
updated: "2026-09-15"
updated: "2026-09-27"
related:
- INFD-WP-0001
- STATE-WP-0092
@ -99,7 +99,7 @@ auto-approval, no agent disposition.
```task
id: INFD-WP-0002-T03
status: wait
status: done
priority: high
depends_on: [INFD-WP-0002-T02, INFD-WP-0001]
state_hub_task_id: "917e3e34-b9de-5c51-ab29-e820957a7407"
@ -184,11 +184,19 @@ cut over from T03. Named recipient reused from existing presentations
(not written to git). Store has seven `infd-20260914-*` memos plus the
three T03 records. Human bind remaining. Task stays `wait`.
**Done, discovered stale 2026-09-27:** both acceptance conditions have long
been satisfied and were never flipped. The three `SECRETS-WP-0010-T03-*`
credential memos were human-bound with confirmed engine submissions (noted
already as of 2026-09-14 in this same task's history, above), and decision
memos have been human-bound through this surface repeatedly since, most
recently `infd-20260927-b01` today by platform-root. The durable store
currently shows 9 confirmed submissions total.
## Feed outcomes back to State Hub without hub-authoring
```task
id: INFD-WP-0002-T04
status: wait
status: done
priority: medium
depends_on: [INFD-WP-0002-T03]
state_hub_task_id: "26d8ff42-65bb-582e-9ecf-dbd367eaa7a8"
@ -202,3 +210,7 @@ either stay in a later batch or are declined with a reason.
Done when the assessment’s credential/decision examples that were in
the sitting show file-level status changes and a progress event naming
the memo ids.
**Done, discovered stale 2026-09-27:** satisfied by T03's file-level update
above plus this session's own `progress/` events naming `infd-20260927-b01`
and the T03 memo ids. `INFD-WP-0002` is finished.

View file

@ -4,11 +4,11 @@ type: workplan
title: "Comfortable decision review — a `list` action for the overview"
domain: infotech
repo: informed-decision
status: active
status: finished
owner: claude
topic_slug: netkingdom
created: "2026-09-21"
updated: "2026-09-21"
updated: "2026-09-27"
related:
- INFD-WP-0003
- INFD-IN-0005
@ -61,7 +61,7 @@ regression and needs fixing regardless of `list`. Record the finding under
```task
id: INFD-WP-0004-T02
status: wait
status: done
priority: high
state_hub_task_id: "3d5f51ac-c226-5489-bfb6-d5829c70e6f6"
```
@ -71,6 +71,11 @@ as `INFD-IN-0008`, owned by flex-auth. Sent 2026-09-21 to the flex-auth inbox
(message `a7b9ef3b-f95c-4c50-bfc5-7628d16881f6`); waiting on flex-auth. Done when flex-auth publishes a package, version
and digest that answers `list`, with fixtures.
**Done, discovered stale 2026-09-27:** flex-auth admitted `list` in
`FLEX-WP-0032` (v3, 2026-09-21, `FLEX-DEC-2026-017`) — this task was never
flipped from `wait` even though the answer landed the same day it was asked.
The package has since moved to v6 (`examples/informed-decision-sitting/policy.md`).
## Consumer side: `list` action and limited-disclosure overview
```task
@ -101,7 +106,7 @@ digest `sha256:f45e366d…`. Chromium passes 13 of 13 through the real Flex Auth
```task
id: INFD-WP-0004-T04
status: wait
status: done
priority: high
state_hub_task_id: "65d6dd6e-208a-54ee-93c0-40b6ab1d8adf"
```
@ -111,3 +116,10 @@ version and digest. The operator then applies the configuration and the image
built from T03. Verify that the overview shows all eleven memos without a fresh
MFA, that opening a memo still enforces the strict `read` rule, and record the
rollout in `docs/evidence/`.
**Done, discovered stale 2026-09-27:** rolled out days ago and reconfirmed
live today — the overview lists memos on the 12-hour `list` window while a
specific memo's `read`/`accept` still enforces the strict 900-second window
(observed directly in `policy_observations` while diagnosing a platform-root
review session: identical requests alternated `allow`/`policy_denied` purely
by action and assurance age). `INFD-WP-0004` is finished.