A policy-as-code capable authorization registry/control-plane service.
Find a file
tegwick ae295824bd
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Register qonto-assistant as a protected system (finance.qonto.read)
QONTO-WP-0004-T04. Modeled directly on examples/tenant-engine/: one
resource type (finance-snapshot), one action (finance.qonto.read),
two registered subjects (an agent-harness session identity and the
founder's human identity), and a Rego policy gating on
resource.system + action + subject.type + tenant match. Tenant
capability-role/plan liveness (VEN/CUS) is deliberately NOT encoded
here -- that's qonto-assistant's separate tenant-engine live-lookup
check, per this package's own scope note.

Verified: flex-auth test-policy (6 rego tests + 6 fixtures, all pass),
load-registry, and CLI check for both an allow and a deny case. Also
verified end-to-end over real HTTP: a live flex-auth serve loaded with
this exact registry+policy, hit by qonto-assistant's actual
FlexAuthCheckClient (not a mock) -- allow for tenant:friendly:binky,
deny (wrong_tenant) for a mismatched tenant.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-24 00:19:26 +02:00
.claude/rules docs: workplan-first agent guidance prose (CUST-WP-0055 T04 batch 2) 2026-07-08 16:41:17 +02:00
.forgejo/workflows Add Forgejo CI smoke workflow (enablement template) 2026-07-08 12:32:37 +02:00
.github/workflows Land foundations: assessment, ADR-001/002/003, FLEX-WP-0005, Go skeleton 2026-05-16 01:54:44 +02:00
cmd/flex-auth FLEX-WP-0007: production registry fixture, tests, and sync runbook 2026-06-24 14:52:35 +02:00
docs FLEX-WP-0008 T01-T02: tenant-engine resource/action vocabulary + policy package 2026-07-23 23:05:57 +02:00
examples Register qonto-assistant as a protected system (finance.qonto.read) 2026-07-24 00:19:26 +02:00
internal FLEX-WP-0008 T03-T04: tenant-engine live-lookup context adapter, close 2026-07-23 23:33:34 +02:00
pkg/api FLEX-WP-0006: implement ops-warden signing gate policy 2026-06-23 21:17:42 +02:00
registry Add capability registry with seed entry from reuse-surface 2026-06-16 01:46:54 +02:00
schemas FLEX-WP-0006: implement ops-warden signing gate policy 2026-06-23 21:17:42 +02:00
workplans FLEX-WP-0008 T03-T04: tenant-engine live-lookup context adapter, close 2026-07-23 23:33:34 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-07-23 23:33:56 +02:00
.gitignore Land foundations: assessment, ADR-001/002/003, FLEX-WP-0005, Go skeleton 2026-05-16 01:54:44 +02:00
.golangci.yml Land foundations: assessment, ADR-001/002/003, FLEX-WP-0005, Go skeleton 2026-05-16 01:54:44 +02:00
.repo-classification.yaml Human-review .repo-classification.yaml (CUST-WP-0050 follow-up) 2026-06-22 17:56:17 +02:00
AGENTS.md Regenerate agent instructions from state-hub templates (CUST-WP-0055 T01) 2026-07-08 14:50:24 +02:00
CLAUDE.md Add credential routing instructions for all agent runtimes 2026-06-18 22:48:37 +02:00
go.mod Implement policy package loader 2026-05-17 05:30:40 +02:00
go.sum Implement policy package loader 2026-05-17 05:30:40 +02:00
INTENT.md docs(intent/scope): align with ops-warden as first shipped consumer 2026-06-27 20:37:07 +02:00
LICENSE Initial commit 2026-05-04 14:21:47 +00:00
Makefile Pin FlexAuthResourceManifest schema (resource-registration-v0) 2026-05-16 02:04:00 +02:00
README.md Refine workplans for CARING profile 2026-05-17 04:15:38 +02:00
SCOPE.md docs(scope): reflect baseline complete — all FLEX-WP-0001..0007 done 2026-06-30 01:40:19 +02:00
WORK-RECORDS.md chore(consistency): sync WORK-RECORDS.md for FLEX-WP-0008 closure [auto] 2026-07-23 23:34:04 +02:00

flex-auth

Policy-as-code authorization registry and control plane for NetKingdom-aligned systems.

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.