coulomb/informed-decision
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Promote INFD-WP-0001 to active with a review note

Browse source 
C-23 flagged lifecycle drift: the workplan was still 'proposed' while T02 sat at
'progress'. ADR-007 correctly refuses to auto-promote, so this is a deliberate
promotion rather than a status the tool inferred.

The plan is genuinely being worked and the review it was pending has happened:
against approval-engine's INTENT/SCOPE/layer.yaml/WP-0002 and its keycape
service registrations, the accepted security layer model v0.7 and companion,
the repo-classification and project-repository-flavor standards, and the schema,
state-transition tables and vectors in history/.

Also corrected the body text, which claimed T03-T05 would all be rewritten if
the ruling differs. That was too broad: only T05 and T07 depend on the catalog
row. T03, T04 and T06 describe what the surface must do and what the evidence
must contain, and neither changes with layer placement.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V3W1dQG7GFFM9d94jFx7iR

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1565372@bnt-lap001
Assistant-Session: 16bb2f25-b34c-49ef-8e94-5fec3567a568
This commit is contained in:
tegwick 2026-09-09 14:12:52 +02:00
parent 7e5fb59ddf
commit 7ae67b2f4e
2 changed files with 22 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

6
WORK-RECORDS.md
View file

@ -10,9 +10,9 @@
| --- | --- | --- | --- | --- |
| workplan | INFD-WP-0001 | proposed | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T01 | done | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T02 | todo | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T03 | todo | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T04 | todo | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T02 | progress | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T03 | done | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T04 | done | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T05 | todo | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T06 | todo | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |
| task | INFD-WP-0001-T07 | todo | — | workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md |

24
workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md
View file

@ -4,11 +4,23 @@ type: workplan
title: "Founding specs and approver-UI ownership"
domain: infotech
repo: informed-decision
status: proposed
status: active
owner: claude
topic_slug: netkingdom
created: "2026-09-09"
updated: "2026-09-09"
reviewed_at: "2026-09-09"
reviewed_against_commit: "ee2cca5"
reviewed_note: >-
Reviewed against approval-engine's INTENT, SCOPE, layer.yaml,
APPROVAL-WP-0002 and docs/keycape-service-registrations.md; the accepted
NetKingdom security layer model v0.7 and companion v0.2; the
repo-classification and project-repository-flavor standards; and the
Decision Memo schema, state-transition tables and canonicalization vectors in
history/20260909-initial-exploration. Repo-owned specification work can
proceed. T05 and T07 remain externally gated on the gate-house ruling
requested as INFD-IN-0001; T08 is additionally gated on
APPROVAL-WP-0002-T01 and a deployed approval-engine.
origin: founding
origin_ref: history/20260909-initial-exploration/InitialExploration.md
state_hub_workstream_id: "a985a65a-08f7-5a39-8645-b618ea022657"
@ -30,10 +42,12 @@ engine. That component is not in this repo."* `APPROVAL-WP-0002-T01` remains
`progress` partly because of it. This workplan closes that gap by naming the
owner and shipping the contract.
**Status is `proposed`, pending review** against the current `approval-engine`,
`access-engine`, `key-cape`, `gate-house` and `audit-core` contracts, and
against the deployment estate. T02 is the gate: if `gate-house` places this
component differently, T03–T05 are rewritten before they are written.
**Reviewed 2026-09-09; the plan is active.** Reviewed against the contracts
listed in the frontmatter. T02 remains the gate for the *architecture*: if
`gate-house` places this component differently, T05 and T07 are rewritten before
they are written. T03, T04 and T06 are independent of the ruling because they
describe what the surface must do and what the evidence must contain, neither of
which changes with the catalog row.
Scope boundary for this workplan: **specification and contract, plus one
walking skeleton**. Full L3 product build is residual and belongs to