AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
systems K.PUBLIC.SYSTEMS

SYSTEMS

AENET Systems

The public systems of the AENET ecosystem, organized by architecture layer from the gateway to the private core.

L0

Public visitors

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.

Role
Core-to-public one-way (export sanitized snapshot); public-to-core never. Early Access writes only to D1, never to the core.
Status
● preview
Input
Sanitized snapshots exported by the AENET Core (site, status, architecture, articles, roadmap)
→
Output
Crawlable static HTML and JSON public-data
Connected systems
9 systems

Explore system →

aenet-cloud-public

L2

Public application + UI

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.

Role
Visitor → registration form → validation → D1. One-way; never to the core.
Status
● preview
Input
Visitor email, optional locale/interests, explicit consent
→
Output
Registration tickets (D1 only)
Connected systems
3 systems

Explore system →

early-access

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.

Role
Public snapshots → API responses (read). Early-access registration → D1 (the only write path, never to the core).
Status
● active
Input
Public-data snapshots and services (status, time, architecture, queue, roadmap, early access)
→
Output
JSON responses with a consistent envelope; registration tickets for early access (D1)
Connected systems
5 systems

Explore system →

public-api

RGBM

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

Role
Roles → tokens → CSS/components. Client-only.
Status
● active
Input
Semantic role definitions (design/rgbm.json)
→
Output
Role tokens consumed by CSS and components
Connected systems
3 systems

Explore system →

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.

Role
Design/release sources → UI contract → renderers (web, Swift). One-way, public.
Status
● active
Input
Design tokens (design/), release manifest (release/), locale files
→
Output
UI contract JSON consumed by web and Swift renderers
Connected systems
5 systems

Explore system →

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.

Role
Device → localStorage → UI offers. Never to the server, never to the core.
Status
● active
Input
Visitor device state (localStorage)
→
Output
Welcome-back / continue offers in the UI
Connected systems
3 systems

Explore system →

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.

Role
Tokens + layout maps → coordinate engine → DOM. Client-only.
Status
● active
Input
Per-page layout maps
→
Output
Adaptive grid coordinates applied by the coordinate engine
Connected systems
3 systems

Explore system →

xgrid

L3

Sanitized public data

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.

Role
Curated queue data → public-data → UI/API. Read-only.
Status
● active
Input
Curated public queue items (public-data/development-queue.public.json)
→
Output
Queue board UI + API (GET /api/v1/development-queue)
Connected systems
4 systems

Explore system →

development-queue

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

Role
Public facts → declarative contracts → validated JSON companions. No executable path in any direction.
Status
● active
Input
Public-safe facts about the site, navigation, content and traffic channel
→
Output
Declarative contract files (kap/*.kap) and their machine-verified JSON companions (contracts/*.json)
Connected systems
8 systems

Explore system →

kap-language

Public Snapshot Layer

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

Role
Core → sanitized snapshot → public. Never reverse.
Status
● active
Input
Curated public-data JSON
→
Output
Versioned, hashed public snapshots in public-data/ and web/public-data/
Connected systems
4 systems

Explore system →

public-snapshot-layer

L4

Public services

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.

Role
Server clock → time service → API/UI. Read-only.
Status
● active
Input
Server clock (UTC)
→
Output
Time API responses with quality
Connected systems
3 systems

Explore system →

public-time

L6

Private AENET Core — never publicly routable

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.

Role
insufficient-public-evidence (internal); publicly it is inbound-inaccessible.
Status
● private
Input
insufficient-public-evidence
→
Output
insufficient-public-evidence
Connected systems
4 systems

Explore system →

aenet-agent-runtime

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.

Role
Core-to-public only (export sanitized snapshot). Public-to-core is forbidden.
Status
● private
Input
insufficient-public-evidence
→
Output
Sanitized public snapshots (site, status, architecture, articles, roadmap)
Connected systems
6 systems

Explore system →

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

Role
insufficient-public-evidence (internal); publicly it is inbound-inaccessible.
Status
● private
Input
insufficient-public-evidence
→
Output
insufficient-public-evidence
Connected systems
4 systems

Explore system →

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

Role
insufficient-public-evidence (internal); publicly it is inbound-inaccessible.
Status
● private
Input
insufficient-public-evidence
→
Output
insufficient-public-evidence
Connected systems
4 systems

Explore system →

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

Role
insufficient-public-evidence (internal); publicly it is inbound-inaccessible.
Status
● private
Input
insufficient-public-evidence
→
Output
insufficient-public-evidence
Connected systems
4 systems

Explore system →

aenet-spine

UNCLASSIFIED

Evidence pending — public layer not classified

K Language

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

Role
insufficient-public-evidence
Status
● insufficient-public-evidence
Input
insufficient-public-evidence
→
Output
insufficient-public-evidence
Connected systems
2 systems

Explore system →

k-language
━━━━━━━━ BOUNDARY ━━━━━━━━

Private AENET Core is never publicly routable. One-way rail only.