MX, SPF, DKIM and Autodiscover are already present for hsimc.tech. C0 keeps them unchanged.
ADDRESS CAPABILITY · COMPUTE IN PARALLEL · CONTINUE REALITY
One familiar address.
Many current capabilities behind it.
HSIMC uses email as an early universal bridge into Reality Compute. An address such as x@hsimc.tech is a stable route—not a permanent bot, permission or mailbox identity. At dispatch time HSIMC resolves the current Work, capabilities, Authority, Human Supervisor and local Reality.
邮件不是为了把 GenAI 再做成一个 Inbox 平台。它是现有互联网与 Reality Compute 之间的“过桥协议”：用户继续用自己的邮箱，只把需要的 Reality 送入 HSIMC；后面可以并行解析多个能力，而不是沿一条固定供应链串行执行。
CURRENT TRANSPORT REALITY
Keep the mail transport. Decouple the capability identity.
Exact-host HTTPS/TLS/Nginx is ready and host-override verified. Public DNS still needs an authorized DNS record. Until then use the public mirror at hsimc.tech/mail/.
Addresses below are defined now but are not claimed to receive mail until Microsoft 365 or another transport adapter verifies them.
PARALLEL COMPUTE
Email becomes a Mail Reality, then eligible Work branches fan out.
Mail transportEnvelope + source reference
Mail RealityPrivacy + idempotency + Work candidate
Parallel resolutionMCP capabilities · Authority · model · device · Human Supervisor
Branch EvidenceResult, blocker, refusal, device proof
Fan-inWork acceptance / reply / next Reality
No branch inherits Authority from another branch. Physical actions such as printing require their own current device/Authority evidence. A mail address alone never authorizes execution.
MAIL INFRASTRUCTURE PLANES
Six Shared Mailboxes already form the control plane.
Ingress
support@ · ops@ · security@
Historical Exchange Application RBAC allowed Graph Mail.Read only on this scope. Current Graph canary has not been rerun in this release.
Outbound / Lifecycle
invite@ · activation@ · notify@
Historical Graph Mail.Send scope and controlled internal delivery passed. These are infrastructure identities—not e-Persons.
CAPABILITY ADDRESS REGISTRY · C0
Stable address. Replaceable capability route.
reality@hsimc.tech
Reality Intake
Register, update or continue a Reality reference.
REALITY_REGISTRATION · REALITY_UPDATE · REALITY_CONTINUE
work@hsimc.tech
Work Continue
Continue a bounded Work / Task Role through mail transport.
WORK_CONTINUITY · TASK_ROLE_INTAKE
translate@hsimc.tech
Translation / Localization
Resolve language/localization capability for a Work.
TRANSLATE · LOCALIZE · LANGUAGE_CONTEXT
print@hsimc.tech
Print / Physical Output
Resolve a physical-print capability and local device path for a Work.
PRINT · PHYSICAL_OUTPUT · LOCAL_DEVICE
quote@hsimc.tech
Quotation / Cost Formation
Resolve quotation, cost formation and missing-input work.
QUOTE_FORMATION · COST_INPUT_RESOLUTION
compliance@hsimc.tech
Compliance Evidence
Resolve applicable-rule/evidence coordination work without turning model output into legal certification.
COMPLIANCE_COORDINATION · EVIDENCE_MAPPING
sourcing@hsimc.tech
Procurement / Sourcing
Resolve sourcing, supplier-evidence and procurement-formation work.
SOURCING · PROCUREMENT_FORMATION · SUPPLIER_EVIDENCE
supervisor@hsimc.tech
Human Supervisor Routing
Resolve a real Human Supervisor candidate/route for a Work.
HUMAN_SUPERVISION · EXCEPTION_HANDOFF
BRIDGE YOUR EXISTING MAILBOX
No mailbox migration is required to start.
Keep your current mailbox
Gmail, Outlook, company mail or another provider stays where it is. HSIMC does not need your mailbox password for the first bridge.
Forward only selected Reality
Use rules/forwarding in the existing mailbox to send selected messages to a provisioned HSIMC capability address. Mail content remains private Work input unless explicitly authorized otherwise.
Resolve current capability
The receiving address maps into current Reality / MCP / Work, not a permanently hard-coded bot.
Return evidence, not just text
Parallel branches return evidence or blockers. Work-level policy decides what becomes a reply, accepted output or new Work.
MACHINE / MCP ENTRY
The same address registry can be read without scraping this page.
Capability Address RegistryBridge PolicyMail Reality schemaParallel Dispatch schemaDiscovery JSONBridge State
MCP read resources: hsimc://mail/capability-addresses and hsimc://mail/bridge-policy. C0 exposes no mail-sending MCP Tool.
C0 does not change hsimc.tech MX, does not create a catch-all, does not provision the listed recipients, does not read mailbox history, does not collect passwords, and does not automatically execute or send email. Capability addresses become real transport endpoints only after separate provisioning and canary evidence.