AENET ecosystems PUBLIC GATEWAY
Request a Pilot
GATEWAY READY
EN ไทย 中文
system-detail K.PUBLIC.SYSTEM

SYS.ID.01 D02 early-access

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.

Domain: Identity & Access STATUS: preview Public boundary: OBSERVATION ONLY Last updated: 2026-08-16
KAP-GRID K.PUBLIC.SYSTEM.C03

System ID

early-access

Status

preview

Architecture layers

  • L2 Public Application
  • L4 Public Service (D1 store)

Inputs

  • Visitor email, optional locale/interests, explicit consent

Outputs

  • Registration tickets (D1 only)
  • Success/unavailable responses to the visitor

Public interfaces

  • GET/POST /api/v1/early-access/register

Connected systems

Security boundary

Early access registration is the only public write path, and it writes only to D1 — never to the core. Applicant data is never indexed, never exported, never in sitemaps, never published.

Data direction

Visitor → registration form → validation → D1. One-way; never to the core.

Public interfaces

Derived from the API registry

GET /api/v1/early-access aenet.public.early-access.v1 active READ-ONLY
POST /api/v1/early-access/register aenet.public.early-access.registration.v1 active WRITE

Security

Early access registration is the only public write path, and it writes only to D1 — never to the core. Applicant data is never indexed, never exported, never in sitemaps, never published.

What

Let interested visitors request early access to the gateway while keeping every applicant record private and bounded.

Why

AENET needs a way to know who wants early access without building an account system or exposing personal data. Early Access is a consent-based waitlist with private D1 storage.

How

Visitor → registration form → validation → D1. One-way; never to the core.

  • Serve the early access page and registration form
  • Validate email, locale, interests and consent
  • Reject unknown and sensitive fields
  • Store applicant records in D1 only
  • Be duplicate-safe per ticket without revealing private data
  • Fail closed when Turnstile verification is unavailable

Example

A visitor requests early access: the form validates consent and interest, Turnstile checks the visitor, the intake shield normalizes the email, and a ticket (EA-…) is stored privately in D1 — never published.

Inputs

  • Visitor email, optional locale/interests, explicit consent

Outputs

  • Registration tickets (D1 only)
  • Success/unavailable responses to the visitor

Dependencies

aenet-cloud-publicpublic-apiturnstile-policy

Lifecycle

  • waitlist foundation
  • consent capture
  • turnstile verification
  • D1 storage

Use cases

  • A person requests early access to the gateway
  • The system records the request privately in D1

Limitations

  • Waitlist only — not an account system
  • Registration may be unavailable (fail closed) without Turnstile
  • Applicant records are never public

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

Questions people ask

These questions are answered by the content on this page.

  • What is AENET Early Access?
  • How do I request early access to AENET?
  • Is early access data private?
  • Does early access require an account?

Evidence

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

  • server/services/early-access-validator.js
  • migrations/0001_early_access.sql
  • docs/EARLY_ACCESS.md
  • docs/TURNSTILE_POLICY.md

Next step