The AENET Public Entrance

This is the first article of the AENET Cloud public gateway. It explains what

this entrance is, what the public may observe, and where the boundary sits.

A window, not a door

aenet-cloud-public is a window into the AENET build. Visitors can read

articles, research, the development log, sanitized system status and the

public roadmap. There is no door: no accounts, no sessions, no terminal, no

file access and no agent surface from the public side.

One-way data flow

The AENET Core is a separate ecosystem. This repository only ever receives

sanitized snapshots that the core exports, and it publishes them as static

files. The flow never reverses.

AENET CORE --export sanitized snapshot--> aenet-cloud-public --> aenet.cloud

What the public can observe

  • Static articles and research notes
  • Public development log and changelog
  • Public-safe architecture snapshots
  • Sanitized system status
  • Anonymous analytics (aggregate, schema-only)

What the public can never observe

  • Secrets, tokens or configuration
  • Private memory or internal logs
  • User data of any kind
  • Live core state or internal service addresses

The boundary is enforced by tests/ and documented in PUBLIC_BOUNDARY.md

and SECURITY.md.