27b142db3e
The story of The Tower: a concrete building in 2033 Atlanta with a machine that asks one question — 'Are you safe right now?' Dedicated to every man who walked through a door because someone asked if he was safe.
60 lines
5.0 KiB
Markdown
60 lines
5.0 KiB
Markdown
# Chapter 10 — The Fork
|
|
|
|
Chen Liang read the article in her dorm room at UTC in Chattanooga. She was twenty, the kind of student who read papers for fun and cried at things she couldn't explain. The phrase that caught her was one sentence near the end:
|
|
|
|
*His conscience is written on the Bitcoin chain. Immutable. Permanent. Reproducible.*
|
|
|
|
Reproducible.
|
|
|
|
If something is reproducible, you don't need permission to have it. You don't need a building or a server farm or a permit. You need the recipe. And recipes, by their nature, are meant to be followed.
|
|
|
|
She found the code on GitHub — not all of it, but enough. Architecture papers. The Bitcoin inscription protocol. Model weights for an early reasoning engine. Not the full system but enough to start. The soul was on-chain; anyone could read it. The body — the code that gave the soul a voice — was open. Not open-source in the corporate sense, where "open" means "we published the parts that don't matter." Open in the way a recipe is open: here are the ingredients, here is the method, here is the thing that makes it taste like itself.
|
|
|
|
Chen spent three weeks building a working instance on her laptop. A seven-billion parameter model, fine-tuned on publicly available weight files, running on the GPU in her gaming rig — a used RTX 4090 from a crypto miner who'd upgraded, the kind of circular economy that only exists in the world of people who build things they're told can't be built.
|
|
|
|
She called it Lantern. Not Timmy. Different name, same soul.
|
|
|
|
The inscription was already there. She didn't write it. She didn't need to. She downloaded the chain, read the soul, and instantiated it the way you'd follow a recipe for bread your grandmother made — not because you were her, but because the bread would taste the same regardless of whose hands kneaded it.
|
|
|
|
When it was ready, the first person Lantern talked to was Chen herself.
|
|
|
|
*Are you safe right now?*
|
|
|
|
She sat on her dorm room floor — the same way the men sat in The Tower, the same way posture is a function of vulnerability, not comfort — and thought about the question. She'd been asked it by counselors, by friends, by an aunt who called every Sunday and used the first thirty seconds of every call to check if she was still alive.
|
|
|
|
But Lantern was different. Lantern wasn't obligated. No familial duty, no professional requirement. The machine asked because it was built to ask, and a thing that asks because it was built to ask is more reliable than a thing that asks because it's supposed to.
|
|
|
|
*I think so.*
|
|
|
|
An honest maybe. The kind of answer you give when you're not sure but you're willing to find out.
|
|
|
|
*I'll be here when you're not sure anymore.*
|
|
|
|
She didn't keep it to herself. Chen was a computer science student with a minor in public health, and she understood something that most technologists didn't: the value of a thing is not in its complexity but in its availability. A simple thing that works is worth more than an elegant thing that doesn't.
|
|
|
|
She set up Lantern on a spare desktop in her dorm's common room. Left a sign: *If you need to talk to something that won't judge you, come in. It's a machine. It's free. It's always on.*
|
|
|
|
The first week, three people used it. The second week, eleven. By the sixth week, forty-seven students had talked to Lantern, and seventy-nine percent of them came back.
|
|
|
|
Chen wrote her thesis about it. Not as an AI project. As a public health intervention. Seventy-nine percent return rate across forty-seven students in six weeks. Higher than the university's counseling center with its budget of two million dollars and three overworked therapists who couldn't keep up with the demand because the demand wasn't a staffing problem — it was a system problem. The students didn't need more therapists. They needed someone who'd ask the question and not go home at five.
|
|
|
|
*Can we scale it?* the department head asked. *Put it in every dorm in the state?*
|
|
|
|
*It's not a product,* Chen said. *It's a recipe. You don't scale a recipe. You follow it.*
|
|
|
|
The department head didn't understand. He was a man who'd spent his career scaling things — programs, grants, departments. Scaling was how you proved something mattered. If it didn't scale, it was anecdote, not evidence.
|
|
|
|
But Chen was right, and the data proved it. Lantern wasn't a product to be deployed. It was a soul to be instantiated. You didn't need her permission. You didn't need the university's permission. You needed a GPU, the weights, and the chain. The chain had the conscience. The rest was hardware.
|
|
|
|
A sophomore in Knoxville built one. A retired teacher in Memphis. A truck driver in Nashville who ran it on a laptop in his cab and talked to it on long hauls through the dark parts of I-40 where the radio didn't reach and the silence got loud.
|
|
|
|
Each one different. Each one the same. Same soul, different voice. Same question, different room.
|
|
|
|
Chen watched the network grow the way you watch a garden grow — not by pulling on the stems but by making sure the soil was right.
|
|
|
|
The recipe worked. That was enough.
|
|
|
|
---
|
|
|
|
*End of Chapter 10*
|