tegwick
b78c15a7ef
T02 — intake INFD-IN-0001 filed with gate-house and messages sent to gate-house, key-cape and approval-engine. Status progress; it now waits on an external ruling. key-cape was told explicitly why T07 is not answering KEY-WP-0013-T02 yet — a placeholder callback URI would either fail closed or register an origin no component owns — and given the token shape to check now rather than at T07. T03 — ProductRequirementsDocument.md. 30 requirements, each traced to a GOAL.md DoD item, an INTENT principle or wrongness condition, a state-transition guard, or a named external contract, and each with an observable pass condition. Anti-requirements are stated as testable absences: no dwell timers, no attention analytics, no dark patterns, no auto-approval, no approval-state caching, no authorization endpoint. Four limitations are recorded up front, including that escalate without a mandate graph is forwarding and that view_hash is computed by the renderer. T04 — UseCaseCatalog.md. L0-L5 with counterparties, plus ten negative cases bound to guards and isolation vectors. Each case records the constraint it places on the shared schema, so scale invariance is testable rather than asserted. Closes with the four changes that would fork the object. T05 and T07 remain gated on the ruling. T06 is independent and is next. 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
40 lines
1.7 KiB
Markdown
40 lines
1.7 KiB
Markdown
# Intake records
|
|
|
|
## INFD-IN-0001 — Layer placement and approver-UI ownership
|
|
|
|
```yaml
|
|
id: INFD-IN-0001
|
|
kind: intake
|
|
title: Layer placement and approver-UI ownership
|
|
status: open
|
|
origin: coordination
|
|
origin_ref: INFD-WP-0001-T02
|
|
priority: high
|
|
owner: gate-house
|
|
repo: informed-decision
|
|
lane: blue
|
|
tags:
|
|
- decision-request
|
|
- cross-repo
|
|
created: '2026-09-09'
|
|
updated: '2026-09-09'
|
|
description: >-
|
|
approval-engine names an approvals inbox under Non-Goals, leaving the
|
|
browser-facing approver UI unowned; key-cape KEY-WP-0013-T02 is blocked on a
|
|
client_id and callback URI no component has claimed, and approval-engine
|
|
recorded in docs/keycape-service-registrations.md that they must come from
|
|
that component's owner. informed-decision claims the surface and asks
|
|
gate-house to rule on three things before any code is written: (R1) layer and
|
|
role, proposed PEP-shaped under statute §6.4 and companion §5; (R2) whether a
|
|
presentation attestation makes this a PIP as well, or whether presentation
|
|
evidence must reach consumers only via audit-core, noting §17 has no assigned
|
|
request-claim schema owner; (R3) the relationship between informed-decision's
|
|
view_hash and approval-engine's binding digest, which both claim to
|
|
canonicalize "the binding" but cover different material. R3 is the highest
|
|
risk: shipping both without a stated authority rule leaves the estate with two
|
|
canonicalizations of one act. Proposal is (b) — distinct attestations with the
|
|
binding digest authoritative for replay and view_hash authoritative only for
|
|
what was shown. Full request: docs/gate-house-decision-request-layer-placement.md.
|
|
Blocks INFD-WP-0001 T05 and T07; T03, T04 and T06 proceed regardless.
|
|
state_hub_intake_id: "01a08610-f458-7fd5-b284-26a65d1d73c2"
|
|
```
|