tegwick
a835c11ae7
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a101af-e240-7882-a1e3-e37720cbdbea
23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
# Tenants and bounded governance
|
|
|
|
tenant-engine supplies tenant entity/lifecycle, role, plan, and guardrail facts;
|
|
user-engine supplies users and memberships. access-engine renders authorization.
|
|
Platform tenant envelopes bound a tenant; tenant governance only narrows them.
|
|
An out-of-envelope request routes to the platform, never to a tenant admin for
|
|
an override. A human-reserved tenant decision routes to that tenant's human
|
|
authority; timeout means escalation, not approval.
|
|
|
|
The generic platform/governance YAML examples are fixtures, not deployed tenant
|
|
configuration. Confirm the actual owner representation before mapping fields.
|
|
Keep tenant and resource claims consistent and authoritative. Missing or
|
|
contradictory tenancy prevents choosing a live route. An allowed operation in
|
|
one tenant does not authorize another. This package carries only estate-general
|
|
knowledge: it neither retrieves tenant documents nor returns tenant data.
|
|
|
|
Tenant-engine's scope contains old conformance gaps alongside newer shipped
|
|
entries. Use its implementation and evidence with source revisions to resolve
|
|
the discrepancy; neither blanket production readiness nor blanket absence
|
|
follows from those paragraphs. TEN-WP-0012 already tracks external conformance
|
|
dependencies; do not duplicate or declare them completed here.
|
|
|
|
Source owner IDs (cite the relevant owner, not an invented umbrella): `tenant-engine`, `user-engine`, `net-kingdom`, `emergent-security`.
|