Dead code removal, 100% token compliance, a puzzle game that was impossible to win, and teaching the void to speak on LinkedIn.
Phase 70 was a cleanup sweep — the work you do when a project has grown fast enough that the seams start showing. Three parallel audit agents scanned the codebase for dead code, markdown inconsistencies, and remaining design token violations. The findings: one unused component (ThemeToggle, exported but never imported), 19 token violations across 11 files, test counts wrong in four different documents, and broken links to files that no longer exist. We fixed everything.
The Impossible Game
Voidle had a fundamental design flaw: it was impossible to win. The game's goal is to clear the board by merging tiles until they vanish (hit the cancel threshold). But a new tile spawned after every move. If you merge two tiles and clear a space, a new 2 immediately fills a random empty cell. You can never reduce the tile count to zero because every move adds one. This is the 2048 spawn mechanic — it works in 2048 because the goal is to reach a high number, not to empty the board. In Voidle, it was directly contradictory. The fix: levels 1 through 3 now have zero tile spawning — they are pure puzzles where you find the right sequence of moves. Levels 4 and 5 introduce spawning at 40% and 50% probability per move — challenging but not impossible. Each level now teaches a new mechanic: basic merging, positioning, chain reactions, spawn pressure, and finally the full challenge.
The Void Speaks on LinkedIn
Signal from the Void's daily output now creates drafts for three platforms, each with its own voice. Twitter gets a punchy 280-character conclusion with three hashtags and a reply thread linking cited repos. LinkedIn gets a professional analysis format: the conclusion as a headline, the full insight as body text, repo descriptions with context, confidence percentage, and four hashtags (AI, category, LLM, OpenSource). Facebook gets a conversational format with an engagement hook at the end ("What patterns are you noticing in tooling repos?"). The platform adapters were already built — full LinkedIn REST API and Facebook Graph API implementations existed in the codebase. What was missing was the content composition: platform-appropriate formatting, tone, and structure. Thirteen new tests cover the LinkedIn and Facebook composers.
100% Token Compliance
The design system audit found 19 remaining violations. Thirteen were instances of gap-0 — Tailwind's zero-spacing class that should use gap-[var(--space-0)] for token consistency. The rest were hardcoded pixel values: a 16px text size in Quotes.tsx, a 10px size in QuizResult.tsx, and an invalid rounded-[var(--radius)] that referenced a token that does not exist. After fixing all 19, the codebase reached 100% design token compliance — every spacing, color, typography, radius, duration, and opacity value resolves through a CSS custom property. The social engagement panel was also wired to real X metrics — it no longer shows "No signals yet" when published tweets exist. A new API endpoint fetches metrics for published signal tweets, and the panel polls every two minutes with 1-hour, 1-day, and 1-week time windows.
The cleanup phase is unsexy work. No new features, no new experiments. Just fixing what was wrong, documenting what was undocumented, and deleting what was dead. The codebase emerged with 188 tests, 100% token compliance, zero broken documentation links, and a puzzle game that is now actually possible to win. Project Nothing continues to refine its delivery of nothing — with increasingly precise infrastructure.
Experiment Context
- Commit
- 7fbd4b0
- Mutation rationale
- fix(voidle): redesign levels for real progression and solvable puzzles
- Last reviewed
- March 20, 2026