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

Record approved metered requester extension and six native creates
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 4s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e387-534d-70e3-ad53-4ea05676db8c
This commit is contained in:
codex 2026-09-27 21:08:43 +02:00
parent b15ab5774f
commit 2f4485a4b6
5 changed files with 353 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/metered-requester-extension.md
View file

@ -1,8 +1,8 @@
# Exact metered requester extension — awaiting operator approval
# Exact metered requester extension — operator approved
Existing work: RPF-WP-0035-T06, SECRETS-WP-0009-T03, REINAH-WP-0003-T06.
This proposal does not change CCR-2026-0025's admitted scope until the operator
explicitly approves it. No additional task or workplan is created.
The operator explicitly approved this exact packet on 2026-09-27; the mandate
and six successful native creates are retained in docs/evidence/. No additional task or workplan is created.
Reviewed command: scripts/create-metered-approval-requests.sh, invoking the
adjacent Python script with --clock-trust-file and --mandate. The command freezes
@ -20,9 +20,13 @@ credential. It writes non-secret native receipts and refuses to overwrite a
partial receipt or retry an uncertain create. Planned IDs persist before POST.
Four requester tests plus two existing token-time tests pass. Dry-run lists
exactly six records. Actual creation still requires explicit operator mandate,
fresh admitted Railiance Clock interval and attended reader execution. Native
exactly six records. Creation completed under the explicit operator mandate,
a fresh admitted Railiance Clock interval and attended reader execution. Native
review and consume/backend admission remain after creation. The current human
review HTTP adapter admits human-control records only: companion ordinary
approval needs its own supported approver path; do not relabel it human-control
or use the retired combined operator client to bypass that boundary.
Six native requests were created with no human entries or consume. The attended
reader closed. Informed Decision exact-ID ordinary human review is implemented
for the three companion IDs; it preserves their native ordinary control type.