GPT-6 Astra creative capabilities and the AFTERLIGHT build

Findings

The most useful creative capability demonstrated by Astra is the ability to carry a project through several different kinds of work: spatial construction, programming, application control, and verification. A polished screenshot is one kind of evidence. An executable artifact, a source repository, and a record of the work provide progressively more ways to inspect the claim. The strongest direction for an overnight showcase is an original playable system whose behavior can be examined directly.

AFTERLIGHT takes that direction. It combines procedural 3D architecture, a small resource-management game, an exact time machine, alternate-future comparison, a directed short film, and browser-generated sound. The viewer can watch the same city face the same event with different preparation. This makes the central claim tangible: the attractive world is connected to a working model of consequences.

This review uses public material accessed on September 12, 2026. It distinguishes original sources from promotional selection, repositories from independently rerun experiments, and functional design from claims about scientific accuracy. No public demonstration establishes a guaranteed eight-hour autonomous success rate. The build therefore uses its own acceptance tests rather than treating a benchmark or a viral post as a completion certificate.

Evidence ledger

What the demonstrations actually show

Detailed worlds and complete artifacts

OpenAI's launch material includes a house constructed in Blender and presented as a walkable Unreal Engine scene, and a playable kart-racing showcase credited to Pietro Schirano. The relevant implication is that a creative workflow can cross geometry, rendering, interaction, and presentation. The page is a selected demonstration, so it would be unwarranted to call these outputs typical or to infer their complete prompt histories from the finished clips. AFTERLIGHT adopts the range of work while keeping the runtime in a browser to reduce packaging and compatibility overhead. OpenAI launch

The Qingming river-city repository provides another concrete comparison. Its documented experience includes modeled buildings, people and boats, selectable locations, time-of-day settings, and capture tools. It also provides prompts and implementation notes, which make its claims easier to investigate than a standalone video. The project describes local bundled assets and an HTTP launch workflow. The transferable principle is a cohesive scene with useful routes through it, backed by a reproducible delivery. AFTERLIGHT uses original procedural geometry rather than copying these models or its historical reconstruction. Original repository

Sustained perception and action

CozyBlaze's original Portal repository states that the run reached the credits on September 5, 2026. The game paused while the model reasoned. Screenshots, position and camera angles informed actions, and a controller advanced the game for selected ticks. The creator reports approximately 23 hours and 43 minutes, including capacity interruptions, and says they resumed the run and changed to Fast mode. This is materially more qualified than a claim that the model played continuously in real time without operational help. Its lesson for the build is the observation-action loop: inspect a result, perform a bounded action, then inspect again. Original repository

SuperAstra uses a different kind of loop: a desktop companion for investigating and changing an emulated SNES game. Its README identifies BizHawk, live memory tools, platform prerequisites, an API key requirement, and bounded validation results. Those details are part of its capability, because the tools and environment enable the model's actions. It is a useful reminder that “Astra did it” is incomplete without the surrounding system. AFTERLIGHT makes its own tool boundary explicit: the model authored the project, but the finished game has no model service or secret running inside it. Original repository

Procedural life and sound

ABYSSAL documents a continuous generated underwater landscape with coordinate-derived seeds, bounded detailed tiles around the camera, instanced scenery, and fixed-step animal steering. It describes pause behavior for animation and optional synthesized sound, and states that its population display counts loaded animals. These are useful examples of making an attractive simulation's limits legible. AFTERLIGHT uses a fixed world, repeated instanced components, clock-driven people and ferries, and optional synthesized sound. It does not imply that its inhabitants are autonomous language-model agents or that its fictional star obeys astrophysical equations. Original repository

Gaps and claims excluded

An aggregator of Astra demonstrations was useful for discovery, but its popularity counts, superlatives, and summaries were not treated as final evidence. Original posts that could not be opened were not promoted into verified facts. Research-service summaries were retained separately as a discovery map, and decisive claims were checked against original pages or repositories.

No attempt was made to rank all Astra creations. The public examples are a selected sample with differing prompt histories, tool access, hardware, iteration counts, and disclosure. The review did not rerun Portal, install Unreal Engine, execute emulator patches, or establish the performance of someone else's project on this machine. It also did not use speculative claims that programming is solved, all software can be generated without supervision, or a visually persuasive simulation is scientifically accurate.

The API reference advertises substantial context and output capacity, but these are not substitutes for a compact project state. A persistent build plan, small modules, deterministic tests, screenshots, and bounded review make continued work easier to verify than an ever-growing conversation. Model reference

The original design decision

Three possible directions were considered: a purely cinematic cosmic scene, an AI-driven society, and a playable time machine. A cinematic scene has immediate visual appeal but limited replay value. A live AI society introduces latency, operating cost, service access and difficult-to-verify claims about autonomy. The time machine offers a visible, testable surprise: the viewer can make an alternative outcome rather than simply admire a render.

The setting makes the controls part of the story. The Harbor gathers returns, the Garden protects living things, and the Spire returns a song to the star. Gather, Shelter and Resonate are the entire action vocabulary. The clock and shields expose their consequences without requiring a tutorial full of abstract systems. Each district's architecture gives it a recognizable silhouette, so selection does not depend solely on labels or colors.

The visual direction is a miniature observatory made from ivory stone, dark metal, botanical greens, and warm brass. A luminous captive star creates the center. Orbital rails and ferries connect the districts. The typography combines a literary serif with sparse technical labels. The opening leaves room for one large statement; the game reveals its controls around the edge of the world.

Bruno Simon's portfolio provides a useful interaction precedent: visitors learn about the site by moving through a place. AFTERLIGHT adapts that principle through district close-ups, whole-city orbit, a ferry ride, and a photo mode. It does not copy his environment or vehicle. Creator's site

Outer Wilds provides the temporal precedent. Its developer describes a solar system whose places change with time and whose exploration is organized around an endless loop. AFTERLIGHT uses a much smaller three-minute cycle and a directly controllable history. The intended similarity is curiosity about changing places, with an original setting and rules. Developer's description

How the time machine works

The simulation advances in quarter-second steps. Each step reads the current district modes, updates bounded resources, advances the star, and applies any event scheduled at that exact time. Three waves arrive at 45, 90 and 135 seconds. Dawn arrives at 180 seconds. The objective is to have all districts at or above 35% life and the star at or above 60% light.

A decision is a small record: time, district, and mode. Rewinding replays those records from the initial state up to the selected time. The process is quick because the world is deliberately small. Rendering uses the same clock, so ferries and inhabitants follow the selected moment. This avoids trying to reverse accumulated frame-rate-dependent physics.

When a decision changes earlier than the furthest observed time, the former command history is preserved as one alternate future. The new history discards later commands and begins a branch. Compare computes both histories at the same time. Its displayed resources and district condition are actual state values. The violet geometry represents the previous future's shield strength.

The opening film is a scripted demonstration of this mechanism. It first shows an unprepared Harbor taking a hit, then moves backward through time and presents a protected alternative. It is a directed explanation, not an improvised AI performance. Taking the controls removes later scripted decisions and gives ownership of subsequent choices to the visitor.

Rendering, sound and delivery

Repeated towers, ribs, trees, windows and structural pieces are collected into instanced meshes. A custom fragment shader creates the star's turbulent surface. Other effects use ordinary geometry, lightweight shaders, and optional bloom. Repeated geometry is a strong candidate for instancing because many objects can share geometry and material while varying their transforms. Three.js API reference

Quality controls reduce pixel density, disable bloom and shadows, and lower particle count. The phone begins with the lighter setting. The desktop and phone use different camera framing, because shrinking a desktop screenshot is not enough to make a scene usable on a narrow display. Reduced-motion preference stops automatic opening motion and starts the game clock paused.

The soundscape consists of synthesized tones, a generated reverb, and sparse notes. The star and district singing influence musical layers. Sound begins only after a deliberate button press and goes quiet while time is paused, a dialog is open, or the tab is hidden. No microphone or audio service is required.

The game stores a validated future in local browser storage and can encode the same history in a share link. A local address is identified as local in the share dialog. A postcard is exported as an actual PNG from the rendered scene. The production build consists of static files and bundled fonts; it does not require an API key at runtime.

Design evidence

The Disney+ playback reference and Paramount+ playback reference were visually inspected. Their useful common pattern is the separation of immersive content from a low-profile transport bar. That pattern is adapted to a time machine with event markers and a branching-history control.

Two 21st.dev metadata candidates were reviewed: Video Player by thegridcn (catalog demo 19339) and Video Player Pro by ruixen.ui (catalog demo 7479). Their descriptions suggested HUD framing and fuller media-control stacks. Both were rejected as implementation dependencies. No component source was retrieved or copied. Original HTML controls are smaller and better suited to the simulation's unusual timeline behavior.

Verification standard

The build is complete only when its executable evidence supports the result. Unit tests cover exact replay, event boundaries, bounded resources, branch isolation, invalid save rejection, and known successful and failed strategies. Browser checks exercise the actual controls through an ending, rewind, altered future, comparison, save and resume, share import, photo export, camera modes, sound toggle, help, film and takeover.

Responsive checks cover portrait phones, short landscape, a laptop and a larger desktop. A separate reduced-motion context verifies paused startup. Blocked storage, malformed share data, and lost WebGL context are checked explicitly. Console errors and external requests are recorded. Screenshots are inspected after generation. Browser automation provides reproducible interaction evidence; hardware performance measurements must separately identify the rendering backend.

The project also uses a bounded independent review through the configured Claude courier after its local gate passes. A failure or timeout is recorded as missing review evidence, never described as a clean review. The final status belongs in the build's delivery notes and QA artifacts, because that status changes as fixes are made.

Sources and scope

The ledger above contains the principal sources and exact links. All were accessed September 12, 2026. OpenAI pages are vendor sources; public repositories are source-available creator artifacts; Mobbin screenshots are product-design references; the game-developer pages are original prior-work references. The GDC page was used only to identify the original rewind talk. The research discovery transcript is preserved in discovery-notes.md with an explicit warning that its generated synthesis is not independently verified evidence.