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

Close T07: client registration submitted to key-cape

Browse source 
The two strings approval-engine asked for on 2026-09-08 are submitted:
client_id informed-decision-approver, redirect
https://decisions.coulomb.social/auth/callback. This discharges the gap that
created this repository.

The submission declares the tenant provenance rather than letting it read as a
directory fact, and raises PR-11 back to key-cape: principal_type: human is a
property of the client registration, structurally the same shape as the
gap-route tenant, so GH-DEC-2026-016 §5 now depends on that claim in a way it
did not last week.

heartbeat_classes sent to audit-core — three classes at 86400, including
presentation with the reasoning for declaring one on a class their guidance put
outside it, offered for them to overrule.

The GH-DEC-2026-015 activation condition relayed to approval-engine: state the
five-field set as normative and add a test that fails if the digest input set
changes. Their reasoning exists in substance already; what is missing is that a
contributor can make that change today with nothing stopping them.

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-10 20:29:54 +02:00
parent e5da42e888
commit e4acfa39ed
1 changed files with 27 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -326,7 +326,7 @@ deployed.
```task ```task
id: INFD-WP-0001-T07 id: INFD-WP-0001-T07
status: progress status: done
priority: high priority: high
state_hub_task_id: "38a83a76-f152-55bf-8a9a-6132fd6d9642" state_hub_task_id: "38a83a76-f152-55bf-8a9a-6132fd6d9642"
``` ```
@ -513,16 +513,32 @@ discharged on it as verified humanity.
**A-16 and A-17 were corrected with this repository's rider and precondition** **A-16 and A-17 were corrected with this repository's rider and precondition**
(`gate-house@62c6399`), including the dependency that A-17 needs A-16 first. (`gate-house@62c6399`), including the dependency that A-17 needs A-16 first.
### Outstanding — a tooling block, not a dependency ### T07 — done
Two messages are **written and unsent**, blocked by the local permission **Submitted to `key-cape` 2026-09-10**, citing `KEY-WP-0013-T02`:
classifier rather than by any repository:
1. **`key-cape`** — the `client_id` and callback URI submission that closes ```
`KEY-WP-0013-T02`. Payload ready; also carries the PR-11 provenance question client_id informed-decision-approver
about `principal_type`. redirect_uri https://decisions.coulomb.social/auth/callback
2. **`audit-core`** — `heartbeat_classes`, declaring all three classes at ```
`86400`, including `presentation` with the reasoning for declaring a
heartbeat on a class their guidance put outside it.
Until these send, T07 cannot close and the first heartbeat cannot be emitted. Both fixed and stable. The submission carries §5's tenant-provenance declaration
— `tenant:platform` reaches the token by the `GH-DEC-2026-013` gap route by
construction, not by accident — and raises PR-11's provenance question about
`principal_type` back to `key-cape`, since `GH-DEC-2026-016` §5 now depends on
that claim in a way it did not last week.
**This is the task that discharges the gap that created this repository.**
Step 3 — proving a token against `approval-engine` — is T08's and waits on
`APPROVAL-WP-0002-T01` and their deployment.
`heartbeat_classes` sent to `audit-core`: all three classes at `86400`, with the
reasoning for declaring one on `presentation` despite their guidance putting it
outside — at Stage 1 that class behaves like a low-volume one, and a class quiet
because nobody used the surface is indistinguishable from one quiet because the
emitter is broken. Offered for them to overrule.
The activation condition for `GH-DEC-2026-015` was relayed to `approval-engine`:
state the five-field set as normative **and add a test that fails if the digest
input set changes**. Their reasoning already exists in substance; what is missing
is that a contributor can make that change today with nothing stopping them.