flex-auth/README.md
tegwick dcda1e603f
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Build and Publish Container Image / build-and-push (push) Successful in 1m16s
Prepare the access-engine repository coordinate without applying the rename.
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
2026-09-15 23:38:48 +02:00

29 lines
1.3 KiB
Markdown

# flex-auth
Policy-as-code authorization registry and control plane for NetKingdom-aligned
systems.
The live Forge and State Hub coordinate is still `flex-auth` (repository UUID
`fda8ad85-a7d7-4055-8f21-902a533e59df`, Forge ID `42`). `FLEX-WP-0020` will
rename that coordinate to `access-engine` and keep the Go module, binary,
`FLEX_AUTH_*` variables, Helm releases, container package
`coulomb/flex-auth`, and policy/API vocabulary unchanged. Work-record
frontmatter stays `repo: flex-auth` until State Hub rebind. Planned clone:
`https://forgejo.coulomb.social/coulomb/access-engine.git`.
Start with [INTENT.md](INTENT.md) for the project boundary and direction.
Research notes and ADRs live in [docs/](docs/) and [docs/adr/](docs/adr/).
The product boundary is captured in [SCOPE.md](SCOPE.md), and the current
Product Requirements Document is
[docs/ProductRequirementsDocument.md](docs/ProductRequirementsDocument.md).
The 2026-05-15 pre-implementation assessment that shapes the current
sequencing is in
[docs/pre-implementation-assessment.md](docs/pre-implementation-assessment.md).
The CARING reference-implementation approach is captured in
[docs/caring-architecture-blueprint.md](docs/caring-architecture-blueprint.md).
Workplans live in [workplans/](workplans/), with sequencing captured in
[docs/workplan-planning-map.md](docs/workplan-planning-map.md).