Name what CheckRequest.tenant denotes; record the access-engine rename intake
TEN-DEC-2026-002 answers flex-auth's FLEX-WP-0022-T01, open since 2026-09-15: `tenant` denotes the target tenant record, equals `resource.id` by intent, and the write API is cross-tenant by design — no action is refused on the subject/tenant relationship, and tenant.guardrail.read must not differ because flex-auth itself calls it across tenants. docs/flex-auth-integration.md states the relation in this repo's voice. TEN-IN-0004 is the live record flex-auth asked for on FLEX-WP-0020. Runtime names stay flex-auth (FLEX-DEC-2026-013) and all deploy, cluster and settings coordinates verify as retained; only five documentation repository paths change when the rename lands. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 63291@bnt-lap001 Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
parent
6e59840379
commit
d132db064f
4 changed files with 221 additions and 0 deletions
|
|
@ -79,4 +79,6 @@
|
|||
| intake | TEN-IN-0001 | closed | yellow | docs/intakes/residuals.md |
|
||||
| intake | TEN-IN-0002 | closed | red | docs/intakes/residuals.md |
|
||||
| intake | TEN-IN-0003 | closed | — | intakes/intakes.md |
|
||||
| intake | TEN-IN-0004 | open | — | intakes/intakes.md |
|
||||
| decision | TEN-DEC-2026-001 | resolved | — | decisions/decisions.md |
|
||||
| decision | TEN-DEC-2026-002 | resolved | — | decisions/decisions.md |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue