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

public-snapshot-layer

Public Snapshot Layer

The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.

Status: active Last updated: 2026-08-16

System ID

public-snapshot-layer

Status

active

Architecture layers

  • L3 Public Data

Inputs

  • Curated public-data JSON
  • content/ markdown (articles, research, development log, roadmap)
  • Anonymous traffic summary

Outputs

  • Versioned, hashed public snapshots in public-data/ and web/public-data/

Public interfaces

  • public-data/*.json (served statically)

Connected systems

Security boundary

Snapshots are sanitized before publishing. Forbidden data (secrets, private memory, internal logs, user data) is excluded by contract and boundary tests. The layer is read-only for the public.

Data direction

Core → sanitized snapshot → public. Never reverse.

What

Give the public a read-only, deterministic view of the AENET build through sanitized snapshots — never live queries.

Why

The public side must never run live queries into the core. The snapshot layer pre-generates sanitized JSON so the public can read facts without any live connection.

How

Core → sanitized snapshot → public. Never reverse.

  • Publish site, status, architecture, changelog snapshots
  • Generate articles, development-log, roadmap and traffic-summary snapshots from content/
  • Envelope every snapshot with version, generatedAt and contentHash
  • Copy snapshots into web/public-data/ for the static host
  • Enforce schema contracts

Example

The build pipeline validates and copies sanitized snapshots into public-data/ and web/public-data/, versioned and hashed, so pages and the API read from the same source.

Inputs

  • Curated public-data JSON
  • content/ markdown (articles, research, development log, roadmap)
  • Anonymous traffic summary

Outputs

  • Versioned, hashed public snapshots in public-data/ and web/public-data/

Dependencies

aenet-cloud-public

Lifecycle

  • content curation
  • build-public-index generation
  • envelope + hash
  • static publish

Use cases

  • The UI renders pages from snapshot JSON
  • The Public API serves snapshot-backed data
  • Crawlers and developers read public-data directly

Limitations

  • No live data — snapshots are pre-generated
  • Only sanitized, contract-allowed datasets
  • Traffic summary is aggregate-only

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.
  • 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.
  • KAP Language — A declarative contract style used across this repository to describe the public site, navigation, content, layout, motion, time, traffic and early access in machine-readable files (.kap).
  • 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.

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 Public Snapshot Layer?
  • What snapshots does AENET publish?
  • How are public snapshots generated and hashed?
  • Can the public query live core data?

Evidence

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

  • scripts/build-public-index.js
  • public-data/*.json
  • contracts/aenet-public-snapshot.contract.json
  • docs/PUBLIC_DATA_BOUNDARY.md

Next step