01
Origin condition
Why it exists
Building a game often requires stitching together tools that hide state, lock creators into formats, or make exported work difficult to inspect. Parallax PixelForge exists as a local-first browser studio where maps, quests, dialogue, inventory, flags, and playable scenes remain understandable and exportable.
Can a creator tool make world-building approachable without hiding the logic that makes the world run?
02
Working system
What it does
- ▦Builds structured worlds
Creates maps, entities, quests, dialogue, inventories, conditions, and story flags from inspectable records.
- ▶Previews playable scenes
Runs deterministic previews so creators can test consequence and progression before export.
- ⇱Exports portable projects
Preserves project data and generated builds outside a proprietary hosted account.
03
System anatomy
Architecture
PixelForge uses a local project model, browser editors, deterministic validators, preview runtime, asset pipeline, and export targets.
Project graph
Scenes, entities, quests, dialogue, flags, assets, and relationships.
Creator editors
Map, narrative, rules, inventory, and content editing surfaces.
Validation runtime
Deterministic checks for broken references, impossible states, and export readiness.
Export pipeline
Playable browser builds and future engine-specific packages.
04
Present tense
Current state
Parallax PixelForge is recorded as Active at the Growing stage. The inventory currently marks 6 artifact lanes Ready, 2 Partial, and 0 Missing.
B3 Tier 1 room draft · Core canon · Operational evidence · public candidate
05
Honest edges
Known limitations
- The toolchain is evolving and does not yet replace mature commercial engines for every genre or platform.
- Browser performance and asset size constrain large scenes.
- Exported projects still require licensing and provenance checks for every included asset.
- A stable public demo and creator documentation need to be packaged together.
06
Claim boundary · v1.1.0
What we are—and are not—saying
PixelForge has a v0.1–v0.4 canon, working local-first prototypes, deterministic validation concepts, and connected game projects that exercise the toolchain.
The current room does not claim complete engine parity, console certification, unlimited scale, or compatibility with every third-party format.
07
Development memory
Ledger
B3-PF-001-01PixelForge v0.1–v0.4 architecture consolidated as the creator-tool lineage.
✓ DocumentedB3-PF-001-02Local browser studio and export workflows represented in working prototypes.
✓ PrototypeB3-PF-001-03Tier 1 creator room drafted with a playable-demo publication gate.
✓ DraftCurated project receipts · source-file binding and human review remain pending
08
Directional, revisable
Roadmap
Package one canonical demo
Choose a small exported world that demonstrates editing, validation, preview, and portability.
Publish the creator path
Document project creation from empty workspace through validated export.
Expand target adapters
Add formats only when round-trip behavior and custody remain inspectable.
10
B10 evidence trail
Featured evidence
Direct original-source trail
B11 adds README-verified public repositories, live experiences, publications, or creator channels. These establish source availability without proving every project claim.
Parallax PixelForge — Public Repository
Open-source retro game creation studio for cartridge-style games, sample adventures, and the 369 PocketGames release lane.
Open bound artifactParallax PixelForge — Project Field Card
B4-generated visual identity card built directly from the reviewed constellation registry.
Open bound artifactParallax PixelForge — Public Genome Snapshot
Public-safe JSON snapshot of the current project registry or expanded Project Genome.
Open bound artifactM
B11 original media
Open the original trail
The original open-source game-creation repository.
Parallax PixelForge — Public Repository
Open-source retro game creation studio for cartridge-style games, sample adventures, and the 369 PocketGames release lane.
Open original sourceGitHub · MichaelWave369/parallax-pixelforge · README verified 2026-07-2511
Publication intake
Artifacts & sources
PixelForge v0.1–v0.4 canon
Architecture and feature lineage.
View archive recordarchive:intake/pixelforge-canonLocal browser studio
Working prototypes exist; one publication candidate must be selected.
View archive recordarchive:intake/pixelforge-browser-studioCanonical playable export
Required centerpiece for the public room.
View archive recordarchive:intake/pixelforge-playable-exportSource basis
archive:intake/parallax-pixelforge/source-basisinternal-prototypeportal:project/parallax-pixelforge@v0.4-b3planning-inventoryReview: Canon, claims, privacy, accessibility, and publication review · pending
12
Move with evidence
Next actions
The strongest evidence for PixelForge is a world that can be opened, tested, and exported.
reviewReview the artifact registerSee which source packages, visuals, demonstrations, and public links are actually ready.
secondaryTrace related projectsFollow documented dependencies and neighboring systems without inventing connections.