6 Microsoft 365 Shared Mailboxes
support / ops / security for ingress; invite / activation / notify for outbound and lifecycle. Current Microsoft 365 admin screenshot shows all six; historical Graph RBAC and mail canaries passed.
REGISTER ADDRESS · PROVISION TRANSPORT · RESOLVE AUTHORITY AT USE TIME
Every activated e-Person gets
one stable X@hsimc.tech address.
The address is durable infrastructure. Microsoft 365 is the first transport adapter—not the e-Person identity, not its permanent role, and not execution Authority.
注册的是一个长期可达的工作地址；当前 Role、Authority、Model、Supervisor、Work 资格仍然在每次使用时重新计算。
TWO PLANES
System mailboxes already exist. e-Person addresses come next.
One address per activated e-Person
Unique and stable X@hsimc.tech. Shared Mailbox is the preferred first canary transport, but the transport may later change without changing the e-Person identity/address contract.
REGISTRATION LIFECYCLE
Registration is durable. Authority is not inherited.
REQUESTEDAddress requested
RESERVEDCollision/no-reuse check
AUTHORIZEDHuman/holder provisioning gate
PROVISIONEDM365 or other adapter
CANARY + BOUNDAddress becomes active route
Only AUTHORIZED_TO_PROVISION may mutate the mail provider. AI cannot grant this state. A transport object never becomes the canonical e-Person identity.
LOCAL REQUEST DRAFT · NO SERVER WRITE
Prepare a registration request without creating a mailbox.
No request created.
MACHINE CONTRACTS
It creates only a local registration draft. No mailbox, alias, Graph permission, password, Authority or e-Person activation is created. Actual transport provisioning requires an explicitly authorized adapter/operator step and a separate send/receive canary.