AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
architecture K.PUBLIC.ARCHITECTURE

AENET ARCHITECTURE

AENET Architecture

How the AENET public gateway is composed: layers, data flow, API flow and the public/private boundary.

SYSTEM STRUCTURE VISUAL

Public traffic, static web, public API, sanitized snapshots, and private boundary are shown as a one-way display path.

7flows 5layers 17systems

API Flow

The Public API is a bounded read-only surface. It reads public snapshots and services, returns a consistent envelope, rejects preview/private routes with 403, and routes the single write path (early access registration) to D1 — never to the core.

  • Client→GET /api/v1/*read-only public endpoints
  • GET /api/v1/*→Public snapshots + servicesstatus, time, architecture, queue, roadmap
  • Public snapshots + services→Clientconsistent JSON envelope
  • POST /api/v1/early-access/register→Validation + D1the only write path, never to the core
  • Client→/preview/* and private routes403 — intentionally unavailable

Data direction Snapshots → API (read). Early access → D1 (write, only sanctioned path).

Security boundary Read-only, bounded, no authentication, no API keys issued, no core access.

Data Flow

Sanitized snapshots are exported one-way from the core, validated, versioned with a content hash and copied into web/public-data/. The UI and Public API read those snapshots. Anonymous traffic flows in the opposite direction as an observation signal and is reduced to aggregates.

  • AENET Core→Sanitized snapshotexport, one-way, contract-gated
  • Sanitized snapshot→public-data/*.jsonvalidation + version + contentHash
  • public-data/*.json→web/public-data/static host
  • web/public-data/→Public pages / APIrendered read-only
  • Visitor→Traffic channelanonymous observation events
  • Traffic channel→Public traffic summaryaggregates only, no raw publish

Data direction Core → public for content; visitor → aggregates for observation.

Security boundary Snapshots are sanitized before publish; raw traffic events are never published.

Development Flow

Curated content (articles, research, development log, roadmap) and curated snapshots are validated by the content index builder, enveloped with version/generatedAt/contentHash, and copied into web/public-data/. Everything is then deployable as static assets. The verification suite gates every change.

  • content/ + public-data/→build-public-indexparse front matter, generate snapshots
  • build-public-index→public-data/*.jsonvalidate + envelope + hash
  • public-data/*.json→web/public-data/static copy
  • web/→Wrangler deploystatic assets to Cloudflare edge
  • Any change→npm run checkverification gates: boundary, routes, contracts

Data direction Content → build → public-data → web → edge. One-way.

Security boundary Content is public-safe by construction; verification fails the build on boundary violations.

Public Gateway Architecture

The public gateway is a static-first, read-only observation surface. It layers a Cloudflare edge, a static front end, a bounded public API, sanitized snapshots and public services in front of an unreachable private boundary.

  • Internet→aenet.cloudTLS + edge routing
  • aenet.cloud→Static Web / Public APIHTML, assets, read-only JSON API
  • Static Web / Public API→public-data/*.jsonsanitized pre-generated snapshots
  • public-data/*.json→AENET Corenever — reverse path is forbidden

Data direction Core → sanitized snapshot → public. Public → core: never.

Security boundary One-way and read-only. The gateway can never query, proxy or control the core.

Public / Private Boundary

Everything public sits on one side; the AENET Core sits on the other. The only sanctioned crossing is the export of sanitized snapshots through the snapshot contract. Early Access is the only public write path, and it writes only to D1 — never through the core.

  • Public gateway→Sanitized snapshotcore exports only sanitized data
  • Sanitized snapshot→Public pages / APIstatic + read-only
  • Public write path→D1early access registration only
  • Public side→AENET Coreforbidden: no proxy, no live query, no control

Data direction Core-to-public only. Early access → D1 only.

Security boundary forbiddenReverse: true. The core is labeled PRIVATE SYSTEM — NOT PUBLICLY ROUTABLE.

Search Flow

Public knowledge (knowledge blocks, content, public-data, locales, templates) is compiled at build time by the Go Search Compiler into static HTML with metadata, JSON-LD, sitemaps, hreflang sets and canonical URLs. The static output lands in web/, and Cloudflare serves it at the edge. The worker still owns routing, API and security.

  • Knowledge + content + public-data→Go Search Compilerbuild-time compilation, deterministic
  • Go Search Compiler→web/en|th|zh-cnfull static HTML pages
  • Go Search Compiler→sitemap + robots + search-graphcrawl surface
  • web/→Wrangler deploystatic assets to Cloudflare edge
  • Crawlers→Cloudflare edgecrawlable, fast, static-first

Data direction Knowledge → compiler → static web → edge → crawlers/people. One-way, build-time.

Security boundary The compiler reads only allow-listed public sources and never touches the core, private memory or raw analytics.

Time Flow

The server clock feeds the public time service, which returns canonical UTC timestamps with an explicit quality (SERVER_UTC today). The UI shows a live time rail using one baseline fetch plus a monotonic client clock. Atomic verification is never claimed without a verified source.

  • Server clock (UTC)→Time servicecanonical source, SERVER_UTC quality
  • Time service→GET /api/v1/timetimestamp + quality, never fake precision
  • GET /api/v1/time→UI time railone baseline fetch + monotonic client clock
  • Atomic source→ATOMIC_VERIFIEDfuture — only when verified, atomicVerified=false today

Data direction Server clock → time service → API/UI. Read-only.

Security boundary Read-only time; exposes no internal clocks and no identity.

Related 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-agent-runtime

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-cloud-public

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.

aenet-core

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-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-model-router

AENET Spine

A private AENET Core system (spine). Public evidence is limited to its presence as a private, unreachable topology node (core-spine).

aenet-spine

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.

development-queue

Early Access

The public waitlist for testing the AENET public gateway. Applicant records live only in D1, are never indexed, exported or published, and registration is fail-closed without Turnstile verification.

early-access

K Language

The language family that KAP declarative contracts are associated with. This repository contains limited public evidence about K Language internals.

k-language

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).

kap-language

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-api

Public Snapshot Layer

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

public-snapshot-layer

Public Time

The public time service of AENET Cloud Public. It serves canonical UTC with an explicit quality, and never claims atomic verification without a verified atomic source.

public-time

RGBM

The semantic color role system of the AENET public UI. Components reference roles (navigation, action, insight, guard, system, warning) — never raw color names.

rgbm

UI Contract

The single source of truth for the public UI structure — pages, navigation, components, coordinates, states, motion, colors, typography and locales — consumed by both the web and Swift renderers.

ui-contract

Visit Memory

Device-local continuity for AENET visitors: preferred locale, last route, visit count and read progress — stored in the browser only and never identifying a person.

visit-memory

XGRID

The adaptive spatial grid system of the AENET public UI: desktop 12 / tablet 8 / mobile 1 columns, content-intrinsic sizing, with a 1920x1080 canvas used only as a design reference.

xgrid