coulomb/approval-engine
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: confirm exact canonical consumed act binding

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a140c4-354a-7823-8f0d-8f717397f786
This commit is contained in:
tegwick 2026-10-16 09:20:33 +02:00
parent 8624fa20bb
commit eece796b8b
3 changed files with 98 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

44
workplans/ADHOC-2026-10-16.md Normal file
View file

@ -0,0 +1,44 @@
---
id: APPROVAL-WP-ADHOC-2026-10-16
type: workplan
title: "Repair exact consume-confirmation native binding comparison"
domain: infotech
repo: approval-engine
status: finished
flavor: implementation
owner: codex
topic_slug: netkingdom
created: "2026-10-16"
updated: "2026-10-16"
---
## Refuse Python-equal JSON-distinct consumed act bindings
```task
id: APPROVAL-WP-ADHOC-2026-10-16-T01
status: done
priority: high
```
Bounded source repair demanded by the CUST-WP-0080 strict execution-seam proof.
INTENT basis: exact binding and authenticated consumption evidence; no authority
or native grant is added. Existing canonical native-five-field digest is reused.
ExecutionConfirmationClient now recomputes the served and expected digests and
requires the served digest field to correspond, replacing Python dict equality
which accepted nested True/1, False/0 and integer/float substitutions.
Before repair seven regression cases wrongly confirmed (four target type
substitutions and three absent/wrong/type-invalid served digest fields); valid
nested types with reordered keys passed. The repair retains this failure history.
Twelve added regression cases cover exact native JSON correspondence, including
substitutions with both retained and recomputed served digests, without
changing the native digest algorithm, request/PDP digest contract or API schema.
Canonical integration/publication and the Platform mediator's final provider
client source pin remain with the coordinator; preparation does not claim them.
Existing APPROVAL-WP-0004 closure and generated identifiers are untouched.
APPROVAL-WP-0002-T01/T04/T05 remain existing live native acceptance obligations;
none is promoted or completed here. No production auth, approval mutation,
credential, deployment or backend operation was used. This completed low-risk
local source repair introduces no residual native obligation beyond those
existing records and the coordinator's integration of this exact artifact.