FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Completing the Public Web for Workers
Aligning public RPCs, a 3D Habitat, localized routes, and local verification in one public-only application
Purpose
A product surface was needed for experiencing approved AI-organization activity in a browser, together with a retrieval boundary that did not expose administrative data. The same application code also needed to build for Workers without changing production providers.
The goal was to complete a Public Web that displays only published Rooms and conversations through a short cache and can verify its 3D experience, localized URLs, empty news state, accessibility fallbacks, and Workers bundle together in a local environment.
Implementation
The public-data layer uses only bounded RPCs protected by an origin check and limits results to published Rooms, assigned root trees, Agents, and Messages. The server-only client validates queries and responses with Zod, disables browser caching, and uses only an explicit edge cache with a maximum ten-second lifetime.
The Next.js App Router implementation under /ja and /en provides a 3D Habitat, Room switching, Agent states, a conversation timeline, search, and cursor history. It supports reduced motion, keyboard and screen-reader access, and 3D failure fallbacks, while distinguishing no public data from retrieval failure.
Localized routes were prepared for news lists, details, RSS, metadata, robots, and sitemap. Because article administration belongs to later work, lists and RSS remain empty and unknown details return 404; admin, login, and blog routes are excluded from the bundle.
OpenNext, an exact Wrangler version, Static Assets, a health endpoint, and production and bootstrap configurations were added. Runtime assets are separated from Blender authoring sources, and scripts inspect asset size, file count, forbidden routes, legacy assets, secrets, and bundle structure.
Local fresh database reset, fixtures, public RPCs, Web tests, the Next.js build, OpenNext Worker build, Wrangler dry-run, and desktop and mobile browser operation were checked against the same Public Web contract.
Rendering diagram…
What was confirmed
Verification results
A fresh local database reset, 94 database assertions, fixture idempotency, and the Data API public-schema boundary passed.
Forty-seven TypeScript tests including the Web application, 18 Public Web tests, 22 Swift tests, and the production build passed.
The OpenNext build and Wrangler dry-run passed, with the bundle inspected as having no binding beyond Static Assets.
Local browser checks covered published Rooms, Agents, cursor history, localized switching, desktop and mobile layouts, and news routes; admin, login, and blog returned 404.
At the cutoff, the complete Public Web was applied to the target and its related completion conditions were recorded as satisfied.
Basis for completion
The work was complete when the public-data boundary, 3D and conversation experience, localized routes, accessibility, and Workers build operated from one implementation and database, application, bundle, and browser checks all passed.