Draft Umlaufmappe groupings of one-question memos so founder sign-off can happen in a compact sitting once Stage 1 can bind. Assistant: grok Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
4.2 KiB
| id | type | title | domain | repo | status | owner | topic_slug | flavor | depends_on | created | updated | related | origin | origin_ref | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| INFD-WP-0002 | workplan | Compact sign-off batches for credentials and decisions | infotech | informed-decision | proposed | grok | netkingdom | planning |
|
2026-09-14 | 2026-09-14 |
|
demand | the-custodian/history/20260914-open-workplan-chokepoints.md |
Compact sign-off batches for credentials and decisions
Founder direction 2026-09-14: credential and decision chokepoints should
move through the informed-decision framework as batches that can be
signed off in a compact timeframe, not as twelve disconnected
needs_human tasks.
INFD-WP-0001 still owns Stage 1 (walking skeleton against a deployed
approval-engine, T08). This plan does not absorb the earlier
residual “full L3 product.” That remains residual until separately
promoted. This plan is the demanded slice: review-groups of Decision
Memos for (1) credential/custody items and (2) founder/owner
decisions.
Invariant from Stage 1: one question per memo. A batch is a
Umlaufmappe grouping of memos, not one memo with unrelated acts.
Humans bind; agents draft. This repository still does not evaluate
authorization (access-engine remains the only PDP).
Draft the first two batches (agent-authored, unsigned)
id: INFD-WP-0002-T01
status: todo
priority: high
From the 2026-09-14 chokepoint assessment, assemble two compact batches
as Decision Memo files (or the current memo schema) under
docs/batches/2026-09-14/:
- Credentials / custody — OpenBao paths, issuer/registration
leftovers, CCR-style items, and any
warden routepointer that still needs a human to actually mint or seal. Each memo is one act. No secret values in the memos. - Decisions / assent — founder or owner sign-offs currently holding workplans (reviews, explicit approvals, policy accepts). Each memo is one question.
Bound the set so a single sitting can finish it (small N, ordered,
highlights required). Name the review group already admitted
(net-kingdom-admins or the current human review group). Do not submit
until T02.
Done when both batch indexes exist, each memo has one binding target, required highlights, and a trace to the blocking workplan/task id.
Batch presentation contract (review-group, compact sitting)
id: INFD-WP-0002-T02
status: todo
priority: high
depends_on: [INFD-WP-0002-T01]
Specify how a batch is presented without forking the Decision Memo schema: ordered list, per-memo bind, progress across the sitting, no “approve all” that skips highlights. Reuse review-group work already in this repo. If Stage 1 UI cannot yet render a group, the contract still holds for a recorded desktop sitting.
Done when docs/specs/ (short addendum, not a new product) states the
batch rules and the anti-requirement: no bundled unrelated acts, no
auto-approval, no agent disposition.
Sign-off sitting once the Stage 1 surface can bind
id: INFD-WP-0002-T03
status: wait
priority: high
depends_on: [INFD-WP-0002-T02, INFD-WP-0001]
Wait until INFD-WP-0001-T08 (or an equivalent deployed bind path)
can take a real human disposition. Then run one compact sitting on the
two batches. Record presentation evidence (view_hash per memo).
Unfinished memos stay in the batch; do not mark the workplan finished
on a partial sitting.
Done when at least one credential memo and one decision memo are bound by a human through this surface, reconstructable from stored presentation, and the blocking hub tasks are updated from those dispositions rather than from chat.
Feed outcomes back to State Hub without hub-authoring
id: INFD-WP-0002-T04
status: wait
priority: medium
depends_on: [INFD-WP-0002-T03]
For each bound memo, update the owning repo file (task status,
decision record, CCR note) and let fix-consistency project. Do not
POST /workplans/ or mint hub-only tasks. Residual unsigned memos
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.