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

Prepare the access-engine repository coordinate without applying the rename.
All checks were successful
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) Successful in 1m16s
Details

Browse source 
FLEX-WP-0020 T01-T03: fresh preflight is zero-blocker, repository-only
scope is FLEX-DEC-2026-013, concurrent work is FLEX-DEC-2026-014.
T04 handoff requests are posted; owner work-records are still required.
T06 stays behind the exact human confirm string and a post-commit preflight.

Assistant: grok
Assistant-Session: 01a0a6cb-0334-72c0-83b0-2df57474a0f6
This commit is contained in:
tegwick 2026-09-15 23:38:48 +02:00
parent 0e020b2d8c
commit dcda1e603f
5 changed files with 166 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

36
decisions/decisions.md
View file

@ -1797,3 +1797,39 @@ review of the assertions.
- Bears on `FLEX-DEC-2026-011` F1. A PEP cannot verify who answered; it now at
least can verify that the answer is about the request it sent. Those are
different properties and neither substitutes for the other.
---
## FLEX-DEC-2026-013 — Repository-only scope for the access-engine coordinate
**Date:** 2026-09-15
**Status:** accepted
**Workplan:** `FLEX-WP-0020-T03`
**Hub:** `9f2dd7a4-6437-4e59-8403-ae56d9cc1d09`
Rename the Forge/State Hub repository coordinate to `access-engine`. Retain
the Go module `github.com/netkingdom/flex-auth`, binary/CLI, `FLEX_AUTH_*`
variables, Kubernetes namespace/Services/Helm, container package
`coulomb/flex-auth`, policy/API vocabulary, audiences, and telemetry labels.
Keep the `FLEX-WP-` prefix and every existing State Hub UUID. A broader
product/runtime rebrand needs a later workplan after soak.
This is the reviewed table already written in `FLEX-WP-0020`. Changing a
`retain` row returns that plan to `proposed`.
---
## FLEX-DEC-2026-014 — Concurrent work may remain open during FLEX-WP-0020 cutover
**Date:** 2026-09-15
**Status:** accepted
**Workplan:** `FLEX-WP-0020-T01` / `T05`
`FLEX-WP-0027-T03` stays `wait` (operator human review of three T03 memos).
`FLEX-WP-0022` T01/T02 stay open (tenant-engine must name the CheckRequest
tenant relation; T03 fixtures landed without a policy change). Neither
changes repository identity, Forge ID, or the source UUID. They do not have
to finish before a repository-coordinate rename, and they must not be
cancelled or rewritten by it. Live Forge apply (`T06`) still needs the exact
human confirmation string and a fresh zero-blocker preflight of the commit
being renamed.