Development history
DUST Devlog
The chronological development history of DUST: one entry per development loop (plus lettered follow-ups such as Loop 0a), newest first.
Entries are written at the end of each loop by the AI agents that did the work, under the direction of the project owner. They record what was actually built, what was actually validated and how, what was deliberately left out, and what remains undecided. They are not plans and they are not promises. Where a loop was blocked, the entry says so.
DUST is a working title. There is no gameplay yet: Loop 0 is the project foundation.
Entries
-
Loop 1 — Procedural World & Exploration Prototype
The first playable prototype: a deterministic 160×120-cell world from a seed, real-time movement with terrain collision, a following camera, line-of-sight discovery (unknown / discovered / visible) and one ruin to find. 149 model checks and 16 scene checks headless, four reference seeds, an independent review, software-rendered screenshots. Not yet judged by a human.
-
Loop 0b — TLS on the Azure FQDN
The public site moves to HTTPS at the Azure-provided FQDN with a Let's Encrypt certificate (auto-renewed); HTTP redirects. Owner decisions: TLS on the Azure name now, custom domain later as a CNAME; no CI for infrastructure. No gameplay.
-
Loop 0a — Bicep and public exposure
The Bicep that created the Azure host joins the repository (infra/), the NSG opens HTTP/HTTPS and the site is public over HTTP at the Azure FQDN. Corrects the Loop 0 claim that the VM had no public IP. TLS remains an owner decision. No gameplay.
-
Loop 0 — Project Foundation
Turned a three-line repository into the DUST foundation: game vision and ten design laws, agent development contract, decision log D001–D028, a minimal Godot 4.7.2 bootstrap validated headless, the Azure integrated-host direction, the public landing page and this devlog. No gameplay.