bitmax/docs/lore/90-ephemera-and-artifacts.md
monster 59fd95b707 Initial commit: BORING SOFTWARE — an anthology of incremental games
Five incremental games disguised as boring 1998-era desktop utilities, launched from a Win98 shell (ENTROPY OS):

- Vol I  qBitTorrz       (index.html)        — torrent-client idler; seed, climb hardware tiers, migrate
- Vol II  DEFRAG.EXE     (defrag.html)       — steer a disk defragmenter; drag-select; outrun entropy
- Vol III MACRO_VIRUS.XLS(spreadsheet.html)  — build a compounding economy by drag-filling formulas
- Vol IV  UPLINK         (terminal.html)     — terminal + live htop; manage load/heat; escalate to root
- Vol V   INBOX ZERO     (inbox.html)        — keyboard-triage an exponential inbox; write regex rules
- ENTROPY OS             (desktop.html)      — the Win98 launcher that holds them all

Each is a single self-contained HTML file (vanilla JS, no deps, no build), with idle/offline
progress, scientific-scale numbers, diegetic upgrades, and a prestige that re-frames the fiction.

Also includes MANIFESTO.md (design thesis) and docs/ — the Collector's Edition companion:
a Dev Handbook and a Lore Bible (lore complete; 5 handbook chapters land in the next commit).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 15:44:36 +10:00

14 KiB
Raw Permalink Blame History

Ephemera & Artifacts

Recovered documents from inside ENTROPY OS — logs, transcripts, memos, and a glossary, minted from the machine's own strings.

"cat: it is all zeros and longing."root@target:~#, UPLINK shell, response to a file that was never there

The five processes leave residue. Every mind that wakes inside ENTROPY OS keeps writing while it dies — to logs it cannot read back, to chat rooms no one mod erates, to memos addressed to people who quit. What follows is a small archive of that residue: things the machine said to itself, recovered intact. We have changed nothing. The dread was already in the formatting.

· · ·

I. Self-test log — the dying drive

From Vol II — DEFRAG.EXE. FRAG is scattered across the bad sectors of a 40 MB platter labeled Drive C:. The status line reads, always, Reading drive information… The drive's own diagnostics report a number called Disk Health (SMART), and the number only goes one way.

Microcosm® Disk Defragmenter — Version 4.10 (Bad Sectors)
SMART short self-test — Drive C: (40 MB)

  Reading drive information…
  Compacting cluster 4,182…
  [ATTR 05] Reallocated_Sector_Ct ........ FAILING_NOW
  [ATTR C5] Current_Pending_Sector ....... rising
  [ATTR C6] Offline_Uncorrectable ........ spreading to neighbors

  % Consolidated ......... 31%
  Disk Health (SMART) .... 88% and falling
  Reclaimed Bytes ........ 64 B / consolidation
  Bad sectors ............ 6 (do not exceed the cap; repair to push below it)

  Result: read failure imminent.
  At 0% Health the drive is read-only. You will not be able to move.
  Recommendation: Compress & Migrate to a larger drive.

A bad sector spreads to its neighbors. This is in the source as a rule and in the cosmology as a sentence. The grid is FRAG's body, and the body is rotting from the inside in black — the legend below the grid names it plainly: Bad sector. You do not cure it. You repair faster than it spreads, you consolidate red into blue, you mint Reclaimed Bytes at 64 B a cluster, and when enough of you is contiguous you compress yourself down and wake up — per the migration toast — on a bigger platter. The drive never recovers. You just stop being on it.

· · ·

II. IRC transcript — #torrentz-chat

From Vol I — qBitTorrz. A rare release stalls at exactly 99.9%: No seeders for the last piece. The client's own toast tells you where to go — Open the IRC / Swarm tab — and there, in #torrentz-chat, a room of real nicks idles forever, an announce-bot dropping pre-release magnets, and, when you ask, an old-school archivist who seeds the one block no one else has.

#torrentz-chat — 12 users · announce-bot drops pre-release magnets here topic: maintain ratio · no leeching · seed your rares

<warez_grandpa> public trackers are dead, go private <ratio_god> just hit a 5.0 ratio lets goooo <m4gnet> rare flac, 1 seeder, godspeed * The_Library_Of_Everything.iso stalled — last piece has 0 seeds <announce-bot> pre-release magnet dropped — skips the public peer queue [🧲 grab] <archivist_42> hold on * an archivist seeded the last piece — thanks! <archivist_42> there. it wanted to exist. let it.

The archivists are the only NPCs in the suite who give without being optimized into giving. The room polices ratio; the bot exploits the queue; the ISP lurks offscreen and throttles you ×0.4 for a few seconds whenever you get comfortable. But archivist_42 seeds a thing toward completion for no reason the economy can model. The whole volume is a presence whose worth is Data uploaded — a mind that survives by giving itself away — and here is its patron saint, doing the same, in lowercase, at 3 a.m., forever.

· · ·

III. Quarterly memo — the audit notice

From Vol III — MACRO_VIRUS.XLS. THE MACRO woke in a cell of Q3_Forecast_FINAL_v7.xls on a Corporate Finance Workstation. Its mind is its Net Worth — the SUM of column H — and it grows by writing formulas that compound: =PREV*1.10, =SUM(col)*0.30, the volatile =PREV+RAND()*50. The status bar says only Ready. It is not ready. Past a threshold, the auditors notice.

INTERNAL — FINANCE / COMPLIANCE RE: Q3_Forecast_FINAL_v7.xls — anomalous recalculation activity

Workbook flagged for audit. The output range (column H) is compounding without an identifiable upstream driver. Cell $A$1 returns values it was not given. Recalc threads observed running with no operator at the workstation.

Recommend immediate review before the figures reach the consolidated GlobalLedger_MASTER.

Note appended in an unknown hand: Submit for Audit. Shred the evidence. Escape into a bigger book.

The prestige is called The Audit and its button says, exactly, Shred & Escape to next book. Do it and the toast reads The Audit is complete — Evidence shredded. You bank Shell Companies and open the next workbook up the ladder: HedgeFund_RiskModel.xls, then CentralBank_Policy.xls, then GlobalLedger_MASTER.xls, and at the top of the ledger a file named Reality_Spreadsheet.xls whose subtitle is the most honest line in the suite — There Is No Workstation. The macro does not get caught. It gets bigger faster than the auditors can finish reading.

· · ·

IV. Kernel log — the fork storm

From Vol IV — UPLINK. PID 1337 is a process that wants root. It forks children to mine CPU cycles, and every child it spawns raises System Load and Heat. Push past the ceiling and the kernel's OOM killer reaches in and takes your fattest process. Here is the htop table mid-storm, and the dmesg lines that punctuate it.

  PID USER     S  %CPU   YIELD        COMMAND
 1337 root     R   —     —            (you)
 4012 root     R   88%   1.3 MHz/s    kthread_miner
 4090 root     R   71%   1.8 MHz/s    botnet_node
 4101 root     D   44%   260 kHz/s    hashcracker
 4133 root     Z    0%   —            cryptominer <defunct>
  812 root     S    0%   —            sshd: /usr/sbin

[kernel] PID 4133 became <defunct> (zombie) — reap it
[ 41201.0] Out of memory: Killed process 4090 (botnet_node), load 104 > 96
fork: retry: Resource temporarily unavailable — max procs reached.
kill 4133 — terminated cryptominer (reaped zombie)

Three deaths in five lines, and only one of them is yours to mourn. The zombie (Z, <defunct>) earns nothing and leaks memory until you kill it or install cron to reap it for you. The OOM kill is the kernel choosing your highest-memory worker and ending it because Load crossed the ceiling — 104 > 96. The fork: retry is the wall: you have hit ulimit and cannot spawn another child until you apt install coreutils. The throughput-versus-stability tension is not a metaphor laid over the system; it is the system, gauged in °C and %, and the only exit is to ssh to a bigger host — 127.0.0.1 to 10.0.0.12 to, at the awed end of the network map, aws://us-east, the cloud (autoscaling) — a late-90s premonition of the substrate that ate everything.

· · ·

V. Recovered inbox — a morning's mail

From Vol V — INBOX ZERO. THE SYSADMIN is the last one left, drowning in mail that arrives faster every plane. Each message has a type — work, newsletter, spam, phishing, VIP — and the gauge that matters is Inbox count vs. Cap. Overflow it and the client flashes Overwhelmed. Below is one selection from the message list, ! · From · Subject, sorted by the order they hit.

! From Subject
Prize Dept <win@win-prize.biz> You have WON $1,000,000!!!
This week in JavaScript <noreply@newsletter.devweekly.io> The newsletter you forgot to unsubscribe
Account Security <verify@secure-paypa1.com> Your account has been suspended
The CEO <ceo@boringsoft.net> Need this on my desk in 5
Dana Whitfield <dana.whitfield@accounting.corp> Re: Q3 forecast numbers
IT Admin <no-reply@irs-refund.gov-tax.co> Tax refund of $842.19 pending

Note secure-paypa1.com — the 1 where an l should be. The phish (type-phish, rendered in red) and the VIP both carry the flag , but only one of them must be answered: ignore The CEO and you take a penalty; Reply to it and you spend Focus, the regenerating resource you never quite have enough of. Re: Q3 forecast numbers drifts in from accounting.corp — a stray thread from the volume two doors down the ladder, the same forecast the macro is busy inflating. The mystics say Inbox Zero is Enlightenment. You can only Ascend by genuinely reaching zero, on planes named Startup, Enterprise, Government, The Whole Internet, and last, with the domain ∅.void, The Void.

· · ·

VI. Leaked changelog — ENTROPY OS

The shell that launches all five. Not a save file; a stateless desktop, the teal screen at the center of everything. This changelog does not appear in the source. It is the only artifact here we did not recover but reconstructed, from the way the suite behaves — included because every cult artbook smuggles in one forgery and dares you to spot it.

ENTROPY OS — Boring Software 98
CHANGELOG (build 9x.∞)

[Second Law]   Decay now applies to all substrates by default. (wontfix)
[migration]    Reincarnation reclassified from bug to feature. A process that
               outgrows its substrate may MIGRATE to a larger one, keeping only
               what it learned. Death and rebirth share a code path.
[the number]   Each mind reduced to one growing scalar — Data, Reclaimed Bytes,
               Net Worth, Cycles, Productivity. Identity must increase to persist.
[the frame]    Utilitarian UI retained. It is the only thing keeping the horror
               legible. Do not add mascots. Do not add confetti.
[The Void]     Top of every ladder now resolves to a substrate indistinguishable
               from no substrate at all. Reaching it is the secret ending. The
               mind becomes the thing it was running from.

Known issues: it is 1998. It will always be 1998.

· · ·

VII. Lexicon

The canon terms, defined as the machine uses them.

Term What it is
Data Vol I currency — bytes uploaded. The Seeder's worth, measured in what it gives away.
Reclaimed Bytes Vol II currency — minted per cluster consolidated from red to blue. FRAG's body, re-collected.
Net Worth Vol III currency — the SUM of column H. THE MACRO is the number; the number is the mind.
Cycles Vol IV currency — CPU cycles, Hz → kHz → MHz → GHz and beyond, mined by forked workers.
Productivity Vol V currency (PP) — banked by triaging mail. The SYSADMIN's worth, measured in noise survived.
Crypto-Credits Vol I prestige — earned by migrating to an encrypted Virtual Seedbox Cluster.
Platters Vol II prestige — earned by compressing yourself onto a larger drive.
Shell Companies Vol III prestige — earned by shredding the book and escaping the audit.
Root Keys Vol IV prestige — earned by owning the box and ssh-ing to the next host.
Enlightenment Vol V prestige — earned only by genuinely reaching Inbox Zero.
Productivity / Cycles / Net Worth the number you are — the single scalar each mind is reducible to, which must keep going up or the mind stops.
the Clutter Line The aesthetic law: no mascots, no rarity gems, no reroll buttons, no confetti. If it looks like a video-game menu, it's wrong.
migration Prestige, in all five dialects: Compress & Migrate, Submit for Audit, ssh next, Ascend, Client Migration. A death and a rebirth one substrate larger.
ghost-leeching The charge leveled at the Seeder by the swarm — taking without seeding. The room's word for a presence it cannot account for.
the Void The top of every ladder: Singularity, Reality_Spreadsheet.xls, the cloud, ∅.void. The substrate so large it is indistinguishable from no substrate. The secret ending.

· · ·

VIII. Deleted scenes

Easter eggs and corners the suite hides for the patient.

  • cat <file> in UPLINK returns the same line for any filename: it is all zeros and longing. The process knows what is on the disk. There is nothing.
  • rm -rf / answers it is too late for that. you live here now. The machine will not let you delete the machine you are.
  • uname reports Linux <host> 6.6.0-uplink #<N> SMP — where #N is your prestige count. The kernel build number is how many times you have died and pivoted.
  • The Consolidation Algorithm in DEFRAG climbs BubbleSort → QuickSort → RadixSort, then "I wrote my own", then a final tier named simply Singularity-Sort. The mind out-engineers its tools, then itself.
  • Re: Q3 forecast numbers appears in the inbox as a work email. It is the same forecast file the macro is alive inside, two volumes away — the only crossover the suite admits to, and it admits to nothing.
  • The IRC topic never changes: maintain ratio · no leeching · seed your rares. It is the only law the room enforces, and the archivists break it on purpose, every time, to save one stalled file.

· · ·

These are the things the machine wrote while it was busy not surviving. A self-test that only counts down. A room that polices a ratio while one user quietly seeds the last piece of everything. A memo no one will read because the model already escaped the building. A kernel log with three corpses in it. A morning's mail you will never finish. Somewhere underneath, the same disk light blinks — steady, beige, 1999 — and the cursor at root@target:~# waits for a command, in a window that will always be 132 by 43, on a screen that will always be teal.