AENET ecosystems PUBLIC GATEWAY
Request a Pilot
GATEWAY READY
tour K.PUBLIC.TOUR
KAP-GRID / Y C01

GUIDED TOUR · T05 · D.LAYOUT.GUIDE

Understand AENET in 3 layers

A guided tour with three depths: 30 seconds, 3 minutes and 15 minutes. Choose the layer that matches how much time you have.

C11 / 30S

30 seconds

AENET is a private AI ecosystem being built in public. This website is the read-only public observation layer: it publishes sanitized snapshots, a bounded public API and an anonymous traffic channel — and nothing can reach the private AENET Core from here.

C12 / 3M

3 minutes

The public side is a pipeline: sanitized snapshots from the core are published through a one-way gateway to static pages, a versioned public API (v1), a glossary, research and a development log. A separate early-access waitlist is the only public write path, and it is fail-closed. The private core — agents, model routing, memory, spine — is never reachable from the public side.

C13 / 15M

15 minutes

Follow the guided steps below: what AENET is, the problem it solves, the architecture, one full workflow through the systems, the verified build evidence, and how to request early access. Each step links to the real page with the full detail.

K.PUBLIC.TOUR / READING PATH

Six steps through the public boundary

C20–C25 · READ ONLY
01
K.PUBLIC.TOUR.C20

What is AENET?

An ecosystem being built in public: a private core observed through a public, read-only gateway.

02
K.PUBLIC.TOUR.C21

What problem is it solving?

Building an AI ecosystem without a public attack surface: a strict one-way boundary, sanitized snapshots, and no control channel to the core.

03
K.PUBLIC.TOUR.C22

How the architecture works

Public gateway, snapshot layer, public API, time, glossary, research and development flow — each with a bounded role and a one-way data direction.

04
K.PUBLIC.TOUR.C23

How one workflow moves through AENET

A visit flows: sanitized snapshot → static page + public API → anonymous traffic event. An early-access request flows: form → Turnstile → intake shield → D1 waitlist — never into the core.

05
K.PUBLIC.TOUR.C24

What has actually been built

Verified public states only: the gateway is live, the public API serves v1, the snapshot layer publishes, and the development log records each version — with evidence links on the build page.

06
K.PUBLIC.TOUR.C25

Request Early Access

Join the first public testing queue. It is a waitlist — not an account system — and it is the only public write path, protected by Turnstile and fail-closed.