MM.to Gabe · 10:47 PM
the essay thing
I tried it. It actually got me unstuck. We can rewrite the weird parts afterward.
Don’t laugh at the icon.
PROJECT / NORTH STAR
Restore the files. Recover the story.
Saved locally
RECOVERY PROCESS / SIGNAL DETECTED
Something is broken.
Something answered.
A forgotten recovery process wakes inside a damaged machine. Restore what still responds. Let the files tell you whose computer this is.
HOST DATA INTEGRITY42%
FILE CHAIN×431 BLOCKS RESTORED
Every line recompiles data
Clears rebuild scripts, files, and memories. A familiar falling-block action always advances the recovery.
Files make Gabe more than grades
Drafts, playlists, waitlists, trophies, and song fragments slowly turn an anonymous host into someone worth protecting.
Malware changes the rules
Telegraphed routines inject crooked data, spike gravity, seal rotations, and hide the queue without stealing attention from your board.
THE 45-SECOND HEARTBEAT
Place. Recompile. Reveal. Adapt.
- 01Read the fragment queue
Plan around the next three weighted data shapes.
- 02Rebuild the sector
Complete clean lines or prepare a risky recovery chain.
- 03Restore a file
Clears reduce corruption and surface pieces of Gabe's life.
- 04Install a module
Alter the queue so the next damaged system needs a different plan.
VERTICAL-SLICE QUESTION
Does recovery make us care?
Protect the connection between falling-block skill, file recovery, and empathy before expanding the story.
RECOVERY PROCESS / 3 ROUTINES MISSING
Construct yourself.
A damaged computer is still answering. Restore movement, orientation, and commit routines before entering its files.
C:\USERS\UNKNOWN / 01:23 AM
A damaged process is still answering.
Follow the signal. Restore what remains intact.
CURRENT RUNHOST-01 · SIGNAL FOUND
RECOMMENDED TEST / BUILD 0.8
Can the first 12 minutes teach themselves?
Play without reading the rest of the workbook. Stop after recovering Almost.docx.
STOP POINT4 DATAARTIFACT 01
- 01Watch the openingCan you explain what Gabe downloaded and why?NOT STARTED
- 02Construct RE:COMPILEDo move, rotate, and commit feel obvious and responsive?LOCKED
- 03Recover 4 dataDo line clears feel like repair, combat, and progress at once?LOCKED
RECOVERY ROUTE / GABE'S COMPUTER
Build yourself. Follow the evidence.
DATA GATHERED0 / 18ARTIFACTS0 / 3
BOOT SEQUENCE / HOST UNKNOWN
Stabilize the damaged directoryNo identity attached. Recover enough data to read what remains.PERMANENT DELETE01:15Clear the quarantine lock before the timer reaches zero.
SECTOR 01LINES 0RESTORED 0CHAIN ×0MEMORY 0 KB
ROUTINE 1 / 3Restore movement
Use ← or → to reconnect locomotion.
C:\USERS\HOST-01\DOCUMENTS
DATA RESOLVED
Almost.docxESSAY DRAFTRECOVERED DATA
0 / 18
ACTIVE ROUTINECLEAR
RECOVERY CODEX / VOLUME I
The book of fragments.
Every silhouette is a recoverable data shape. Each entry records its job, liability, and the question that earns it a place in the queue.
VOLUMEI21 / 21 ENTRIES
RECOVERY CODEX / VOLUME II
The book of modules.
Twenty hypotheses for changing draws, geometry, memory, routine answers, and linked-process conversation. Pin only what deserves the next implementation slot.
VOLUMEII20 / 20 ENTRIES
NARRATIVE ROUTE / THE NIGHT BEFORE
Follow the fragments back to Gabe.
Each machine changes the recovery rules and complicates RE:COMPILE's understanding of its host. The full campaign is authored; optional recovered files change details, not the emotional spine.
Gabe, then Dad
B+ grades, waitlists, unfinished drafts, second-place trophies, and rehearsal clips initially make Gabe's “almost” story look true.
TURN: Dad preserved these files because he was proud.Sister, then friend
Hopeful messages and distributed song fragments reveal a fuller Gabe. His friend confesses that fear—not cruelty—led him to share the fraudulent writing tool.
TURN: enough fragments exist to locate a deleted master.Return and sacrifice
RE:COMPILE recovers the finished song and rebuilds a heartfelt essay, but lost sections require Gabe to supply their meaning.
TURN: Gabe finishes the words; RE:COMPILE finishes the upload.THREAT GRAMMAR / SYSTEM PRESSURE
Every routine should feel like a computer problem.
Fragment Injection
SHAPEForces malformed data into the queue.
CPU Spike
TEMPODoubles process speed for two commits.
Permission Lock
CONTROLRejects rotation for the active fragment.
Index Loss
READHides the fragment preview for two commits.
DISCOVERY LADDER
Evidence changes what “almost” means.
| Machine | What RE:COMPILE finds | First interpretation | Later truth |
|---|---|---|---|
| Gabe | Grades, drafts, deadline | Chronically unfinished | His measurable record is incomplete |
| Dad | Trophies, waitlists, rehearsal fragments | More evidence of almost | Dad saved them because he was proud |
| Sister | Hopeful messages, song remainder | Someone still believes in him | Gabe trusted her with his progress |
| Friend | Confession, shared insecurity | Cause of the disaster | A flawed friend frightened by the same future |
| Gabe again | Deleted master song | Another lost project | The one important thing he finished |
BALANCE / FRAGMENT QUEUE
See the odds before you trust them.
Tune an example recovery bag, inspect exact draw probability, and simulate one hundred data fragments.
BAG WEIGHTS
Relative draw weight
THEORETICAL DISTRIBUTION
Every draw, disclosed
SEEDED SAMPLE
Ready to draw
The sample uses a repeatable seed so a balance change can be compared honestly.
RULES / RECOVERY MODEL
One stack, readable consequences.
These are the standing rules for the narrative vertical slice. Every system must strengthen recovery, discovery, or escalating computer pressure.
BAG
Weighted independent draws
Every unlocked piece has a visible relative weight. Three-piece preview protects planning; no hidden pity system in the first test.
RECOVERY
Restored blocks suppress corruption
Every sent block reduces malware integrity and restores one kilobyte of usable memory. One number drives progress and resources.
ROUTINES
Pressure is telegraphed
Malware casts timed shape, gravity, permission, and index routines. The next mutation is always named in advance.
CO-OP
Relay ownership
Partners alternate pieces, share one queue and stack, and earn a team combo only through consecutive clears. Hold begins locked for the whole team.
STORY
Files are playable evidence
Recovery milestones surface short artifacts. Their order changes RE:COMPILE's interpretation of Gabe without pausing for exposition.
FAILURE
Top-out loses the sector
A failed recovery restarts the current machine. Learned information stays with the player, while the board remains a clean mechanical retry.
FIRST-PROOF NUMBERS
Recovery contract
| Action | Base output | Why |
|---|---|---|
| Clear 1 / 2 / 3 / 4 | 4 / 10 / 18 / 30 blocks | Every clear suppresses corruption and restores memory |
| Restored block | 1 corruption + 1 KB | One readable number drives combat and modules |
| First three clears | One recovered file each | Story progress follows demonstrated play |
| Mutation routine | Every 11 seconds | Enough time to read and adapt |
| Trash escape | 75-second purge clock | Human action becomes an environmental boss |
| Board | 12 × 22 cells | Room for wonky fragments and prebuilt damage |
| Cache | Locked · 90 KB module | A familiar safety tool becomes progression |
EDITABLE SCOPE
Feature board
Every feature carries a proof statement. Move the evidence, not just the card.
PLAYTEST LAB / CONTROLLED RECOVERY
Test one thing at a time.
Load a repeatable setup, watch behavior instead of teaching, then record the decision. The new priority is proving that file recovery makes the falling-block loop more meaningful.
SESSION PROTOCOL
Keep a friend test under 25 minutes.
- 01Say only the goal and controls printed on screen.
- 02Run one preset without changing the rules mid-fight.
- 03Ask what they planned—not whether it was “fun.”
- 04Record keep, tune, remove, or retest before discussing new ideas.
SESSION MEMORY
Evidence and decisions
MVP / NARRATIVE PROOF GATE
One clear finish line.
The current priority is a stable 15–20 minute slice where players recover Gabe's files, understand the malware pressure, and want to follow RE:COMPILE into Dad's recycle bin.
MVP READINESS50%6 / 12
CURRENT TARGET
Narrative Recovery Build 01
Gabe's laptop · three recovered files · Ghostwriter Worm · Dad trace · timed trash escape · structured story/combat feedback.
DEFINITION OF READY
Interactive checklist
PRIORITY GUARDRAIL
When a new idea arrives, ask one question.
Does this unblock the next friend playtest or answer an open experiment?
If yes, place it in Now. If not, capture it on the Feature board and keep moving. Side quests are welcome; they just should not quietly replace the milestone.
PRODUCTION DOCS
Keep the build explainable.
STANDING PROMPT
Protect the differentiator.
Build the smallest proof that falling-block recovery can reveal character. Keep probabilities visible, malware pressure telegraphed, and every story artifact earned through play.