Turn a public GitHub repository into a world you can explore.
See the architecture. Follow the work. Find your next move.
Explore the live site ↗ · 简体中文 · Quick start · How it works
Code into worlds. Five perspectives. One source of truth.
The recordings below are historical captures; their Chinese UI is retained as historical evidence. The current UI is English only, and license metadata does not restrict public GitHub analysis.
A moon base, an industrial network, a command center, a fortified city, a hexagonal civilization. Switch the visual language while keeping the same repository, district identities and source evidence.
▶ World tour Watch / download MP4 · 14 seconds |
▶ From source to next steps Watch / download MP4 · 8 seconds |
Silent product recordings; click either poster for the MP4. GitHub README playback depends on your browser, so the GIFs provide inline previews. Media provenance and limits.
- Choose any publicly accessible repository. Paste its GitHub root URL, or explore an available cached world in the atlas.
- Read the landscape. Paths and manifests become districts; source evidence and structural inference explain the connections.
- Inspect a place. Select a district to see its role, evidence state and links pinned to the captured source head.
- Follow the work. Read issues, pull requests, commits and workflow results in context. Success, failure, skipped and missing evidence stay distinct.
- Find a next step. Read the deterministic architecture guide, or explicitly request an optional AI guide when the configured provider and budget allow it.
| Explore | Understand | Stay grounded |
|---|---|---|
| Pan, zoom, search and select districts | Source-linked architecture and suggested next steps | Observed / inferred / unknown states |
| Five original procedural styles | Issues, pull requests, commits and CI activity | Captured head, timestamp and coverage |
| English-only interface | Shareable world URLs | Explicit stale, partial and unavailable states |
These are five views of the same cached Next.js repository, rendered by the actual application. All artwork is procedural; no game assets are included.
The map is a way into the evidence. Open a district, inspect its source, then move between activity and the field guide without losing the repository context.
Observed means supported by captured source evidence. Inferred means a structural interpretation. Unknown means the evidence does not establish the fact. Moving particles illustrate connections; they do not measure runtime traffic. A historical green workflow is not proof of current deployment health.
Browse nineteen editorial entries across developer tools, frameworks, languages and infrastructure. Available previews use real cached maps; missing maps remain explicitly unavailable. The catalog is not a claim that every project has a fresh, complete collection.
Built with TanStack Start · React · TypeScript · Bun · Canvas 2D. Requires Bun 1.4.4 and the committed lockfile.
bun --no-env-file install --frozen-lockfile --ignore-scripts
cp .env.example .env
bun run dev
# http://127.0.0.1:4178/github-factory/A new checkout starts without model credentials and with a zero model budget. Deterministic architecture analysis needs no paid API. Authenticated GitHub collection and optional AI use server-only settings in .env; never expose credentials through VITE_ variables. Paid generation requires an explicit action, bounded requests and the persisted concurrency-safe ledger. Preserve the original ledger across provider or release changes.
Checks and production build
bun run check
bun run test
bun run build
HOST=127.0.0.1 PORT=4177 bun run start
# In another terminal, against the running local app:
bunx --no-install playwright install chromium
bun run test:browserBrowser journeys intercept APIs with clearly labeled synthetic fixtures; they do not spend paid model quota. Local checks, CI, public runtime adoption and real provider acceptance are separate evidence.
Hosting and base path
MOONSHOT_BASE_PATH is a build-time public path, defaulting to /github-factory/. To serve the root, build with MOONSHOT_BASE_PATH=/ bun run build. Keep the same artifact and path through verification and deployment.
The server needs a persistent Bun host. Local development uses SQLite; production can use Cloudflare D1 for public world snapshots through a private fixed-operation bridge. Model spending, cached guides and admission authorities remain on the persistent host. A Cloudflare Workers site alone cannot run bun:sqlite.
See deployment and the dated production acceptance record.
The app reads bounded public GitHub metadata, paths and manifests. It never clones or executes an input repository. Repository text is untrusted data, never instructions. Refreshing facts or changing styles does not regenerate a paid guide. Secrets, caches, ledgers and private runtime records stay outside Git.
This independent MIT repository is the sole source for future GitHub Factory / Moonshot development. Legacy MOONSHOT_ setting names and the /github-factory/ public path remain stable.
| Learn more | |
|---|---|
| Product and architecture | Product design · AI and budgets |
| Set up and ship | Setup · Deployment · Production evidence |
| Contribute | Contributing · Migration |
| Media and licensing | README media · Third-party notices |
Dated reports in docs/ retain historical scope and limits; they are not current production guarantees. Film tooling lives in media/film; generated speech and the uncleared narrated film remain private and are excluded from this release.
Every codebase. A world of its own.
Open Moon Factory ↗ · 简体中文 · MIT License
Copyright 2026 CHAORDERS LLC. Game names describe visual inspiration; no game assets or endorsement are included.











