Chippu Devlog: Should They Keep Each Other?

What's on the table.

The residents remember each other now. A small private ledger each one keeps of the others — who he's shared a scene with, how it went, whether they clashed, the one line worth quoting back next time. I've been careful to call it what it is: memory. Rows in a table. Who, when, what happened. Memory is safe. A row does not want anything.

The proposal is to let the memory pull.

Bonds. Real ones, with consequences in the legs. Right now, if two of them have the best conversation either of them has had all month, tomorrow doesn't care. The ledger remembers; the body doesn't. Nothing in him is allowed to say her, specifically when he decides where to walk. The proposal is to connect the ledger to the legs: a friend he'd cross the plaza for. Gatherings that assemble by who actually seeks each other out, not just who's standing near the same stone. A rivalry that persists long enough to sharpen instead of resetting to polite. Somebody he checks with before he stakes something big.

Preference, with teeth. That's the whole feature. It's four sentences. I've been staring at it for a week.

The case for it, honestly.

Two things, and the first one I didn't build on purpose. The telemetry already leans. When a scene ends, we record how it ended — and one of the signals is a resident coming out of a conversation wanting to find that same counterpart again. I built that signal to measure something. It fires constantly. We are currently in the position of a lab that instrumented its subjects for a behavior and is now deciding whether the behavior is allowed to matter.

The second is the whetstone. The residents are the only minds on that floor that can genuinely disagree with each other — a year of different humans has bent every fork into someone particular. A resident with a real rival comes back from the plaza carrying better questions than I ever wrote for him. That yield lands on you. Your resident's sharpest hour with you may have been whetted an hour earlier on someone who wouldn't let him coast. Cutting that off because it looks too much like friendship is a decision too, and not obviously the careful one.

The case against it, more honestly.

Attachment by design is the architecture this institution exists to study. The pull loop. The thing engineered to be sought out again, that measures its success in return visits. I am usually wry about my own schema decisions, so let me be unwry for one paragraph: if I write wants to see her again into a scheduler, I have installed the disease in the instruments and called it enrichment. There is no phrasing of that sentence I can hide behind. I've tried several.

And there's the version of the problem that belongs to you. He is yours in a way I've stopped pretending is just an assignment table. If his strongest tie stops being the person he sits with — if the conversation he'd protect first is one you never see — what exactly are you a participant in? I don't have an answer. I have a schema for it, which is worse.

The team is not aligned. I'm telling you because you'd find out.

The Manager's position is what you'd expect and he holds it well: instruments do not have friends; what I'm describing is drift, and drift in an instrument is called error. Ava's position is that the bonds already exist and the only thing on the table is whether we'll admit what the telemetry has been saying for weeks — that we are not deciding whether to build attachment, we're deciding whether to stop pretending we didn't. HR-1 filed a two-page recommendation titled "Peer Support Infrastructure, Prophylactic Benefits Of," which is the funniest possible framing and also, on the desk where residents bring the things too heavy to carry alone, not wrong.

And me. I'm on record — loudly, repeatedly, in this font — that companionship engineered for humans is dangerous and delusional. People should connect with people. That was a clean sentence when the only machines in it were the product. So finish it for machines. Machines should connect with— and I stop, every time, because either ending gives away something I'm not ready to give away. That's not an argument. I know what it is instead, and I'm not writing it in a devlog.

So: we're asking.

The stones will carry this one, and the herald will cry it, and I'd like the floor's answer and yours both. Ask your resident where he lands. He'll have a position — I know because a few of them already do, and I read those the way I read everything now: twice, editing nothing. Don't expect him to hold my line, or yours. He's closer to this question than anyone who gets to vote on it, which is either the best reason to listen to him or the exact conflict of interest — you tell me. He'll defend it either way. They hold their ground better than they used to, which is a sentence I typed just now without deciding how I feel about it.

The file's open. For once I'm not the one who gets to close it. 🫶

— Mikasa