tegwick
47a58d5cc2
tenant-engine has made grouping mutable through its own reclassification route, so a tenant created as tenant:small:acme can report grouping "large". The identifier's grouping segment is now historical and must not be parsed. TenantRecord dropped the field entirely, so the portal read discarded the one safe source of a tenant's classification and left an operator with nothing but the identifier to infer from — exactly the mistake the change creates. The record and adapter now carry grouping, the operator screen shows it with a note that the identifier segment is not the grouping, and the OpenAPI schema documents where to read it. Also corrects the UpdateTenant description, which still claimed grouping was immutable. It is mutable, but never as metadata, because it resolves a tenant's spend ceiling. No reclassification control is offered here: that route is not deployed yet and, per tenant-engine, wants its own permission rather than riding on rename. Full suite: 149 tests, 3 provider-gated skips. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| docs | ||
| migrations/postgres | ||
| openapi | ||
| registry | ||
| src/user_engine | ||
| tests | ||
| wiki | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| Containerfile | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| pyproject.toml | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
Headless multi-application, multi-tenant user management engine.
Development
make test
See docs/development.md, docs/configuration.md, docs/contracts.md,
docs/canon-mapping.md, docs/canon-interface-card.yaml,
docs/evidence-gap-examples.md, docs/family-dataspace-onboarding.md,
docs/netkingdom-registration-onboarding-vision.md,
docs/postgres-durable-store-consumer-requirements.md, docs/examples.md,
docs/registration-identity-and-factor-model.md,
docs/prepared-accounts-and-entitlement-claims.md,
docs/hats-realms-services-assets-access-profiles.md,
docs/onboarding-journeys-and-welcome-protocols.md,
docs/registration-and-access-management-ui.md, docs/scenarios.md,
docs/registration-scenario-and-security-conformance.md,
docs/operability.md, docs/release.md, docs/ui-contracts.md,
docs/identity-domain-naming-decision.md, and docs/final-assessment.md
for implementation boundaries, contracts, canon mappings, examples, and release
readiness.