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

Complete renamed image source and verify bounded consumer migration readiness
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Failing after 1m2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
This commit is contained in:
tegwick 2026-10-11 23:25:19 +02:00
parent dd15d8cf3f
commit 16ca97b277
13 changed files with 455 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

29
workplans/FLEX-WP-0036-runtime-rename-access-engine.md
View file

@ -65,7 +65,9 @@ written.
```task
id: FLEX-WP-0036-T01
status: progress
status: wait
needs_human: true
intervention_note: "Exact new runtime principals/naming are included in the single daily red batch with the nine TokenReview grants; no per-item question."
priority: high
state_hub_task_id: "4f9a796d-832f-5936-8a34-eb980f6e1b57"
```
@ -82,6 +84,8 @@ Gate: decision accepted by the founder.
`flex-auth` is a stub that prints the rename and exits 2. The other target
names in the table still need the founder's acceptance.
2026-10-11: target names are captured as proposed FLEX-DEC-2026-021. The new reviewer subjects are the scope-expansion component and are already in the single daily red batch. Binary disposition FLEX-DEC-2026-020 remains accepted; no founder acceptance of this broader table is fabricated.
## Inventory every consumer reference and open handoffs
```task
@ -115,9 +119,9 @@ current source must now come from `./cmd/access-engine`.
```task
id: FLEX-WP-0036-T03
status: progress
status: wait
priority: high
depends_on: [FLEX-WP-0036-T01]
depends_on: [FLEX-WP-0036-T01, FLEX-WP-0036-T04, RPF-WP-0044-T07]
state_hub_task_id: "487525e5-c89e-586e-8e9b-54ac6da0804e"
```
@ -144,11 +148,15 @@ PDP-self resource lane in these pin packages; the old inventory's
fetch package. No new self-lane or caller grant is created to fill that absence.
T03 remains progress until the new image and ordered live checks are proven.
2026-10-11: source compatibility is tested and locally built. The next native step waits for the accepted runtime table, published exact artifact and the ordered Argo ownership proof (RPF-WP-0044-T07). No new founder rollout question; the source/public-package scope lives in the existing single batch.
## Rename the source
```task
id: FLEX-WP-0036-T04
status: progress
status: wait
needs_human: true
intervention_note: "New public coulomb/access-engine image package publication is included in the single daily red batch. Local source/build checks pass; paired publication has not run."
priority: medium
depends_on: [FLEX-WP-0036-T01]
state_hub_task_id: "ff7fd369-326f-5044-aaa4-96c5f45c80e9"
@ -177,6 +185,8 @@ which are immutable on a `helm upgrade`, so it ships with the new releases.
Also the image package and the `/opt/flex-auth` paths, which every live pin's
args reference.
2026-10-11: source now includes canonical `/opt/access-engine/examples` and retains the legacy paths for existing pins. The lifecycle Containerfile starts the renamed engine rather than the retired stub. The old Topaz integration variable remains usable for one release with a warning; an explicit new value takes precedence. CI builds once, publishes to the already admitted legacy package on normal push, and has an explicit paired-publication dispatch for the new package. `tools/publish-runtime-images.sh` independently compares both registry manifest digests; a local image ID or equal config alone is not publication proof. The new public package is a daily red-batch item; no paired dispatch has run. T04 remains progress until accepted publication resolves both repositories to the same immutable digest.
## Stand up the access-engine namespace next to flex-auth
```task
@ -219,7 +229,7 @@ native action occurred. T03/T04 and ordered predecessor gates remain unchanged.
```task
id: FLEX-WP-0036-T06
status: todo
status: wait
priority: medium
depends_on: [FLEX-WP-0036-T02, FLEX-WP-0036-T05]
state_hub_task_id: "f0470e5c-3ea7-506c-b8bb-3ade0b57ff88"
@ -233,6 +243,15 @@ allow and a live deny against the new pin, and no traffic left on the twin
Gate: every inventory row closed with owner evidence.
2026-10-11 native dependency wait qualified once on existing T02/T05 and
ordered predecessor live proof; no consumer switch executed. Actual source work
adds a deterministic `MigrationReadiness` classifier and public-source
re-derivation/owner handoff report. All five owners still require source work;
operator and tunnel custody remains with their owners. The verifier refuses to
turn comments, spoofed hosts, unsigned readiness flags or source-only changes
into native readiness. Owner-authenticated live allow/deny and timed old-twin
no-traffic/soak evidence remain necessary; this task is not closed by the report.
## Retire the flex-auth runtime
```task