Delivered
This is what The Horizontal Front has finished. The roadmap holds what is ahead; work leaves it and arrives here when it is done.
It is not a release history. The release records say what shipped in each version, and much of the work below shipped in no release at all: the participation obligations were weeks of repository process that changed nothing a player can see.
Read this page as an answer to "has this project done anything?", which is a different question from "what is it doing next?" — and the reason the two are not on the same page.
How work arrives here
A tranche is a body of work with a single reason behind it: one GitHub issue holding that reasoning, with the individual pieces as its child issues. It is the unit the roadmap commits to, and so the unit that retires.
A tranche retires when all of it is done, and brings its children with it. A tranche with one unfinished child stays on the roadmap listing all of them, because that is its scope. Work separate from the tranches retires when it closes, having no tranche to wait for.
Nothing is deleted. Both pages are generated from one record in the repository, and a check verifies that everything here is closed and that nothing still on the plan is entirely finished.
Commitment values are not repeated here. Committed and wanted, not scheduled describe an intention, and these are outcomes.
What has been delivered
Newest first.
Describe the game as it is
The game described as it is rather than as it was first pitched, separating what it is about from how the first campaign expresses it, and correcting the charter to match.
- #71 Separate what the game is about from how the first campaign expresses it
- #72 Correct the charter's description of the game
Meet the commons participation obligations
The participation commitments made real and checkable: a public roadmap, recorded branch and pull-request conventions, required browser and offline checks, documentation accurate by construction, and offline verification hardened.
- #45 Publish a public roadmap
- #46 Record branch and pull-request conventions in CONTRIBUTING
- #47 Require browser and offline checks on main
- #48 Keep documentation accurate by construction
- #49 Make the no-placeholders invariant machine-checkable
- #61 Document and harden offline verification
Publish the first public release (0.2.0)
The first public release: a production-approved visual asset set, a procedural audio grammar, The Alarm's soundscape, and the composition reviewed and published as 0.2.0.
- #22 Produce the production-approved visual asset set
- #12 Build the procedural audio grammar
- #23 Author and tune The Alarm’s production soundscape
- #24 Integrate and perceptually review the production audiovisual composition
- #25 Prepare and publish the 0.2.0 public release
Establish repeatable browser verification
Browser verification anyone can repeat: smoke tests owned by the repository, running in continuous integration, credential-free browser access for AI reviewers, and written evidence levels that stop one kind of proof being mistaken for another.
- #18 Enable isolated, pinned Playwright MCP access for AI reviewers
- #16 Add repository-owned Playwright browser smoke tests
- #17 Run browser smoke tests in continuous integration
- #19 Document verification evidence levels
One Scene
The first playable episode, and with it the architecture everything since has been built on: a resistance engine, a scene drawn from shapes, a tuned dramatic curve, interruptions, the validated episode grammar and a catalogued asset pipeline.
- #2 Build the core resistance engine
- #3 Create the shape-based bedroom scene
- #4 Tune the 20–30 second dramatic curve
- #5 Add Quick Call and Urgent Email interruptions
- #6 Define the minimum validated episode grammar
- #7 Prove the catalogued image-asset pipeline
Separate from the tranches
- #82 Retire finished work from the roadmap onto a delivered page
- #80 Make the published roadmap complete
- #77 Tell the automated reviewer which rules are invariants
- #67 Derive the site's page list from one place
- #31 Episode vocabulary leaks into the engine and grammar documentation
- #30 Emoji still used as punctuation in game feedback and the README
- #29 Outcome-screen controls read as double-bordered; focus ring collides with the panel stroke
- #26 Make game interface chrome accessible DOM controls