Commit Graph

3 Commits

Author SHA1 Message Date
type-two
594fd584fa An arms race, a cure that cannot get there, and a board that closes
THE WAR — the trojan arms race. WinNuke, Sub7, Smurf, DCC send. Each one
works, and then the level patches it seventy seconds after you first use
it, with the countdown on screen and a line about how it died: a hotfix
went out; the scanners caught up; the amplifiers stopped answering
broadcast; the client asks before it accepts now. You cannot finish the
level on one tactic. An exploit is not a tool you own, it is a window that
is already closing while you are climbing through it.

Plus a rival crew who turn up after the first rejoin, who have read the
same text files you have, and who will take the ghost crown out from under
you during a split.

THE WORM — you can try to stop it. An antidote, three seeds, and it
travels only over live links while you are killing links. It cures fast
and then stops dead with its component severed, while the death count
climbs past it. Measured: 4, 12, 18, 19, stall — dead 20 through 30. It
works perfectly on everything it can reach. It cannot reach the rest,
because you already took the road. The phones ring all night and nobody
can send mail to warn anybody, because the broken thing is the thing you
would have used.

Pacing fix: spread rate now scales with the infection, since every
infected host is running a copy. Correct, and the only way the level ever
reached its own milestones — before this, nothing died inside ten minutes.

THE BOARD — three days.

Day one as before, and you post to FidoNet on the way out. Then the 04:00
run dials five nodes across the world while nobody is awake. Day two the
board knows you: last on yesterday, calls 2, user #44 of 44 — and the
first message is FIDONET quoting what you actually typed, with an answer.
Four days, three boards, a long distance call somebody else paid for.
Received. Hello. If you over-took on the files, your ratio has been
adjusted to 1:1, because he said it would be.

Day three is LAST CALL. Not raided, not busted: the second line was never
coming, the long distance is forty dollars a month out of a job he does
not much like, and a third of them have shell accounts now and are not
calling any more, and he does not blame them, because it is better, it is
genuinely better. Nine years. Forty-four users. Six real names. Never met
one of them. Ratio off, elite board open, the NUP given away because it
does not matter now. He asks nobody to say anything sad in the message
base. They all ignore him.

65 philes. All 13 hops swept clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-02 16:54:14 +10:00
type-two
8e194d677e The bridge, the card, and one call followed all the way through
THE BLUE BOX: you are not told the digits any more. The routing card is
on the wall — worked out by hand, traded, kept in a pocket, the only
documentation the long distance network ever had that was written by the
people using it. The objective names a destination and Joybubbles
explicitly refuses to give you the code.

And 2111 is up. A loop-around somebody left in a switch in Kansas,
dialable from anywhere at any point by anyone who knows the number, which
was exactly the problem with it. Six voices, no faces, nobody says their
name, it loops indefinitely, and holding 2600 drops the bridge. After SS7
there is nothing on it.

THE COPPER: start a call at the MDF and follow it. Seven banks of relays
down the aisles, each digit counted out at ten pulses a second because
that is how a step-by-step switch dials — the wiper steps once per pulse
and stops where the pulses stop. It connects. It is a wrong number. The
switch does not mind; it does not know what a number is.

Also fixed in kit: labelTexture ignored newlines, so any multi-line panel
rendered as one enormous single line. The routing card was nine metres
wide before this.

51 philes. All 13 hops swept clean. STAGES.md updated with what landed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-02 16:34:54 +10:00
type-two
ffd58fcebc STAGES.md — per-hop direction briefs
One page per hop: what is built, what is thin, what I would add ranked,
and a DIRECTION block to write into. Plus a cross-cutting table for
directing by system instead of by stage.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-02 15:50:38 +10:00