Security Service Module
What This Service Is For
Security owns memberships and authentication identities, access definitions, assignments, staff grants, machine principals and their security history. It provides evaluated context to the console and protected human API requests, while machine calls use their separate cloud-role/principal path.
Boundary
Eligibility owns rule definitions and evaluation; Security stores the resulting assignments. Committees owns appointments and supplies their source-managed derived assignments. CRM owns contacts and candidate matching data; Security owns member linking and possession challenges. Licensing owns license state read by permission and application evaluation. Console Shell owns navigation and boot gating from evaluated security context. Websites and Sites determine when their workspace needs portal onboarding.
Operations in Words
The operations group personal context and access explanation; member invitation and lifecycle; role, policy and assignment administration; staff entry and principals; and portal registration, recovery and contact linking. Their operation rows identify exact access and planning capability references.
Operation rows preserve route-declared access, permission and planning capability references. None declares a Submissions binding. The module makes no model inference call; its inference list is empty.
Events and Jobs
The declared job inventory covers durable execution and queued background work. Event declarations distinguish actual provisioning notifications from the absence of domain-change events.
Consistency Guarantees
The consistency rows distinguish database authority, external provider effects, queued work, gateway caching and registry publication. Suspension and reinstatement have no durable provider retry; revocation and deletion do. Acceptance is the explicit provider-before-database exception, with its credential race recorded as a finding.
Catalog and route-registry activation cross separate stores. CRM contact creation and membership linking also cross transaction boundaries. These gaps and missing failure-recovery proofs remain open rather than being described as atomic guarantees.