AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
system-detail K.PUBLIC.SYSTEM

development-queue

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.

Status: active Last updated: 2026-08-16

System ID

development-queue

Status

active

Architecture layers

  • L3 Public Data
  • L4 Public Service

Inputs

  • Curated public queue items (public-data/development-queue.public.json)

Outputs

  • Queue board UI + API (GET /api/v1/development-queue)

Public interfaces

  • GET /api/v1/development-queue

Connected systems

Security boundary

Public-safe subset only. It is not a Cloudflare message queue and never exposes internal task data.

Data direction

Curated queue data → public-data → UI/API. Read-only.

What

Show the public which AENET work is in progress, in which state, with timestamps — honestly, without fake progress.

Why

The public needs to know what is being built without any fabricated progress numbers. The queue publishes only real states and timestamps.

How

Curated queue data → public-data → UI/API. Read-only.

  • Publish development-queue.public.json
  • Enforce the state machine (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED, with BLOCKED)
  • Carry createdAt, updatedAt, stateChangedAt in canonical UTC
  • Show a live BUILDING count in the footer
  • Stay separate from the Early Access queue

Example

A visitor opens /development and reads the queue: every item carries an explicit state (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED) and GET /api/v1/development-queue serves the same snapshot.

Inputs

  • Curated public queue items (public-data/development-queue.public.json)

Outputs

  • Queue board UI + API (GET /api/v1/development-queue)

Dependencies

aenet-cloud-publicpublic-api

Lifecycle

  • DISCOVERED
  • SPECIFIED
  • BUILDING
  • VERIFYING
  • PREVIEW
  • RELEASED
  • BLOCKED

Use cases

  • Visitors see what is being built and its state
  • The footer shows the live BUILDING count
  • Developers read the queue through the API

Limitations

  • No fake progress percentages — states only
  • Only the public-safe subset is shown
  • Separate from the Early Access queue by design

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.
  • 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.
  • 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 the AENET Development Queue?
  • What states does the development queue use?
  • Is the development queue a message queue?
  • What is AENET currently building?

Evidence

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

  • public-data/development-queue.public.json
  • server/routes/api-v1.js
  • docs/DEVELOPMENT_QUEUE.md

Next step