access-engine/README.md
tegwick f758381cea
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 6s
Build and Publish Container Image / build-and-push (push) Successful in 1m23s
FLEX-WP-0036: Go module is github.com/netkingdom/access-engine; T02 consumer inventory
- module path renamed (no external importers); golangci local-prefixes
- ACCESS_ENGINE_RUN_TOPAZ_INTEGRATION replaces FLEX_AUTH_RUN_TOPAZ_INTEGRATION
- README title and identity paragraph reflect the landed renames
- docs/runtime-rename-inventory.md: per-consumer references by kind and order
- chart name, image package and /opt paths deliberately left for T05

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 735967@bnt-lap001
Assistant-Session: 5971967f-77f8-4ced-9e02-c6ef67040ffc
2026-10-10 15:29:00 +02:00

31 lines
1.5 KiB
Markdown

# access-engine
Policy-as-code authorization registry and control plane for NetKingdom-aligned
systems.
The Forge and State Hub coordinate is `access-engine` (`FLEX-WP-0020`;
repository UUID `fda8ad85-a7d7-4055-8f21-902a533e59df`, Forge ID `42`; hub alias
`flex-auth`). The binary is `access-engine` (`FLEX-DEC-2026-020`; `flex-auth`
is now only a stub that prints the rename), and the Go module is
`github.com/netkingdom/access-engine`. The runtime still uses `flex-auth`: the
namespace, Helm releases, Services, caller audience and container package
`coulomb/flex-auth`. `FLEX-WP-0036` moves those to new pins that run alongside
the old ones while consumers switch. 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).