Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 605711@bnt-lap001 Assistant-Session: 1f5e2256-181f-49ed-b7b1-a1c34bf37a61 |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| .github/workflows | ||
| .repo-manager | ||
| adapters/go/decisionpep | ||
| charts | ||
| cmd | ||
| decisions | ||
| deploy | ||
| docs | ||
| examples | ||
| history | ||
| intakes | ||
| internal | ||
| pkg | ||
| railiance | ||
| registry | ||
| schemas | ||
| tests | ||
| testsupport/signfixture | ||
| third_party/approvalfact | ||
| tools | ||
| values | ||
| workplans | ||
| .generated-work-records.json | ||
| .generated-work-records.mk | ||
| .gitignore | ||
| .golangci.yml | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| cadence.yaml | ||
| CLAUDE.md | ||
| Containerfile | ||
| Containerfile.lifecycle | ||
| Containerfile.t03-review | ||
| go.mod | ||
| go.sum | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SCOPE.md | ||
| tenancy.yaml | ||
| WORK-RECORDS.md | ||
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 for the project boundary and direction. Research notes and ADRs live in docs/ and docs/adr/.
The product boundary is captured in SCOPE.md, and the current Product Requirements Document is docs/ProductRequirementsDocument.md.
The 2026-05-15 pre-implementation assessment that shapes the current sequencing is in docs/pre-implementation-assessment.md.
The CARING reference-implementation approach is captured in docs/caring-architecture-blueprint.md.
Workplans live in workplans/, with sequencing captured in docs/workplan-planning-map.md.