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

aenet-core

AENET Core

The private AENET ecosystem. It is never publicly routable and may export only sanitized public snapshots to aenet-cloud-public through the snapshot contract.

Status: private Last updated: 2026-08-16

System ID

aenet-core

Status

private

Architecture layers

  • L6 AENET Core (private, never publicly routable)

Inputs

  • insufficient-public-evidence

Outputs

  • Sanitized public snapshots (site, status, architecture, articles, roadmap)

Public interfaces

  • None — the core has no public interface

Connected systems

Security boundary

The core sits behind the private boundary (L6 in the public topology, reachable: false). The public side can never query, proxy or control it. Snapshot export is the only sanctioned crossing, one-way only.

Data direction

Core-to-public only (export sanitized snapshot). Public-to-core is forbidden.

What

Host the private AENET systems (agents, memory, spine, models and more) and expose only sanitized, pre-approved snapshots to the public side.

Why

The ecosystem needs a private side that can build and operate without ever becoming reachable from the public internet. The core exports only what the snapshot contract allows.

How

Core-to-public only (export sanitized snapshot). Public-to-core is forbidden.

  • Run the private AENET systems
  • Export sanitized public snapshots one-way through contracts/aenet-public-snapshot.contract.json
  • Never accept inbound connections from the public side

Example

The core exports a sanitized snapshot of site status and articles through contracts/aenet-public-snapshot.contract.json; the public gateway publishes it, while the core itself never accepts a public connection.

Inputs

  • insufficient-public-evidence

Outputs

  • Sanitized public snapshots (site, status, architecture, articles, roadmap)

Dependencies

insufficient-public-evidence

Lifecycle

  • insufficient-public-evidence

Use cases

  • Produce sanitized public snapshots consumed by aenet-cloud-public
  • Remain fully private during public observation

Limitations

  • Internal architecture details are not public evidence in this repository
  • Never reachable from the internet

Connected systems

  • AENET Agent Runtime — A private AENET Core system for agents. In the public topology it appears only as a private, unreachable node; no public surface exists.
  • 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.
  • AENET Memory — A private AENET Core system for memory. Public evidence is limited to its presence as a private, unreachable topology node (core-memory).
  • AENET Model Router — A private AENET Core system for models. Public evidence is limited to its presence as a private, unreachable topology node (core-models).
  • AENET Spine — A private AENET Core system (spine). Public evidence is limited to its presence as a private, unreachable topology node (core-spine).
  • Public API — The read-only public API v1 of AENET Cloud Public. It serves public status, time, architecture, development queue, roadmap and early access — with a strictly bounded surface.
  • Public Snapshot Layer — The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.

Related research

  • The AENET Public Entrance — What this public entrance is, what the public may observe, and where the one-way boundary sits.

Questions people ask

These questions are answered by the content on this page.

  • What is the AENET Core?
  • Is the AENET Core publicly reachable?
  • How does data leave the AENET Core?

Evidence

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

  • PUBLIC_BOUNDARY.md
  • ARCHITECTURE.md
  • public-data/system-topology.public.json
  • contracts/aenet-public-snapshot.contract.json

Next step