generated from coulomb/repo-seed
tegwick
8354485632
Remove external reference points so the intent stands on its own at the abstract, stable level: drop named identity/SSO systems, named PDP/policy products, named directory/enterprise systems, the named first-consumer project, and the external IAM-profile path. Keep all of flex-auth's own substance — purpose, responsibility boundary (stated as abstract roles: identity layer / authorization / enforcement points), design principles, concepts, API shape, standalone vs delegated mode, non-goals, early work. Relationships to other systems belong in interface contracts and the orchestration responsibility map, not in intent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.