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

22 lines
880 B
Markdown
Raw Permalink Normal View History

Established INTENT.md
2026-05-04 17:52:29 +02:00
# flex-auth
Initial commit
2026-05-04 14:21:47 +00:00
Established INTENT.md
2026-05-04 17:52:29 +02:00
Policy-as-code authorization registry and control plane for NetKingdom-aligned
systems.
Start with [INTENT.md](INTENT.md) for the project boundary and direction.
Land foundations: assessment, ADR-001/002/003, FLEX-WP-0005, Go skeleton Pre-implementation assessment and boundary review (docs/pre-implementation-assessment.md) lead to three ADRs: - ADR-001 Go + repo skeleton - ADR-002 Rego-in-Markdown policy package format - ADR-003 Topaz-aligned MVP (Topaz spike moves into foundations) New workplan FLEX-WP-0005 (Foundations and Topaz Alignment) is inserted between WP-0001 (done) and WP-0002 (core). WP-0002 pins Rego-in-Markdown for P2.3; WP-0004 P4.1 refocused from Topaz evaluation to Topaz adapter. Go skeleton at repo root: cmd/flex-auth + internal/{registry,policy, decision,audit,adapters} + pkg/api + Makefile + .golangci.yml + GitHub Actions CI. make ci green locally; bin/flex-auth --version works. INTENT/SCOPE cite the NetKingdom IAM Profile and add the ops-warden / ops-bridge disjoint-surface clarifications. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-16 01:54:44 +02:00
Research notes and ADRs live in [docs/](docs/) and [docs/adr/](docs/adr/).
Workplan sketch out and statehub registration
2026-05-04 18:15:59 +02:00
Initiated flex-auth with Scope and PRD
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).
Land foundations: assessment, ADR-001/002/003, FLEX-WP-0005, Go skeleton Pre-implementation assessment and boundary review (docs/pre-implementation-assessment.md) lead to three ADRs: - ADR-001 Go + repo skeleton - ADR-002 Rego-in-Markdown policy package format - ADR-003 Topaz-aligned MVP (Topaz spike moves into foundations) New workplan FLEX-WP-0005 (Foundations and Topaz Alignment) is inserted between WP-0001 (done) and WP-0002 (core). WP-0002 pins Rego-in-Markdown for P2.3; WP-0004 P4.1 refocused from Topaz evaluation to Topaz adapter. Go skeleton at repo root: cmd/flex-auth + internal/{registry,policy, decision,audit,adapters} + pkg/api + Makefile + .golangci.yml + GitHub Actions CI. make ci green locally; bin/flex-auth --version works. INTENT/SCOPE cite the NetKingdom IAM Profile and add the ops-warden / ops-bridge disjoint-surface clarifications. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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).
Refine workplans for CARING profile
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).
Land foundations: assessment, ADR-001/002/003, FLEX-WP-0005, Go skeleton Pre-implementation assessment and boundary review (docs/pre-implementation-assessment.md) lead to three ADRs: - ADR-001 Go + repo skeleton - ADR-002 Rego-in-Markdown policy package format - ADR-003 Topaz-aligned MVP (Topaz spike moves into foundations) New workplan FLEX-WP-0005 (Foundations and Topaz Alignment) is inserted between WP-0001 (done) and WP-0002 (core). WP-0002 pins Rego-in-Markdown for P2.3; WP-0004 P4.1 refocused from Topaz evaluation to Topaz adapter. Go skeleton at repo root: cmd/flex-auth + internal/{registry,policy, decision,audit,adapters} + pkg/api + Makefile + .golangci.yml + GitHub Actions CI. make ci green locally; bin/flex-auth --version works. INTENT/SCOPE cite the NetKingdom IAM Profile and add the ops-warden / ops-bridge disjoint-surface clarifications. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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).
Reference in a new issue Copy permalink