AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
system-detail K.PUBLIC.SYSTEM

SYS.COM.01 D03 mail

AENET Mail

AENET Mail is the encrypted workspace mail system of AENET. It provides a private mailbox workspace (inbox, compose, reader, contacts, account) with end-to-end encryption primitives, a mail gateway, and an email archive pipeline. This public snapshot is a sanitized, read-only description of the system. It exposes NO live mailbox, NO account access, NO message content, and NO control surface.

Domain: Communication STATUS: development Public boundary: OBSERVATION ONLY Last updated: 2026-08-18

System ID

mail

Status

development

Architecture layers

  • L2 Public Application (static overview)
  • L4 Public Service (snapshot contract)

Inputs

  • Private user actions in the workspace mail runtime

Outputs

  • Sanitized public snapshot (aenet.email.public.v1)
  • Public overview page at /system/mail

Public interfaces

  • versioned public snapshot contract
  • /system/mail

Connected systems

Security boundary

AENET Email is a private system. The public cloud observes a sanitized snapshot only; it never controls, writes, or reaches the email runtime, database, mailbox, secrets, or localhost surface. The connection is an artifact contract (EXPORTS_SANITIZED_SNAPSHOT), never a network control channel.

Data direction

Private runtime → sanitizer → public snapshot → public registry → static site. One-way only; the flow never reverses.

Security

AENET Email is a private system. The public cloud observes a sanitized snapshot only; it never controls, writes, or reaches the email runtime, database, mailbox, secrets, or localhost surface. The connection is an artifact contract (EXPORTS_SANITIZED_SNAPSHOT), never a network control channel.

What

Give AENET users a private, encrypted workspace mail system while keeping the public web surface strictly read-only and snapshot-based.

Why

AENET needs private mail with strong encryption and archive pipelines. The public cloud must be able to describe Mail without ever controlling, writing to, or reaching the private mail runtime.

How

Private runtime → sanitizer → public snapshot → public registry → static site. One-way only; the flow never reverses.

  • Provide a private mailbox workspace (inbox, compose, reader)
  • Manage contacts and account settings privately
  • Apply end-to-end encryption primitives to message payloads
  • Run a mail gateway and an email archive pipeline
  • Publish only a sanitized public snapshot — never live data

Example

A user opens the private Mail workspace, reads and composes encrypted messages in inbox/compose/reader. Separately, the public site renders a sanitized snapshot of Mail's architecture and capabilities — never a live mailbox.

Inputs

  • Private user actions in the workspace mail runtime

Outputs

  • Sanitized public snapshot (aenet.email.public.v1)
  • Public overview page at /system/mail

Dependencies

aenet-cloud-publicpublic-snapshot-layerdevelopment-queue

Lifecycle

  • Planned
  • Development
  • Verifying
  • Preview
  • Active

Use cases

  • A visitor reads the public Mail overview page
  • The public registry reflects Mail's status and capabilities
  • The public importer validates and imports the sanitized snapshot

Limitations

  • No live mailbox, no webmail access, no send/receive on the public site
  • No account or identity data is ever published
  • Public status transitions only with verified evidence

Connected systems

  • AENET Cloud Public — The public-facing entrance and observation layer for the AENET ecosystem. It publishes sanitized snapshots, static pages, a public API and an anonymous traffic channel — nothing more.
  • Development Queue — The public view of what the AENET system is building — a state machine (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED) with no fake progress percentages.
  • Public Snapshot Layer — The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.

Questions people ask

These questions are answered by the content on this page.

  • What is AENET Mail?
  • Is AENET Mail available publicly?
  • Can the public site open a mailbox?
  • How does AENET Mail keep the public/private boundary?

Evidence

Verified states only — nothing on this page is a prediction.

  • contracts/aenet-email-public-v1.contract.json
  • public-data/mail-public-snapshot.json

Next step