Human actor
Owner
Only non-API user; human administrator with account and tenant/system authority.
This entry is recorded as Human actor in the Items section.
The source states this firmly, rather than as a suggestion.
Source-qualified discovery inventory
Human actors, tenancy, provisioning, authentication, oversight, and administration.
Document context
Every value below mirrors the JSON document. Friendly labels and explanations add context without replacing the exact field name or recorded value. Follow any “raw record” link to inspect or edit the same data.
schema_versionVersion of the discovery-inventory document shape.
0.1.0catalogue_statusMaturity of this catalogue data, not implementation status.
discovery_inventoryauthorityHow this document may be used and what it must not be mistaken for.
Evidence-derived inventory; not a final implementation-governing SSOT. Preserve source modality and consult conflicts.json.categoryStable subject area used to organize the inventory.
identities_tenancy_ownersdescriptionHuman-language explanation preserved by the inventory.
Human actors, tenancy, provisioning, authentication, oversight, and administration.Structured collection
9 top-level entries. Nested values are expanded inside each entry.
Human actor
Only non-API user; human administrator with account and tenant/system authority.
This entry is recorded as Human actor in the Items section.
The source states this firmly, rather than as a suggestion.
Human actor
First Owner with owner_scope=system; creates/suspends Owners, enters oversight, and reviews system information without Author impersonation ability.
This entry is recorded as Human actor in the Items section.
This records how the historical source describes the system.
Human actor
Subsequent Owner, normally owner_scope=tenant, with total human administrative authority over the tenant subject to system safety controls.
This entry is recorded as Human actor in the Items section.
This records how the historical source describes the system.
Administrative boundary
Boundary separating Owner and Key data and authority.
This entry is recorded as Administrative boundary in the Items section.
The source places this concern inside the first functional MVP.
Classification
Internal classification: system_gift, commercial, migration, development; must not affect API output, authorization, limits, security, features, or authority.
This entry is recorded as Classification in the Items section.
The source states this firmly, rather than as a suggestion.
Administrative flow
System Owner entry into another tenant requires step-up, reason, distinct UI, event, and short expiry.
This entry is recorded as Administrative flow in the Items section.
The source states this firmly, rather than as a suggestion.
Authentication component
Opaque random token stored hashed in PostgreSQL; stateless JWT dashboard sessions are rejected by one source.
This entry is recorded as Authentication component in the Items section.
The source states this firmly, rather than as a suggestion.
Security control
Required at minimum for high-risk Owner actions.
This entry is recorded as Security control in the Items section.
The source states this firmly, rather than as a suggestion.
Owner flow
Username/email/password signup, verification, login, secure sessions; SMTP is considered for verification, recovery, and alerts.
This entry is recorded as Owner flow in the Items section.
The source places this concern inside the first functional MVP.