PUBLIC OBSERVATION INTERFACE · AENET.CLOUD
AENET Cloud is the read-only public observation layer for the AENET ecosystem: sanitized snapshots, a bounded public API and a strict one-way boundary.
PUBLIC VISUAL SYSTEM
Read-only public display grid for sanitized snapshots, architecture maps, and public route contracts.
AENET is an ecosystem being built and observed through aenet.cloud. The public side is an observation layer: it can read sanitized snapshots, articles, research and public status, but it can never reach the private AENET Core. There are no accounts, no terminal, no file bridge and no agent surface on the public side.
Evidence-backed use cases for the AENET ecosystem: what each one solves, who it is for, how the workflow moves through the systems, and its current availability.
The development queue is an active, public system: a canonical state machine (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED) recorded in a public snapshot and mirrored by a development log with one entry per gateway version.
AENET documents two language threads in public: KAP, an active declarative contract style with machine-verified JSON companions in this repository, and K Language, whose internals are honestly marked insufficient-public-evidence because the public repository does not document them.
The AENET Model Router is the private system responsible for routing requests to the right model. It is documented in the public knowledge model as a private system — public evidence covers its role, inputs and outputs, not live behavior.
A guided tour with three depths: 30 seconds, 3 minutes and 15 minutes. Choose the layer that matches how much time you have.
Organized by architecture layer, from the public gateway to the private core.
A private AENET Core system for agents. In the public topology it appears only as a private, unreachable node; no public surface exists.
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.
The private AENET ecosystem. It is never publicly routable and may export only sanitized public snapshots to aenet-cloud-public through the snapshot contract.
A private AENET Core system for memory. Public evidence is limited to its presence as a private, unreachable topology node (core-memory).
A private AENET Core system for models. Public evidence is limited to its presence as a private, unreachable topology node (core-models).
A private AENET Core system (spine). Public evidence is limited to its presence as a private, unreachable topology node (core-spine).
The public view of what the AENET system is building — a state machine (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED) with no fake progress percentages.
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.
The language family that KAP declarative contracts are associated with. This repository contains limited public evidence about K Language internals.
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).
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.
The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.
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.
The semantic color role system of the AENET public UI. Components reference roles (navigation, action, insight, guard, system, warning) — never raw color names.
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.
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.
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.
Only verified repository and public states — no fake benchmarks, no invented usage numbers.
The public development history of the AENET gateway, version by version.
Read the Public API and integration surface.
Explore research, knowledge blocks and the observation model.
Understand the model router, agent runtime and K/KAP language research.
Read the architecture layers, data flow and the public/private boundary.
Request early access to the public gateway waitlist.
Start with the guided tour and the glossary.
Join the first public testing queue for AENET Cloud.