2026-10-10 15:29:00 +02:00
|
|
|
# access-engine
|
2026-05-04 14:21:47 +00:00
|
|
|
|
2026-05-04 17:52:29 +02:00
|
|
|
Policy-as-code authorization registry and control plane for NetKingdom-aligned
|
|
|
|
|
systems.
|
|
|
|
|
|
2026-10-10 15:29:00 +02:00
|
|
|
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:
|
2026-09-15 23:38:48 +02:00
|
|
|
`https://forgejo.coulomb.social/coulomb/access-engine.git`.
|
|
|
|
|
|
2026-05-04 17:52:29 +02:00
|
|
|
Start with [INTENT.md](INTENT.md) for the project boundary and direction.
|
2026-05-16 01:54:44 +02:00
|
|
|
Research notes and ADRs live in [docs/](docs/) and [docs/adr/](docs/adr/).
|
2026-05-04 18:15:59 +02:00
|
|
|
|
2026-05-04 19:16:26 +02:00
|
|
|
The product boundary is captured in [SCOPE.md](SCOPE.md), and the current
|
|
|
|
|
Product Requirements Document is
|
|
|
|
|
[docs/ProductRequirementsDocument.md](docs/ProductRequirementsDocument.md).
|
|
|
|
|
|
2026-05-16 01:54:44 +02:00
|
|
|
The 2026-05-15 pre-implementation assessment that shapes the current
|
|
|
|
|
sequencing is in
|
|
|
|
|
[docs/pre-implementation-assessment.md](docs/pre-implementation-assessment.md).
|
|
|
|
|
|
2026-05-17 04:15:38 +02:00
|
|
|
The CARING reference-implementation approach is captured in
|
|
|
|
|
[docs/caring-architecture-blueprint.md](docs/caring-architecture-blueprint.md).
|
|
|
|
|
|
2026-05-16 01:54:44 +02:00
|
|
|
Workplans live in [workplans/](workplans/), with sequencing captured in
|
|
|
|
|
[docs/workplan-planning-map.md](docs/workplan-planning-map.md).
|