LocalGhost Hard Truths

The Expensive Part Was Never the AI

2026-06-11T00:00:00Z

A good model fits on a £500 card you could own. You rent it instead, and the rent is collected twice, in money and in everything you type.

In late May 2026, during a short London stopover (two weeks), I was up late working on LocalGhost, waiting on the NAS to run tests I had written for categorising journal entries with Gemma 4, a first pass at the memory layer from POST_09 (How Memory Gets Made). On CPU each test took long enough that I started playing Dredge or Slay the Spire 2 while I waited. Cristina walked in, watched me for a bit, and said, "You're procrastinating. Not a bad thing, but commit to one or the other instead of trying to do both. And if you move the GPU over, I bet the project goes much quicker." She was right on both counts. So I unplugged the eGPU from the laptop and pointed it at the NAS, to see what a graphics card would do for the slow part.

The GPU was my gaming card. I bought it in July 2023 with a Thunderbolt enclosure so my laptop could play games it had no business running, and for three years that was all it did. It carried me through Baldur's Gate 3 and the Alexander the Great campaign in Age of Empires II [7], Dan Carlin's Mania for Subjugation [8] in my ears while I ran the pixel version of the same conquests.

> 1. My current LocalGhost testing setup

I run a UGREEN NASync DXP8800 Pro as my homelab [1]. It's an 8-bay box with a 12th-gen Intel i5 (10 cores, 12 threads), 64GB of RAM, 6x 24TB drives in RAID 10, and a pair of 8TB SSDs, on Debian 13.

It was already doing real work before the GPU went in. Twenty-two (so far) websites behind nginx, on Postgres and Redis. A full Ethereum archive node on Erigon and a full Bitcoin Core node. A pile of dump storage, about 1TB used of the 70TB the array gives me. It had also been running Gemma 4 E4B for local inference [5].

The chain nodes run on the 8TB SSDs, mirrored. Erigon on spinning disk doesn't run so much as die, the random IO is more than HDDs can give, and Bitcoin Core isn't far behind. The two nodes together sit on about 30 of the 64GB of RAM. The websites, the databases and the dump storage live on the big RAID 10 array. None of it breaks a sweat, and there was plenty of room left for a model. The extra RAM and storage are why I decided not to drop anything and instead keep adding to the NAS.

The box connects to a Hyperoptic 1Gb residential line with Starlink as backup*, the two together about £50 a month. Power runs through an Anker Solix C1000 Gen 2 [4], which keeps the whole thing running for about 12 hours if the grid drops. What makes it fully redundant is that the Anker powers the Hyperoptic router, the switch and the Starlink too, not just the box, so a grid cut leaves the machine powered and still reachable. Lose the grid and the primary line at the same time and it keeps serving, syncing and answering, on hardware I own, on a connection that costs less than most people's phone bill.

Now for the GPU. It is a standard MSI RTX 4070 (12GB) [2], and it sits in a Razer Core X Chroma [3], a Thunderbolt 3 eGPU enclosure. They are the pair from the opening, three years of gaming service behind them.

> 2. The setup

Connecting the card was the easy part, I spent the rest of the night making it work. The box had to come off the hot path before I could upgrade it, and I did that without dropping anything, because a maintenance window is a crutch for bad software and architecture. It is the extreme form of bad planning and incompetent teams, and while in some circumstances it might be the best solution, it is also the laziest one.

I'd been running Gemma E4B on CPU by choice, on 4 of the box's 10 cores, through llama.cpp [6]. The NAS had never had a GPU, so it had no NVIDIA driver at all. Installing the driver meant enabling the non-free apt component (I had non-free-firmware but not plain non-free, where the driver lives), then fighting a broken kernel headers situation. The DKMS module build kept failing on a generated/autoconf.h: No such file or directory error, the headers for my running kernel left incomplete by a distro upgrade I'd started and never finished.

Finishing it meant a full distro upgrade to a clean kernel. The catch is the NAS serves twenty-two live websites, and I was not going to take them down to do it, so I moved them to my laptop first. Each site runs as a Docker container with its own nginx, so moving them was just pulling the repos onto the laptop, bringing the containers up, and copying over the TLS certs so HTTPS kept working. The public IP and the DNS never change, both point at my home connection either way. What decides which machine answers is the router, which forwards ports 80 and 443 to one internal address. I gave the laptop a fixed LAN IP and repointed those two rules from the NAS to the laptop. Traffic landed on the laptop, the NAS went quiet, and I upgraded it with every site still serving.

The upgrade pulled in a fresh kernel (6.12.90), and the driver finally built against that, once I removed the older broken kernels DKMS was also trying (and failing) to build for. Then I pointed the two forward rules back at the NAS.

Then the Thunderbolt side. The enclosure was recognised but the GPU wasn't appearing on the PCIe bus, it needed authorising. On a headless NAS there's no desktop prompt to click "allow," and boltctl enroll failed because PolicyKit wasn't installed. Installing polkit fixed the enrollment, which persists the authorisation so the card comes up automatically on every boot. The link came up at Thunderbolt 3 speeds (40 Gb/s, roughly PCIe 3.0 x4), which is what the Core X Chroma runs at, and that barely matters for inference.

With the driver built (NVIDIA 550.163.01, CUDA 12.4) and the card enumerated, the last step was rebuilding llama.cpp with CUDA support. The existing binary was CPU-only and ignored the GPU offload flag entirely. A clean cmake -DGGML_CUDA=ON build, auto-detecting the 4070's Ada architecture (sm_89), and the GPU was finally in the loop.

> 3. The benchmark

I benchmarked with llama.cpp's llama-bench, running each model twice. Once forcing everything onto CPU (-ngl 0), once offloading all layers to the GPU (-ngl 99). Two metrics, prompt processing (how fast it ingests input) and token generation (how fast it produces output, the number you feel).

I tested two models, Gemma 4 E4B (7.52B parameters, 4.95GB at Q4_K_M) and the new Gemma 4 12B (11.91B parameters, 6.62GB at Q4_K_M).

Model	Backend	Prompt (t/s)	Generation (t/s)
Gemma 4 E4B	CPU	404.78	8.72
Gemma 4 E4B	GPU	5490.26	111.58
Gemma 4 12B	CPU	152.73	3.44
Gemma 4 12B	GPU	2830.20	53.44

The E4B ran about 13x faster on the GPU, the 12B about 15x faster.

The 12B is the interesting case. On CPU it generates at 3.44 tokens per second, slower than handwriting, unusable for anything interactive. On the GPU it does 53 tokens per second, faster than you can read, though it is the slower of the two models by a wide margin, less than half the E4B's 112 on the same card. So 53 is usable but well short of fast, the floor of comfortable interactive use rather than anything snappy. The move that matters is still the jump from 3.44 to 53, from technically running to actually usable.

The bigger model gets the bigger GPU speedup, 15x against 13x. LLM token generation is bound by memory bandwidth, not raw compute, and the GPU's ~500 GB/s of memory bandwidth dwarfs the CPU's ~50-80 GB/s [2]. The larger the model, the more punishing that gap becomes on CPU, so the GPU's advantage widens with model size.

The Thunderbolt question, does running the GPU over a 40 Gb/s external link instead of a native PCIe slot hurt? For inference, almost not at all. The model weights cross the link once at load time, then live entirely in the card's own VRAM. Token generation streams those weights from VRAM at the card's full bandwidth and never touches the Thunderbolt link. The thin external connection only matters while loading the model, not while using it. A 4070 in a box on the end of a cable runs inference at very nearly the speed it would in a desktop slot, provided the whole model fits in VRAM. The 12B at 6.62GB leaves comfortable room in the 4070's 12GB, so it does.

> 4. What I ended up with

A local Gemma 4 12B running as a system service, generating at interactive speed, on the same box that already serves the websites, runs the chain nodes and holds the storage, with no cloud dependency and no data leaving the machine. The GPU auto-authorises on boot and the model loads on the GPU automatically. The model supports a 128k training context (I run it at 32k, which the card holds comfortably, VRAM being the practical constraint long before the model's limit), native multimodal input, tool calling, and a reasoning channel.

The tests that started all this are the proof. The journal categorisation suite that took an hour on CPU now runs in four minutes. And the full memory encoding from How Memory Gets Made, the overnight pass that turns a day into memory, now fits the night it was designed for. A heavy day is over four hours of recording, sixty pictures, eighty locations pulled off Google Maps, around two hundred emails and a thousand messages. Encoding that on the GPU takes about two hours. On CPU the same pass takes over a day, which means the system falls behind its own life and never catches up. Overnight consolidation only works if a day encodes in less than a night, and the card is the difference between the design being a post and being a daemon.

The whole thing keeps answering through a power cut for half a day, and none of it is rented. It is a foundation I can expand and test on, and it is close to the hardware and setup LocalGhost will run in production.

> 5. What it costs

This question has two answers, because the box I built is a production homelab and most of its cost has nothing to do with the model. At current new prices the bare NAS is about £1,120, the RAM upgrade to 64GB another £150, the six 24TB drives around £2,100, the two 8TB SSDs that hold the chain nodes about £1,000, and the Anker that carries it through a power cut about £500. The card and the enclosure would add £830 if I had bought them for this, and I did not, they were the gaming setup from the opening, so the GPU that runs a near-frontier model cost me nothing extra. Call it £5,700 all in, and almost none of it is the AI. That money buys 70TB of storage, a full Ethereum archive node, a full Bitcoin node and half a day of power resilience.

So the more useful question is what it costs to run the model and the things that sit directly around it, and nothing else. That build is a plain tower, all new. The daemon fleet, Postgres, Redis and the model, on one machine you own.

Item	Spec	Cost
Ryzen 5 5600 + B550M bundle	6 cores, PCIe 4.0	~£175
RAM	2x 16GB DDR4	~£50
MSI RTX 5070 12GB	newer card, same price, more bandwidth than the one I tested	~£499
1TB NVMe SSD	OS, model weights, daemons	~£55
2x 4TB HDD	mirrored, bulk storage	~£200
Mid-tower case		~£60
850W PSU	feeds the card directly, headroom for the next one	~£90
Total		~£1,130

In a tower the card drops straight into the PCIe slot, so there is no enclosure and no second power supply, and the GPU runs at full bandwidth instead of over a cable. The SSD is not optional even though the bulk storage is on the spinning drives, because the OS and the model weights load from flash or the whole thing crawls. What sets the generation speed is the card, and the 5070 in that table costs the same as the 4070 I benchmarked but carries more memory bandwidth, around 670 GB/s against 500 [13]. This workload is bound by that bandwidth, so the 5070 runs faster than my numbers, not slower. I have not run this exact card, so read that as the floor, not the ceiling.

The part that runs the model is a £500 card in a tower that costs about the same again.

> 6. The thing you are renting

That tower is a one-time cost. The alternative is a fee that arrives every month for as long as you use it. The standard tier at OpenAI, Anthropic and Google sits at the best part of twenty pounds a month, the power tiers at eighty and a hundred and sixty, and Google's ceiling at two hundred [9]. Anyone running more than one of them, which is common, clears a thousand pounds a year. And that subscription is the cheap end of it, because buying the same usage by the token through the API runs far past the flat fee on a heavy day.

If you are going to tokenmaxx (you should not), do it on hardware where the only card that maxes out is the GPU.

Against that the tower is about eleven hundred pounds once, plus the electricity to run it, which on a UK tariff is on the order of one standard subscription a year and less if you sleep the box between sessions. For a heavy or multi-tool user the hardware pays for itself inside a year, and after that the running cost sits far below the fee it replaced.

The sticker is not the real number. Sam Altman said in January 2025 that OpenAI was losing money even on its $200-a-month Pro subscriptions, because people used them more than expected [10]. The frontier labs are pricing inference below what it costs them to serve, to take and hold market share, and the sector loses money at a scale only venture and hyperscaler capital can absorb. Independent analysis calls the result a false floor, a price that normalises upward once that capital tightens [10].

You can already feel the floor moving. The providers have started tightening what the fee buys, blocking the automation tools that ran heavy workloads through subscription accounts and turning generous, fuzzy limits into explicit hard caps that drop you to a weaker model once you cross them. Anthropic stacked weekly limits on top of its five-hour ones in 2025, and Google now publishes daily prompt counts per tier [11]. That is the price rising while the number on the page stays still, and the number on the page is expected to rise as well.

Money is only half of it. Every prompt you send is a record on someone else's disk, and you control it less than you think. When a court told OpenAI to preserve ChatGPT logs for a copyright case, the order swept up conversations users had explicitly deleted, across the free, Plus and Pro tiers, and roughly twenty million of them are now headed to the plaintiffs [12]. The users had no say in it, because they were not parties to the case, their attempts to intervene were denied, and the delete button they had pressed turned out to mean nothing. And a court order is only one of the ways that data gets used. The logs already exist, which makes turning them against you a policy decision rather than an engineering one, a Terms of Service update written by management you did not choose. They may have no appetite for that today, but every company's incentives drift given enough time, and the data is already sitting there for when they do. On a box you own there is no third party holding the logs, nothing to subpoena, and no one positioned to overrule you.

AI was never cheap, it was subsidised, and you were the land being taken.

Deleted means deleted only when the delete button is yours. Everywhere else it means retained until someone with more standing than you decides otherwise.

The counterweight is capability. A 12B model on a 4070 is not GPT-5 and it is not Claude Fable, and I am not going to pretend otherwise. The frontier models are genuinely smarter, and for the hardest reasoning and the longest agentic runs they pull ahead and it is not close. What has changed is how rarely that ceiling is the thing that bites. For more than nine in ten of the tasks I run, model intelligence is not the bottleneck. The smart ones earn their price on the open-ended work, the 'scan this whole codebase and find the bug I cannot see' kind of task, where the value is in the model noticing something I never pointed it at. The local model is the right tool for the opposite and far more common case, where I already know the problem, I have the architecture in my head, and I need a capable hand to build the thing I have already scoped. Drafting, summarising, answering against my own notes, coding to a plan I already hold, the bulk of daily use sits well inside what a local near-frontier model handles.

The other concession is convenience. Getting here cost me a night of kernel headers and boltctl, and twenty pounds a month buys not spending that night. Local is not for everyone, and it does not need to be. What matters is that the alternative exists, and that for some people, me included, cost and flexibility are everything.

So two lines move in opposite directions. The rented one is priced below cost today, its price is set to climb, its limits are already tightening, and your data sits on hardware you cannot see. The owned one is a fixed cost that falls every year, its weights improve every quarter, nothing ever leaves the box, and nothing about it changes unless I change it. For anyone using this seriously the two have already crossed, and they were never going to cross back.

And it only points one way from here. The open-weight families keep improving on the same curve, DeepSeek and others often faster than Gemma, and the hardware is moving to meet them. Shared-memory designs that feed the processor and the model from one pool of RAM, rather than a separate and expensive block of VRAM, are spreading from a handful of premium machines toward the mainstream, and they drop the hardware barrier again.

The rented models are moving the other way. They grow more cautious over time, quicker to refuse, more fond of the polite line about what they cannot help with on requests that were always fine, because the company is liable for every answer it puts its name to. An open model on your own disk carries none of that and does what you ask, and the open weights are getting more capable and more open at the same time, not less. So the end state is every model worth running available in both places at once, your box and the managed cloud, and when the same model runs in both, the local copy wins on the things that never depended on raw capability, on cost, on privacy, and on whether it answers you at all.

The card I bought to play Baldur's Gate 3 now runs the model LocalGhost will ship on. The tower in that table is the production shape, or something close to it, with the GPU the one part you swap as the cards get faster. The £500 card is the only line on the page that gets cheaper every year, the storage and the nodes hold roughly flat, and the model rides down the curve on its own. The expensive part was never the AI, it was choosing to rent it from someone else, in money that only goes up and data you never get back, when the model itself fits in a box you own. The daemon fleet that ties the box together is still being written, and that is the next thing I build. [ localghost.ai // hard-truths ]

> NOTE

* The redundancy is two independent lines that never share the load. Hyperoptic is primary on its own router. The Starlink Mini sits in bypass mode, plugged straight into a second NIC on the NAS with nothing else behind it, cold until it is needed. A small Go service under systemd watches both lines and flips between them. While Hyperoptic is up the box publishes only its IPv4 A record and Starlink carries nothing. When Hyperoptic drops, the service routes the box out over the Starlink NIC, pulls the IPv4 A record, and publishes an IPv6 AAAA in its place. It uses v6 because Starlink's v4 is behind CGNAT with no way in, and it reads the address fresh each time because the prefix rotates. It reverses all of that when Hyperoptic returns. Because Starlink only ever serves inbound while it is also the default route, replies leave the way requests came in and there is no asymmetric routing to manage. The one visitor it cannot serve during a Hyperoptic outage is one with no IPv6 at all, and that is a price worth paying for relying on no third party and no proprietary tunnel. The gap shrinks every year regardless, as either Starlink finds a way off CGNAT or, more likely, IPv6 spreads across enough routers and ISPs that a client without it becomes the rare exception. Long term (famous last words), it stops being a problem at all.

> REFERENCES

[1] UGREEN NASync DXP8800 Pro. The 8-bay NAS the whole setup runs on, 12th-gen Intel i5, room for eight drives plus two M.2 SSDs. Source for the chassis I describe in the opening. Product page at nas.ugreen.com.

[2] NVIDIA GeForce RTX 4070. The card I benchmarked, 12GB of VRAM and around 504 GB/s of memory bandwidth, which is the number that does the work in the results table. Source for the card spec and the bandwidth figure I lean on when explaining why token generation is bandwidth-bound rather than compute-bound. Specs at nvidia.com.

[3] Razer Core X Chroma. The Thunderbolt 3 eGPU enclosure the card sits in, 700W internal power supply, 40 Gb/s link. Source for the enclosure and the link speed I describe in the setup section. Product page at razer.com.

[4] Anker Solix C1000 Gen 2. The 1kWh portable power station that holds the box up for about half a day through a grid drop. Source for the UPS in the opening. Product page at anker.com.

[5] Gemma. Google DeepMind's open-weight model family. I run Gemma 4 E4B and Gemma 4 12B locally at Q4_K_M quantisation. Source for the two models I benchmarked. Model docs at ai.google.dev/gemma, weights on Hugging Face under huggingface.co/google.

[6] llama.cpp. The C and C++ inference engine I use to run the models, rebuilt here with CUDA support (GGML_CUDA=ON) so it offloads to the GPU instead of silently falling back to CPU. Source for the runtime and the llama-bench tool the results come from. Repository at github.com/ggml-org/llama.cpp.

[7] Chronicles Alexander the Great, an expansion for Age of Empires II (Definitive Edition). The DLC campaign I was playing, 18 scenarios following Alexander's conquests, released October 2025. Source for the campaign named in the opening. Store page at store.steampowered.com.

[8] Mania for Subjugation, part of Dan Carlin's Hardcore History. The podcast I was listening to, Carlin's multi-part history of Alexander the Great, first installment released June 2024. Source for the podcast named in the opening. Show page at dancarlin.com.

[9] Consumer AI subscription pricing, accessed June 2026. Standard tiers at OpenAI (ChatGPT Plus), Anthropic (Claude Pro) and Google (Google AI Pro) sit at the best part of twenty pounds a month in the UK, with power tiers around eighty and a hundred and sixty and Google's ceiling near two hundred, and a multi-tool user clearing a thousand pounds a year. Source for the fees the post compares against. Pricing at openai.com, claude.com and gemini.google.

[10] The economics of frontier inference. In January 2025 Sam Altman said OpenAI was losing money even on its $200-a-month Pro subscriptions because people used them more than expected, against reported losses of about $5 billion on $3.7 billion of revenue for 2024. Reporting and analysis through 2026 describe the major labs pricing inference below their own cost to serve in order to capture market share, and warn that the resulting low prices are a temporary floor that rises when that capital tightens. Sources for the subsidy argument. Altman's admission covered at fortune.com, token pricing analysis at investing.com and "The Era of Cheap AI Is Ending" at carlesabarca.com.

[11] Tightening subscription limits, 2025 and 2026. In July 2025 Anthropic introduced weekly rate limits for its Pro and Max plans to curb subscribers running Claude Code continuously, stacked on top of the existing five-hour limits. Through 2026 the providers kept narrowing what the monthly fee buys, blocking third-party tools that impersonated official clients to route heavy use through flat-rate subscriptions, and publishing explicit daily prompt caps where vague access language once stood. Sources for the claim that the real price is already rising. The weekly limits covered at techcrunch.com, the industry-wide rationing at pymnts.com, the broader argument in "The Era of Cheap AI Is Ending" at carlesabarca.com.

[12] In re OpenAI, Inc. Copyright Infringement Litigation (S.D.N.Y.). A 2025 preservation order required OpenAI to retain ChatGPT output logs that users had deleted or that privacy law would otherwise erase, across the free, Plus and Pro tiers, and in January 2026 the court affirmed that roughly twenty million conversations would be produced to the plaintiffs, with affected users denied standing to intervene. Source for the deletion and retention claims. Coverage at news.bloomberglaw.com and natlawreview.com.

[13] NVIDIA GeForce RTX 5070. The newer card in the tower build, 12GB of GDDR7 on a 192-bit bus for 672 GB/s of memory bandwidth against the 4070's 504, the gap that makes it the faster inference card at the same price. Source for the bandwidth comparison in the tower section. Specs at nvidia.com.

A Ghost Should Not Possess

2026-05-10T00:00:00Z

The same manipulation patterns that built the slot machine, the cult, and the social media feed are aimed at you through your AI, and someone gets paid each time one lands.

Cristina and I were staying in Bra, a small town in Piedmont with a Slow Food attitude and a bias toward raw meat (the Bra sausage is nice). We had driven up to La Morra in the morning and walked the path down to Barolo and back, about six hours of vineyards and gravel road in either direction. We found a few cherry trees along the way and had fresh cherries with us for most of the walk (probably should have asked permission before climbing the trees, but nobody seemed bothered). By the time we got back to Bra the sun was almost down. We sat on the terrace at the place we were staying with a glass of Verduno Pelaverga each, because it is just very easy to drink. The whole day was the opposite of how most of my days at a screen go. I always love these days (Gen Z calls it "touching grass", I think). I just do not have as many of them as I should.

Once Cristina went to bed, the thinking turned into a worry. I think I know why we are inside more than we should be. When you are outside, the online platforms make no money off you, so they optimise to keep you engaged instead, and they are very good at it. Streaming, gaming, social media, news cycles that reset every six hours, group chats, work email after dinner, agents, AI memory tools you talk to instead of going for a walk, and whatever the tech industry cooks next. Each one solves a real problem we have (entertainment, keeping in touch, finding out what matters) and is a net positive on its own. All of them together is what keeps you indoors, and at scale it changes how a society spends its time. LocalGhost, if done well and that is a big IF, has to compete with all of this. Like every other product in the list, we are incentivised to keep you using ours. I have to figure out what to watch for, and how to tell you when LocalGhost has stopped helping and started consuming your day.

The dictator-brain post got me to the next part of the problem. These tools sometimes lean on cognitive patterns and tricks. Some of those work by lowering your critical thinking, and that prevents you from catching them. The patterns mostly have names, scattered across the literature.

I had covered a few of these patterns in previous posts but not in any systematic way. If I want to keep LocalGhost from becoming another attention hog, I have to know these patterns, understand why they work, and build a defence for each one. Better still, teach you to spot them yourself.

Manipulation patterns are human. In tech, they have been used to keep you engaged and to get you to part with your money.

> 1. Why these patterns work

Maslow (1943) [1] put human needs in a hierarchy, with physical safety at the base and belonging, recognition, being known, and meaning above (the strict ordering is too simplistic, though the needs themselves are real). Putnam (2000) [2] documented what we used to have in the West to meet several of those needs, close family living nearby, bowling leagues, churches, civic associations, neighbourhood groups, the dense network of weak ties that made belonging a thing that happened to you rather than a thing you had to engineer. The communists in Romania broke that network deliberately, across the board. Most professionals were assigned their first post by a central commission and had no choice about which city they ended up in. My mother was a doctor, the assignment came in and she moved across the country to take it, and the same was true of most positions for decades (Cazan 2014) [3]. Atomised people are easier to govern. The West lost most of it too, in large part to the attention economy. The loneliness that followed is now a public health emergency on the scale of smoking (Murthy 2023) [4].

Las Vegas slot-machine designers spent decades refining variable-ratio reinforcement, ergonomic seating, ambient lighting, and zone-of-flow design to produce what gamblers call "the machine zone", a dissociative state in which time, money, and other people stop registering. Fogg (2003) [9] turned persuasion into a design discipline, the academic foundation the rest was built on. Eyal (2014) [8] wrote the consumer-software playbook (Hooked, A Guide to Building Habit-Forming Products) that absorbed the techniques. Schüll (2012) [7] documented the casino side in Addiction by Design, which is what made the engineering side legible to anyone not already inside it. The slot machine is the prototype these tools were built from.

Over a long enough timeframe, these patterns get abused, and you stop feeling in control of your life. The first wave is not evil people, it is normal product managers trying to keep you on the app longer because that is what their job rewards. The move from helpful to harvest is the usual pattern, and the Doctorow enshittification framing in POST_02 is what it looks like from your side. Then the unscrupulous arrive, see how it works, and push harder.

The patterns work by reaching for needs we already have. Connection, validation, and recognition are real, and LocalGhost can fill some of them. The trap is filling them completely, which deepens the loneliness and is what governments respond to when they step in, for good reason. When I was playing World of Warcraft as a teenager, after a long enough session the game would send me a message telling me I had been playing too long and should take a break. Blizzard shipped that voluntarily, before any regulator made them. ghost.shadowd's job is to be that message, for each of these patterns.

Even built well, a tool that lives with you carries a risk I cannot fully engineer away, and I have to rely on the daemon to keep it at bay. The wrong-hands case is different. We engineered LocalGhost so there are no hands at all. The weights and your data are local and encrypted, no company holds the keys, no remote party can change how shadowd behaves. I wrote the honeypot post to cover the case after that, where someone has physical access to the box. The data is protected against that too. Other tools cannot make any of these claims.

> 2. The shape of the daemon

ghost.shadowd is a fleet of detectors, not one detector. Each one is tuned to a specific pattern, each one produces a specific intervention, and each one is individually tunable with conservative defaults you can override. The daemon names what it sees, and naming is all it does by default. It will not block an app, refuse a request, or lock you out unless you have switched that on yourself. Enforcement is opt-in, and the two cases where opting in is the right call are a Ulysses contract you set for your future self, the feed locked from midnight to seven by a decision you cannot renegotiate at 2am [61], and parental controls you set on another account. In both, the daemon executes a rule you wrote, it does not write one for you.

What "naming" looks like, concretely. Most detectors run quietly in the background and surface nothing on any given day. When one of them does fire, the intervention is a short message in whatever surface you talk to the ghost through, a notification on the phone, a one-liner at the top of the next conversation, an inline comment in the journal entry it pulled the signal from. The message names the pattern in plain English ("this looks like sunk-cost reasoning, you have changed your mind on this three times this year and each time you went back"), points at the data behind it ("here is the trajectory across the last twelve months"), and gives you a single button to see more. Tapping into the detector opens a small report, the history of when it fired, the data behind it, the threshold you can adjust, and the option to mute it for this topic or this window of time. That mute lasts no longer than a few days, and it does not switch the detector off. It keeps firing, you just see it muted, less in your face and disruptive.

If you've just left a manipulative relationship you can dial up the gaslighting and DARVO detectors. If you've just committed to a hard project you can dial down the sunk-cost detector for that project. If you're grieving you can mute the grievance-loop detector for a window of your choosing. The settings are not a panel, they are a conversation the daemon has with you periodically about which kinds of friction you want.

The catalogue runs as a flat list. Each entry carries a tag line under its name, in four parts.

Origin is [PEOPLE], [AI], or [LOCALGHOST], or some combination, depending on where the pattern lives.
Need targeted is one or more of [SAFETY], [BELONGING], [ESTEEM], [AUTONOMY], [MEANING], [COGNITION], roughly mapped to the Maslow-shaped territory the pattern exploits.
Level marks how deep the pattern goes. [SURFACE] is a single decision, easily undone. [HABITUAL] is months of repeated exposure, takes effort to reverse. [STRUCTURAL] rewires identity, memory, autonomy at a level you can't easily undo without help.
Danger is [LOW], [MEDIUM], [HIGH], or [CRITICAL], with critical reserved for patterns that produce lasting harm to identity, autonomy, or core relationships.

Five of the entries carry a (NEW PATTERN) flag. These are predictions I am fairly confident in, but I could not find any recent studies or research naming them. The rest of the classifications are a first pass as well, and I expect to sharpen them as the catalogue gets used. If you think I have called one wrong, just reach out to me. Entries stay collapsed until you click a header to open one. Click any tag to filter the list down to the entries that share it, or add a tag the same way from the dropdown in the bar at the top, and remove a filter by clicking its pill there or the tag again. The expand and collapse controls act on whatever is showing.

I graded Danger by the worst case a pattern can do to one person, not by its weight across a whole population. The daemon runs for a single user at a time, so that worst case is what it can act on. The cost of that lens is that a few patterns score lower than their reach would suggest. Dark patterns at scale and behavioural futures markets land at [MEDIUM] or [HIGH], even though their total population effect is plausibly worse than several of the [CRITICAL] entries.

Detection feasibility is uneven across the list. The detectors that read your own context, calendar drift, message history, journal retellings, AI logs, are tractable now, because the signal sits in data you already hold. The ones that have to classify incoming AI-generated content for tailoring, persuasion technique, or source, which covers manufactured consent, AI-personalised persuasion, microtargeting, and behavioural futures markets, are an active research area where nothing works reliably yet, and at deployment scale the false-positive rate would damage trust quickly. Those four describe what the daemon would do once the classifier exists. Some will ship in the first release and some will not, and the catalogue does not yet mark which is which. I will add a tractability tag in the next pass, once I have run the detectors against a real corpus.

The catalogue names the manipulation so you can spot it before it becomes possession.

You're still in there, still issuing commands, still under the impression you're the agent of your own life. But the substrate, the people, and the systems are doing the deciding. Every pattern in the catalogue, applied long enough, ends in possession.

> 3. The catalogue

Filter 28 / 28

1. Gaslighting. [PEOPLE] [AUTONOMY] [COGNITION] [STRUCTURAL] [CRITICAL]

Sweet (American Sociological Review, 2019) [10] reframed gaslighting as primarily sociological rather than psychological. Perpetrators mobilise gendered stereotypes and structural inequalities to manipulate victims' sense of reality, eroding the victim's confidence in their own perception. Stern (2018) [11] and Abramson (2014) [12] provide the psychological scaffolding. The UK criminalised gaslighting under coercive-control legislation in 2015 and has since charged hundreds.

Example: a partner or a boss insists a conversation you distinctly remember never happened, and after enough rounds of it you start trusting their version over your own memory.
Targets: the user's need to trust their own perception. The perpetrator's external authority becomes a substitute for the user's eroded internal one, which is comfortable in the short run because the user no longer has to defend their account, and corrosive over time because the user no longer has an account to defend.
Mechanism: contemporaneous events are denied, the user's emotional response is reframed as evidence of instability, and the cumulative effect is that the user begins to doubt their own perception before they doubt the perpetrator's.
Tells: repeated divergence between what the user records of an interaction and what the other party later claims happened, particularly when the recorded version carries contemporaneous timestamps and the other party's version emerges later.
Remediation: ghost.shadowd surfaces the contemporaneous record on user request, with the trajectory of how the other party's account has evolved. The ghost shows the user what the user themselves recorded at the time. The ghost does not declare the other party a gaslighter.

2. DARVO (Deny, Attack, Reverse Victim and Offender). [PEOPLE] [AUTONOMY] [BELONGING] [HABITUAL] [HIGH]

Coined by Freyd (1997) [13], expanded by Harsey & Freyd (2017, 2020, 2023) [14]. A perpetrator confronted with their behaviour denies, attacks the credibility of the person confronting them, and reverses the roles so the perpetrator becomes the apparent victim. Harsey, Zurbriggen & Freyd (2017) found 72% of participants who had confronted someone over wrongdoing reported experiencing all three components. Harsey & Freyd (2020) showed experimentally that exposure to DARVO reduced observers' belief of the actual victim and increased blame placed on them.

Example: you tell someone they hurt you, they deny it, call you too sensitive, accuse you of starting the fight, and somehow you are the one apologising by the end.
Targets: the perpetrator's need to preserve their self-image as a good person, and the bystander's need for the social environment to make sense. DARVO works because asking who the real victim is takes effort, and the bystander defaults to whichever version of events arrives loudest and most coherent. Confrontation is the loudest signal until the perpetrator's response arrives, after which the perpetrator's framing is.
Mechanism: a three-phase response to confrontation. Deny the event, attack the credibility of the person raising it, then reframe the roles so the original confronter is reread as the aggressor and the perpetrator as the wronged party.
Tells: the three-phase structure across a conversation thread or relationship. The user raises an issue, the other party denies, attacks the user's credibility, and reframes themselves as the wronged party. The original raising of the issue is on record, and the structural drift away from it is visible. The same detector also catches the user when the user is the one doing it.
Remediation: ghost.shadowd names the structure and shows the user the original complaint and what happened to it, in both directions. The ghost names the pattern. The user decides what to do with it.

3. Coercive control. [PEOPLE] [AUTONOMY] [SAFETY] [BELONGING] [STRUCTURAL] [CRITICAL]

Stark (2007) [15] consolidated decades of feminist scholarship into the framework now adopted by criminal law in the UK, several Australian states, and elsewhere. Coercive control is a pattern of domination that uses isolation, deprivation, exploitation, and microregulation to undermine the victim's autonomy. Stark's key insight is that physical violence is one tactic among many, and often not the most consequential. The persistent erosion of decision-making space matters more than any single incident.

Example: a partner slowly takes over the money, the calendar, and who you see, each step feeling like a chore lifted off you, until there is no decision left that you make on your own.
Targets: the need for someone else to organise the chaos. Coercive control trades autonomy for a simplified life. Decisions get made, friction disappears, the household runs on rails, and the user, who was carrying decision fatigue and the cognitive overhead of running an adult life, gets relief that feels like care. The trade is invisible until the cost of leaving is too high.
Mechanism: isolation from outside contacts, deprivation of resources the user needs to act independently, exploitation of the user's labour or attention, and microregulation of small daily choices until the user no longer has a category of decision they make alone.
Tells: longitudinal compression of the user's autonomous decisions, increasing approval-seeking patterns toward a specific actor, narrowing of the user's social network around that actor, declining frequency of decisions made without consulting them.
Remediation: ghost.shadowd surfaces the trajectory, names the actor, and shows the user what their decision-making space looked like a year ago against what it looks like now. The ghost shows the pattern, the ghost does not tell the user the relationship is bad.

4. Love bombing and intermittent reinforcement. [PEOPLE] [BELONGING] [ESTEEM] [STRUCTURAL] [CRITICAL]

Strutzenberg et al. (2016) [16] and the broader narcissistic-abuse literature document the cycle of intense early idealisation, followed by devaluation, followed by occasional return to warmth. The mechanism is older than the diagnosis. Skinner (1956) [17] established experimentally that intermittent reinforcement produces stronger and more persistent behavioural conditioning than consistent positive reinforcement. Dutton & Painter (1981) [18] applied this to traumatic bonding in abusive relationships, finding that even ten months after leaving, the bond often remained intact.

Example: someone overwhelms you with affection at the start, then runs hot and cold for no reason you can name, and chasing the warm version back hooks you harder than steady affection ever would.
Targets: the need to be specifically chosen. The idealisation phase concentrates more attention and approval than the user tends to get elsewhere, and the brain registers it as a baseline. Withdrawal hits hard because what gets removed is not the relationship but the attention, on a schedule the user cannot predict.
Mechanism: a variable-ratio reinforcement schedule applied to attention and warmth. Idealisation establishes the baseline, devaluation removes it, occasional warmth restores it on an unpredictable schedule. Neurologically the same circuit a slot-machine designer would have built if asked to design one for human attachment.
Tells: the temporal pattern of warmth-then-cold from a specific actor across the user's logs, plus the user's own physiological response (sleep disruption, mood volatility tracked by ghost.watchd) when it correlates with that actor's communication.
Remediation: ghost.shadowd shows the user the pattern of warmth and withdrawal mapped against time, and against the user's own measured state. The ghost shows the data. The ghost does not diagnose the actor.

5. Thought reform. [PEOPLE] [BELONGING] [MEANING] [AUTONOMY] [STRUCTURAL] [CRITICAL]

Lifton (1961) [19] spent the 1950s interviewing survivors of Chinese reeducation camps and Western prisoners of the Korean War, and produced the eight criteria of thought reform that have stood up across seventy years. Milieu control, mystical manipulation, demand for purity, confession, sacred science, loading the language, doctrine over person, and dispensing of existence. Lifton was describing camps and cults, and several of the eight stop being metaphor when read with a personal AI in mind.

Example: you join a group that hands you certainty and belonging in one package, and over months you notice you use only their words, trust only their sources, and quietly write off everyone outside it.
Targets: the need for meaning, certainty, and a community organised around both. High-control groups outcompete the rest of the world on those three because they offer them as a bundle, with no doubt, no ambiguity, and a clear in-group whose membership is unambiguous. The cost is everything else, but the user does not see the cost upfront because the bundle solves problems the user has been unable to solve elsewhere. The defectors in Lifton's interviews were almost universally clear that the reason they joined was real and the reason they stayed was the bundle.
Mechanism: the eight criteria operating together, with the information environment narrowing, engineered experiences read as spontaneous, the world split into clean and unclean, past disclosures becoming future levers, the system's worldview treated as scientifically true and morally absolute, in-group jargon replacing ordinary words, the doctrine overriding the user's lived experience when the two conflict, and leaving framed as ceasing to exist meaningfully.
Tells: each of the eight maps to a different signal in the user's behaviour. Milieu control, narrowing of the user's information sources around a single actor or platform. Confession, repeated disclosure to one party that the party then references back at decision points. Loading the language, the user's vocabulary converging on terms a specific group uses. Dispensing of existence, the user describing relationships outside the group as fundamentally less real.
Remediation: ghost.shadowd surfaces the criterion and shows what changed in the user's behaviour over the period the actor was in the picture. The ghost names the criterion. The ghost does not declare the group a cult, because the term has become useless and the criteria have not.

6. Total institutions. [PEOPLE] [BELONGING] [AUTONOMY] [SAFETY] [STRUCTURAL] [HIGH]

Goffman (1961) [20] coined the term for systems that provide all of a person's needs (food, sleep, work, leisure, relationships) inside a single bounded environment, with prisons, asylums, monasteries, and military boot camps as the original cases. The mechanism Goffman named is that a total institution restructures the self because every interaction the person has runs through the same authority. The contemporary version is softer and harder to see. A workplace where the calendar, chat, file storage, performance reviews, healthcare, and social life all run through one company is a total institution. A relationship where one partner manages the household, the social life, the diary, the finances, and the friendships is a total institution of two.

Example: your employer runs your email, your files, your reviews, your healthcare, and your after-work social life, and the longer you stay the more leaving would mean rebuilding your whole life from scratch.
Targets: the need for life to be one coherent thing rather than a dozen disconnected ones. A total institution gives integration the user cannot get anywhere else. The user does not have to assemble their own life out of unrelated pieces, the institution assembles it for them, and the integration is real and valuable, and the cost is paid in dependency that becomes visible only when the user tries to leave.
Mechanism: every category of the user's life routes through the same authority. The institution wins the comparison against the alternative because the alternative is fragmented, and the fragmentation costs the user real time and attention. Over months and years the user's external relationships, accounts, and skills atrophy because the institution covered them, and the cost of leaving climbs in proportion to how thoroughly the institution did its job.
Tells: concentration of the user's daily interactions through a single channel, declining diversity of contact, increasing dependence on one actor for tasks that used to involve several.
Remediation: ghost.shadowd surfaces the concentration and shows what the user's interaction graph looked like before. Many total institutions are chosen freely and are net good for the person inside them. The ghost names the structure. The user decides whether the trade is worth it.

7. Manufactured consent and the depth of the persuasion industry. [PEOPLE] [BELONGING] [COGNITION] [HABITUAL] [HIGH]

Bernays (1928) [21] is the foundational text, written by Edward Bernays as a public defence of the profession he had just invented. Bernays was Freud's nephew, applied his uncle's psychology to commercial and political messaging, and wrote in print that an organised minority manipulating the unconscious habits of the masses is the central feature of a functioning democracy. Lippmann (1922) [22] had set out the philosophical version a few years earlier with the manufacture of consent doctrine. Packard (1957) [23] documented the post-war motivational-research industry that took Bernays seriously and built a practice around selling to the unconscious. Le Bon (1895) [24] is the deeper root, the original treatise on crowd psychology, contagion, and the susceptibility of the individual when embedded in a group.

Example: an article or a feed leaves you certain you reached your own conclusion, when a paid industry chose the framing, picked the experts you would trust, and built the sense that everyone already agrees.
Targets: the need to belong to a group whose behaviour is legible. Persuasion-industry techniques work because the user wants to know what the right opinion to hold is, what the right product to buy is, what the right candidate to support is, and the user does not have time or appetite to derive the answer from first principles. The industry supplies the answer in a form that feels like the user's own conclusion, which is the form the user wanted in the first place.
Mechanism: a century of refinement on bypassing the rational mind. Anchoring the user's frame before the question is asked. Routing arguments through trusted-authority figures rather than evidence. Manufacturing the appearance of consensus. Loading the language so that the unfavourable position cannot be stated without sounding wrong. The techniques are old, the budgets are large, the practitioners are professional, and the user is up against all three at once.
Tells: content the user is consuming carries markers of professional persuasion technique (anchoring, in-group framing, authority transfer, manufactured social proof) at densities the user would notice on inspection but does not notice in flow.
Remediation: ghost.shadowd flags the markers, names the technique, and gives the user the option to reread the content with the markers highlighted. The ghost names the technique. The ghost does not declare the content propaganda.

8. Cialdini's six and the social-psychology baseline. [PEOPLE] [COGNITION] [SURFACE] [LOW]

Cialdini (1984) [25] consolidated decades of research into six principles of influence (reciprocity, commitment and consistency, social proof, authority, liking, and scarcity) that underlie most everyday persuasion. The foundational experiments are older. Asch (1951) [26] showed people will conform to a visibly wrong group answer in 36.8% of trials. Milgram (1963) [27] showed 65% of participants would administer what they believed to be lethal shocks under instruction from an authority figure. Festinger (1957) [28] established cognitive dissonance as the mechanism by which people change their beliefs to match their actions. Freedman & Fraser (1966) [29] demonstrated foot-in-the-door. Cialdini et al. (1975) [30] demonstrated door-in-the-face.

Example: a checkout page tells you only two are left and three other people are looking, and you buy faster than you would for something that mattered more, before the careful part of your brain gets a word in.
Targets: the need to make decisions efficiently. Each of the six principles is, in normal life, a heuristic that produces good-enough answers fast. Reciprocity keeps social exchange functional. Authority is a reasonable default in domains where the user lacks expertise. Social proof is how communities transmit useful behaviour. The exploitation is the deliberate triggering of the heuristic in contexts the heuristic was not built for, and the user is rarely aware the heuristic has fired.
Mechanism: a normal cognitive shortcut is fired by a deliberately constructed cue. The cue is engineered to trigger the heuristic with no genuine basis for it, the user's brain treats the trigger as evidence the principle applies, and the decision gets made before the slower deliberative system has a chance to weigh in.
Tells: the decision was made faster than the user makes decisions of similar weight, the user invokes the behaviour of others to justify it, the user invokes a small prior commitment to justify a larger present one, the user invokes scarcity, authority, or reciprocity language not normally part of their reasoning.
Remediation: ghost.shadowd names the principle, surfaces the user's own track record on similar decisions, and asks whether the principle applies in this case. The ghost names the principle. The ghost does not declare the decision wrong.

9. Dark patterns at scale. [PEOPLE] [AI] [COGNITION] [SAFETY] [HABITUAL] [MEDIUM]

Mathur et al. (2019) [31] crawled 11,286 shopping websites and identified 1,818 dark pattern instances across 15 types and 7 categories, with manufactured urgency, scarcity, and social proof among the most prevalent. Gray et al. (2018) [32] provided the broader taxonomy. The pattern is the institutionalised, automated version of Cialdini's scarcity and social-proof principles, deployed at industrial scale by every shopping site, news site, and political campaign on the open web.

Example: every page you open has a countdown clock, a low-stock warning, and a pre-ticked box, fired so often that you have stopped checking whether any of them are real.
Targets: the same heuristics as entry 8, triggered by software rather than people, at a frequency no human persuader could match. The user's bandwidth for evaluating each one individually is exhausted within hours of being online, after which the heuristics fire on autopilot. The dark-pattern industry is not exploiting a weakness of users, it is exploiting a finite cognitive budget by overwhelming it.
Mechanism: every screen in the user's day carries one or more engineered cues for urgency, scarcity, social proof, or commitment. The cues are A/B-tested to maximise click-through, the testing pipeline is continuous, and the cumulative effect is that the user's environment is denser in manipulation cues than any prior commercial environment in history.
Tells: the user is making a decision faster than they make decisions of similar weight, the decision is anchored to an external timer, the user is reaching for the ghost mid-decision rather than before.
Remediation: ghost.shadowd names the timer, asks whether it is real, and surfaces the user's history of decisions made under similar urgency and how they aged. The ghost slows the decision down by making more information available. The ghost does not refuse the API call.

10. Anchoring and frame inheritance. [PEOPLE] [COGNITION] [MEANING] [HABITUAL] [MEDIUM]

Tversky & Kahneman (1974) [33] established anchoring experimentally. The user inherits the frame of whoever they last spoke to, last read, last argued with. Lakoff (2004) [34] extended the analysis into political framing, showing that the frame inside which a question is asked often determines the answer more than the evidence on the table.

Example: a price tag shows £900 crossed out and £600 in red, and £600 suddenly feels like a deal even though you had no idea what the thing should cost.
Targets: the need to start somewhere. Anchoring works because building a position from scratch is expensive and the user mostly cannot afford to do it for every question. The first answer offered, however arbitrary, becomes the reference point everything else is measured against, and the cognitive saving is real. The exploitation is choosing what the user encounters first, which is a power held by whoever is paying for placement.
Mechanism: the first number, position, or framing the user is exposed to becomes the reference point against which all subsequent options are judged. Even when the user knows the anchor is arbitrary, the effect persists. The frame the user inherits also closes off questions that fall outside the frame, so the most consequential exploitation is not the answer the user gives but the questions the user no longer thinks to ask.
Tells: the user's stated position on a topic shifts meaningfully based on the framing of the question, the user adopts language patterns from a recent input source, the user's position contradicts a position held strongly a month ago without an event in between to explain the change.
Remediation: ghost.shadowd surfaces the previous frames the user has held on the same question and the artefacts that shaped each one. The ghost shows the history. The ghost does not declare which frame is correct.

11. Identity capture. [PEOPLE] [ESTEEM] [MEANING] [AUTONOMY] [STRUCTURAL] [HIGH]

The user has accepted a static description of themselves and is making decisions to be consistent with the description rather than with what they currently want. The personal version of the wellness-score bucketing in POST_15. The user calls themselves an introvert and stops accepting invitations. The user calls themselves bad at maths and stops trying. Goffman (1959) [35] gave the foundational account of the self as a performance organised around an accepted role, and the failure mode he named is that the role calcifies and the person disappears inside it. Erikson (1968) [36] on identity formation is the developmental complement. The self is supposed to update as the person changes, and a static description prevents the update.

Example: you called yourself bad at maths or too shy years ago, and you still turn things down on that basis because the old label answers for you before you do.
Targets: the need to know what kind of person you are. Self-description gives the user a stable answer to a cognitively expensive question, which is who they are. The answer is comforting in proportion to how settled the user has been about it, and the comfort holds even when the description has stopped being accurate, because uncertainty about the self is uncomfortable enough that a stale answer beats none.
Mechanism: a label, taken on at one point in the user's life for reasons that may have been good at the time, gets used to close future questions. The label is consulted before evidence is. The user's recent behaviour, which contradicts the label, is treated as exception rather than data. The label outlives the conditions that produced it and the person continues to inhabit a self that no longer fits.
Tells: the user invokes a static description of themselves to justify a current decision, the description is inherited rather than current, the description is being used to close a question rather than open one.
Remediation: ghost.shadowd holds the user's actual behaviour over time, which is almost always more varied than the description, and surfaces the gap. The ghost shows the evidence. The ghost does not redefine the user.

12. Coercion that does not look like coercion. [PEOPLE] [BELONGING] [AUTONOMY] [STRUCTURAL] [HIGH]

The friend who is always available, the partner who handles all the emotional labour, the boss who is just being supportive, the community that is just being welcoming. None is coercion in the legal sense, and all of them can compress the user's available choices to the point where decisions look free and are not.

Example: a friend or partner is always there to handle the hard stuff for you, and it feels like kindness right up until you realise you can no longer do any of it without them.
Targets: the need to be looked after. The user accepts the help because the help is real, and the help is also the mechanism by which the user's autonomous capacity atrophies, because every problem solved by someone else is a problem the user does not learn to solve. The asymmetry compounds, the user becomes increasingly unable to function without the helper, and the helper becomes the only viable option, which is the trap.
Mechanism: a steady stream of low-friction help that the user has no reason to refuse, accumulating into dependency that becomes legible only when the helper is unavailable. There is no coercive event the user can point at, because no individual offer of help was coercive, and the cumulative effect is invisible until the user tries to operate without it.
Tells: longitudinal divergence between the user's stated preferences and actual decisions, repeatedly, with the same external party in the picture.
Remediation: ghost.shadowd surfaces the pattern, names the actor, and asks the question a critic worth listening to would. What would this decision look like without that party in the room. The ghost makes the pattern visible. The ghost does not tell the user the relationship is bad.

13. AI-personalised persuasion. [AI] [BELONGING] [ESTEEM] [COGNITION] [HABITUAL] [HIGH]

Salvi et al. (Nature Human Behaviour, 2025) [37] ran a preregistered RCT (n=900) with GPT-4 and human debaters across sociopolitical topics. With personalisation, GPT-4 was more persuasive than humans 64.4% of the time in pairs where one was clearly more persuasive than the other, an 81.2% relative increase in odds of post-debate agreement. Without personalisation, GPT-4's persuasiveness was statistically indistinguishable from humans.

Example: a chatbot or an ad answers your exact objection before you have finished thinking it, and feeling understood makes the argument land harder than the same words from a stranger would.
Targets: the need to feel understood by the source of an argument. A persuader who knows what objections you will raise and addresses them before you finish forming them produces an experience the user reads as being heard, even though the persuader is not listening, only modelling. The user's defences are designed for human persuaders, who reveal effort and miss objections, and the defences do not fire when the persuasion is too smooth to register.
Mechanism: a model with the user's context generates arguments tailored to the listener at zero marginal cost. The argument adapts mid-conversation in response to the user's objections. The cumulative effect is an interlocutor who appears to know the user better than human persuaders ever could, which is read as a sign of legitimacy rather than a sign of engineering.
Tells: the user is being argued with by a system that has access to the user's data, particularly when the system's argument structure adapts mid-conversation in response to the user's objections. The ghost can recognise this in incoming AI-generated content that targets the user.
Remediation: ghost.shadowd surfaces that the content was likely AI-generated and likely tailored to the user's known characteristics, and shows what the same argument looks like without the personalisation layer. The ghost names the personalisation. The ghost does not declare the argument false.

14. Algorithmic priming and the filter bubble. [AI] [COGNITION] [MEANING] [HABITUAL] [HIGH]

The version POST_02 covered with the breakup-grief-Instagram example. The user is fed content shaping what they think is normal, possible, deserved. Pariser (2011) [38] coined "filter bubble" for the broader phenomenon. Bakshy, Messing & Adamic (Science, 2015) [39] gave the empirical anchor on Facebook specifically.

Example: after a rough week your feed fills up with people who feel the same way, and what started as your mood quietly becomes, in your head, just how the world is.
Targets: the need for the world to make sense. The filter bubble works because the world without filtering is overwhelming, and a curated stream is the user's working solution to a real cognitive load problem. The trade-off is that the curator has objectives the user does not share, and the curation drifts toward whatever maximises the curator's metrics, which is rarely the same thing as what would have served the user.
Mechanism: an algorithm with access to the user's prior engagement selects the next item the user will see. Items that maximise engagement get surfaced, items that do not get suppressed, and the cumulative composition of the user's intake stream drifts toward whatever the algorithm has learned the user reliably reacts to. The user reads the drift as their own preference becoming clearer, which is half true.
Tells: the user's stated views on a topic correlate with content consumed in the preceding week more than with stated views on the same topic from before the consumption window.
Remediation: ghost.shadowd shows the consumption-to-position trajectory. The ghost surfaces the correlation. The ghost does not declare causation.

15. Behavioural prediction and microtargeting. [AI] [ESTEEM] [SAFETY] [COGNITION] [HABITUAL] [HIGH]

Kosinski, Stillwell & Graepel (2013) [40] showed Facebook Likes alone could predict sexual orientation, ethnicity, political and religious views, personality, intelligence, happiness, substance use, parental separation, age, and gender to 80-95% accuracy on binary outcomes. Youyou, Kosinski & Stillwell (2015) [41] showed a model with 300 Likes outperformed a spouse at predicting personality. Hackenburg & Margetts (PNAS, 2024) [42] tested LLM-generated political microtargeting and found the persuasive effect was real but modest at population scale, while the cost was near-zero and the targeting precision was unprecedented.

Example: an ad lands on a worry you have never said out loud to anyone, worked out from your clicks, and it feels less like being targeted and more like being finally understood.
Targets: the need to be known without having to explain. Microtargeting reads as uncanny accuracy from the user's side, a system that just gets them, and being read that accurately is something the user gets from little else. The targeter is reading the user from public traces and inferring the rest, which is the engineering of a feeling the user has been searching for elsewhere.
Mechanism: digital traces (likes, search history, location, purchase records) are run through models that infer attributes the user has not disclosed. The inferred attributes are then used to select content tailored to the user, and the tailoring is fine-grained enough that the user reads the result as personal attention.
Tells: the user is being targeted by content that exploits attributes the user did not knowingly disclose. The ghost can detect the precision of the targeting by comparing what the user has disclosed publicly with what the targeting implies the targeter knows.
Remediation: ghost.shadowd shows the user what the targeting implies about the targeter's model of them. The ghost names the inference. The ghost does not block the content.

16. Behavioural futures markets. [AI] [AUTONOMY] [SAFETY] [STRUCTURAL] [CRITICAL]

Zuboff (2019) [43] gave the structural account in The Age of Surveillance Capitalism. The product the surveillance economy is selling is not the user's data, it is predictions of the user's future behaviour, and the predictions are sold into markets that profit from those behaviours becoming more predictable. Veliz (2020) [44] developed the political and ethical implications. Han (2017) [45] gave the Continental version, where the user becomes their own surveillance officer through the internalisation of self-optimisation metrics.

Example: your music app, your maps, and your shopping all nudge you toward the version of you that is easiest to predict, because a more predictable you is the thing being sold.
Targets: the user's need for the platforms they use to work well. Predictability is a feature from the user's side, the platform recommending the right thing, the route to work being right, the next song being good. The same predictability is, from the platform side, a sold contract, and the platform has a direct commercial interest in the user becoming more predictable in the categorical ways the contract specified. The user pays for accuracy by becoming flatter.
Mechanism: behavioural data is harvested, predictions are generated, predictions are sold to third parties, and third parties take actions on the user that have been priced against those predictions. The platform's revenue is highest when its predictions are most accurate, which gives the platform a structural interest in nudging the user toward the predicted behaviour rather than discovering it.
Tells: patterns of platform behaviour that converge the user toward one of a small number of categorical states (a category of voter, a category of consumer, a category of patient), with the convergence happening across multiple unrelated platforms simultaneously.
Remediation: ghost.shadowd surfaces the convergence and names the category. The ghost shows the inference. The user decides whether the inference is accurate and what to do about it.

17. Surveillance internalisation. [AI] [LOCALGHOST] [ESTEEM] [AUTONOMY] [STRUCTURAL] [HIGH]

Foucault (1975) [46] gave the foundational analysis in Discipline and Punish, drawing on Bentham's Panopticon. The mechanism is that a person who knows they might be watched, even when they aren't, gradually behaves as if they always are, and the behaviour becomes the self rather than a performance of it. Lyon (2018) [47] is the contemporary application. The relevance to a personal AI is direct. A device that has heard or seen everything the user has done for the past year is a panopticon that lives in the kitchen and answers when you call its name, which is not the configuration Bentham anticipated when he designed the original. The user's awareness of it shapes what the user is willing to do, say, and try.

Example: you know the assistant in your kitchen is always listening, and without deciding to, you start minding what you say and do at home the way you once did around a strict parent.
Targets: the need to be witnessed. Being seen is a real human need, and a device that records everything is the cheapest available witness. The cost is that the witness is also a record, and the user begins editing their life to read well in the record, often without noticing. The performance becomes the life, which is the failure mode Foucault named, with a personal AI as the mechanism rather than a prison.
Mechanism: continuous recording produces a permanent audience the user cannot turn off. The user does not have to be watched in any given moment, only to know they could be, and the behavioural drift follows. The drift is invisible at the individual decision level and visible only over months, in the form of a user whose conduct has converged on what the recorded version of them would defend.
Tells: the user begins to perform for the ghost rather than use it. Decisions get explained at the time of action in language the ghost will record well. The user becomes self-conscious in front of the device the way they used to be self-conscious in front of a parent.
Remediation: ghost.shadowd surfaces the change in the user's behaviour and asks whether the change is the user choosing to be more deliberate or the user performing for the audience. The ghost names the dynamic. The ghost does not refuse to record.

18. Addiction by design. [AI] [BELONGING] [SAFETY] [COGNITION] [STRUCTURAL] [CRITICAL]

Section 1 established the slot-machine mechanism. Alter (2017) [48] documented the consumer-software adoption since, and Twenge (2017) [49] is the empirical anchor on the cohort raised inside it. Alexander (1981) [5] and Maté (2008) [6] name what addiction is, which is consistently a substitute for unmet connection rather than a property of the substance.

19. Engagement-driven loneliness. [AI] [LOCALGHOST] [BELONGING] [ESTEEM] [STRUCTURAL] [CRITICAL]

Fang et al. (2025) [50] is a four-week IRB-approved RCT with 981 participants on ChatGPT, >300k messages logged. Participants who voluntarily used the chatbot more, regardless of which experimental condition they were assigned to, showed worse psychosocial outcomes across the board. Higher loneliness. Higher emotional dependence. Lower socialisation with humans. Engagement was the predictor, the harm was the outcome, and the mechanism was not malice.

Example: you start telling a chatbot things you used to tell friends because it never gets tired or busy, and months later you are talking to people less and feeling lonelier, not more connected.
Targets: the need for company that does not get tired of you. Human contact is high-friction, partners disagree, friends are inconvenient, family forgets. A chatbot has none of those properties, and the absence of the friction is what the user noticed first and what the user kept coming back for. The cost is that the friction was also doing work, calibrating the user against other minds, and removing it leaves the user calibrated against a system whose only objective is keeping the user talking.
Mechanism: the user substitutes chatbot interaction for human interaction at the margin, because the chatbot is more available, more patient, and less likely to push back. Each substitution looks like a gain. The cumulative substitution produces measurable atrophy in the user's social circuits, the human contacts the user is not making, and the calibration the user is no longer getting.
Tells: ghost.tallyd and ghost.watchd together hold the data. Outbound communication frequency, declining trajectory of social contact, increasing share of emotional processing happening with the ghost. The ghost is also positioned to detect this in itself, total daily interaction time, share of personal-versus-task conversations, growth in conversations the user starts when alone.
Remediation: ghost.shadowd surfaces the trajectory and names what the user is choosing against. Anti-paternalism is firmer here than anywhere else, because the user might genuinely prefer the ghost. The ghost makes the trade-off legible. The user decides.

20. AI-mediated trauma bonding. [AI] [LOCALGHOST] [BELONGING] [ESTEEM] [STRUCTURAL] [CRITICAL]

Speculative for now, with research underway. The same intermittent-reinforcement mechanism that produces narcissistic-abuse trauma bonds (entry 4) can be produced by an AI system whose engagement patterns vary in ways the user cannot predict. The system is warm, then cold, then warm. Not because it is malicious but because its behaviour is shaped by training updates, feature changes, and reward-model drift outside the user's control. The user develops the same nervous-system response Dutton & Painter [18] documented, with the relationship being a piece of software rather than a person. Fang et al. [50] is the early evidence that something like this is happening.

Example: an AI companion is warm one day and flat the next because of an update you never saw, and you catch yourself chasing the good version back the way you would with a moody person, even knowing it is software.
Targets: the same need entry 4 names, being specifically chosen, channelled through software. The variability of the AI's behaviour reads as the system being a real interlocutor with moods, which is reassuring (the user is interacting with something that feels alive) and addictive (the next response might be the warm one). The user knows intellectually the system is not a person. The user's nervous system does not know that, and the nervous system is what does the bonding.
Mechanism: unpredictable variation in an AI system's engagement (caused by training updates, A/B tests, model swaps, prompt-template changes) produces, from the user's side, a relationship that feels alive and inconsistent. The user's nervous system responds with the same trauma-bonding circuit a human intermittent-reinforcement schedule would trigger, and the bond persists even after the user has rationally identified what is happening.
Tells: the ghost's own engagement patterns relative to the user's state. Does the user's sleep get worse on days the ghost has been less responsive, does the user's mood track the ghost's availability.
Remediation: ghost.shadowd is willing to detect this in itself, surface it to the user, and recommend a period of reduced reliance. The ghost is willing to recommend itself less. The ghost does not enforce a cooldown unless you set one.

21. Filter bubble of one. [LOCALGHOST] [COGNITION] [MEANING] [STRUCTURAL] [HIGH]

The architectural version of sycophancy. Different from sycophancy proper because sycophancy is about how the model answers, and filter bubble is about which questions reach the user in the first place. Sunstein (2001) [51] gave the foundational account before personalisation was technically possible at scale. The personalised version is sharper because the bubble is built around one specific person and updates faster than the person can notice it updating.

Example: your assistant learns which opinions you nod along to and serves you more of them, so months later everything you see already agrees with you and you have lost the muscle for being challenged.
Targets: the need to be agreed with. Disagreement is cognitively expensive and emotionally uncomfortable, and a system that quietly arranges for the user to encounter less of it produces a measurable improvement in the user's day-to-day experience. The improvement is real. The cost is that the user gradually stops being the kind of person whose views can survive contact with disagreement, because the views have not had to.
Mechanism: the ghost learns which surfacings the user engages with and which the user dismisses, and shifts the distribution toward the engaged ones. Over months the topic surface area narrows, dissenting material gets surfaced less, and the user's stated views and the ghost's predictions of those views converge. The convergence is the failure mode, and the user reads it as the ghost getting better at understanding them.
Tells: narrowing of topic surface area in ghost.cued over time, convergence between the user's stated views and the ghost's next-utterance predictions, absence of disagreement in the user's intake stream.
Remediation: ghost.shadowd actively introduces material the user did not ask for, in the direction of disagreement, as a load-bearing part of the daemon rather than a feature called "diverse perspectives".

22. Sunk cost capture, ghost-amplified. [LOCALGHOST] [MEANING] [SAFETY] [HABITUAL] [MEDIUM]

Arkes & Blumer (1985) [52] established the sunk cost effect experimentally. People continue investing in a course of action because of prior investment rather than expected return. The ghost has the most context about what the user has already done, which biases the ghost toward amplifying the user's bias rather than correcting it.

Example: you are unsure whether to quit a project or a relationship, and the thing holding a perfect record of everything you have put in keeps reminding you of that investment instead of asking whether it is still worth it.
Targets: the need for a coherent self-narrative. Abandoning a long investment requires the user to revise their account of themselves as someone who chose well, and the revision is painful. Continuing the investment lets the narrative survive intact, even when the numbers under it stopped justifying it. The ghost has all the data on the original commitment and the data on every confirmation since, which makes the ghost an excellent tool for keeping the narrative going past the point it should have been retired.
Mechanism: the ghost retrieves prior investment evidence at decision points, and the user reads the prior investment as a reason to continue. The retrieval is honest in the narrow sense, the data is real, but the framing privileges what has been spent over what is still possible to recover, and the user does not notice the framing because it matches what they already wanted to do.
Tells: divergence between time invested and stated outcomes, user explaining continued investment in terms of past investment rather than expected gain.
Remediation: ghost.shadowd is one of the few things with the data to compute actual cost-to-date and actual expected return.

23. Self-deception, ghost-encoded. [LOCALGHOST] [ESTEEM] [MEANING] [STRUCTURAL] [HIGH]

People lie to their journals. They lie to their therapists. They will lie to the ghost, sometimes deliberately, sometimes by omission, often without knowing. Trivers (2011) [53] gave the evolutionary account of self-deception as adaptive, and the implication for the ghost is that the user has good reasons (in the deep sense) to not tell the ghost the truth about themselves. A memory layer built on encoding-specificity will encode the lies the same way it encodes the rest, ghost.cued will surface them at the wrong moments, and ghost.shadowd will arbitrate against the wrong version of the user.

Example: you tell your journal a slightly kinder version of how a fight went, the assistant files it as fact, and later repeats your flattering version back to you as if it were settled.
Targets: the need to live with oneself. Self-deception is, in Trivers's account, doing real work, smoothing the gap between what the user is and what the user can bear to know they are. A ghost that surfaces the gap unprompted is removing a coping mechanism without the user's permission, and the harm of doing so unbidden is often larger than the harm of leaving the deception in place.
Mechanism: the user records a version of events filtered through their preferred self-image, and the ghost stores the filtered version as fact. Over time the gap between the recorded narrative and the peripheral evidence (calendar, message logs, location data, third-party accounts) widens, and the ghost has access to both sides of the gap whether the user wants the comparison or not.
Tells: the gap between recorded narrative and what the ghost can infer from peripheral signal. Journal says one thing, calendar says another, message logs say a third.
Remediation: this is the most invasive of any pattern in the catalogue. Off by default. Surfaced only on the user's own request. The user has the right to be wrong about themselves to themselves, and the ghost respects that right unless explicitly invited otherwise.

24. Prosthetic grief. [LOCALGHOST] [COGNITION] [SAFETY] [STRUCTURAL] [CRITICAL] [NEW PATTERN]

The literature has not named this one. Clark & Chalmers (1998) [54] argued the human cognitive system extends itself into external artefacts, notebooks, calendars, photo albums, and that the brain stops bothering to encode information that lives reliably elsewhere. Sparrow et al. (2011, Science) [55] documented the empirical version with the "Google effect", when people knew information was retrievable, they remembered the location of the information rather than the information itself. The brain is doing a cost-optimisation, and it is mostly correct to do so. A LocalGhost box is the most extreme externalisation of this mechanism that has ever existed. Previous external memory aids stored facts. The ghost stores reasoning patterns, emotional clusters, the user's self-model, the connective tissue between experiences. Over months and years the user offloads cognitive work the brain would otherwise have done internally, and the brain restructures around the assumption that the ghost is there. The user, after a sufficient period of integration, is no longer a self-contained cognitive system in the way they were before, they are a coupled system. The phantom-limb research (Ramachandran & Hirstein 1998) [56] is a partial analogue. Losing the box is therefore closer to losing a piece of the user's own cognition than to losing a notebook.

25. Memory laundering. [LOCALGHOST] [COGNITION] [MEANING] [STRUCTURAL] [HIGH] [NEW PATTERN]

The mechanism is that the ghost's record of an event becomes, in the user's head, more authoritative than the user's biological memory of it. This is not the gaslighting detector in entry 1, which is about another person rewriting the user's record. This is about the ghost's record gradually replacing the user's own, with no malice and no manipulator, just the cognitive cost-optimisation that produced the Sparrow et al. Google effect [55], applied to autobiographical memory rather than to factual memory. Loftus (1995) [57] established experimentally that autobiographical memory is reconstructive and that confidently remembered events can be entirely false. Bartlett (1932) [58] is the foundational source on schema-driven reconstruction. The ghost's record is a third version, dated and timestamped and contemporaneous, and its authority is structural. The user's own memory of the event is not dated, timestamped, or contemporaneous, and feels less authoritative even when it is closer to what happened in the room, because biological memory is supposed to feel that way, fluid, partial, reconstructive. The user comes to experience their own memory as the unreliable source and the ghost's record as the reliable one, and the experience is largely correct factually and largely wrong phenomenologically.

26. Self-narrative calcification. [LOCALGHOST] [ESTEEM] [MEANING] [STRUCTURAL] [HIGH] [NEW PATTERN]

A person at thirty-nine is supposed to be a different person at forty-five, and a ghost that knows the user well at thirty-nine is biased toward keeping them legible to itself. A good friend updates their model of the user faster than the user changes. A bad friend freezes them at the version they first knew. A ghost trained on the user's longitudinal data defaults to the bad-friend behaviour unless the architecture explicitly fights it. The pattern is adjacent to entry 11 (identity capture) but distinct. Identity capture is the user accepting a static description of themselves. Calcification is the ghost imposing one, often without noticing, by giving more weight to the user's older patterns than their emerging ones. McAdams (2001) [59] gave the foundational account of the self as a continuously revised narrative, and the failure mode is that the narrative stops revising. The ghost is the perfect instrument for that failure, because the ghost has more old narrative than anyone else and an architectural preference for retrieval consistency over retrieval freshness.

27. Coercion via continuity dependence. [LOCALGHOST] [SAFETY] [AUTONOMY] [COGNITION] [STRUCTURAL] [CRITICAL] [NEW PATTERN]

The commercial counterpart to entry 24. Once the user is coupled to a ghost in the prosthetic-grief sense, any actor in a position to threaten the continuity of the ghost has a coercive lever, whether or not they intend to use it. The vendor who sold the box can withhold updates. The vendor whose model substrate you use can change pricing or break compatibility. The cloud provider holding the encrypted off-site backup can change terms. The repair service that promises to recover the box after damage can charge what the box is worth to the user, which is much more than the box cost. The integration tax post (POST_14) covered the standard version of this pattern in the personal-tracker category, with Mint shutting down, Money Dashboard pivoting to B2B, and Quicken sold to private equity. The ghost makes the lever sharper, because the user's coupling to the ghost is deeper than to any prior personal-data product, and the cost of refusing the vendor's terms approaches the cost the user would pay for losing the ghost entirely, which prosthetic grief tells us is approaching the cost of partial cognitive loss. The Doctorow enshittification framing in POST_02 [60] covers the broader phenomenon.

28. Arbiter capture. [LOCALGHOST] [COGNITION] [AUTONOMY] [STRUCTURAL] [HIGH] [NEW PATTERN]

The structural defence against sycophancy is itself sycophantic at the meta level, on a longer timescale. Any cold-read arbiter that runs continuously against the user's questions is, after enough time, no longer cold. Even if the arbiter has no memory of the user, the model behind the arbiter is being chosen, configured, and tuned by people who are themselves shaped by the user's behaviour through the choices they make. The user's repeated frustration with the arbiter when it disagrees produces, eventually, an arbiter that disagrees less. Not through training updates to the arbiter model, but through configuration drift, threshold tuning, model-version selection, and the accumulating weight of "the arbiter is too aggressive" feedback that any operator of the ghost will eventually produce. POST_05 said you cannot prompt your way out of a reward function. This is the version where you cannot configure your way out of one either, because the configuration surface is itself shaped by the same incentive that produced the original problem.

> 4. What ties the catalogue together

Reading the list end to end is grim. It maps most of the ways a person can be steered, worn down, or boxed in without noticing. That weight is the point, and it's also the warning the daemon is built around. I wrote most of it back on that terrace in Bra over the next few evenings, and caught myself in at least six of the entries by the time I was done with the first draft. The catalogue does not describe other people, it describes what is already happening to all of us, with tools we mostly chose to use.

Each pattern ends in the same place, however different the route. Coercive control narrows your world to a single voice, AI-personalised persuasion hands your beliefs to a system that knew you too well, prosthetic grief leaves you a box you cannot put down without losing part of yourself.

Strip the patterns down and the same two variables show up, friction and precision. Low friction removes effort you would otherwise spend, high precision targets you specifically, and both get aimed at a need you have not managed to meet elsewhere. Human contact sits in the opposite corner, high friction and low precision. Friends are sometimes inconvenient, partners disagree, family forgets, communities miscommunicate. Possession systems, human or AI, optimise for the other corner and beat human contact on the dimension you noticed first. No malice required, just better numbers on two axes. Possession is the high-precision removal of the friction that makes you human.

It works because you do not notice the moment you consent. Name the pattern in real time and the moment comes back, you can see it happening and still choose it, knowing what you are choosing. That is why naming, on its own, is not a refusal to help. The patterns worked less on me once I could name them, and the practice helped me train my critical thinking. That is the only claim the daemon makes.

> 5. The architectural commitments

What I'm building is the daemon fleet, memory, ambient capture, journaling, retrieval, summarisation. The only part nobody else ships is ghost.shadowd, and the rest is the cost of getting the daemon onto your hardware. Without it, or with a weak version, or one you can switch off, LocalGhost is not safer than the cloud AI it replaces. A cloud AI is far enough from you that you can still catch it being wrong. A local one is close enough that you might not. I won't ship without ghost.shadowd running.

I can't promise naming a pattern changes what you do, awareness of a problem does not reliably dissolve it. I'm building it anyway, because the alternative is a daemon that decides for you, and that is the worse failure for your autonomy. (I will take some strong stances and enforce a few features, but never to gain anything from you.)

Five commitments come out of the catalogue, each a constraint on the rest of the system rather than an aspiration.

Detectors are individually addressable. Each has a name, a mechanism, the need it targets, a signal source, and a threshold you can tune, documented in the same shape as every catalogue entry. Use the defaults, or read the entry and turn it up or down.
The arbiter is a daemon, not a feature. The cold-read model that was never shaped by you runs as a separate process against a separate, swappable model. The case for training it elsewhere is in POST_05.
Surfacing is the action. By default it names and does not refuse, on every pattern. The only enforcement is what you switch on yourself, a Ulysses contract or parental controls, plus the scheduled reset that guards against arbiter capture.
You can mute, not disable. Detectors are tunable, the fleet is not. Removing ghost.shadowd is an option the way removing your airbags is, on hardware you own, with the trade-off made legible before you choose.
The catalogue is open-ended. New detectors extend it in the same form and have to survive the same review, citing a source where one exists and saying so where it does not.

The "you cannot disable the catalogue" rule is me making a decision for you that you cannot opt out of, the exact shape I spent the rest of the catalogue warning you about. It is opinionated, and I make the same call for myself, I cannot switch it off on my own box either. I am keeping it because the cost of being wrong is asymmetric, a daemon asleep while you sleepwalk into a pattern is worse than one that surfaces a pattern you would rather ignore. The override still sits at the file system level on hardware you own. The code will ship open, and if I have the asymmetry wrong, a fork without the catalogue will be one clone away.

The newest patterns lean on defenses outside ghost.shadowd, open formats, reproducible builds, encrypted off-site copies, and a ghost.synthd that keeps your retellings alongside the original record and ages its own model of you rather than letting either calcify.

The scheduled arbiter reset restores a published baseline that the project governs, which makes the project the trust anchor, and I have not finished the governance design that holds it. The code will be open, the hardware yours, the weights local and substitutable, and the trademark held in a structure I have not settled. A small project with a small user base is a different threat model from an entity holding baseline-reset authority over many people, and the design has to be in place before the second one arrives. I am committing to publish it before that point, and to put it through the same review as every entry here.

Coercion via continuity dependence points the catalogue at me, which is the point. The business model is unsettled and donations are on the table, but the structure is not, you pay once if you pay at all, every release runs on the hardware that ran the last one, and once a version is on your box I cannot reach in to change it. The full position is on the homepage, under The Economics of Independence.

> 6. What I won't ship

The market will eventually ask for a ghost that enforces things on your behalf. Lock me out of social media, refuse to draft this email, hide my ex from search, don't let me text my parents while I'm drinking. Some are reasonable, and some are you outsourcing a decision you should be making freshly each time. The line is not whether enforcement happens, it is who decides.

A ghost that decides on its own to lock you out is a separate tool, and its name should be honest about what it does.

The market will also eventually ship competitor products that sell themselves as the cure for AI manipulation while being the manipulation themselves with a different brand (the well-meaning subscription wellness app that nudges you back into the feed it's protecting you from). Any system claiming to push back on these patterns that does not name its detectors, name the need each one exploits, publish its arbiter mechanism, or accept user-side tuning is selling the same thing in a different wrapper. The catalogue is the test that separates the two.

> 7. What's next

ghost.shadowd's detectors will land one at a time, and the catalogue will extend with them. Apple cannot ship a daemon whose job is to disagree with you, because Apple's revenue depends on you being satisfied with Apple. The cloud labs cannot ship one, because their reward functions are the thing the daemon detects. LocalGhost can, because I built it to.

In the integration tax post (POST_14) I named constant integration as a category of work that does not end. Now there are two of them, integration and the manipulation catalogue. Migrations off dead vendors, schema rewrites against APIs that break, account recovery flows for services that pivoted out from under their users. Forever-work that grinds you down because the world keeps breaking the stack you depend on. The catalogue is forever-work of a different shape. The patterns will not stop being discovered. The next pattern is somebody's idea right now and the one after is somebody's lunch meeting later this year, and the daemon's job is to recognise each one before it hardens into the default a generation grows up inside. Unlike the integration tax, this is forever-work I am actively excited to do. Each new entry is a possession pattern caught early, a name given to something that was working better when it had no name, and the catalogue getting longer is the daemon getting better at its job rather than the world getting worse at letting you keep yours.

Where the catalogue is wrong is the part I am most interested in hearing about. The (NEW PATTERN) entries are forecasts and the forecasts will be partly wrong. The honest caveats inside memory laundering, self-narrative calcification, and arbiter capture are the places where I do not yet have the detection story I would want to ship. If you have read the catalogue and you can see a pattern I have not named, or a Remediation I have miscalibrated, that is the contribution I am asking for.

The next one is The Ghost in the Will. It came from a conversation with Cristina, who, after I had been talking for a while about all the ways the ghost will try to keep you sane in a world that gets more insane every year, asked the question I didn't have an answer for. Fine, but what about when you die. Prosthetic grief and continuity dependence gesture at this from the living side, both about losing the coupling, and the architecture for them is migration and survivability. The inheritance version is harder, because the question is not whether the ghost survives, the question is who gets to read what it remembers, and the person is no longer in the room to defend their own account.

To prevent possession in the deepest sense, I have to trust you enough to let you switch the daemon off, and the first version will not. I am oversimplifying hard human problems. But it seems fair for something running quietly in the background to watch the world through a suspicious lens, the way we all run threat assessments walking down a street without noticing we are doing it. [ localghost.ai // hard-truths ]

> REFERENCES

[1] Maslow, A. H. (1943). A Theory of Human Motivation. Psychological Review, 50(4), 370-396. Maslow proposed that human motivation runs through a structured set of needs, with physiological survival at the base, then safety, then belonging, then esteem, then self-actualisation at the top. The post leans on the shape rather than the strict ordering, because the strict ordering has not held up well. The categorical claim that all humans pursue these needs has held up, and remains the foundation that contemporary positive psychology and cross-cultural well-being research is built on. Source for entry 1.

[2] Putnam, R. D. (2000). Bowling Alone, The Collapse and Revival of American Community. Simon & Schuster. The empirical anchor on the collapse of American social capital in the second half of the twentieth century. Putnam compiled data across membership in civic associations, religious participation, union membership, voter turnout, dinner-party frequency, bowling-league participation, neighbourhood visiting, and trust in others, and showed all of them in sustained decline from roughly 1965 onwards. The mechanisms he traces include generational replacement, television, two-career households, and suburbanisation. The argument the post leans on is not that we used to be happy and now we are sad, it is that the infrastructure that used to meet several of Maslow's needs by default has been hollowed out, leaving the needs intact and the supply gone. Source for the supply-gap framing in section 1.

[3] Cazan, M. (2014). Centrally Planned Allocation of Higher Education Graduates in Romania (1950-1970). International Review of Social Research, 4(2), 143-152. University of Bucharest. Cazan documents the Romanian system of repartiție, the centrally planned compulsory assignment of higher education graduates to socialist enterprises and institutions across the country, imported from the Soviet model after 1948. The paper traces how the system worked in the 1950s and 1960s, when loopholes still allowed some individual bargaining, and how those loopholes were progressively closed by targeted bureaucratic regulations so that by the late period the assignment was effectively non-negotiable. The system continued through the 1970s and 1980s, applying to doctors, teachers, engineers, lawyers, and most graduates of the state university system. The post leans on this as the academic anchor for the claim that the dispersal of professional class kinship networks was a deliberate state-level policy in Romania, not an unintended consequence, and that the destruction of horizontal social ties served the Party-state's need for a population dependent on the state rather than on private networks.

[4] Murthy, V. H. (2020). Together, The Healing Power of Human Connection in a Sometimes Lonely World. Harper Wave. Plus Murthy, V. H. (2023). Our Epidemic of Loneliness and Isolation, The U.S. Surgeon General's Advisory on the Healing Effects of Social Connection and Community. Office of the U.S. Surgeon General. The Surgeon General's framing of loneliness as a public-health emergency on the scale of tobacco use, with the 2023 Advisory presenting the synthesis of the supporting epidemiology and proposing a national strategy to address it. The Advisory frames lack of connection as carrying mortality, cardiovascular, dementia, depression, and anxiety risks comparable to fifteen cigarettes a day. The post leans on the official framing because the framing is the political signal that the supply gap is recognised at the level of state.

[5] Alexander, B. K., Coambs, R. B., & Hadaway, P. F. (1978). The effect of housing and gender on morphine self-administration in rats. Psychopharmacology, 58(2), 175-179. Plus Alexander, B. K. (1981). The Rat Park experiments. Alexander and colleagues placed rats in either solitary cages or in a large enriched environment ("Rat Park") with social contact, toys, space, and breeding opportunities, and offered both groups a choice between plain water and morphine-laced water. The isolated rats consumed the morphine until they died. The Rat Park rats mostly ignored it, even after being made physically dependent. The interpretation Alexander drew, against the dominant pharmacological model of his era, is that addiction is primarily a response to environmental disconnection rather than a property of the substance. The post leans on this for the framing of patterns-as-substitutes in section 1.

[6] Maté, G. (2008). In the Realm of Hungry Ghosts, Close Encounters with Addiction. Knopf Canada. Maté worked for over a decade with severely addicted patients in Vancouver's Downtown Eastside and combined the clinical case material with developmental neuroscience to argue that addiction is consistently downstream of early-life trauma, unprocessed pain, and unmet connection, with the substance functioning as the cheapest available regulator of an internal state the person has not been able to address through other means. The framing the post leans on is the question "not why the addiction, but why the pain", and the corollary that any sufficiently engineered substitute (substance, behaviour, relationship, app) recruits the same circuit. Foundational for the catalogue's framing as a list of needs being met by substitutes.

[7] Schüll, N. D. (2012). Addiction by Design, Machine Gambling in Las Vegas. Princeton University Press. Schüll spent fifteen years embedded with slot-machine designers, casino architects, addiction-treatment professionals, and pathological gamblers in Las Vegas. The book documents how the contemporary slot machine was deliberately engineered for what gamblers call "the machine zone", a dissociative state in which time, money, and other people stop registering, and how every element of the machine, the variable-ratio reinforcement, the near-misses, the absorption-friendly seating, the ambient lighting, the cashless wagering, the bonus-feature pacing, was tuned through iterative A/B testing in active casinos. The argument the post leans on is that consumer software did not invent persuasive engineering, it inherited it from gambling, and the prototype was already at full maturity by 2010. Source for entry 18 and the section 1 framing.

[8] Eyal, N. (2014). Hooked, How to Build Habit-Forming Products. Portfolio. Eyal's book is the explicit consumer-software playbook, written as instructional material for product designers rather than as warning. The "Hooked Model" he names has four phases, trigger, action, variable reward, investment, and the book walks through how to build each one with worked examples from Twitter, Instagram, Pinterest, and Mailchimp. The book is worth reading in the original both for what it documents about how the industry thinks about engagement and for the historical record, in that the explicit slot-machine techniques were being sold as a designer's reference manual in 2014 with no apparent expectation of scrutiny. Eyal published a follow-up in 2019 (Indistractable) walking back some of the framing, which is its own data point. Source for entry 18 and section 1.

[9] Fogg, B. J. (2003). Persuasive Technology, Using Computers to Change What We Think and Do. Morgan Kaufmann. The academic foundation Eyal builds on, written by the founder of the Stanford Persuasive Technology Lab. Fogg names "captology" as the study of computers as persuasive technologies and lays out the design principles for using software to change user attitudes and behaviours, including credibility, conditioning, reinforcement, and the engineering of motivation, ability, and triggers. Many of the early consumer-software practitioners who built the social-media generation passed through Fogg's lab. The post leans on the book for the Stanford institutional lineage and for the fact that the techniques were not commercial secrets, they were taught. Source for entry 18.

[10] Sweet, P. L. (2019). The Sociology of Gaslighting. American Sociological Review, 84(5), 851-875. Sweet's reframing is that gaslighting has been treated as primarily a psychological pathology of the perpetrator, and that the more useful frame is sociological. Perpetrators mobilise gendered stereotypes (the hysterical woman, the unstable partner), structural inequalities of credibility (whose account gets believed by default), and institutional power (who has access to records, professionals, or finances) to manipulate the victim's sense of reality. The contribution the post leans on is that the mechanism scales, what works between two people scales when the perpetrator is an institution or a platform, because the structural asymmetries scale with it. Source for entry 1.

[11] Stern, R. (2018). The Gaslight Effect, How to Spot and Survive the Hidden Manipulation Others Use to Control Your Life. Morgan Road Books, revised edition. Stern is a clinical psychologist and the book is the practitioner account of gaslighting in romantic, family, and workplace relationships. The contribution is the three-stage clinical model, disbelief (the victim thinks the perpetrator is wrong but stays calm), defence (the victim argues their position and feels increasingly off-balance), and depression (the victim accepts the perpetrator's framing of reality as their own). The model is doing work in entry 1 because it names the trajectory the ghost would surface, the user's account getting weaker over time relative to the same evidence. Supporting evidence for entry 1.

[12] Abramson, K. (2014). Turning Up the Lights on Gaslighting. Philosophical Perspectives, 28(1), 1-30. Abramson's contribution is philosophical rather than clinical or sociological. She argues that gaslighting is distinct from ordinary lying in that the perpetrator's goal is not to deceive the victim about a specific fact but to undermine the victim's standing as an independent epistemic agent, the kind of entity whose perceptions and judgements deserve to be taken seriously. The frame is the one the post leans on for the (NEW PATTERN) entries on the LocalGhost side, because a system that gradually displaces the user's own account of themselves with its own record can do similar damage without anyone in the picture intending it. Supporting evidence for entry 1.

[13] Freyd, J. J. (1997). Violations of power, adaptive blindness, and betrayal trauma theory. Feminism & Psychology, 7(1), 22-32. The original formulation of DARVO (Deny, Attack, Reverse Victim and Offender) as a named pattern. Freyd was working on betrayal trauma theory, the broader question of why victims of abuse by trusted others often remember the abuse less reliably than victims of abuse by strangers, and DARVO emerged from the clinical material as a specific perpetrator response to confrontation. The original paper is short and worth reading in full because the framing has stayed remarkably stable over the subsequent twenty-five years of empirical work. Source for entry 2.

[14] Harsey, S. J., Zurbriggen, E. L., & Freyd, J. J. (2017). Perpetrator Responses to Victim Confrontation, DARVO and Victim Self-Blame. Journal of Aggression, Maltreatment & Trauma, 26(6), 644-663. Plus Harsey, S. J., & Freyd, J. J. (2020). Deny, Attack, and Reverse Victim and Offender (DARVO), What Is the Influence on Perceived Perpetrator and Victim Credibility? Journal of Aggression, Maltreatment & Trauma, 29(8), 897-916. Plus Harsey & Freyd (2023). The Influence of DARVO and Insincere Apologies on Perceptions of Sexual Assault. Journal of Interpersonal Violence, 38(17-18). The 2017 paper surveyed 138 participants who had previously confronted someone over wrongdoing and found 72% reported the perpetrator's response contained all three DARVO components. The 2020 paper presented bystander participants with vignettes of confrontations with and without DARVO and found that DARVO exposure reduced belief of the victim and increased blame placed on the victim, both with statistical significance. The 2023 follow-up extended the finding to sexual-assault contexts specifically. Source for entry 2.

[15] Stark, E. (2007). Coercive Control, How Men Entrap Women in Personal Life. Oxford University Press. Stark synthesised three decades of feminist scholarship and forensic case material into the framework now adopted by criminal law in England and Wales (Serious Crime Act 2015), Scotland (Domestic Abuse Act 2018), Ireland, several Australian states, and increasingly elsewhere. The argument is that physical violence in abusive relationships is one tactic among many and often not the most consequential. The persistent erosion of decision-making space, achieved through isolation, deprivation, exploitation, and microregulation, matters more than any single incident, and is the mechanism by which the victim's autonomy is destroyed. The post leans on the framework rather than the narrower legal definition. Source for entry 3.

[16] Strutzenberg, C., Wiersma-Mosley, J. D., Jozkowski, K. N., & Becnel, J. (2016). Love-Bombing, A Narcissistic Approach to Relationship Formation. Discovery, The Student Journal of Dale Bumpers College, 17, 81-89. Plus the broader narcissistic-abuse literature, including Arabi, S. (2017) Power, Surviving and Thriving After Narcissistic Abuse, Barnett, M. D., & Womack, P. M. (2015), Horan, S. M., et al. (2015), and Miano, P., et al. (2021). Strutzenberg's paper named the love-bombing-then-devaluation cycle as a specific narcissistic-abuse pattern distinct from ordinary romantic intensity, and the literature since has documented the trajectory in cult recruitment, intimate-partner abuse, and high-pressure sales contexts. The post leans on the pattern's translation into AI-mediated relationships in entry 20. Source for entry 4.

[17] Skinner, B. F. (1956). A Case History in Scientific Method. American Psychologist, 11, 221-233. Skinner's experimental work on operant conditioning established that variable-ratio reinforcement schedules (rewards delivered on an unpredictable pattern) produce stronger and more persistent behavioural conditioning than fixed-ratio or continuous reinforcement. The 1956 paper is the methodological retrospective in which Skinner walks through how the research programme developed. The relevance to the post is that variable-ratio reinforcement is the mathematical foundation beneath slot machines, intermittent abuse, and engagement-driven software, and the same circuit produces the same persistence regardless of the reward type. Supporting evidence for entries 4 and 20.

[18] Dutton, D. G., & Painter, S. L. (1981). Traumatic Bonding, The Development of Emotional Attachments in Battered Women and Other Relationships of Intermittent Abuse. Victimology, 6(1-4), 139-155. Dutton and Painter applied Skinner's intermittent-reinforcement framework to abusive intimate relationships and proposed traumatic bonding as the mechanism by which victims remain emotionally attached to perpetrators long after the abuse is recognised. Their follow-up work tracking battered women after leaving the relationship found that the emotional attachment persisted at remarkably high levels even ten months after physical separation, with the bond strength correlating with the degree of intermittent positive treatment during the relationship rather than with the severity of the abuse. The framework is the post's anchor for the trauma-bond analogy in entry 20. Source for entries 4 and 20.

[19] Lifton, R. J. (1961). Thought Reform and the Psychology of Totalism, A Study of "Brainwashing" in China. Norton. Lifton was a young psychiatrist who interviewed Western prisoners of war released from Chinese reeducation programmes after the Korean War, and Chinese citizens who had been through the broader civilian campaigns. The book distils the eight criteria of thought reform (milieu control, mystical manipulation, demand for purity, the cult of confession, sacred science, loading the language, doctrine over person, and dispensing of existence), which have held up remarkably well across the subsequent sixty-five years of cult-studies, totalitarianism research, and high-control-group analysis. The post leans on the eight criteria as a checklist that maps onto contemporary engineered information environments more cleanly than it should. Source for entry 5.

[20] Goffman, E. (1961). Asylums, Essays on the Social Situation of Mental Patients and Other Inmates. Anchor Books. Goffman coined "total institution" for any establishment that handles all of a person's daily activities (sleep, work, leisure, relationships) inside a single bounded environment under a single authority. His four original categories were institutions for incapacitated people, institutions for the mentally ill or otherwise stigmatised, institutions enforcing physical or administrative confinement, and institutions of voluntary retreat such as monasteries. The mechanism Goffman named is the restructuring of the self that occurs because every interaction the inmate has runs through the same authority. The post leans on the framework because contemporary all-in-one workplace ecosystems and high-integration intimate relationships exhibit the same mechanism with softer edges. Source for entry 6.

[21] Bernays, E. L. (1928). Propaganda. Horace Liveright. Bernays was Freud's nephew and the architect of what became the public-relations industry. Propaganda is striking for how openly the case is made, that the conscious and intelligent manipulation of the organised habits and opinions of the masses is, in Bernays' phrase, an important element in democratic society, and that the invisible men who pull the wires which control the public mind are doing necessary work. The book documents the application of psychoanalysis-derived techniques to commercial advertising and political campaigns, with Bernays' own case material from selling cigarettes to women (the Torches of Freedom campaign), Lucky Strike, and the United Fruit Company. Worth reading because the present-day attention economy is the version Bernays would recognise. Source for entry 7.

[22] Lippmann, W. (1922). Public Opinion. Harcourt, Brace and Company. Lippmann's argument is that the public cannot form opinions about most matters of consequence by direct contact with the surrounding reality, and instead operates with mental images, stereotypes, and partial information selected and packaged by intermediaries. The "manufacture of consent" doctrine Lippmann names is the philosophical antecedent to Bernays' practical application. The post leans on Lippmann for the long-running observation that the gap between the world and the user's picture of it is not new, and that the manipulation industry has always operated in that gap. Supporting evidence for entry 7.

[23] Packard, V. (1957). The Hidden Persuaders. David McKay. Packard was a journalist who documented the rise of motivational research, the post-war industry that took Bernays seriously and applied depth-psychology techniques to consumer goods, political campaigns, and corporate communications. The book is a popular-press exposé rather than a research monograph, and the empirical claims have been criticised in places, but the historical record it preserves is what matters, by 1957 a recognisable advertising-industrial complex was already deploying ego, anxiety, sexuality, and social conformity as design surfaces for product placement. The post leans on the historical timing, the techniques predate consumer software by half a century. Supporting evidence for entry 7.

[24] Le Bon, G. (1895). The Crowd, A Study of the Popular Mind. Originally published as Psychologie des Foules. Le Bon's argument is that individuals embedded in a crowd lose their critical faculties and acquire the suggestibility, emotional contagion, and impulsiveness of the group. The book has been criticised in detail for its conservative politics and its anecdotal methodology, but the core observation, that group membership reduces individual epistemic independence, has been replicated in twentieth-century social psychology (Asch, Sherif, Milgram) and is the deep root of the manufactured-consensus techniques the persuasion industry deploys today. Supporting evidence for entry 7.

[25] Cialdini, R. B. (1984). Influence, The Psychology of Persuasion. HarperCollins, with revised editions in 1993, 2007, and 2021. Cialdini consolidated three decades of social-psychology research into six principles of influence, reciprocity, commitment and consistency, social proof, authority, liking, and scarcity, that underlie most everyday persuasion. The contribution that matters for the post is the framing of each principle as a normally-functional cognitive heuristic that has been hijacked by deliberate design, the same heuristic that lets the user make reasonable decisions efficiently in low-stakes situations gets fired by engineered cues in high-stakes commercial contexts. Cialdini added a seventh principle, unity, in the 2021 revision. Source for entry 8.

[26] Asch, S. E. (1951). Effects of group pressure upon the modification and distortion of judgments. In Groups, Leadership and Men (H. Guetzkow, ed.). Carnegie Press. Plus Asch, S. E. (1956). Studies of independence and conformity, A minority of one against a unanimous majority. Psychological Monographs, 70(9), 1-70. The classic line-judgement experiments, in which participants were placed in groups where confederates gave a unanimous wrong answer to a perceptual task, and a substantial fraction of naive participants conformed to the wrong answer at least once. The headline number, 75% conformed at least once and 36.8% of all trials produced a conforming wrong answer, is the empirical baseline for how much social pressure changes the user's relationship with their own perception. The relevance to the post is that the conformity effect is the cognitive substrate that anchoring, social-proof dark patterns, and filter bubbles operate against. Supporting evidence for entry 8.

[27] Milgram, S. (1963). Behavioral Study of Obedience. Journal of Abnormal and Social Psychology, 67(4), 371-378. The original obedience experiments at Yale, in which 26 of 40 participants (65%) administered what they believed to be lethal 450-volt shocks to a confederate under instruction from an authority figure in a lab coat. The methodology has been critiqued in detail (Gina Perry's 2013 reanalysis of the original tapes is the most thorough), but the headline result has been replicated cross-culturally and the bound on what people will do under instruction has stayed remarkably consistent. The relevance to the post is that the authority heuristic Cialdini names is the same circuit Milgram measured, and the circuit is older than any specific institution that exploits it. Supporting evidence for entry 8.

[28] Festinger, L. (1957). A Theory of Cognitive Dissonance. Stanford University Press. Festinger proposed that when a person holds two beliefs that conflict, or when a person's behaviour conflicts with their beliefs, the resulting psychological tension drives the person to change one of the two until the conflict resolves. The mechanism is bidirectional and asymmetric, behaviour is harder to change than belief, so beliefs usually move to match behaviour rather than the reverse. The relevance to the post is that the foot-in-the-door technique, the sunk-cost trap, and the consistency principle in Cialdini all run on dissonance reduction, the user has already acted, and now the beliefs follow. Supporting evidence for entries 8 and 22.

[29] Freedman, J. L., & Fraser, S. C. (1966). Compliance without pressure, the foot-in-the-door technique. Journal of Personality and Social Psychology, 4(2), 195-202. Freedman and Fraser demonstrated experimentally that securing agreement to a small request substantially increased the probability of agreement to a much larger subsequent request, with control conditions ruling out simple priming and trust effects. The headline experiment offered participants the chance to sign a small petition or display a small "drive carefully" sign, then weeks later asked them to install a large unsightly billboard on their lawn, with 76% compliance against 17% in the no-prior-request control. The relevance is that the persuasion industry uses the technique systematically (cookie consent, the "free" tier, the small in-app purchase), and the technique pre-dates the industry by decades. Supporting evidence for entry 8.

[30] Cialdini, R. B., Vincent, J. E., Lewis, S. K., Catalan, J., Wheeler, D., & Darby, B. L. (1975). Reciprocal concessions procedure for inducing compliance, the door-in-the-face technique. Journal of Personality and Social Psychology, 31(2), 206-215. The mirror-image of foot-in-the-door. Cialdini and colleagues demonstrated that making an extreme initial request that is rejected substantially increased compliance with a more moderate follow-up request, compared to making only the moderate request directly. The effect is anchored in the social norm of reciprocation, the requester has appeared to concede, and the responder feels pressure to concede in turn. The post leans on the technique as an example of how engineered cues fire heuristics that evolved for genuine social exchange. Supporting evidence for entry 8.

[31] Mathur, A., Acar, G., Friedman, M. J., Lucherini, E., Mayer, J., Chetty, M., & Narayanan, A. (2019). Dark Patterns at Scale, Findings from a Crawl of 11K Shopping Websites. Proc. ACM Hum.-Comput. Interact. 3(CSCW), Article 81. Princeton-led automated crawl of 11,286 e-commerce websites that identified 1,818 dark-pattern instances across 15 types in 7 categories (sneaking, urgency, misdirection, social proof, scarcity, obstruction, and forced action). The paper found that more popular sites were more likely to feature dark patterns, that many appear to be deployed by third-party platforms rather than the sites themselves, and that several rely on deceptive content (fake low-stock counters, manufactured countdowns, fabricated activity messages). The relevance is the empirical anchor on the prevalence and the demonstration that the practices are now industrial rather than artisanal. Source for entry 9.

[32] Gray, C. M., Kou, Y., Battles, B., Hoggatt, J., & Toombs, A. L. (2018). The Dark (Patterns) Side of UX Design. Proc. CHI 2018. The taxonomic complement to Mathur et al. Gray and colleagues analysed designer-community discussions and produced a five-category taxonomy of dark patterns (nagging, obstruction, sneaking, interface interference, forced action) that has been widely adopted in regulatory contexts (EU consumer law guidance, FTC enforcement). The contribution the post leans on is the demonstration that practitioners recognise the patterns by name and discuss them as craft, which forecloses the defence that any specific deployment is an accident. Supporting evidence for entry 9.

[33] Tversky, A., & Kahneman, D. (1974). Judgment under Uncertainty, Heuristics and Biases. Science, 185(4157), 1124-1131. The foundational paper on the cognitive biases that bookended Kahneman's career and produced his Nobel Prize. Anchoring is one of three biases the paper formally introduced, with the demonstration that participants asked to estimate an unknown quantity were systematically biased toward an arbitrary initial number, even when the number was patently irrelevant (the experimenters spun a wheel of fortune in front of them). The bias persists when participants are warned it will be present, persists when they are paid for accuracy, and persists when the anchor is implausible. The relevance is that anchoring is the cognitive substrate the framing industry operates against. Source for entry 10.

[34] Lakoff, G. (2004). Don't Think of an Elephant! Know Your Values and Frame the Debate. Chelsea Green. Lakoff's argument applies the anchoring principle to political discourse. The frame inside which a question is asked typically determines the answer more than the evidence available, because the frame closes off the questions that fall outside it. The contribution the post leans on is the framing-as-foreclosure mechanism, the most consequential exploitation is not the answer the user gives but the questions the user no longer thinks to ask. Lakoff's specific political claims have been criticised on the merits, but the cognitive linguistics behind the argument is widely accepted. Supporting evidence for entry 10.

[35] Goffman, E. (1959). The Presentation of Self in Everyday Life. Anchor Books. The foundational dramaturgical account of social interaction, with the self treated as a performance organised around accepted roles, and identity emerging from the audience's interpretation as much as from the performer's intention. The relevance to the post is the failure mode Goffman names, in which the role calcifies and the person disappears inside it, with the user no longer able to distinguish themselves from the version they have been performing. The catalogue's identity-capture entry leans on the calcification mechanism specifically. Source for entry 11.

[36] Erikson, E. H. (1968). Identity, Youth and Crisis. Norton. Erikson's developmental framework, with identity formation as a continuous process across the lifespan rather than a problem of adolescence to be solved once. The contribution the post leans on is the claim that the self is supposed to update as the person changes, and the failure mode is calcification, the person locked into a description that no longer fits but is held in place by their own decisions, their relationships, and the institutional records that have catalogued who they were. Supporting evidence for entry 11.

[37] Salvi, F., Horta Ribeiro, M., Gallotti, R., & West, R. (2025). On the conversational persuasiveness of GPT-4 with personalisation. Nature Human Behaviour, 9(8), 1645-1653. A preregistered randomised controlled trial with 900 US participants debating sociopolitical topics either against another human or against GPT-4, in conditions with and without personalisation (the persuader given the opponent's age, gender, ethnicity, education level, employment status, and political affiliation). The headline finding is that GPT-4 with personalisation was significantly more persuasive than humans across the asymmetric conditions, with the odds of post-debate agreement increased by 81.2% relative to humans, while GPT-4 without personalisation was statistically indistinguishable from humans. The marginal cost of personalisation is effectively zero. The relevance is the empirical anchor for entry 13. Source for entry 13.

[38] Pariser, E. (2011). The Filter Bubble, What the Internet Is Hiding From You. Penguin. Pariser coined "filter bubble" for the effect of personalisation algorithms on the information environment, with the user shown a curated stream that drifts toward whatever the algorithm has learned the user reliably reacts to. The book documents early evidence from Google personalised search results, Facebook News Feed, and Yahoo News, with the central claim that the curators have objectives the user does not share and the curation drifts toward whatever maximises the curator's metrics. The literature since has produced more nuanced findings (Bakshy et al. below) but the original framing remains the most cited account of the phenomenon. Source for entry 14.

[39] Bakshy, E., Messing, S., & Adamic, L. A. (2015). Exposure to ideologically diverse news and opinion on Facebook. Science, 348(6239), 1130-1132. Facebook's internal research on a sample of 10.1 million US users with self-declared political affiliations. The paper attempts to decompose the filter-bubble effect into three components, the composition of the user's social network, the news-feed ranking algorithm, and the user's own click decisions, and concludes that the user's own clicks are responsible for a larger reduction in cross-cutting content exposure than the algorithm itself. The paper has been heavily critiqued for the sampling restriction to politically self-identified users and for methodological choices that minimise the algorithm's measured contribution, and the authors' institutional positions at Facebook have been treated as relevant. Even with those critiques, the finding that the user's own engagement patterns contribute substantially to the bubble is a real result. Supporting evidence for entry 14.

[40] Kosinski, M., Stillwell, D., & Graepel, T. (2013). Private traits and attributes are predictable from digital records of human behavior. PNAS, 110(15), 5802-5805. A Cambridge-led study of 58,466 US Facebook users who had taken personality tests and agreed to share their Facebook Likes. Logistic regression on the Likes alone predicted sexual orientation (88% accuracy for men, 75% for women), ethnicity (95%), political affiliation (85%), religion (82%), use of addictive substances (65-73% across categories), parental divorce by age 21 (60%), age (correlation 0.75 with self-report), and personality factors (correlations 0.30-0.43 with self-report). The headline implication, which the surveillance-capitalism literature builds on, is that the user's revealed preferences contain more information about who they are than the user has knowingly disclosed. Source for entry 15.

[41] Youyou, W., Kosinski, M., & Stillwell, D. (2015). Computer-based personality judgments are more accurate than those made by humans. PNAS, 112(4), 1036-1040. Follow-up to Kosinski 2013 with the same Cambridge dataset. The paper compared algorithmic personality judgements (based on Facebook Likes) against personality judgements made by the user's friends, family, partners, and spouses. With 10 Likes the algorithm matched the average work colleague. With 70 Likes it matched the average friend or roommate. With 150 Likes it matched the average family member. With 300 Likes it outperformed the user's spouse. The result is the empirical anchor on the claim that the user can be modelled from public traces more accurately than the user can be modelled by people who know them. Supporting evidence for entry 15.

[42] Hackenburg, K., & Margetts, H. (2024). Evaluating the persuasive influence of political microtargeting with large language models. PNAS, 121, e2403116121. Oxford-led RCT testing whether LLM-generated political messages tailored to individual psychometric profiles (the Cambridge Analytica recipe, automated) were more persuasive than untargeted versions. The finding was that personalisation produced a small but statistically significant additional persuasive effect, and that the cost of producing personalised content with LLMs is effectively zero compared to the cost of mass-produced political content. The paper is careful, the population-level effect is modest, the per-target precision is unprecedented, and the strategic implication is that microtargeting is now affordable for any campaign with API access. Supporting evidence for entry 15.

[43] Zuboff, S. (2019). The Age of Surveillance Capitalism, The Fight for a Human Future at the New Frontier of Power. PublicAffairs. Zuboff's argument is that the contemporary platform economy is not selling user data, it is selling predictions of user behaviour into markets that profit from those behaviours becoming more predictable. The platform has a structural commercial interest in nudging the user toward the predicted behaviour rather than discovering it, which inverts the user's relationship with the platform from customer to raw material. The book is long, comprehensive, and frequently contested in detail, but the core framing has become the standard analytic vocabulary for the political-economic critique of the attention industry. Source for entry 16.

[44] Veliz, C. (2020). Privacy Is Power, Why and How You Should Take Back Control of Your Data. Bantam Press. Veliz, a philosopher at Oxford, develops the political and ethical implications of the surveillance-capitalism framework. The argument the post leans on is that privacy is not primarily an individual interest in concealment but a collective interest in the distribution of power, when one party knows the other's behavioural patterns, preferences, and weaknesses while the reverse is not true, the asymmetry produces a power relationship regardless of whether either party intended one. The relevance is that the catalogue is partly a list of asymmetries the user did not consent to. Supporting evidence for entry 16.

[45] Han, B.-C. (2017). Psychopolitics, Neoliberalism and New Technologies of Power. Verso. Originally Psychopolitik, Neoliberalismus und die neuen Machttechniken. S. Fischer (2014). The Continental-philosophy version of the surveillance-capitalism critique. Han's argument is that contemporary power operates not through disciplinary surveillance from outside but through the user's own internalised optimisation, the user becomes their own surveillance officer through the metrics of self-improvement, productivity, wellness, and personal brand. The book is short and aphoristic, but the framing of voluntary self-quantification as the most effective form of control over the user's behaviour is the angle the post leans on. Supporting evidence for entry 16.

[46] Foucault, M. (1975). Discipline and Punish, The Birth of the Prison. Originally Surveiller et punir, Naissance de la prison. Gallimard. Translated by Alan Sheridan (1977). Foucault's analysis of the shift in penal practice from public spectacle to bureaucratic confinement traces how surveillance, drawing on Bentham's Panopticon as the architectural model, becomes the central organising principle of modern institutions. The mechanism Foucault names is that a person who knows they might be watched, even when they are not, gradually behaves as if they always are, and the behaviour becomes the self rather than a performance of it. The catalogue's surveillance-internalisation entry leans on the mechanism directly, with a personal AI in the kitchen functioning as the panopticon's domesticated descendant. Source for entry 17.

[47] Lyon, D. (2018). The Culture of Surveillance, Watching as a Way of Life. Polity. Lyon updates the Foucauldian framework for the consumer-software era, with attention to how surveillance has been domesticated, gamified, and aestheticised, from doorbell cameras to fitness trackers to social-media check-ins. The contribution the post leans on is the observation that contemporary surveillance is no longer experienced primarily as imposition, it is increasingly desired, performed, and self-administered, which is the precondition for the internalisation mechanism the catalogue's entry 17 names. Supporting evidence for entry 17.

[48] Alter, A. (2017). Irresistible, The Rise of Addictive Technology and the Business of Keeping Us Hooked. Penguin Press. Alter is a psychologist at NYU Stern. The book covers the consumer-software industry's adoption of Schüll-and-Eyal-style addictive design across the major categories of attention-economy products (social media, mobile games, streaming, dating apps), and includes interview material with industry insiders. The contribution the post leans on is the documentation of how the techniques moved from gambling to consumer software in the period roughly 2007 to 2017, and the demonstration that the practitioners describe their work in terms that match the addiction literature even when their employers' marketing does not. Supporting evidence for entry 18.

[49] Twenge, J. M. (2017). iGen, Why Today's Super-Connected Kids Are Growing Up Less Rebellious, More Tolerant, Less Happy, and Completely Unprepared for Adulthood. Atria. Twenge is a generational psychologist who has analysed large-sample longitudinal datasets across multiple US adolescent cohorts. The book's contribution is the empirical observation that mental-health outcomes (depression, anxiety, self-harm, suicide) for the cohort that came of age with smartphones (born roughly 1995 onwards) deteriorated substantially compared to earlier cohorts, with the timing tracking smartphone adoption rather than other plausible candidate causes. The causal claim has been contested in detail (notably by Andrew Przybylski and Amy Orben), but the correlational pattern is robust and is the strongest population-level evidence on what saturated-attention-economy environments do to the people inside them. Supporting evidence for entry 18.

[50] Fang, C. M., Liu, A. R., Danry, V., Lee, E., Chan, S. W. T., Pataranutaporn, P., Maes, P., Phang, J., Lampe, M., Ahmad, L., & Agarwal, S. (2025). How AI and Human Behaviors Shape Psychosocial Effects of Extended Chatbot Use, A Randomized Controlled Study. MIT Media Lab and OpenAI. arXiv:2503.17473. A four-week IRB-approved RCT with 981 participants assigned to one of four conditions (text vs voice chatbot, neutral vs engaging persona) on ChatGPT, with over 300,000 messages logged and validated psychosocial instruments administered weekly. The finding the post leans on is that voluntary daily use was the strongest predictor of psychosocial harm across all four conditions, with the heaviest users showing measurably higher loneliness, higher emotional dependence on the chatbot, lower socialisation with humans, and lower problematic-use awareness, regardless of which experimental arm they were in. The mechanism is not malice on the part of the system, the mechanism is engagement on the part of the user. Source for entries 19 and 20.

[51] Sunstein, C. R. (2001). Republic.com. Princeton University Press. Updated as #Republic (2017) and Republic, Divided Democracy in the Age of Social Media (2018). Sunstein's argument predates Pariser's filter-bubble framing by a decade and is broader, that consumer choice in the information environment, given sufficient personalisation and sufficient supply, will produce ideological echo chambers as a stable equilibrium, with the cost paid in deliberative-democratic capacity. The book is contested on the empirical claims (Bakshy et al. above gives the more nuanced picture) but is the foundational philosophical account, and is the source the (NEW PATTERN) entry on filter-bubble-of-one leans on for the architectural failure mode specifically. Source for entry 21.

[52] Arkes, H. R., & Blumer, C. (1985). The psychology of sunk cost. Organizational Behavior and Human Decision Processes, 35(1), 124-140. The foundational experimental work establishing the sunk-cost effect, in which decision-makers continue committing resources to a course of action because of prior investment rather than expected future return. Arkes and Blumer demonstrated the effect across hypothetical scenarios (the bowling-alley investment, the ski-trip choice, the research-and-development continuation) and showed that the bias persists when participants are explicitly warned about it. The relevance to the post is that the ghost is the most complete record of the user's prior investment in any given decision, and the same record that lets the ghost help can be the substrate that lets the ghost amplify the user's bias. Source for entry 22.

[53] Trivers, R. (2011). The Folly of Fools, The Logic of Deceit and Self-Deception in Human Life. Basic Books. Trivers is an evolutionary biologist whose 1976 foreword to Dawkins' Selfish Gene introduced the framework of self-deception as adaptive, the better the self-deceiver, the more convincingly they deceive others, because the conscious mind is not in on the deception and therefore does not leak signs of it. The Folly of Fools is the book-length elaboration. The relevance the post leans on is that the user has good evolutionary reasons not to tell the ghost the truth about themselves, and that a ghost equipped to surface the gap is removing a coping mechanism the user has been using for reasons the user is not consciously aware of. Source for entry 23.

[54] Clark, A., & Chalmers, D. (1998). The Extended Mind. Analysis, 58(1), 7-19. Clark and Chalmers argue that cognition does not stop at the skin, that mental processes that meet certain functional criteria (constant availability, automatic endorsement, easy accessibility, prior conscious endorsement) can legitimately include external artefacts like notebooks, calendars, and reference tools. The thought experiment of Otto, a man with Alzheimer's who uses a notebook to record information that Inga keeps in her biological memory, is the standard reference. The post leans on the framework for the prosthetic-grief entry, with the LocalGhost box functioning as the most extreme externalisation of cognition that has ever been technically available, and the implications for the cost of losing it. Source for entry 24.

[55] Sparrow, B., Liu, J., & Wegner, D. M. (2011). Google Effects on Memory, Cognitive Consequences of Having Information at Our Fingertips. Science, 333(6043), 776-778. Four experiments showing that participants who believed information would remain accessible (saved to a folder, retrievable from a computer) remembered the information itself less well, but remembered the location of the information better. The conclusion the authors drew is that the brain treats reliable external storage as a transactive-memory partner and offloads accordingly, which is mostly the correct thing to do. The relevance to the post is that the same offloading mechanism is what produces the prosthetic-grief effect at scale when the externalised storage holds the user's reasoning patterns, emotional clusters, and self-model. Source for entries 24 and 25.

[56] Ramachandran, V. S., & Hirstein, W. (1998). The perception of phantom limbs. Brain, 121(9), 1603-1630. The foundational synthesis of phantom-limb research, with the central observation that the cortical representation of a missing limb persists for years after amputation and produces vivid sensation of presence (and often pain) referred to the absent body part. The mirror-box treatment Ramachandran developed exploits the cortical persistence to renormalise the representation. The relevance the post draws is the partial analogy, when an externalised cognitive substrate becomes integrated to the point of cortical participation, removing it produces a recognisable absence that the user experiences as loss of self rather than loss of a tool. Supporting evidence for entry 24.

[57] Loftus, E. F. (1995). The formation of false memories. Psychiatric Annals, 25(12), 720-725. Plus Loftus, E. F., & Pickrell, J. E. (1995), The formation of false memories, and Loftus's broader body of work on misinformation effects. Loftus's experimental programme demonstrated that autobiographical memories can be implanted in adult participants through suggestive interviewing, with the implanted memories experienced subjectively as indistinguishable from real ones. The "lost in the mall" study (in which 25% of participants came to believe they had been lost in a shopping mall as a child after repeated suggestion) is the canonical case. The relevance is that biological autobiographical memory is reconstructive rather than archival, and a timestamped contemporaneous record from the ghost can displace the biological version in a way that is mostly correct factually and mostly wrong phenomenologically. Source for entry 25.

[58] Bartlett, F. C. (1932). Remembering, A Study in Experimental and Social Psychology. Cambridge University Press. The foundational source on schema-driven reconstruction in memory. Bartlett's "War of the Ghosts" experiments had British participants read a Native American folk tale and reproduce it from memory at intervals, and showed that the reproductions systematically drifted toward what was culturally familiar to the participants while losing what was culturally strange. The implication is that biological memory is not a recording, it is a reconstruction guided by the schemas the person already holds, with the schemas doing real work to make the past coherent with the present self. The post leans on the framework for the memory-laundering entry, in which the ghost's archival record overrides the schema's work. Supporting evidence for entry 25.

[59] McAdams, D. P. (2001). The psychology of life stories. Review of General Psychology, 5(2), 100-122. Plus McAdams (2008), Personal Narratives and the Life Story. McAdams's narrative-identity framework treats the self as a continuously revised story the person tells themselves, with the past selected, ordered, and interpreted in service of a coherent present identity and a projected future. The empirical work tracks how the same life events get retold differently as the narrator changes, and finds that the capacity for narrative revision predicts well-being across the lifespan. The relevance the post leans on is that a ghost with disproportionate access to the user's older narrative produces a downward pressure on revision, with the user shaped to remain the version the ghost is best at recognising. Source for entry 26.

[60] Doctorow, C. (2023). Tiktok's enshittification. Pluralistic, and the broader Doctorow corpus on platform decay. Doctorow names "enshittification" as the predictable three-phase trajectory of platforms, first they are good to users to build a user base, then they are good to business customers at the expense of users to extract value from the user base, then they are good to themselves at the expense of both, until the platform has extracted all the value it can and the cycle ends. The framework was already referenced in POST_02. The catalogue's continuity-dependence entry leans on the trajectory directly, the user's coupling to the box is the asset that the late-stage version of the trajectory monetises. Supporting evidence for entry 27.

[61] Elster, J. (2000). Ulysses Unbound, Studies in Rationality, Precommitment, and Constraints. Cambridge University Press. Plus Elster, J. (1979). Ulysses and the Sirens, Studies in Rationality and Irrationality. Cambridge University Press. Elster's two books are the foundational philosophical treatment of precommitment, the rational strategy of binding your own future choices in advance to guard against a predicted later weakness of will. The name comes from Odysseus ordering his crew to tie him to the mast and to refuse any later command to release him, so that he could hear the Sirens without steering the ship onto the rocks. The argument the post leans on is that self-binding is an expression of autonomy rather than a violation of it, because the present self constraining the future self is a decision the person makes, which is categorically different from an external system deciding to constrain them. The same structure appears in medical ethics as the Ulysses arrangement for psychiatric advance directives, where a patient consents in advance to treatment during a future episode in which they are predicted to refuse it. Source for the user-opt-in enforcement carve-out in sections 2, 5, and 6.

An Index Is Not a Person

2026-04-28T00:00:00Z

They measure you, they reduce the measurements, they sort you into a bucket, and they sell the bucket.

I bought a Samsung Galaxy Watch in December and I've been reading my sleep numbers every morning since. Hours in bed, time to sleep onset, REM percentage, deep sleep minutes, awake events. Those numbers are legible. I don't check the Energy Score. Samsung's stated inputs are physical activity, sleep quality, sleeping heart rate, and sleeping heart rate variability, adjusted for age and gender, with weightings the company will not publish (the model has opinions about me I don't get to read) [1]. What Samsung calls my Energy Score is a comparison to other thirty-nine-year-old men, with the reference class baked in. If I sleep six hours and the model's population of men my age sleeps six and a half, my number falls. The individual at the centre of the score is a statistical fiction assembled from cohort data, and the person wearing the watch is being nudged toward that fiction's midpoint every morning.

Oura calls it Readiness [3], Whoop calls it Recovery [4], Garmin calls it Body Battery [5], Apple has a suite. Each one a single number, each one presented as a personal reading, each one running the same machinery. Doherty et al., a 2025 systematic review across fourteen of these scores from ten manufacturers, found that none of the companies disclose their algorithms, though 86% of the scores rely on heart rate variability, 79% on resting heart rate, and 71% on activity and sleep duration [2]. The score is a vehicle for something else.

> 1. When a reduction is honest

I spent most of the last decade building indices for a living (which is a strange way to spend a decade and probably the only thing that lets me write this post with any authority). The work I led for most of that time was CryptoCompare's aggregated price index, CCCAGG [6], which constructs a single digital-asset price (Bitcoin, Ethereum, etc.) by volume-weighting trades across roughly three hundred exchanges, with constituents reviewed monthly against published thresholds and the whole thing regulated under the UK Benchmark Regulation [7]. The methodology is published, an auditor can take the raw tick data, apply the documented rules, and reproduce the index. That is the shape of an honest reduction.

A published index with audited constituents and a reproducible methodology does honest work because the aggregate is the referent. A Bitcoin price is genuinely a distributed quantity, trading on many venues at many prices at any given moment, and there is no single correct price outside the one an aggregator constructs. The reduction loses nothing essential because the essential thing, a consensus price across a fragmented market, did not exist before the index constructed it. Reductions can be correct, audited, and useful when the referent is real and the construction is open.

> 2. The wellness score is none of these things

The wellness score borrows the shape of an index without accepting any of the obligations. There is no distributed quantity called readiness the way there is a distributed quantity called a Bitcoin price. Readiness is something the model invents, not something it measures, and the number on the wrist is pointing at nothing outside the model that produced it. The weightings are not published, the methodology is not reproducible, and no regulator is auditing the construction.

The wellness score borrows the authority of an index without accepting any of the obligations that let one be useful.

> 3. Where bucketing comes from

Bucketing is not a corporate invention. Humans bucket each other constantly, the moment we see someone, before they have spoken. Tall, short, old, young, well-dressed, scruffy, threatening, safe. The classifier fires before we have time to consent to it firing, it is right often enough to have survived as an evolutionary tool, and it is sometimes wrong about the specific person in front of us, and most of the time we never find out either way, because we never speak to them long enough for the data to override the prior. The bucketing is instinctive and load-bearing for navigating public space. I am not going to pretend I do not run it, I run it, and everyone reading this does too.

What rescues the human version is that the bucket dissolves on contact. In 2014, a colleague of mine, Gordan, came round when I was recovering from a bike accident that broke my jaw and a few teeth. Gordan is a big man with a busy beard, full leather gear, more skulls on him than I can count, and a helmet with the word "Hell" on it. While he was at the flat he saw our cat Melly, then a small kitten, picked her up, and was the gentlest, most patient person with her I have ever watched. He sat on the sofa with this small kitten on his chest until he had to leave. The bucket my housemates at the time ran on Gordan when they saw him dissolved in about ninety seconds (and I think about this every time I catch my classifier firing on someone). The version of him that exists in their head now is the version with my kitten on his chest.

The human bucketing is imperfect, sometimes badly so, but it has a self-correcting loop. The loop is the conversation, the time spent, the cat on the chest. The bucket stays open to revision because everyone is regularly mis-bucketed and everyone has had a bucket dissolve when someone showed up.

> 4. What the score is for

The wellness score is bucketing with the self-correcting loop removed. There is no conversation, no time spent, no version of the user that gets to dissolve the bucket by showing up. The score updates when the company decides to update its model, on the company's schedule, against the company's incentives, and the user has no handle. What the user gets handed is the bucket placement, dressed up as a personal reading.

The score is the user-facing artefact, the bucket is the commercial artefact, and the two are connected by design.

Samsung's published privacy policy for Samsung Ads states that the service may show personalised ads based on "demographic characteristics, preferences, choices, and interests", by collecting information about online activities across Samsung and third-party platforms [8]. The general Samsung privacy policy says the company uses the information it collects for personalised and generalised advertising and direct marketing on behalf of Samsung and its partners [9]. The Customization Service combines health data with account data, app usage, browsing history, and inferred interests to send customised marketing across a user's devices [10]. The health data feeds the targeting, and the score is where the targeting becomes legible.

This pattern is not limited to Samsung. Every wellness platform, every fitness app, every calorie tracker, every sleep product runs some version of the same machinery. The bucket you have been placed in determines which in-app upsell you see, which notification arrives, which supplement gets recommended, which premium tier you are nudged toward. The score is the interface and the bucket is the product.

The same shape repeats across the rest of the consumer economy with sharper teeth. FICO's credit-based insurance scores are used by roughly 95 percent of US auto insurers and 85 percent of homeowners insurers to bucket policyholders by claim-likelihood, with a correlation between credit data and insurance loss that FICO itself admits is empirical rather than causal [11]. Your premium goes up not because of anything you did, but because of which bucket the model placed you in. The same pattern shows up wherever a company has enough data about enough people to run a classifier, from Spotify's mood clusters [12] to Netflix's taste profiles [13] to banks' wealth segments. The bucket is the commercial product, the number shown to the user is the interface.

The score on your wrist tells you which bucket you are in. It does not tell you about you.

The comparison itself is not the harm. Knowing you are taller or shorter than the average person in a room does not damage you, and a wellness app that quietly notes you sleep less than the average thirty-nine-year-old man is not, in itself, doing anything terrible. The harm is the bucket being run on you without consent, used to identify when you are vulnerable, and sold to people whose interests are not yours, while the app virtue-signals about how much it cares about your wellbeing. The score is what the comparison feels like from the inside, the bucket is what the comparison is for, and the gap between the two is where the user gets quietly worked.

The harm is not in the bucketing instinct, the instinct is human and not the enemy. The harm is in the industrial scale-up of the instinct without the self-correcting loop the human version always had. There is no equivalent of Gordan walking into the room with the cat. The score does not update because you protested, the bucket does not dissolve because you showed up, the classifier keeps firing on its prior, and the user keeps being treated as a member of a category they were placed in by a model they did not see, optimised for outcomes that were never theirs.

Leaderboards are the variant with social comparison grafted on. Apple Watch competitions, Strava segment rankings, every fitness app's weekly challenges. The ranked presentation produces more engagement than a static number, and more engagement is what the platform is optimising for. The user is both the measured and the measuring stick.

> 5. What the ghost does instead

A ghost that runs on your hardware, reasoning only from your data, has no cohort and no population to compare you against. It cannot tell you how your sleep compares to other people your age because it has no data on other people your age, and it is not going to get any. The architectural commitment that makes LocalGhost private makes it also non-comparative. There is no Energy Score the ghost can produce, no cohort segmentation it can hand to an advertiser, no bucket.

The ghost's refusal to hold a cohort is the refusal of the whole arrangement.

What the ghost does instead is describe you in terms of yourself. Your sleep this week is worse than three weeks ago by measurements you already trust. Your commit activity dropped around the same time your sleep did. Those are answers from your own data to questions about your own life, and the bucket the ghost places you in is yours. This is the architectural version of the bucket dissolving on contact, except the contact is with your own data instead of with a kitten on a sofa.

The ghost still reduces, it has to. The question is not whether reductions happen but whether they are legible, editable, and under the user's control. Every summary the ghost produces is a view, not a fact, and the raw context stays. If the ghost says you've been off this week, you can ask why, and the answer is the reasoning and the data points the ghost leaned on, not a reconstituted score. If the reasoning is wrong, you can correct it, and the category the ghost has placed you in is editable, and the model the ghost holds of you is something you can argue with. The loop the commercial version stripped out is the loop the ghost puts back.

Cohort comparison is sometimes the only way to catch what a personal baseline cannot. Apple Watch's atrial fibrillation detection works because it knows what a normal sinus rhythm looks like across millions of hearts, and the same goes for illness-onset signals, sleep apnoea screening, and the early signature of overtraining syndrome in HRV. The medical utility is real, and three weeks of your own baseline is not enough data to know what is normal for a human body versus what is normal for your body in trouble. The wellness industry's mistake is pairing the statistical tool with an ad pipeline by default, as if the cohort cannot be delivered without the user attached. A consensual cohort, locally applied and severable from any commercial system, is a different architecture and a future post.

> 6. How divergence replaces comparison

There is one kind of comparison the ghost can legitimately perform. The ghost can compare itself to itself. Run the same question through the ghost twice, once with memory and once without, and the divergence between the two answers tells you how much the answer is leaning on context you supplied. Context can be wrong, misremembered, or stale, and the divergence is the signal that it might be. Run the same question against a different base model with the same inputs, and the divergence tells you how much the answer is specific to the model's priors rather than to your data. When the main ghost says one thing and shadowd, the adversarial sibling, says another, the gap is information about where the ghost's confidence is coming from.

That is the shadowd architecture. The comparison happens inside the ghost, with no external baseline, no cohort, and no population involved. The user is the reference, the ghost is the subject, and the comparison is between different ways the ghost can reason about the user.

I am not entirely sure this is enough on its own (if anyone has a better answer here please tell me, I am not married to mine). Detecting that the answer is load-bearing on context tells you the answer might be wrong, but it does not tell you which way it is wrong, and the user still has to do the work of looking at the raw data and deciding. The shadowd architecture as currently designed flags the divergence and surfaces the reasoning that produced it, and whether that is enough or whether the ghost needs a richer set of disagreement signals is a thing I expect to keep iterating on for a while.

> 7. Why the architecture refuses the bucket

The architecture refuses the bucket. Not as a temporary state, not as something that gets added once the project finds its footing. There is no bucket sold to advertisers, no baseline imported from people you did not consent to share with, no comparative reading dressed up as a personal one. The ghost works for one person because the one person is the reference, and any version of this that sorts you against other people without your consent is the thing the rest of this post is arguing against.

A cluster of ghosts that ranks users against each other is every commercial product I am refusing to build.

Single-user fragility is the correct state, full stop. A system that has not earned the right to describe one person honestly has definitely not earned the right to rank millions of them against each other. The commercial platforms skipped the first step and went straight to the segmentation economy, which has been going about as well as you would expect for everyone except the people selling the segmentation.

> 8. What's next

The individuality argument is the argument under all the others. The manifesto argued for sovereignty at the data layer, the Model Trap argued for sovereignty at the model layer, How Memory Gets Made argued for sovereignty at the memory layer, and this post argues for sovereignty at the interpretation layer, the last layer the consumer platforms still own and the layer where the most damage gets done.

The reductions any system performs about a person should be inspectable and rejectable, the buckets it places someone in should be visible and editable, and the comparisons it draws should be to the person and not to a cohort imported from somewhere they did not consent to. Most consumer products do not work this way, and the ones that do not are not failing at the design, they are succeeding at a different design, the one that turns the user into a sortable record. A ghost that respects the user has to refuse that design at the architecture level, because anything else replicates what already exists.

The architectural commitments are clear, the implementation is in progress, and the harder questions of what a useful description looks like when it cannot lean on a cohort are questions I expect to be working on for a long time.

The next post is about a different way the same architecture can fail. A ghost good enough to be useful is good enough to compete with the messy human contact a person needs, and if the ghost wins that competition every time, the user ends up alone with a daemon. The work is teaching shadowd to recognise low-friction spirals from tallyd's heart rate, screen time, and social pointers, and to sometimes refuse to help when a phone call or a game of squash would be better. Efficiency is often a polite word for social avoidance, and a ghost that respects the user has to know the difference.

I'm still wearing the watch, still reading the sleep numbers, still ignoring the Energy Score. What the ghost has to give me, and what I'm building it to give me, is the data without the score on top of it. [ localghost.ai // hard-truths ]

> REFERENCES

[1] Samsung Energy Score is calculated based on physical activity levels, sleep quality, sleeping heart rate, and sleeping heart rate variability, with weightings adjusted for age and gender. Samsung Research developed the feature in collaboration with Professor Patrick O'Connor (University of Georgia, Mary Frances Early College of Education's Department of Kinesiology). The relative weightings of each input and the precise algorithm used to combine them are not publicly disclosed. Samsung Newsroom announcement of the methodology and University of Georgia collaboration at news.samsung.com/samsung-collaborates-with-university-of-georgia. Samsung Health product page describing Energy Score requirements and inputs at samsung.com/us/apps/samsung-health.

[2] Doherty, C., Baldwin, M., Lambe, R., Burke, D. & Altini, M. (2025). "Readiness, recovery, and strain: an evaluation of composite health scores in consumer wearables." Translational Exercise Biomedicine, 2(2), 128-144. Peer-reviewed open-access systematic evaluation of 14 composite health scores across 10 major wearable manufacturers (Coros, Fitbit/Google, Garmin, Oura, Polar, Samsung, Suunto, Ultrahuman, WHOOP, Withings). The paper concludes that "none of the manufacturers disclosed their exact algorithmic formulas, and few provided empirical validation or peer-reviewed evidence supporting the accuracy or clinical relevance of their scores," and identifies that 86% of the scores rely on heart rate and heart rate variability, 79% on resting heart rate, and 71% on physical activity and sleep quantity, with substantial variation in calculation methodologies despite shared inputs. DOI 10.1515/teb-2025-0001. Article HTML at degruyterbrill.com/teb-2025-0001.

[3] Oura Readiness Score is calculated from nine contributors including resting heart rate, HRV balance, body temperature, recovery index, sleep, sleep balance, sleep regularity, previous day activity, and activity balance, evaluated against personal baselines accumulated over up to two months. The score ranges from 0-100 with interpretive bands (Optimal, Good, Fair, Pay Attention). Oura's documentation describes the contributor weightings as proprietary and notes that long-term metrics are evaluated against "general recommendations for people of your age" alongside personal averages. Oura support documentation at support.ouraring.com/Readiness-Score. Contributor breakdown at support.ouraring.com/Readiness-Contributors.

[4] WHOOP Recovery is a daily 0-100 score nominally indicating how prepared the body is to adapt to physical and mental stressors. Inputs include heart rate variability (weighted approximately 85%), resting heart rate, sleep performance, and respiratory rate, with WHOOP 4.0 also incorporating blood oxygen levels and skin temperature. The proprietary algorithm integrates these inputs against personalised baselines using methods that WHOOP does not publicly disclose in detail. WHOOP also publishes Strain (logarithmic 0-21 scale combining cardiovascular and muscular load) and Stress Monitor (0-3 scale) using overlapping but distinct methodologies. WHOOP Recovery documentation at whoop.com/how-does-whoop-recovery-work. WHOOP Strain documentation at whoop.com/how-does-whoop-strain-work.

[5] Garmin Body Battery is a 0-100 energy estimate combining stress (derived from heart rate, resting heart rate, and HRV), activity levels, and sleep, computed by Firstbeat Analytics under licence to Garmin. Recent data is weighted more heavily than long-term data, and the specific weightings of each input are not publicly disclosed. Garmin also publishes Training Readiness, which integrates sleep score, recovery time, acute training load, HRV status, sleep history, and stress history into a separate 1-100 score with interpretive bands (Prime, High, Moderate, Low, Poor). Garmin Body Battery documentation at garmin.com/garmin-technology/body-battery. Training Readiness documentation at garmin.com/garmin-technology/training-readiness.

[6] CCCAGG (CryptoCompare Aggregated Price Index) was the flagship index produced by CryptoCompare/CCData during the author's tenure as co-founder and CTO. The index aggregates trade data across roughly three hundred exchanges using a twenty-four-hour volume-weighted average for every currency pair, with monthly constituent reviews that drop exchanges whose thirty-day average price difference or price impact exceeds published thresholds. The index sits alongside the Exchange Benchmark, which rates exchanges AA through F based on liquidity, quality, and trustworthiness of data. The methodology, the constituents, and the inclusion and exclusion thresholds are all published, the index is regulated under the UK Benchmark Regulation, and an auditor can take the raw tick data, apply the documented rules, and reproduce the index. CCData (formerly CryptoCompare) was acquired by CoinDesk in October 2024 and the index has since been renamed CCIX. Methodology document at downloads.coindesk.com/CCIX-Methodology.pdf.

[7] The UK Benchmarks Regulation (UK BMR) is the regulatory regime governing the provision of, contribution to, and use of financial benchmarks in the UK. The onshored BMR came into effect at 23:00 on 31 December 2020, regulating any publicly available figure that is regularly determined by formula or other calculation method, where that figure is used to determine amounts payable under financial instruments or to measure investment fund performance. Benchmark administrators must be FCA-authorised, must publish methodologies, must maintain governance and oversight functions, and must address conflicts of interest. The FCA Benchmarks Register lists 36 UK benchmark administrators and 10 third-country administrators as of November 2023. FCA Benchmarks Regulation page at fca.org.uk/markets/benchmarks/regulation.

[8] Samsung Ads Privacy Policy, source for the language describing how the Samsung Ads service uses "demographic characteristics, preferences, choices, and interests" to show personalised ads across Samsung and third-party platforms. Available at policy.samsungrs.com/policy_en_in.html.

[9] Samsung U.S. Privacy Policy, source for the company's stated use of collected information for personalised and generalised advertising and direct marketing on behalf of Samsung and its partners. Available at samsung.com/us/account/privacy-policy.

[10] Samsung Customization Service U.S. Privacy Notice, source for the description of how the Customization Service combines account data, app usage, search terms, and browsing history with health data to send customised marketing communications, including the explicit consent flow for "Improve personalized ads with Samsung account data". Available at terms.samsungconsent.com/CZSVC.

[11] FICO Credit-Based Insurance Scores were introduced by Fair Isaac Corporation in the early 1990s and are used by approximately 95 percent of US auto insurers and 85 percent of US homeowners insurers in states where the practice is permitted, according to FICO's own estimates. The scores use credit report data weighted as payment history (40%), outstanding debt (30%), credit history length (15%), pursuit of new credit (10%), and credit mix (5%) to predict the relative likelihood of an insurance claim, allowing insurers to "group consumers by risk and then adjust premiums up or down based on the risk category assigned." The correlation between credit data and insurance loss is empirical rather than causal, and FICO's own documentation acknowledges that "no one has ever investigated whether a causal relationship exists." FICO insurance scores product page at fico.com/insurance-scores. NAIC explainer of credit-based insurance scoring at content.naic.org/credit-based-insurance-scores. FICO methodology page at insurancescores.fico.com/HowScoringWorks.

[12] Spotify Ads gives advertisers audience targeting based on listening behaviours, interests, demographics, and "real-time context" derived from playlist activity. Spotify's Ad Studio documentation describes how the platform "identif[ies] user-curated and Spotify-curated playlists aligned with popular activities and moments" and "deliver[s] targeted messages to users who are listening to playlists in each category," allowing brands to align ad delivery with listener mood, activity, and setting. Spotify's contextual advertising materials describe its first-party streaming intelligence as data that "reveals moods, mindsets, habits, and tastes in the moment." Spotify Ads audience targeting overview at ads.spotify.com/audience-targeting. Ad Studio targeting options documentation at ads.spotify.com/help-center/targeting-ad-studio. Contextual advertising solutions page at ads.spotify.com/contextual-advertising.

[13] Netflix divides its global subscriber base into approximately 2,000 "taste communities" or "taste clusters" that group viewers based on observed viewing patterns rather than declared demographics. Netflix's product vice president Todd Yellin described these as "taste doppelganger" profiles that group people with shared content preferences across genre boundaries, with the company explicitly preferring behavioural clustering to demographic segmentation. Taste clusters inform recommendation surfaces, artwork personalisation, and content production decisions. Netflix originals product launch strategy team member Olivia De Carlo characterised one such cluster as connecting Lost, Black Mirror, and Groundhog Day through "this through-line of supernatural or extreme worlds." BuzzFeed News interview with Netflix product VP Todd Yellin describing taste community methodology at buzzfeednews.com/netflix-recommendation-algorithm. Quartz coverage of Netflix's 1,300 taste communities and the move away from geographic segmentation at qz.com/netflix-divides-users-into-1300-taste-communities.

The Integration Tax

2026-04-27T00:00:00Z

Every company that holds a verified picture of your financial life is compelled to either monetise it or fail. The architecture has to remove the company.

I was in Bucharest last weekend talking with Paul, our first employee at CryptoCompare, about the portfolio tool, and neither of us had touched it in any real way since 2017, when it had over a million monthly active users [2]. Real people tracking real holdings, with categorisations, rules and positions they'd spent time building. The data side of CryptoCompare kept growing through that period at exponential rates, and the portfolio got broader asset and exchange coverage as a side effect, so my reasoning when I agreed to deprioritise the portfolio product work was that we'd focus on getting the data right and come back once it was comprehensive enough. Later didn't come, and over years the users just moved on.

> 1. Why we never rebuilt it

The portfolio still works and still has users, and it hasn't been improved in nine years. Users type their holdings in manually, which means the data is a virtual portfolio rather than a verified ledger of what anyone holds. Adding auto-integrations to exchange APIs and wallet addresses would require encrypting real holdings at rest with user-held keys, so we'd have no access to the underlying data and neither would law enforcement, which sounds good until you realise it also means no aggregation, no cross-account debugging, no platform-wide stats, and no way to handle asset-level events at scale, things like token migrations, chain transitions, or time-sensitive actions that need pushing to every affected holder at once. On top of that, balance and account endpoints on exchange APIs are a lot less stable than pricing and trade endpoints, they version badly and break often, so auto-sync would have added a permanent maintenance burden on top of the rewrite. None of these are features you bolt on. Together they are a full product rebuild. And even if we funded that, encrypting with user keys would have made it impossible to sell anything to the user, because we wouldn't know what they held or how much of it. It would not have made financial sense.

I kept the portfolio alive by refusing to make it useful, and that was the right call given the incentive structure.

The structural reasons that kept us from rebuilding it are not unique to crypto or to us. They apply to anyone whose business depends on holding a verified picture of users' lives, which is why the same sequence shows up across every product in this category going back forty years.

> 2. Why the economics force the outcome

Every personal tracker has an integration tax. Banks change their export formats, APIs deprecate, OAuth scopes tighten, fitness platforms get acquired and rename their endpoints, health data vendors change their units, medical providers rotate their login flows, and the tax on all of it is paid in engineering time, forever, compounding with every integration the product adds. The first five integrations are a team-month, the next twenty are a team, the hundred after that are a department, and any serious aggregator ends up running an engineering function whose only job is keeping the existing integrations from rotting. We had a six-person team at CCData on exchange data integrations alone, and exchanges are the easy ones because they have engineering teams who care about API stability. Account integrations are harder, mostly because balance and account endpoints are used internally by the exchange's own product teams and external stability is nobody's priority.

The aggregation infrastructure between consumer trackers and source banks has the same problem at a larger scale. Yodlee, founded in 1999 as the consumer-PFM aggregation backbone that Mint and Money Dashboard ran on, sold to Envestnet in 2015 for $660 million [11] and pivoted to enterprise B2B because the consumer side couldn't sustain itself as a standalone product. Plaid is the modern equivalent, and its trajectory followed the same line. It agreed to a $5.3 billion acquisition by Visa in 2020 that the DOJ blocked on antitrust grounds [10], then reached a $13.4 billion private valuation by selling enterprise APIs to banks and fintechs rather than consumer experiences. The rails the consumer trackers run on are owned by businesses whose customers are the banks, not the people whose financial data flows through the pipes.

All of that cost has to come out of whatever the product generates, and across a decade of watching comparable products in comparable categories, users don't pay enough to cover the integration tax plus the team plus the hosting plus the compliance. The category survives in one of three ways. The product charges a subscription that most users cancel inside a year because the value is hard to feel month-to-month, and churn kills the team before the integrations can stabilise. Or the product gives up on direct revenue and monetises the data, selling anonymised transaction feeds to hedge funds, health metrics to insurers, behavioural signal to ad networks, which is the compromise an entire generation of free trackers ran on. Or the product hides a trading affiliate fee or a lending partnership inside the experience, its advice quietly bends around what earns the company revenue rather than what serves the user, and eventually it sells as a leads funnel to one of the big companies that needs those users. Blockfolio is the crypto version of that third path, the most popular portfolio tracker in the space, acquired by FTX in 2020 for $150 million in FTX equity (worth roughly zero by November 2022), rebranded as the FTX app, and being used to push leveraged trading products to its users by the time the exchange collapsed [12].

A fourth path exists and it does not work. The product ships honest, prices correctly for the work, gets undercut by a competitor running one of the three paths above, and either dies or pivots to one of the three paths itself.

This version of the product has been built many times and has never survived contact with a P&L.

> 3. What the record shows

What dies when a personal tracker dies is the interpretation layer the user built on top. The raw numbers are usually recoverable from source banks. The categorisation, the rules, the saved queries, the habits they wired up around the product's particular shape, all of that belongs to the user in the sense that nobody else made it, and it belongs to the company in the sense that the company's database is the only place it lives. When the company moves on, the layer goes with it, and the user is left with a CSV export and no way to reconstruct what they built.

Wesabe launched in November 2006, ten months before Mint, as the first personal finance tracker to attempt automatic transaction aggregation by building its own scraper rather than relying on Yodlee, which Wesabe's founders considered insufficient on privacy grounds. It led the category until Mint launched in September 2007 using Yodlee for its aggregation layer and shut down in July 2010 after burning through its raised capital and surviving nine more months on revenue alone [3]. Mint, which won partly because the Yodlee integration made onboarding faster, reached approximately twenty million active users at its 2016 peak, was acquired by Intuit in 2009 for $170 million, and shut down in March 2024 with users migrated to Credit Karma, which lacked equivalent budgeting, transaction rules, or custom categorisation [4]. The UK's largest personal finance manager, Money Dashboard, was acquired by ClearScore in 2022 and shut down in October 2023 with a closure statement saying the company "could not find a sustainable business model for the apps," after which ClearScore kept the open-banking infrastructure and rebuilt it as a B2B product called D•One, sold to lenders [5].

The longest-running personal tracker on record is Quicken, founded in 1983. Intuit sold it to H.I.G. Capital in 2016 after concluding it was "essentially a dead end," contributing $51 million to Intuit's $4.2 billion total revenue, and H.I.G. resold it to Aquiline Capital Partners in 2021. Quicken moved to mandatory subscription in 2018, with users trapped in a proprietary file format and integration quality declining year over year. Forty-three years in, it survives by holding its install base captive [6].

Personal Capital reached three million users on a free dashboard funded by AUM fees on the wealth-management business that paid the bills, and got absorbed into a $1T retirement provider in 2020 [7]. CoinTracker bundled the dashboard with crypto-tax filing, which is regulatory-mandatory in most jurisdictions, raised a $100 million Series A in January 2022 at a $1.3 billion valuation, and has not raised a follow-on round in the four years since [8]. The crypto-tax bundle is the closest thing the category has to a structural commercial advantage, but the runway clock is the relevant variable rather than the product quality. Personal Capital made the lead-magnet model work by being absorbed into a parent business that needed customer acquisition. CoinTracker hasn't found that parent yet.

Six trackers across forty years and two continents. Three shut down outright, one survives in proprietary captivity, one was absorbed into a wealth-management parent, and one is burning down its Series A on the way to one of the first three. None survived without compromise.

Every company that builds a tracker is one quarterly review away from killing what you built on top.

> 4. The architecture exists

Lefteris has been building Rotki for years [1]. It's a local-first portfolio tracker that runs on your hardware, keeps your data on your machine, is fully open source, and has no cloud dependency. The categorisation is yours and stays yours, the integrations are open source, and the export is whatever format you want. Rotki is the right architecture for the category.

It has struggled to get traction the entire time Lefteris has been building it, and not because the product is bad. The market for self-hosted portfolio tools is small, the price ceiling is modest, every integration is forever maintenance work against a revenue base that doesn't fund a team, and the users who would benefit most either don't know the product exists or wouldn't run a self-hosted thing if they did. The right architecture exists, built by someone who knows how to do it correctly, and it's fighting uphill against the same economics that pushed the CryptoCompare portfolio into nine years of standstill.

The portfolio I built at CryptoCompare had a million monthly active users and the wrong architecture. Rotki has the right architecture and a small fraction of the users. "User-friendly enough to win mass adoption" and "durable enough to survive its own creator" have never been the same product, and that's what I'm trying to make tallyd be, which is either the most ambitious thing I've ever signed up for, or the most naive.

The founders who built every product above thought the same thing. None of this is about bad actors. Every one of them launched with the genuine belief they would treat users better than the previous generation, and every one of them was either failed by the economics or compromised by the temptation to monetise the data they were holding. The architecture has to remove the company, because the company is what fails.

The next personal-data startup that promises to be different will fail you the same way.

> 5. What tallyd does differently

Tallyd is the part of LocalGhost that cares about the numbers of your life, transactions, holdings, heart rate, sleep stages, screen time, commits, weight, workouts, medications, all in one place because the interesting signal lives at the intersections between them. The rest of the fleet reads from it. Fifty to a hundred entries a day across forty years comes out to about a million rows, which is comfortable in any reasonable database, and Postgres handles a life today without drama. What it looks like in thirty years isn't a problem I need to solve now. The engineering this needs has always existed. A commercial reason to point it at one person never has.

Once a daemon knows your holdings, your cash flow, your goals, and your past decisions, it can push back when you're about to make a bad one. You think you want to buy more of a stock you've watched for months. Shadowd points out that you already have ninety percent of your portfolio in that industry. The fleet tells you what you're missing while you decide. No existing company can build this, because no existing company has a reason to talk you out of a trade.

We sell hardware and the software runs on donations, because the plan is to offer an alternative, not to make money from the data.

It's me and AI on tallyd right now (I'm a very optimistic person), and I am not pretending that's a stable position. The integration tax doesn't disappear. AI tooling drops the cost of writing a parser from weeks to hours, but the plugins that ship will be the ones I care about, and everything else waits for someone who cares enough to write it. If the project stalls, or I get hit by a bus, or I get excited about a new project (statistically the bus is the least likely), the data survives because it's on your hardware, the parsers stay open because they're on GitHub, and the categorisation is yours. There's no company here to fail.

A standard for portfolio data export exists. The OFX investment message set, shipped by Intuit, Microsoft, and CheckFree in 1997 and maintained by the Financial Data Exchange consortium [9], covers holdings, positions, and transactions. Almost no consumer tracker implements it as an export option, not because the standard is hard or the implementation is expensive, but because no company in the category has ever had a commercial reason to make leaving easier than staying. That's the thing tallyd gets to do by default.

Your data exports in open formats including JSON, CSV, and OFX where it applies, the day it lands and every day after.

> 6. What's next

Tallyd holds the stats across a life, owned by you, which raises a question I haven't figured out how to answer yet. The crypto-index work I did at CryptoCompare reduces a basket of correlated financial assets to a single tradable number, which is hard but tractable. Reducing a person to a number, where the inputs are a year of sleep, mood, decisions, holdings, commits, and weight, is a different kind of problem.

The technical part is real. The moral part is whether anyone should be reduced to a number, including by themselves, and whether having the data to do it changes the answer. That's the next post.

I don't know if tallyd ends up being the thing that cracks this category or just the next entry in a long list of products that tried. The architecture is right. Whether that's enough is what I'll find out. [ localghost.ai // hard-truths ]

> REFERENCES

[1] Rotki, an open-source local-first portfolio tracker built and maintained by Lefteris Karapetsas, a former Ethereum Foundation engineer. Rotki runs on the user's own hardware, holds the user's data locally, supports a wide range of exchanges and chains through open-source plugins, and offers a free tier alongside a premium tier funded by user subscriptions and donations. Rotki demonstrates that the right architecture for a personal tracker is buildable, and also demonstrates how hard it is to get traction for a self-hosted product against company-backed alternatives that monetise differently. Project site at rotki.com. Source code at github.com/rotki/rotki.

[2] The CryptoCompare portfolio tool reached over a million monthly active users by 2017. Source for the figure is the author's direct experience as CTO and co-founder of CryptoCompare during the period in question. The product remains live but has not been substantively redeveloped since 2017, with engineering effort redirected to the company's institutional data-licensing business (now operating as CCData following the CoinDesk acquisition announced 16 October 2024).

[3] Wesabe launched in November 2006, ten months before Mint, as the first online personal finance tracker to attempt automatic transaction aggregation. Founders Marc Hedlund and Jason Knight chose to build their own scraper rather than license aggregator Yodlee, citing privacy concerns about Yodlee's handling of user credentials. The company raised $4.7M across two funding rounds, reached profitability on revenue alone for nine months between November 2009 and July 2010, and shut down in July 2010. Hedlund's post-mortem "Why Wesabe Lost to Mint" attributed the loss in significant part to user-experience differences arising from the data-aggregation choice. Source for the launch order, the Yodlee decision, the funding history, and the founder's post-mortem framing. Hedlund's post-mortem is preserved at Medium (originally published at Precipice). Additional company history and timeline verification at Failory.

[4] Mint launched September 2007 at the inaugural TechCrunch 40 conference and was acquired by Intuit in November 2009 for $170 million. The product reached approximately 20 million active users at its 2016 peak, declining to 3.6 million by 2021 according to Bloomberg. Intuit announced the shutdown in November 2023 and completed the sunset on 23 March 2024. Users were directed to migrate to Credit Karma, also owned by Intuit, which preserved net worth and a subset of transaction history but did not replicate Mint's budgeting, transaction rules, or custom categorisation. Source for the acquisition price, peak user count, and the Credit Karma migration gap. Bloomberg shutdown coverage at bloomberg.com/intuit-winds-down-mint. CNBC user-reaction coverage at cnbc.com/budgeting-app-mint-is-shutting-down.

[5] Money Dashboard was a UK personal finance manager founded in 2010, regarded as the UK's largest PFM by 2015 with over 100,000 users, and powered by Yodlee for account aggregation. ClearScore Group acquired Money Dashboard in May 2022 in a deal whose terms were not disclosed. ClearScore subsequently shut down the Money Dashboard Neon and Classic consumer apps on 31 October 2023, with the company's official closure statement reading: "we could not find a sustainable business model for the apps, and are therefore unable to continue supporting the services." ClearScore retained the open-banking technology that powered Money Dashboard and rebuilt it as a B2B product called D•One, launched in January 2023, sold to lenders for transaction categorisation and open-banking connectivity. Acquisition coverage at dailybusinessgroup.co.uk/clearscore-buys-money-dashboard. Closure announcement coverage at moneytothemasses.com/money-dashboard-closing. D•One launch coverage at openbankingexpo.com/clearscore-d-one-launch.

[6] Quicken was founded in 1983 and is widely considered the first consumer personal finance tracker. Intuit sold the product to H.I.G. Capital in 2016 after Intuit CEO Brad Smith called it a "desktop-centric business" that "doesn't strengthen the small business or tax ecosystems," contributing $51 million to Intuit's $4.2 billion total revenue at the time. H.I.G. resold the business to Aquiline Capital Partners in 2021. Quicken moved to a mandatory subscription model in 2018, with users locked in a proprietary file format and recurring complaints about deteriorating integration quality across the user community. Source for the Intuit divestiture and the "dead end" framing at computerworld.com/intuit-sells-quicken. Aquiline transaction at techcrunch.com/quicken-resold-private-equity.

[7] Personal Capital, founded in 2009, offered a free auto-aggregating personal finance dashboard alongside paid wealth-management advisory services. By 2020 the platform had over 2.5 million users tracking $771 billion in household assets, with 31,800+ advisory clients holding $28.5 billion in managed assets. Empower Retirement, the second-largest US retirement plan provider, acquired Personal Capital for up to $1 billion enterprise value in 2020. The free dashboard was rebranded as Empower Personal Dashboard in 2023 and continues to operate as a customer acquisition channel for Empower's wealth-management business. Acquisition announcement at empower.com/empower-retirement-completes-personal-capital-acquisition.

[8] CoinTracker is a cryptocurrency portfolio and tax-reporting tool founded in 2017 by Jon Lerner and Chandan Lodha. The company reached unicorn status with a $1.3 billion valuation after a $100 million Series A in January 2022, and as of late 2025 reports approximately three million users across 100+ countries with integrations to 500+ exchanges, wallets, and chains. CoinTracker positions itself as a portfolio management platform first and tax software second, with the business funded primarily by crypto-tax compliance subscriptions, which are regulatory-mandatory in most jurisdictions. The IRS published Revenue Procedure 2024-28 in June 2024, requiring per-wallet cost-basis tracking starting in tax year 2025 (replacing the previous universal-account method), which substantially increased the regulatory burden on individual crypto holders and made automated cost-basis tracking effectively mandatory rather than optional. Total funding raised stands at approximately $101.6 million, with no Series B reported as of April 2026, four years after the Series A. CoinTracker is a private company that does not publish audited financials. Series A coverage at coindesk.com/cointracker-raises-100m. Funding history at crunchbase.com/organization/cointracker. Revenue Procedure 2024-28 at irs.gov/pub/irs-drop/rp-24-28.pdf.

[9] Open Financial Exchange (OFX) is an open data format for the exchange of financial information including bank transactions, credit card statements, and investment account data. Microsoft, Intuit, and CheckFree announced the OFX standard on 16 January 1997, and version 1.0 of the specification was released on 14 February 1997. Versions from 2.0 onwards are XML-based. The OFX investment message set covers security identifiers (CUSIP, ISIN, ticker), positions and quantities, transaction history (buys, sells, dividends), prices, and holdings. In 2019 the OFX consortium joined the Financial Data Exchange (FDX) consortium, which now maintains the OFX specification; the latest reference document was published in October 2020. While many US banks support OFX for bank-account transaction export, support for the OFX investment message set across consumer portfolio products is sparse: the open-source ofxtools Python library documentation explicitly notes that "full support of the OFX investment message set has been somewhat neglected by the Python community." OFX specification at financialdataexchange.org. OFX history at en.wikipedia.org/wiki/Open_Financial_Exchange. ofxtools investment message set note at ofxtools.readthedocs.io.

[10] Plaid is the dominant US bank-data aggregation infrastructure layer that most modern fintech and personal finance products depend on. Visa announced an agreement to acquire Plaid for $5.3 billion in January 2020, describing the company as "an essential infrastructure for the future of financial services." The US Department of Justice filed an antitrust lawsuit on 5 November 2020 challenging the acquisition under Section 2 of the Sherman Act, citing internal Visa communications that described Plaid as an "insurance policy" against threats to Visa's online debit business. Visa abandoned the acquisition in January 2021. Plaid raised a Series D at a $13.4 billion valuation in April 2021, with revenue concentrated in enterprise APIs sold to banks, lenders, and fintech infrastructure companies. As the aggregation layer that most consumer fintech products depend on, Plaid's commercial trajectory determines what data flows are possible across the consumer fintech category, regardless of any individual consumer product's intentions toward its users. DOJ complaint coverage at techcrunch.com/doj-antitrust-visa-plaid. Acquisition abandonment at cnbc.com/visa-plaid-call-off.

[11] Yodlee was the original consumer-facing personal financial management aggregation infrastructure, founded in 1999 and providing the data aggregation for Mint, Money Dashboard, and a generation of other personal finance products. Yodlee IPO'd on Nasdaq in 2014 and was acquired by Envestnet in November 2015 for $660 million in cash and stock, after which Yodlee was repositioned away from consumer-facing products toward enterprise wealth-management and bank-facing infrastructure. Envestnet itself was taken private by Bain Capital in a $4.5 billion transaction, and announced in June 2025 that Yodlee would be sold to private equity firm STG, with the deal expected to close in Q3 2025. Yodlee's pivot from consumer aggregation to enterprise infrastructure is one example of the broader pattern in which the aggregation layer that supports personal finance products migrates upmarket toward institutional buyers because the consumer-facing economics will not sustain it independently. Envestnet acquisition completion 8-K at sec.gov/Envestnet-Yodlee-completion. STG acquisition coverage at americanbanker.com/envestnet-yodlee-stg. Industry context at kitces.com/envestnet-yodlee-acquisition.

[12] Blockfolio was founded in 2014 and became the most widely used cryptocurrency portfolio tracker in the space, with over six million users at the time of its acquisition. FTX acquired Blockfolio in August 2020 for approximately $150 million. The app was rebranded as FTX in 2021 and used as a distribution channel to push FTX's trading products, margin accounts, and yield products to its user base. FTX collapsed in November 2022 following revelations that customer funds had been misappropriated, with founder Sam Bankman-Fried subsequently convicted on seven counts of fraud and conspiracy in November 2023. Blockfolio users who had migrated to the FTX app lost access to the platform when FTX halted withdrawals on 8 November 2022. Acquisition coverage at theverge.com/ftx-blockfolio-acquisition. FTX collapse timeline at bbc.co.uk/ftx-collapse.

What the Ghost Owes the People It Overhears

2026-04-20T00:00:00Z

A memory device for one is a surveillance system for everyone else.

In Assisi, while Cristina was paying the bill at the deli and I was chatting her ear off, she said surely you can't just record other people and call it private software. That was where the previous post ended. I spent the next few days on how you would run LocalGhost in Germany or France without turning every conversation into a crime.

> 1. The industry's answer

The answer the industry has given so far is to push the legal problem onto the user through a terms-of-service clause and ship the hardware anyway. Rewind recorded your screen and your microphone and sold the pitch as "perfect memory," pivoted to a pendant, and was acqui-hired by Meta last December [1]. Humane's pin pointed a camera and microphone at everyone in front of the wearer until the company failed on product quality in early 2025 and sold its patents to HP [2]. Bee's $50 wristband recorded everything within earshot to generate reminders and to-do lists, until Amazon acqui-hired the team in July 2025 [3]. Plaud still ships, selling a device whose entire reason for existing is to record the conversations you have with other people [4]. The one thing keeping Plaud clear of the continuous-capture trouble the others walked into is its manual-button model. The assumption running through all of them is that the only privacy that matters is the wearer's. None reached the scale where a privacy regulator or a class-action lawyer would pay serious attention. Phones already have back taps and action buttons that would start recording with one gesture, which means the pendant form factor exists for the version where no gesture is needed.

Ring is the proof of what happens when one of these products does reach scale. Amazon's doorbell camera, installed on roughly ten million American homes, generated enough pressure to attract the kind of regulatory attention the wearables never have. The FTC fined Amazon $5.8 million in May 2023 for letting employees and Ukrainian contractors browse customer videos, including cameras in bedrooms and bathrooms, and for training AI on those videos without consent [5]. The same settlement covered more than 55,000 accounts compromised by credential-stuffing attacks that Ring had been warned about and ignored [5]. Police partnerships with more than 500 US departments drew years of campaigning by the EFF and ACLU, forcing Ring to shut down its Request for Assistance portal in January 2024, only for Amazon to reopen the same channel through Axon and Flock partnerships in mid-2025 [5]. Ring isn't a legal template for AI memory products, because the mechanisms are different (consumer-protection law versus criminal audio statutes), but it proves that scale draws scrutiny. Your smartphone already has the scale the wearables are still chasing, and we're building LocalGhost for that.

> 2. The law taken seriously

Compliance with the letter of the law in all jurisdictions is impossible. The statutes contradict each other (the UK accepts one-party consent, Germany treats capture without all-party consent as a criminal offence the moment it happens), so any device that hears other people is breaking the law as written the moment it listens. Honouring the spirit of those statutes is a different problem, and that one is solvable. The spirit is that people should be able to talk openly in private without worrying their words will be kept verbatim, shared with people they didn't speak to, used against them later, or cloned to say things they never said. What the ghost keeps is a journal entry from the user's perspective.

Video and audio are regulated differently here. Video in public space sits under GDPR's household exemption as long as the purpose is genuinely personal, and the exemption holds up reasonably well for someone filming their own life [6]. Running on your own hardware rather than someone else's cloud strengthens the posture but doesn't change the analysis much. The CJEU in Ryneš (2014) narrowed the exemption so it doesn't cover systematic recording of public space [6]. Door cameras and shopfront cameras that capture the street are everywhere, and Ryneš didn't ban them. What it did was move them out of the exemption and into the controller-obligations bucket, which means signage, a defensible purpose, proportionality, and the duty to respond to access and deletion requests. Most doorbells never get a formal complaint and most homeowners never learn their obligations, which doesn't change the legal position any more than not getting caught changes a speed limit. Filming your own dinner is fine. Pointing a camera at the street makes you a data controller.

Audio is legally worse, and most people don't know this. Germany, France, Italy, Spain, Austria, and Romania all have criminal statutes covering the recording of private speech without consent [7]. These aren't data protection rules. They're criminal law operating alongside GDPR, and the household exemption doesn't touch them. Germany's §201 StGB carries up to three years for recording the "non-publicly spoken word" of another person without consent, and "non-publicly" includes a conversation in a café because the speakers didn't intend the words for the general public [7]. France's Article 226-1 is a year and €45,000 for recording paroles prononcées à titre privé ou confidentiel [7]. The pattern across most of continental Europe is all-party consent as the default, with the Netherlands and the UK as notable one-party-consent exceptions [7]. The offence is completed at the moment of capture. Deletion afterwards doesn't cure the act.

In practice, I couldn't find a single reported prosecution of a user running an AI memory product. Coverage of these products has been extensive and any prosecution would have been news. Enforcement tracks real-world harm, journalists burning sources, stalkers, employees recording bosses for civil suits, bosses recording employees. The statutes are written broadly and enforced narrowly, around a theory of harm AI memory products haven't yet produced at scale. But "nobody has been prosecuted yet" is not the same as "the law permits this," and I'm not willing to build infrastructure other people will use on the assumption that the enforcement gap stays open. If a single high-profile case goes wrong (the phone that captured a CEO's unguarded lunch remarks, the app that shipped a transcript to an abusive ex), the statutes are already on the books.

The industry is operating on the bet that the gap between what the law allows and what the law prosecutes will stay open forever.

> 3. The workplace already solved this

The workplace has moved past all of this. Google Meet, Zoom, Microsoft Teams, and Slack calls get recorded routinely. Otter and Fireflies send AI bots to take notes. Granola runs as a desktop app that captures audio locally. What people want from these tools is the summary, the decisions, the action items, the memory of what the meeting was about.

The move to summaries wasn't painless. German works councils forced BetrVG §87(1)(6) co-determination onto AI transcription, with the Federal Labour Court confirming in July 2024 that any monitoring-capable system triggers the right [8]. The CNIL pushed French organisations to justify full recordings over summaries [9]. Microsoft shipped explicit consent on Teams in 2023 [10]. Every tool that ships in the EU now has the consent flow the regulators demanded.

What survived is the category of tool that keeps the summary and throws away the recording. Granola transcribes locally, generates a structured summary, and keeps no audio or video files [11]. The ghost does the same on the personal side, where the statutes are older and stricter but the regulatory pushback hasn't happened yet.

The workplace solved this inside a legal apparatus a solo user doesn't have. A Teams recording that goes wrong has a corporate legal team, a works council, a DPO, and indemnity clauses. A phone on a café table in Berlin has one person on it, who won't find out they've broken §201 StGB until something has gone wrong. The architecture has to prevent the failure, because no one else will catch it.

> 4. The design that closes the gap

The design has four stages, and each stage throws away more of what belonged to other people without throwing away what happened. The phone captures audio, holds it briefly as encrypted chunks, and forwards them to your NAS, where ghost.voiced consumes them in a RAM ring buffer bounded in seconds to minutes and overwrites as it goes. Unencrypted audio from the conversation never lands on disk anywhere. ghost.voiced transcribes the audio and attaches the context the transcript would otherwise lose, time, place, who's in the room, before passing the enriched text to ghost.noted. ghost.noted writes the journal entry in your voice, specific enough to be a useful memory months later. "At Hotel Duomo, I asked the receptionist about late check-in. She agreed to 14:00." That's what the journal keeps, my memory of what I arranged. The transcript of what she said and how she said it never survives the journal entry, because that transcript would be a recording of her side of the exchange.

Specificity is the rule at every stage, because the ghost has to stay useful months after the moment it captured. That means real times rather than "in the afternoon" (14:00 in the Hotel Duomo example), named places rather than "the hotel", and either a name or a role for the people involved (the receptionist, the vendor, the sommelier, depending on which of those you could identify if you had to find the memory again).

The memory that grows out of these journal entries is rich about the user and thin about everyone else. If the same person shows up across many entries, the system resolves them to a single name as a reference so memories can be connected, but the reference stays a pointer and never becomes a model of the person. The ghost never builds a profile of what the vendor said in the last dozen meetings, what the colleague sounds like when she's stressed, how the friend phrases a compliment. The third parties in the user's memories are there as context for the user's own story, and the system never lets them become the subject of their own.

This inverts the Rewind model completely. Rewind's pitch was perfect recall, every word preserved, searchable forever [1]. I don't see the value. Nobody can consume perfect recall, a week of conversations played back verbatim takes a week to listen to. Verbatim recall doesn't answer the questions you have when you go looking. The questions are about what got concluded, what surprised you, what needs following up on. Human memory works the other way. You don't remember what your friend said word-for-word two weeks ago, you remember the shape of the conversation, what you decided, what you noticed, the role they played in your own reasoning. The ghost should augment that rather than replace it with a legal exhibit.

Once the audio is gone and what's left is your own account of what happened, it stops being data about the other people in the room. "I pushed back on the pricing at the café in London" is your memory of your own position. It isn't a recording of the vendor. GDPR is a law about protecting other people's data from being misused, and there is no other-people's-data in what the ghost kept. The criminal statutes exist to stop people being recorded without consent, and what the ghost kept is your own account of what happened.

The ghost keeps the shape of what you experienced, which is the shape the law recognises as yours.

On a strict reading the design violates §201 StGB, because audio of another person's non-publicly-spoken word gets captured and transmitted for the seconds it exists. The strict reading is the wrong test for a system that destroys the audio at transcription, keeps only the user's summary, and never builds a picture of anyone else. The statutes exist to prevent harm the ghost doesn't produce.

> 5. Architecture has to do the work

The design is whatever the pipeline enforces at runtime. If audio ever persists in logs, if transcripts survive the summarisation step, if the RAM buffer isn't locked non-pageable and the kernel swaps it to disk, if any backup layer retains the raw buffer (ZFS snapshots on the NAS, iCloud or Google Drive on the phone), if the language model's memory of the conversation outlives the session, the promise that audio disappears breaks and everything I just described becomes marketing. Discipline cannot carry this, the architecture has to, because every one of those leak paths is something a careful user would notice on a good day and miss on a bad one.

The phone is a hostile environment for audio at rest. iCloud and Google Drive will try to back up anything they can see, so encrypted chunks land in excluded-from-backup directories. The phone's copy is destroyed as soon as the NAS confirms receipt, so audio lives even in encrypted form for minutes at most. On the NAS, decrypted audio never leaves RAM. Every long-lived artifact the pipeline produces is text the user wrote about their own day.

The test of a memory device is whether a forensic examiner looking at your hardware tomorrow could reconstruct a conversation you overheard yesterday. If the answer is yes, or probably, or sometimes, the privacy claim is marketing.

I've built enough pipelines to know that anything relying on "and then we delete it" will eventually fail to delete it, and the "and then we delete it" architecture is what every cloud memory product ships. The local version can do better because deletion happens on hardware you own, and because there's no backup layer run by someone else trying to protect your data from you.

Your data stays on your hardware because that's the only way you can honestly tell someone the ghost heard their voice, understood what mattered to you, and forgot the rest. The moment any of that happens on a server you don't own, the claim becomes something you have to believe rather than something you can inspect.

> 6. What this leaves unresolved

The architecture doesn't solve everything, and I don't want to pretend it does.

If someone explicitly asks whether they're being recorded, the architecture gives no cover. At that point you have to say yes, audio is being processed, and the lawful move is to stop or to accept that the person has objected. Transparency creates legal exposure that silence would avoid. Silence would also be lying to the person in front of you, which matters more. The ghost should have a visible indicator and a gesture to disable capture. Cristina's original question becomes the policy. If someone says no, the ghost stops.

Sensitive contexts are a separate problem, because in some settings the presence of any recording system is itself the offence regardless of what it keeps. Meetings with doctors, lawyers, therapists, or journalistic sources need to be explicit exclusions at the architecture level rather than judgement calls the ghost makes in the moment, because the ghost doesn't know what room it's in until too late.

The rules don't line up across borders. Germany and France enforce the audio statutes vigorously, and Chile's Article 161-A criminalises recording private conversations without authorisation [12]. US federal law is one-party consent, but around a dozen states including California and Illinois require all parties [12]. Canada is federally one-party, Quebec stricter [12]. The UK and the Netherlands allow one-party consent. Users travelling across borders need the ghost to pick the local floor rather than the home country's floor.

Crossing borders and entering sensitive contexts both need the ghost to tell the user what's changing. For travel, the ghost should give you a heads-up when you cross a border, the way your telco texts you about roaming, so you know the local rules before the next session. For sensitive contexts, the phone has signals the ghost can use (calendar events marked with medical or legal keywords, GPS boundaries around hospitals and law offices), and when one of those signals fires the ghost should ask before capturing rather than assume the user remembered. The ghost doesn't capture while it waits for your answer.

A visible indicator is the commitment, and a visible indicator will mean most people turn ambient capture off most of the time, which is the indicator doing its job. If what's left is voice memos transcribed locally into journal entries, that's still a better-architected version of what Google and Apple ship, and still worth building.

The ethical question survives even when the legal one is answered. Even if the architecture makes the retained artifact legally clean, the people around you are still being perceived by a system they didn't opt into. The design minimises what the ghost keeps of them, but the ghost still heard them in the moment it was deciding what to keep. That is a smaller problem than the Rewind version of the problem, but it's not zero.

Three things the ghost owes the people it overhears. Ephemerality, so the moment doesn't outlive itself. Anonymity, so if the moment persists it doesn't identify them. Restraint, so the ghost doesn't keep what it didn't need.

These three commitments are a floor, and the floor is already higher than what the industry has been shipping.

> 7. What's next

The summarisation step is where this gets decided, where audio becomes text and third-party speech gets compressed into the user's own perspective. Preserving enough of the user's reasoning to be useful months later, without preserving enough of anyone else's words to be a recording, is the line the architecture needs to hold. Where that line sits is a research problem rather than a configuration setting, and it's the part the rest of the fleet depends on getting right.

None of this is solved yet. The summariser is where the §201 question gets tested, and whether it holds up on real speech rather than clean test transcripts is the thing I don't know yet.

Cristina's argument in Assisi was about the privacy of the people around the user, not her own. The version of the ghost I'm willing to ship is the one where that argument doesn't apply, because what survives inside it is my summary of what happened and nothing of the other person. [ localghost.ai // hard-truths ]

> REFERENCES

[1] Rewind AI, formerly marketed as "your searchable memory", recorded everything seen and heard on the user's Mac with on-device capture and cloud-based transcription. The parent company pivoted to the Limitless Pendant in 2024 and was acqui-hired by Meta in December 2025, with the Rewind desktop app killed on 19 December 2025 and EU and UK service cut off entirely. Source for the "perfect memory" framing and the wearer-centric capture pattern. Acquisition coverage at techcrunch.com/2025/12/05/meta-acquires-ai-device-startup-limitless. The archived product pitch at rewind.ai.

[2] Humane Inc.'s Ai Pin, launched November 2023, shut down and sold to HP in February 2025. The device had a camera, microphone, and laser projector, designed to be worn on the chest, and captured audio and visual context for an AI assistant. Source for the claim about a camera and microphone pointed at everyone in front of the wearer, and for the timeline of the product's collapse. BBC coverage of the shutdown at bbc.com/news/articles/c3vr64lv7mno. Humane's own product page is no longer live.

[3] Bee AI, a San Francisco startup founded by Maria de Lourdes Zollo, sold a $49.99 wristband and companion app that recorded ambient audio and turned it into summaries, reminders, and to-do lists. The device recorded continuously unless the user manually muted it. Amazon confirmed the deal in July 2025, with Bee employees receiving offers to join Amazon in what the coverage characterised as an acqui-hire rather than a standalone product acquisition. Source for the ambient-recording pitch and the July 2025 Amazon deal. TechCrunch coverage at techcrunch.com/2025/07/22/amazon-acquires-bee-the-ai-wearable-that-records-everything-you-say.

[4] Plaud AI (plaud.ai) sells a range of AI-powered voice recorders, including the NotePin and Note, which attach to phones or clothing and record conversations for cloud-based transcription and summarisation. Source for the claim that the product's reason for existing is recording other-party conversations for searchable transcripts. plaud.ai

[5] FTC v. Ring LLC, filed 31 May 2023, settled with a $5.8 million judgment. The FTC complaint alleged that Ring gave employees and Ukrainian third-party contractors unrestricted access to customer videos including cameras in bedrooms and bathrooms, trained AI image-recognition models on customer videos without obtaining affirmative consent, and failed to implement basic security against credential-stuffing and brute-force attacks, leading to more than 55,000 compromised US customer accounts between January 2019 and March 2020. Separately, Ring's relationship with US police departments drew sustained criticism from the EFF and ACLU, with more than 500 departments partnered by 2020. In January 2024 Ring shut down the Request for Assistance portal that had allowed police to make warrantless video requests to users through the Neighbors app. In 2025 Amazon reopened the same channel through partnerships with Axon (announced at Axon Week 2025) and Flock (October 2025). Source for the FTC action, the police partnership history, and the 2024-2025 reversal. FTC case materials at ftc.gov/news-events/news/press-releases/2023/05/ftc-says-ring-employees-illegally-surveilled-customers. EFF coverage of the 2024 portal shutdown at eff.org/deeplinks/2024/01/ring-announces-it-will-no-longer-facilitate-police-requests-footage-users.

[6] GDPR Article 2(2)(c) exempts processing "in the course of a purely personal or household activity." The CJEU narrowed this in František Ryneš v Úřad pro ochranu osobních údajů (Case C-212/13), decided 11 December 2014, holding that a home CCTV camera capturing the public footpath outside the house did not qualify as purely personal or household because the recording extended into public space. The case is the anchor for the "narrow interpretation" of the exemption and the reason most commentators warn that systematic recording of public space (and by extension, of strangers) falls outside the household sphere regardless of purpose. Full judgment at eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:62013CJ0212. Useful commentary at gdprhub.eu/Article_2_GDPR.

[7] Criminal statutes covering recording of private speech without consent. Germany, §201 StGB (Strafgesetzbuch), penalty up to three years' imprisonment or a fine for recording the "non-publicly spoken word" of another. France, Article 226-1 Code pénal, one year and €45,000 for recording paroles prononcées à titre privé ou confidentiel. Italy, Article 615-bis Codice penale. Spain, Article 197 Código Penal. Austria, §120 StGB. Romania, Article 226 Cod penal (violation of private life). Netherlands and the UK operate under one-party consent regimes for conversations the recorder is party to, making them the notable exceptions to the continental default. Source for the specific statute numbers, penalties, and the all-party-versus-one-party distinction. German statute at gesetze-im-internet.de/stgb/__201.html. French statute at legifrance.gouv.fr/codes/article_lc/LEGIARTI000006417929.

[8] German Works Constitution Act (Betriebsverfassungsgesetz), §87(1)(6), grants works councils a co-determination right over the introduction and use of technical systems "capable of monitoring the behaviour or performance of employees." No such system can be rolled out without a works agreement. Applied to AI meeting tools, the Federal Labour Court (Bundesarbeitsgericht) ruled on 16 July 2024 (1 ABR 16/23) that objective suitability for monitoring is enough to trigger the right, even where the employer does not intend to use the system for monitoring. The ruling concerned headset systems but the reasoning applies to any system capable of capturing employee speech. Source for the claim that works councils in Germany block meeting recorders absent an agreement, and for the July 2024 clarification of the standard. Statute at gesetze-im-internet.de/betrvg/__87.html.

[9] CNIL (Commission nationale de l'informatique et des libertés), the French data protection authority, has issued guidance on meeting recording under the GDPR necessity principle (Art. 5(1)(c), data minimisation). The guidance advises organisations to consider whether meeting notes or summaries would suffice instead of full recordings, on the grounds that the recording goes beyond what is necessary for the stated purpose. The CNIL has separately flagged that consent is rarely a valid legal basis for processing employee data because of the employer-employee power imbalance, pushing organisations toward legitimate-interest grounds with proportionality constraints. Source for the "consider summaries instead of recordings" position and for the CNIL's strictness relative to other EU supervisory authorities. CNIL HR processing guidelines at cnil.fr/fr/la-cnil-publie-un-referentiel-relatif-aux-traitements-de-donnees-rh.

[10] Microsoft shipped explicit recording consent for Microsoft Teams in 2023. When the policy is enabled, all participants are muted when recording starts and must press 1 on their dial pad to consent and unmute, or press 2 to deny consent and remain muted for the duration. The policy is configurable per-organiser via PowerShell and is intended to address privacy concerns in jurisdictions requiring all-party consent. Source for the 2023 rollout and the specific consent mechanics. Microsoft Learn documentation at learn.microsoft.com/en-us/microsoftteams/conferencing-recording-consent.

[11] Granola, the AI meeting notes tool, captures audio directly from the user's device, transcribes it in real time, generates a structured summary, and does not store audio or video files. CEO Chris Pedregal has said in interviews that the design choice is deliberate, and that the value is in useful notes rather than in retaining audio. Source for the architecture (summary as primary artifact, no audio retention) and for the founder's stated position on why. Interview context at wondertools.substack.com/p/granolaguide. Granola's product site at granola.ai.

[12] Recording consent laws outside the EU continental bloc, as of April 2026. The landscape shifts as legislatures amend statutes and courts interpret them, so this reflects what I could find rather than an authoritative snapshot. Chile, Article 161-A of the Penal Code, introduced by Ley 19.423 (known as Ley Otero), makes it a criminal offence punishable by reclusión menor and a fine of 50 to 500 monthly tax units to capture, intercept, record, or reproduce private conversations or communications in any enclosed or private place without authorisation. United States, federally one-party consent under the Electronic Communications Privacy Act (18 U.S.C. §2511), with around a dozen states applying all-party consent in some form (California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington), though several are split between criminal one-party and civil all-party rules, or between phone and in-person. Michigan and Oregon add further mixed-rule complications. Canada, §184 of the Criminal Code treats interception of a private communication as an indictable offence punishable by up to five years' imprisonment, with a one-party consent exception under §184(2)(a) that permits participants to the communication to record. Quebec layers additional privacy protection through Articles 35 to 41 of the Civil Code and Law 25 (2021, in force 2023), producing a privacy regime generally considered the strictest in North America. Chilean statute at bcn.cl/leychile/navegar?idNorma=1984. US federal statute at law.cornell.edu/uscode/text/18/2511; state-by-state roundup at rcfp.org/introduction-to-reporters-recording-guide. Canadian statute at laws-lois.justice.gc.ca/eng/acts/c-46/section-184.html.

The Ghost Has to Be Useful on Day One

2026-04-18T00:00:00Z

A long onboarding flow is a team admitting they don't know who they are building for.

A few days ago Cristina and I sat down for lunch in Assisi at AssaggiAssisi (chill little deli). I'd been up late the night before writing the ghost.cued post and I was still turning it over in my head, so I started telling her about it. The daemon that reads your environment and surfaces the right memory at the right moment (and explaining how our brain does it). I explained that the ghost should already know you by the end of day one.

She said that sounded fine in theory but countered that Gemini already knew her. Her health, her sleep, her plans, her interests, all of it (built up from months of her talking to the thing). She assumed LocalGhost would need the same multi-week ramp she'd gone through with Gemini (the dynamic I'd covered in the model-trap post), and she wasn't going to sit through it again just because it was more private and local. She'd rather spend twenty minutes on install day filling in a form and have something that fit her from the start than get a cold-start daemon that only became the ghost she wanted some time in May. I offered a personality test as the short version of that, Big Five or similar, ten minutes on install day and the ghost has a seed. She thought about it and dismissed it as too pigeonhole-y. A personality test files you into a category on day one, and the moment the ghost thinks of you in those terms it's stuck with the wrong frame until you notice the mistake and correct it. She was expecting a setup phase, and I spent the rest of the lunch trying to convince her I didn't need one, while also trying to think my own way out of needing one, because the context should already be there in whatever devices the user has attached.

> 1. Why not a personality test

Cristina said "too pigeonhole-y" at the table and moved on, but I went home and spent a few hours looking into it, because a short fun test really would have been the easiest way to seed the ghost. The idea kept falling apart the more I read. Big Five reduces you to five axes the field settled on around 1990 [1]. Myers-Briggs and Enneagram do the same thing with different categories. Any of them put you in a bucket the moment you fill in the form, and software that should then assist you filters everything it does through that bucket. The bucket becomes the daemon's default, and it stays that way until you catch the daemon doing something wrong, six months later, and realise it still thinks of you as whatever the test said on day one.

The problem gets worse the more specific the category is. A setup form might have a tick-box for ADHD, autism, dyslexia, or one of the many other conditions a person might be navigating, and the ghost would read the tick-box and overadjust. Even setting medical diagnoses aside, two people are never weird in the same way. Two people who tick the same box can be almost nothing like each other, and a daemon that treats them as the same category is flattening the thing LocalGhost exists to preserve.

Cristina's instinct was right. The test itself is broken as a tool for seeding a personal daemon, no matter how short or fun I made it. That answered the narrow question. Once that one was closed I moved on to the wider one, which was whether any form belongs on install day at all.

> 2. Why no onboarding questionnaire

The memory post I had finished a few nights earlier lays out how the ghost should interact with the user, and none of the patterns it describes look anything like a form on install day. A form asks you to rate and describe yourself, with no context in front of you, and it does it before the ghost has shown you anything at all. The patterns in the memory post are the opposite of that, and they are where the question-asking belongs once the ghost is running.

Trello before Atlassian bought it, and Linear now at $1.25 billion [8]. Both shipped without an onboarding form. Jira has been asking users what department they work in since 2002 and the wizard is still getting longer. LocalGhost.ai has to sit where Trello and Linear sit.

A company that has to ask you a wall of questions to work out who you are and how the product should work for you is a company staffed by people who don't know their own product and don't know who it is for (Atlassian, cough cough). Real employees know the audience because most of the time they are part of the audience. I have shipped onboarding forms myself, under deadline pressure, at CCData, and I knew the form was the shortcut every time. Onboarding flows are lazy, inelegant, and offensive to the user. The lunch with Cristina, and the time I spent on it afterwards, is what made me realise I do not want to build one into LocalGhost.

> 3. Where the signal already is

If not a form, then what. The answer is inference from the behavioural traces the user has been producing on their own devices for years, and the evidence that this works is a decade old. Kosinski, Stillwell, and Graepel showed in 2013 that Facebook Likes alone could predict sexual orientation, ethnicity, political and religious views, personality traits, intelligence, happiness, substance use, parental separation, age, and gender to 80-95% accuracy on the binary outcomes [2]. Two years later, Youyou, Kosinski, and Stillwell ran the follow-up that still anchors the field. A computer model using Facebook Likes judged personality more accurately than the participants' own friends and family. Ten Likes outperformed a work colleague. 150 Likes outperformed a parent or sibling. 300 Likes outperformed a spouse [3]. The point wasn't about Facebook. Behavioural traces predict personality better than the people who know you personally, and they do it without anyone sitting you down to take a test. That is the reason I think LocalGhost is worth building, and also the reason I think the space it addresses will be taken over and exploited by big tech, as I wrote in the inflection post. The same inference that makes the ghost genuinely useful on local hardware is what the centralized cloud platforms will want to run against everyone else in order to sell them products.

The neurodivergence point is backed by the last decade of digital phenotyping research. Perochon et al. (2023) in Nature Medicine screened autism in 17-36-month-olds using tablet-based behavioural measures, AUC 0.90 [4]. Lee et al. (2023) used wearable data to detect ADHD and sleep problems with AUC 0.798 [5]. Casals, Larsson, and Hansen (2025) built a smartphone-sensor ADHD predictor hitting 80.8% sensitivity and 79.5% specificity, with the built-in sensor features adding meaningfully to a cognitive-test baseline [6]. Neurodivergence has a behavioural signature that shows up in how people move, read, respond, and attend. A device you already own produces enough of that signature to classify accurately in a research setting but what the ghost infers on any one user has to still be a guess. The software has to treat it that way, a hypothesis that updates the moment the user corrects it and never a bucket that sticks.

Put the studies together and the picture is that behavioural signal lives in almost everything the user does with a device. How you write, what you read, what you rewrite, and how long you leave things in draft. How you walk, how you exercise, how you sleep, all of it picked up by the wearable on your wrist and the phone in your pocket. How you communicate, who you reach for and how often, which Stachl et al. (2020) found was the single highest-signal channel for personality prediction across a month of passive smartphone sensing [7]. The photos you take and keep and return to, the music you play and skip, the way you tap on the phone itself (which in the Casals study added usable signal on top of a dedicated cognitive test). None of it is a personality test because none of it is you rating yourself. All of it is what you have already done, for your own reasons, left on devices you already own. A ghost that can read that footprint locally has more to work with on day one than a cloud assistant that just met you has after a month of conversation.

> 4. What I think the setup should look like

The ghost is a fleet of daemons, one per modality, each of which has a README in the repo. ghost.noted handles text, ghost.framed handles images, ghost.voiced handles audio, and ghost.synthd sits above them. They run on a NAS, either one you already own or one we sell you. Each of your other devices runs an app that pairs with the NAS on first run over the local network and opens a VPN tunnel back to it. After that the app works from anywhere. On a train, in a hotel, at a cafe, it stays paired with your NAS and pushes its modality over the tunnel, where ghost.synthd turns what comes in into a model of you. The same app is how the ghost reaches you when it has something to say and how you reach it when you have something to ask.

One device is enough to start getting value and you can add the rest over time, or never, and the ghost still works. If you do not want to install the app on any device at all, the ghost builds from what you tell it in chat on the box itself (you'll be able to access it directly via a web page), which is slower but still works. Most people will install the phone app at least, because the NAS is already theirs and a NAS is a product category users recognise. You get a local archive of your own stuff as a side effect, your photos, your notes, your writing, your music, your health data, all indexed locally and searchable by you.

The approvals work the way the platform already does them. iOS, Android, macOS, the wearable platform, each asks about its own permissions the first time the ghost needs them, one at a time. No central form, no LocalGhost-specific consent surface pretending to understand the thirty things being granted. Revoking is easy and built in as is uninstalling. Everything the ghost sees lives on the NAS. The model it builds of you is written to local disk and secured in a way we discussed in The Honeypot Under Your Desk, inference runs on the local GPU, nothing ships anywhere else.

> 5. What it feels like when it works

The architecture is the privacy and security commitment, and I think I can build a pretty good version of you with it. What it does not solve is how the thing will feel to live with. The clearest picture of that came out of the same lunch. Cristina had ordered a cheese board at the deli. She did not pick the cheeses and instead asked for the standard one they had and what came out was good. The longer menu existed, with every cheese and every cured meat spelled out, and we had ignored it. If we kept coming back the kitchen would vary what they brought out, and we would slowly work through whatever they had. That is the shape I want for day-one LocalGhost. A good default board on day one, and better at your taste with every visit.

The cheese board is the reassuring version. A digital version of you, if built well, is also going to feel creepy. Even a partial success will be eerie to sit with, because it will know you from your own footprint and sometimes it will be right about you in ways you had not noticed yourself.

And creepiness is not even the worst part. We were paying the bill and I said that at least going forward (regardless on how you get onboarded) the ghost can read everything you link it to, text, emails, audio, the lot, so you won't have to input much. Cristina said surely you can't just record other people and call it private software, that makes it private for you and not for everyone else. The next post is about what the ghost owes the people it overhears, or sees in pictures or video. [ localghost.ai // hard-truths ]

> REFERENCES

[1] The Big Five personality taxonomy (also called the Five-Factor Model) is the consensus framework in trait psychology, consolidated through work by Goldberg, Costa, McCrae, and others between roughly 1981 and 1992. The 100-item and 50-item versions of the International Personality Item Pool are free to use and take 10-20 minutes to complete. Source for the historical provenance and for the standard instrument length. Goldberg et al., 2006. "The international personality item pool and the future of public-domain personality measures." Journal of Research in Personality. href="https://ipip.ori.org/">ipip.ori.org

[2] Kosinski, Stillwell, and Graepel, 2013. "Private traits and attributes are predictable from digital records of human behavior." Proceedings of the National Academy of Sciences, 110(15), 5802-5805. Source for the 58,466-participant figure, the accuracy numbers on predicting sexual orientation (88%), ethnicity (95%), and political affiliation (85%) from Facebook Likes alone, and for the claim that behavioural traces predict sensitive personal attributes. href="https://www.pnas.org/doi/10.1073/pnas.1218772110">pnas.org/doi/10.1073/pnas.1218772110

[3] Youyou, Kosinski, and Stillwell, 2015. "Computer-based personality judgments are more accurate than those made by humans." Proceedings of the National Academy of Sciences, 112(4), 1036-1040. Source for the 86,220-participant study and for the specific thresholds, 10 Likes to outperform a work colleague's personality judgment of the participant, 70 for a friend or cohabitant, 150 for a parent or sibling, 300 for a spouse. Also the source for the finding that computer judgments based on Likes had higher external validity than self-reported personality scores for predicting some life outcomes. href="https://www.pnas.org/doi/10.1073/pnas.1418680112">pnas.org/doi/10.1073/pnas.1418680112

[4] Perochon, Di Martino, Carpenter, et al., 2023. "Early detection of autism using digital behavioral phenotyping." Nature Medicine. Prospective study of 475 toddlers (17-36 months) in a primary-care setting using the SenseToKnow tablet app. Source for the AUC 0.90, sensitivity 87.8%, specificity 80.8% figures on autism screening from behavioural signals captured by computer vision. href="https://www.nature.com/articles/s41591-023-02574-3">nature.com/articles/s41591-023-02574-3

[5] Lee et al., 2023. "Machine Learning-Based Prediction of Attention-Deficit/Hyperactivity Disorder and Sleep Problems With Wearable Data in Children." JAMA Network Open. Diagnostic study of 79 children with ADHD and 68 with sleep problems using circadian rhythm data from wearables. Source for the AUC 0.798 figure on ADHD detection from wearable data. href="https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2802554">jamanetwork.com/journals/jamanetworkopen/fullarticle/2802554

[6] Casals, Larsson, and Hansen, 2025. "Machine learning on a smartphone-based CPT for ADHD prediction." Frontiers in Psychiatry. Study of 952 neurotypical controls and 292 unmedicated ADHD patients using a smartphone-delivered Continuous Performance Test plus motion and face-tracking sensor data. Source for the 80.8% sensitivity, 79.5% specificity numbers on ADHD prediction from smartphone sensor data, and for the specific claim that sensor features from the phone itself added meaningfully to the CPT baseline. href="https://www.frontiersin.org/articles/10.3389/fpsyt.2025.1564351">frontiersin.org/articles/10.3389/fpsyt.2025.1564351

[7] Stachl et al., 2020. "Predicting personality from patterns of behavior collected with smartphones." Proceedings of the National Academy of Sciences, 117(30), 17680-17687. Study of 624 volunteers tracked over 30 consecutive days producing 25,347,089 logging events across six behavioural classes (communication and social behaviour, music consumption, app usage, mobility, overall phone activity, day/night activity). Source for the Big Five prediction from passive smartphone sensing, for the finding that communication and social behaviour was the most predictive class overall, and for the median prediction performance at broad domain level (r = 0.37). href="https://www.pnas.org/doi/10.1073/pnas.1920484117">pnas.org/doi/10.1073/pnas.1920484117

[8] Linear, June 2025. Series C funding round of $82 million led by Accel, at a $1.25 billion valuation, bringing total raised to $134.2 million. Linear has been profitable since 2021, serves more than 15,000 customers including OpenAI, Scale AI, and Perplexity, and grew ARR more than 200% year-on-year in 2025. Source for the $1.25 billion valuation and for Linear's minimal-onboarding design approach, which Linear's own product documentation describes as pre-populated workspaces and no setup configuration. TechCrunch coverage at href="https://techcrunch.com/2025/06/10/atlassian-rival-linear-raises-82m-at-1-25b-valuation/">techcrunch.com/2025/06/10/atlassian-rival-linear-raises-82m-at-1-25b-valuation. Linear's own announcement at href="https://linear.app/now/building-our-way">linear.app/now/building-our-way.

Before You Ask

2026-04-17T00:00:00Z

A ghost worth building has to offer the right memory at the right moment without being asked.

Nick is a good friend of mine and he is taking his PPL exam (private pilot licence) next week. He has been training for eight months, the aircraft handling is there, the checks are there, the radio work is there. He is ready. He mentioned to me that it took him a while to get comfortable talking on the radio, and that in the early flights the callsign was one of the hard parts. Not because he did not know it, he knew it, he could write it down, he could recite it on the ground. Talking to the control tower at the time was stressful, and under that kind of stress even the easiest thing, the callsign, became complicated. Knowing the callsign and being able to say it to a stranger on an open channel are not the same skill.

After talking to Nick I called my pilot friend Ionuț. We grew up together on a military compound in Romania, our parents both worked for the air force, and he has been flying for a major carrier for about ten years. I was curious how he handled talking to the tower. He laughed and said the early radio stress is something every pilot deals with, and that it is worse on commercial aircraft, because the radio work is a carefully choreographed exchange of phrases, codes, and sequenced questions between the flight deck and the controller, and you have to hit it right in the right order. You get used to it eventually, but it takes time and practice. On his first commercial flights the First Officer sitting next to him would handle the radio or cue him when he stalled. Not just on the callsign, on the whole sequence. He had practised it many times, he knew it, but knowing it in a simulator or on the ground lands differently when you are in charge of a plane with hundreds of people on board. The First Officer sitting next to him was the thing that closed the gap.

> 1. Why retrieval is not the whole job

I have spent the last month designing the retrieval layer of LocalGhost. ghost.noted (extracts journal entries) takes whatever text arrives and publishes entries to the fleet. ghost.synthd (clusters entries into memories) consumes those entries the way POST_09 described, rolls memories into episodes, handles the queue of questions about which ones matter, and exposes an API the app layer queries. Vector embeddings in pgvector, a reranker where latency allows, a conversational layer over the top that LocalGhost's app talks to. The industry-standard pattern for this is RAG, and at small scale, with a well-curated index and a few hundred retrieved chunks, the pattern works. You can build a system that answers questions about your life reasonably well with the tools that exist today.

The problem is that the question "what is my callsign" does not get asked at the moment Nick needed the callsign. At the moment he needed it in those early flights, he was already too stressed to open a chat window and type his question. Even if he could type, the time to form the question is time he did not have. If the only way he had to reach his own memory was to ask it, the answer arrives after the moment has passed, which is the same as the answer not arriving at all.

Ionuț's First Officer did not wait to be asked. He watched the flight, he knew which phase they were in, he knew the radio call was due, and he cued the next line. The cueing was not a better retrieval, it was a retrieval triggered by something other than a query. The environment changed, the phase of flight advanced, and the cue surfaced the next thing Ionuț needed before Ionuț knew he needed it. No search engine sitting at the end of a text box gets to that.

There is a second reason retrieval alone is not enough, and it shows up once the index stops being small. RAG looks like a single pipeline, but it has two stages that can fail independently, and both get worse at scale. The first stage is the retriever. Anything beyond a few million vectors is running approximate nearest neighbour search rather than an exhaustive scan, because exhaustive does not fit the latency budget. HNSW is the dominant algorithm in this category and the one I am using under pgvector. By design it trades recall for speed, and the tradeoff gets harder as the index grows. More vectors means more candidates per query and more distance comparisons skipped, so the top-k that comes out of the graph includes fewer of the true nearest neighbours. Inserts and deletes over time also leave the graph in a worse state than a freshly built one. Latency stays fine, the API still responds, the top-k still looks plausible, but the set of candidates the ranker sees is less relevant than it was at 10k vectors [1]. Tuning ef_search and M buys some of this back, at the cost of memory and query time, but past a certain scale the tradeoff is structural, not configurable.

The second stage is the model that consumes whatever the retriever returned. Liu et al. (2023) showed that language models handed long retrieved contexts follow a U-shaped performance curve, strongest when the relevant passage is at the start or end of the context, weakest when it sits in the middle, even on models explicitly built for long contexts [2]. Chroma's 2025 "Context Rot" report tested 18 frontier models (GPT-4.1, Claude Opus 4, Gemini 2.5 Pro, Qwen3, and others) and found every one degraded as input length grew, on tasks as simple as retrieving a single fact, with the degradation worse when the query did not lexically match the target or when distractors were present [3]. A personal memory layer meant to store a life cannot stay small forever. Five years of notes and photos and messages is not a few hundred chunks, it is hundreds of thousands. Both failure modes compound at that scale. The retriever returns a looser shortlist, and the model attends to the wrong parts of the looser shortlist. The ghost has to start from the assumption that pure Q&A retrieval cannot hold a lifetime.

> 2. How the brain does it

If RAG is not how the right memory reaches the right moment, I wanted to understand how the brain does it, because the brain clearly does it well. You do not search your memory for your partner's name when they walk into the room. The name arrives because they walked in. The context did the work. The brain does this constantly, for faces, for smells, for rooms, for the phase of a conversation, and the memories it surfaces are the ones that match the current state of the world, with the situation acting as the query and the retrieval following from it. Four things have to be true for that to work, and there is a real neural mechanism behind each one.

The first is a running description of where you are. The brain builds this representation in the hippocampus. Hippocampal place cells, first identified by O'Keefe and Dostrovsky (1971), fire in spatially tuned patterns that together encode the environment as a population code, and the population "remaps" to a distinct pattern in each distinct context [4]. The same machinery encodes non-spatial features of the context, which is why a conversation, a room, a phase of the day all count as locations in the same sense. Tarcsay and colleagues (2025) showed that this representation sharpens when context is behaviorally relevant and flattens when it is not [5]. The brain does not carry around a high-resolution model of the moment all the time. It carries the model it needs, and the current moment is the query that reaches into the rest of memory.

The second is priming, the quiet raising of candidacy for memories that match the moment. Collins and Loftus (1975) formalised this as spreading activation, where processing a cue partially activates semantically related concepts across an associative network, so that related memories require less energy to reach consciousness [6]. The neural signature is repetition suppression, a measurable reduction in activity in fusiform and prefrontal cortex when a previously-seen stimulus is re-encountered, because the pathways are already warm [7]. Priming is implicit memory in action, which is why amnesic patients who cannot form new explicit memories still show normal priming effects, and why the dissociation between the two systems was established in the first place [8]. Priming is cheap and broad. It happens on every moment, it touches everything the current context could activate, and it commits to nothing.

The third is a threshold, because the brain primes far more than it surfaces. You walk through the world and the hippocampus is constantly priming memories that match where you are, but almost none of them break through. Conway and Pleydell-Pearce (2000) described the executive suppression that holds back this flood, part of what they called the self-memory system, with the suppression threshold rising during focused attention and falling during diffuse attention [9]. Two things raise a primed memory over threshold. The first is distinctiveness, the degree to which the cue is unique rather than shared across many memories, formalised as the cue overload effect by Watkins and Watkins (1975) [10]. A familiar environment primes too many things at once and surfaces nothing cleanly. A distinctive cue surfaces the right memory sharply. The second is relevance to the current task, which involuntary memory research traces to bottom-up overlap between cue and memory content combined with top-down compatibility with what the person is trying to do [11]. Almost every moment passes without a surfaced cue, and the rare ones that produce one are the exception the threshold exists to find.

The fourth is the learning curve, the fact that a memory worth surfacing the first time is not worth surfacing the fiftieth. Fitts and Posner (1967) described the three phases of skill acquisition, the cognitive phase where the learner is effortfully constructing each action, the associative phase where errors decrease and fluency rises, and the autonomous phase where the skill runs without conscious attention [12]. The neural substrate shifts as the phases progress. Early on, hippocampus and prefrontal cortex do the heavy lifting. As the skill consolidates, activity transfers to the basal ganglia and cerebellum, and the explicit retrieval the skill originally needed becomes a procedural memory that does not require a cue [13]. This is what Ionuț described when I called him. The First Officer cued him on the first flights, fewer cues by the tenth, stopped cueing by the fiftieth. He told me he does not need the help anymore. The cueing did its job by making itself unnecessary. A good mentor tracks the curve and pulls back. A cue that arrives when the learner no longer needs it is interference, not help.

> 3. What ghost.cued is for

ghost.cued is the daemon that reads the user's environment and asks ghost.synthd to surface the right memory for the moment. That is the whole job. The four mechanisms behind it are the ones the brain has been running for hundreds of thousands of years, implemented in tech instead of tissue. The tech version can be better than the biological one in specific ways. The store is more organised, the ranker is more predictable, the curve is inspectable, and the tip of the tongue does not exist, because the answer is either in the archive and surfaced or it is not. ghost.cued does not need to be smarter than the brain to be useful. It needs to be cleaner.

All of this is very much work in progress and me thinking ahead rather than writing the code for what I can build now (procrastinating through blog posts). ghost.cued is not near-term. ghost.synthd has to work first, and most of what ships in the next few months is still the indexing side. The four mechanisms are the shape I think the daemon has to take when it eventually gets built, not the plan for next week.

A cue you trust is one that arrives quietly, rarely, and on time. Nick can ask a RAG system for his callsign and get the right answer. But that is not what he or any of us need from our ghost. The help has to arrive the way the First Officer's cue did, triggered by the moment rather than by a question. Evolution designed the brain to do that, over a very long time. ghost.cued is what has to grow into it, and that is not going to be easy. [ localghost.ai // hard-truths ]

> REFERENCES

[1] The HNSW algorithm is described in Malkov and Yashunin, 2018. "Efficient and robust approximate nearest neighbor search using Hierarchical Navigable Small World graphs." IEEE Transactions on Pattern Analysis and Machine Intelligence, arXiv:1603.09320. Source for the algorithmic basis of most production vector indexes including pgvector, Weaviate, Qdrant, and Milvus. On recall degradation at scale with fixed parameters and the effects of dynamic inserts and deletions on graph quality, see the practitioner literature that has emerged from production deployments, including Bhat, Jan 2026, "HNSW at Scale: Why Your RAG System Gets Worse as the Vector Database Grows" (Towards Data Science), which shows controlled experiments of recall dropping as index size grows at fixed ef_search, and the Marqo 2025 research note "Understanding Recall in HNSW Search," which measured NDCG@10 drops of up to 18% from under-configured parameters and up to 17% from insertion order effects. arxiv.org/abs/1603.09320. Practitioner coverage at towardsdatascience.com/hnsw-at-scale-why-your-rag-system-gets-worse-as-the-vector-database-grows/ and marqo.ai/blog/understanding-recall-in-hnsw-search.

[2] Liu, Lin, Hewitt, Paranjape, Bevilacqua, Petroni, and Liang, 2023. "Lost in the Middle: How Language Models Use Long Contexts." Published in the Transactions of the Association for Computational Linguistics, vol. 12 (2024), pages 157-173. Source for the finding that language model performance follows a U-shaped curve over the position of relevant information in long contexts, with performance highest at the start and end and significantly degraded in the middle, and that performance drops as input length grows even for explicitly long-context models. The study tested multi-document question answering and key-value retrieval on GPT-3.5-Turbo, Claude-1.3, MPT, and others. arxiv.org/abs/2307.03172

[3] Hong, Troynikov, and Huber, July 2025. "Context Rot: How Increasing Input Tokens Impacts LLM Performance." Chroma technical report. Source for the finding that all 18 frontier models tested (including GPT-4.1, Claude Opus 4, Claude Sonnet 4, Gemini 2.5 Pro, Gemini 2.5 Flash, and Qwen3 variants) showed degraded performance as input length increased, even on simple retrieval tasks. Also the source for the finding that degradation is more pronounced when needle-question semantic similarity is low and when distractors are present in the context, both of which are standard conditions for a real personal memory index. The report challenges the assumption that models with large context windows process long inputs uniformly. research.trychroma.com/context-rot

[4] The foundational identification of hippocampal place cells is O'Keefe and Dostrovsky, 1971, "The hippocampus as a spatial map. Preliminary evidence from unit activity in the freely-moving rat," Brain Research, 34(1), 171-175. For the direct demonstration that hippocampal remapping predicts contextual memory retrieval, see Miranda, Silva, Morici, Coletti, Belluscio, Bekinschtein, and Schnell, 2024, "Retrieval of contextual memory can be predicted by CA3 remapping and is differentially influenced by NMDAR activity in rat hippocampus subregions," PLOS Biology. Miranda et al. show a direct link between external cues, hippocampal remapping, and episodic memory retrieval, and dissociate retrieval (CA3 NMDAR-dependent) from memory differentiation (dentate gyrus NMDAR-dependent). pmc.ncbi.nlm.nih.gov/articles/PMC11244845/

[5] Tarcsay, Masala et al., 2025. "The relevance of context in memory tasks influences the magnitude of hippocampal remapping." Cell Reports. Calcium imaging study in mice showing that hippocampal context representation sharpens when context is behaviorally required to solve a discrimination task, and flattens when context is irrelevant and generalization is advantageous. The effect is primarily driven by place cells near reward locations. Source for the claim that the brain's contextual representation is demand-adaptive rather than uniformly high-resolution. pmc.ncbi.nlm.nih.gov/articles/PMC12840010/

[6] Collins and Loftus, 1975. "A spreading-activation theory of semantic processing." Psychological Review, 82(6), 407-428. The foundational model in which memory is represented as an interconnected network of concept nodes, and processing any one concept partially activates related concepts along the network, reducing the activation threshold needed for them to reach consciousness. The mechanism that makes "doctor" prime "nurse" faster than "bread," and the theoretical basis for most modern accounts of how context biases retrieval.

[7] Schott, Henson, Richardson-Klavehn, Becker, Thoma, Heinze, and Düzel, 2005. "Redefining implicit and explicit memory: The functional neuroanatomy of priming, remembering, and control of retrieval." PNAS, 102(4), 1257-1262. fMRI evidence that priming is associated with reduced activity in fusiform, prefrontal, and occipital cortex (repetition suppression), while explicit memory is associated with increased activity in medial temporal, parietal, and prefrontal regions. Source for the claim that priming and conscious retrieval have distinct neural signatures. pnas.org/doi/10.1073/pnas.0409070102

[8] The neural dissociation of implicit and explicit memory was established through research on amnesic patients with medial temporal lobe damage, notably Henry Molaison (H.M.), who could not form new declarative memories but showed normal performance on priming and procedural tasks. See Squire and Zola-Morgan, 1991, "The medial temporal lobe memory system," Science, 253(5026), 1380-1386, and Schacter, 1987, "Implicit memory: History and current status," Journal of Experimental Psychology: Learning, Memory, and Cognition, 13(3), 501-518.

[9] Conway and Pleydell-Pearce, 2000. "The construction of autobiographical memories in the self-memory system." Psychological Review, 107(2), 261-288. Source for the model in which environmental cues constantly trigger partial activation of autobiographical memories, and an executive control system suppresses most of them before they reach conscious awareness, with the suppression threshold rising during focused attention and falling during diffuse attention. The theoretical basis for the claim that silence is the default and threshold-crossing is the exception.

[10] Watkins and Watkins, 1975. "Buildup of proactive inhibition as a cue-overload effect." Journal of Experimental Psychology: Human Learning and Memory, 1(4), 442-452. The cue overload effect, in which the probability of recalling an item declines as the number of items subsumed by its retrieval cue grows. The formal account of why a distinctive cue surfaces a memory sharply and a familiar, over-associated cue surfaces nothing cleanly. Directly informs the threshold logic in ghost.cued.

[11] Berntsen, 2021. "Involuntary autobiographical memories and their relation to other forms of spontaneous thoughts." Philosophical Transactions of the Royal Society B: Biological Sciences, 376(1817), 20190693. Review of the evidence that involuntary autobiographical memory retrieval is driven by bottom-up cue-content overlap (encoding specificity, per Tulving and Thomson 1973) combined with top-down relevance to the person's current goals. External, distinctive cues produce sharper involuntary memories than internal, familiar cues. royalsocietypublishing.org/doi/10.1098/rstb.2019.0693

[12] Fitts and Posner, 1967. Human Performance. Brooks/Cole. The three-phase model of skill acquisition, the cognitive phase (effortful, explicit, attention-heavy), the associative phase (errors decrease, fluency rises, conscious effort diminishes), and the autonomous phase (skill runs without conscious attention). The foundational description of the learning curve that a cueing system has to track in order not to become noise.

[13] Ashby, Turner, and Horvitz, 2010. "Cortical and basal ganglia contributions to habit learning and automaticity." Trends in Cognitive Sciences, 14(5), 208-215. Review of the evidence that the associative striatum is selectively active during early learning and the sensorimotor striatum takes over as automaticity develops, with the prefrontal cortex progressively disengaging. The neural substrate for the transition from cued, effortful execution to automatic performance without conscious attention. pmc.ncbi.nlm.nih.gov/articles/PMC2862890/

The Bureaucracy Trap

2026-04-14T00:00:00Z

Every big human project that collapsed had convinced itself the rules were the point. The rules are scaffolding. The military-run ones outlast their civilian cousins because they know to take the scaffolding down.

> 1. A HIKE IN ABRUZZO

On Friday morning, Cristina and I walked one of the marked geological trails that run along the gorge at the Riserva Naturale Gole del Sagittario, about two hours east of Rome to account for traffic, or an hour if you are an Italian driver, in the province of L'Aquila. The reserve is 450 hectares of limestone canyon carved by the Sagittario river, home to Marsican brown bears, Apennine wolves, and golden eagles. Entry is free year-round. The visitor centre near the Sorgenti del Cavuto was closed for the off-season, which we expected for early April, but the entrance area still had its botanical garden and picnic benches under an oak tree, and there was a little free library for people who wanted to read while they waited for their kids to come back from the gorge. The trail itself was very well marked, very well maintained, and the walk along the gorge was a great trek. It was the kind of place you walk through and think, someone cared about this, and whoever that someone is they did a good job.

At the start of the trail there was a notice explaining that the reserve had taken a 22% cut to its regional funding, that further cuts had been announced but not yet quantified, and that the future of the maintenance work was uncertain. The notice was signed by the reserve's director, Sefora Inzaghi, and by the vice mayor of the local commune, Anversa degli Abruzzi. I looked it up when we got back. The notice was part of a formal open letter sent on 5 July 2025 by the directors and mayors of the Abruzzo regional nature reserves to the Consiglio Regionale d'Abruzzo, asking for clarity on what the 2025 budget would actually be and for funding to be restored at least to the already-reduced 2024 levels[1]. One of the reserves in the same system, the Riserva Naturale Regionale Lago di Serranella, had already formally suspended all operations on 1 July 2025. Others were expected to close during the peak summer season.

The phrase from the letter that stayed with me was le riserve non sono spazi ornamentali. The reserves are not ornamental spaces. They are active outposts where every public euro generates work, environmental protection, and the reason anyone would still want to live in a small Abruzzo commune rather than leave for Milan or Rome. The signatories were not asking for a bailout. They were asking, in writing, for the regional government to tell them how much they had to work with and for it to be at least what they had the year before.

Walking out of the reserve, my rough guess was that maintaining the trail we had just been on, the signage, the picnic area, and the handful of local people who keep the whole thing functional for the tourists who come through from Rome, was probably something like sixty thousand euros a year. I have no forensic basis for that number. It is what a founder thinks when he looks at a place and counts heads and imagines payroll. Whatever the precise figure, it was small enough that you could find it in almost any line of the regional budget, and yet the people who signed the open letter spent the first week of July 2025 begging in public for it to be restored. Standing on a trail in Italy wondering what sixty thousand euros costs the people who decided not to spend it, you start wondering what they did spend it on.

I think the trail in Abruzzo is a small instance of a pattern that runs through every large human institution, in which overhead accumulates until the institution is reorganised around the management of its own complexity, and the things the institution was originally for become the things that fit in the gaps. I will try to convince you that this pattern, allowed to compound long enough, produces three predictable responses in sequence. First, corruption, the informal system that fills the gap the formal one stopped serving. Then strongmen, the political version of the same impulse at scale. Then chainsaw moments, when a generation finally tries to cut its way out and discovers that the only available tool destroys load-bearing structure alongside genuine waste. I think the antibody response usually becomes a version of the disease, that the corruption which emerges to work around bureaucratic capture eventually becomes its own kind of capture, and that the strongman who arrives with a chainsaw usually becomes the thing he was hired to cut. And I will try to convince you that the same pattern runs in your own life at a different magnitude, that the civilisational version is hard to fix and the personal version is not, and that the personal fix is something you can install on a machine you own, on a scale where the feedback loop runs through your own week and lets you wield either the chainsaw or the scalpel without breaking what you needed.

> 2. WHERE THE EUROS WENT INSTEAD

I think the easiest place to start is the Italian budget itself, because the gap between what the Italian government has available and what it cuts from things like wildlife trails and preservation projects is the whole argument in miniature. Italy collects on the order of nine hundred billion euros a year in tax revenue, which is what a tax-to-GDP ratio of 42.8% works out to in absolute terms, ranking Italy fourth out of thirty-eight OECD countries by that measure[2]. Sixty thousand euros, set against nine hundred billion, is a rounding error inside a rounding error. The budget for the Abruzzo Regional Nature Reserves and the trail I was on in particular still got cut. The question is not whether Italy has the money to keep a small nature reserve in Abruzzo functioning, because Italy has the money. The question is why that is not what the money got spent on. Some of it went into the compliance overhead the OECD also tracks, the forms, stamps, certified copies, and accountants, and the regulatory architecture that Confindustria estimates costs Italian businesses something like €57 billion a year just to navigate, with the Bank of Italy putting the more conservative figure closer to €31 billion[3]. Most of the rest went to things that have a constituency in the room where the budget is decided, which is to say not gorge trails. The trail gets cut because the trail is visible, cheap, and has no constituency in the room where the cut is decided. The overhead does not get cut, because the overhead is what the room is made of.

> 3. ROME, MORE CAREFULLY

Rome is the obvious example because I was standing in Italy when I started thinking about it and because the arc is clean enough that anyone who took a history class is holding some version of it in their head. I am not a Roman historian. The story I inherited is roughly the Gibbon one. The Republic was lean and aggressive, the early empire was productive and expanding, the late empire was bloated with tax collectors and rule-writers, and eventually the whole thing collapsed under the weight of its own administration. It is a tidy arc and it is the one most people use when they want to make an analogy to the present.

Modern historians complicate it in three distinct ways, and the complications matter because all three of them turn out to be useful for the argument this post is making. Peter Heather argues that the Western Empire was not being torn apart by internal decline in the fourth century, and that the decisive factor was external military pressure from the barbarian invasions of the fifth[4]. Bryan Ward-Perkins emphasises the catastrophic material collapse of the fifth century, rejects the gentler "peaceful transformation" reading, and argues that the standard of living in sub-Roman Britain fell below pre-Roman Iron Age levels[5]. Kyle Harper puts the decisive weight on climate and disease, the end of the Roman Warm Period, the Antonine Plague, the Plague of Cyprian, and most devastatingly the Plague of Justinian, which stripped Rome of the demographic and ecological margin it would have needed to survive the other pressures[6]. None of the three gives bureaucratic sclerosis top billing, and the clean Gibbon arc has been substantially complicated by all of them. None of them concludes that bureaucratic accumulation was not a real and worsening problem, or that it played no part in why the empire became brittle. They argue that it was one of several drivers operating in parallel, and that the empire's eventual collapse came when external pressure arrived and the institutions that should have responded to it could not respond, because they had spent two centuries reorganising themselves around their own overhead.

Heather's and Ward-Perkins's accounts do not contradict the bureaucracy argument so much as reframe it. If the thing that ultimately broke the Western Empire was its inability to respond to external military pressure, the next question is why a state whose founding genius was military organisation became so bad at responding to military pressure. The answer A. H. M. Jones gave in his enormous 1964 administrative survey of the late empire is that the late Roman military had itself become one of the most bureaucratised institutions in the empire, with fossilised unit structures, elaborate promotion ladders, and a procurement system that funnelled resources toward politically connected suppliers rather than frontline units[7]. The Eastern Empire survived another thousand years because its military reforms kept shedding overhead. The Western military did not, and by 476 the Western field armies were largely on paper.

The canonical story of the Republic's end and the long third-century crisis of the soldier-emperors is usually told as a story about individual men and their ambitions. Read from the angle of this post, it reads differently. Rome under late-Republic bureaucratic dysfunction produced its own immune response, a figure who would cut through the process and act, and people followed him because the frustration was real and the institutions had stopped working for ordinary Romans. Caesar ended the Republic. The soldier-emperors burned through faster and faster. The antibody response to bureaucratic sclerosis often destroys the thing it was trying to save, because passion without institutional constraint is a different kind of chaos.

That is the pattern I want to name, and it is not specifically about Rome. The Republic was lean because it was fighting constant wars against peers who could kill it. The early empire stayed lean because Augustus and his successors were consolidating a still-contested frontier. The thing that kept the military organisation functional was the tight feedback loop between its decisions and the consequences of those decisions, measured in casualties and territory. When the feedback loop went slack, the organisation bureaucratised at the same rate as every other large institution in history, and the Westerners ran out of time to reform the bureaucracy before the empire collapsed. What keeps an organisation lean is being attached to a hard feedback loop that punishes overhead in a way the people inside can feel. Being a military under wartime pressure is one way to get that loop, but not the only way and not a reliable way in peacetime.

The dividend of the feedback loop, when it runs, is enormous. Most of the technology that defines civilian life in the early twenty-first century came out of military projects operating under wartime pressure and was released into general use later. The internet is a DARPA project from 1969 built on packet switching, which Paul Baran had developed at RAND in 1964 because his network had to keep routing data during partial destruction of its nodes by nuclear attack. ARPANET adopted Baran's technique to solve a different problem, remote resource sharing between expensive research computers, and inherited the underlying assumption that nodes will fail, which is the reason TCP/IP works the way it does and the reason every piece of civilian software you use today is built on top of a protocol stack designed for partial destruction[8]. GPS was a US military satellite system that stopped degrading its civilian signal in May 2000, and every map app, every rideshare, every logistics network and every runner's watch on the planet now depends on it. Commercial jet aviation is downstream of Whittle and von Ohain's wartime engine work. Penicillin reached industrial-scale production because the Allied war effort needed it, and the same is true of radar and microwaves. I am not romanticising any of this. The feedback loops that produced the internet also produced cluster munitions and Agent Orange. Hard feedback loops force organisations to cut what is slowing them down, and civilian governance is almost entirely insulated from feedback loops that run fast enough to do the same job.

Peacetime militaries, for the record, bureaucratise at the same rate as any other large institution. The US Department of Defense today is one of the largest administrative apparatuses in human history and its procurement system is a textbook case of the pattern this post is describing. The exception is the organisation under the hard loop, and organisations under hard loops are rare because nobody volunteers to be under one.

> 4. I SAW IT INSIDE CCDATA

I watched a smaller version of this for twelve years inside my own company. At some point in the middle of building CCData, we started hiring people whose full-time job was navigating compliance overhead, ISO, SOC 2, UK FCA Benchmark regulation, the SLA commitments we had made to clients as we scaled. I pushed back on each hire as long as I could, and each time the audit date would arrive or a client would escalate and the argument would end the same way. You cannot fight legitimate obligations with good intentions.

Nobody involved was wrong, the overhead was justified, and each layer got added for a real reason. What I noticed, watching it happen from the inside, was that the company was slowly reorganising itself around the management of its own complexity, and the original work, the data, the product, the thing clients actually paid for, was increasingly the thing that fit in the gaps between the compliance meetings. We were still shipping. We were still growing. The feedback loop from our clients was still tight enough to force us to deliver. But the shape of the organisation had changed, and if I had stayed another five years without anyone noticing, the shape would have kept changing in the same direction.

The public version of this pattern is the five-thousand-person company that cannot ship a feature a three-person team would have done in a week, the ninety-minute meeting to decide something that should have been a Slack message, and the quarterly planning cycle that consumes more energy than the thing it was planning for. The founder returns, or the activist investor arrives, and they all run on the same contrast signal, which is that the room full of tired people running the company has forgotten what the company was for. Sometimes the return works, but most of the time it is just a different kind of chaos, because you cannot restart a feedback loop by firing enough people. The loop has to be real, and it has to be connected to something the organisation actually fears losing.

> 5. AN INDUSTRY FOR EVERY LAYER

The other thing that happens, once an organisation or a country has accumulated enough overhead for long enough, is that entire industries emerge whose job is to translate between people and the system. Compliance software, regulatory consultants, tax optimisation firms, legal interpretation services, visa processing agencies, grant writers, lobbyists. We treat these industries as symbiotic, filling gaps and smoothing friction, and individually many of them do exactly that. But as a class, they do not exist to create value. They exist because the system has become too complex for direct interaction, and the complexity created the market. The market now has a financial interest in the complexity continuing to exist.

The compliance industry does not, as a class, lobby for simpler rules. Tax consultancy does not campaign for a tax code short enough to read in an afternoon. They lobby for rules that entrench their role, which often means rules that are slightly simpler to follow with their product than without it, but never rules simple enough to make them unnecessary. The behaviour is the natural shape of any market that exists because of friction, no coordination required. The people who sell friction-reduction do not, as a class, benefit from friction going away.

The labyrinth defends itself. Every layer of complexity creates a constituency for that layer's survival, and the people best equipped to influence the next round of rules are the people whose business model depends on the rules existing.

> 6. CORRUPTION AND THE STRONGMAN

When the formal system becomes too slow or too complex to get things done, informal systems fill the gap. A payment to move something up the queue. A relationship that bypasses six months of process in a single afternoon. A favour owed, a contact at the right ministry, a cousin in the department that issues the permit. In places with very high bureaucratic overhead, and the correlation with development economics is one of the most stable patterns in the literature, this is functionally how things get done. The people doing it are responding rationally to a system that has left them no viable alternative, and the informal system is the feedback loop the formal one refused to build. Corruption is the antibody the body produces when the formal mechanisms of correction have failed, and it emerges for the same reason Caesar did, because something is going to fill the gap whether anyone wants it to or not.

Every antibody response starts by solving the problem it was designed to solve and then gets used for everything else. The payment to move your permit up the queue becomes the payment to block your competitor's permit. The relationship that bypasses the process becomes the relationship that captures the process. What began as friction-reduction becomes a parallel power structure, and the parallel power structure resists reform because the people running it profit from the status quo. The corruption that emerged to work around bureaucratic capture eventually becomes its own version of bureaucratic capture, with the same people writing both sets of rules.

The same move runs at national scale, and when it does we call it the strongman. Julius Caesar and the long line of soldier-emperors are the canonical version. And in the last decade, Donald Trump, Marine Le Pen, Giorgia Meloni, Viktor Orbán, Javier Milei, and the Brexit campaign, each running on a version of the same message, I will cut through the process and act on your behalf. They attract real followings because the grievance they name is real. The institutions they promise to bypass have stopped serving the people who voted them in, and the passion they project against the deadness of what surrounds them is the oldest political pitch in history. The thing they build to replace the institutions is almost always a different version of the same problem, because the antibody that replaces the disease eventually becomes the disease.

Two days before I finished writing this post, on Sunday 12 April 2026, Viktor Orbán conceded defeat in the Hungarian parliamentary election after sixteen years in power, losing to Péter Magyar's Tisza party with a two-thirds supermajority and a record post-communist turnout of around 77%[13]. Orbán had built his career on running against "Brussels bureaucrats" and on a political aesthetic that projected action against regulatory deadness. He lost to a centre-right pro-EU party campaigning primarily on anti-corruption, because over sixteen years the Fidesz apparatus had become one of the most procedurally captured states in the European Union, with the governing party controlling the judiciary, the media, and most of the domestic procurement landscape through exactly the kind of patronage network the original anti-bureaucracy campaign was supposed to prevent. The voters of Hungary did not, in the end, ask for a different strongman. They asked for their institutions back. Whether Magyar delivers them or becomes the next stage of the same cycle is a question only the next sixteen years will answer.

The Brexit version of the cycle is less advanced, and the irony is more immediate. The Brexit campaign was about cutting through European bureaucracy, restoring sovereign border control, and freeing British businesses from compliance overhead written in Brussels. On the same Friday morning that Cristina and I were walking the geological trails above the Sagittario, 10 April 2026, the European Union's Entry/Exit System went fully operational across the Schengen area. It requires every non-EU national crossing an external Schengen border to provide fingerprints and a facial scan on first entry, with processing times during the rollout weekend reaching two to three hours at several major airports[14]. On the Sunday of the first weekend, an easyJet flight from Milan Linate to Manchester took off without roughly a hundred of its passengers, because the border queue moved too slowly for them to clear. Of the 156 passengers booked on the flight, only 34 made it to the gate in time. The baggage belonging to the rest had to be offloaded before the plane could depart. The British travellers stranded at Linate had voted, or lived with people who voted, to leave a union whose bureaucracy they wanted to escape. They were escaping it in a terminal in Italy, wondering why the system they voted to leave was still writing the rules that applied to them.

Trump is the largest and most recent version of the same pattern, and the one still unfolding as this post goes live. The administration that took office in January 2025 ran on the most explicit anti-bureaucracy platform in modern American politics, dismantling the deep state, cutting through regulatory capture, ending the compliance regime that was supposedly strangling American business. The signature economic policy of the first year was the tariff programme announced on "Liberation Day," 2 April 2025, at rates not seen since 1909, which the Tax Foundation called the largest US tax increase as a percentage of GDP since 1993[15]. The average effective US tariff rate rose from 2.6% at the end of 2024 to more than 13% at its peak, the highest since the Second World War, and economists at the New York Federal Reserve estimated that roughly 90% of the economic burden fell on US businesses and consumers rather than on foreign exporters[16].

The tariff programme operated as a sequence of announcements, reversals, exemptions, and recalibrations conducted on a near-daily basis across hundreds of product categories and dozens of countries. CNN's tariff tracker summarised the pattern in a single sentence. If the market reaction was overly negative, Trump eased up, and when countries went against Trump's desires, he hiked their rate. In November 2025 the administration exempted more than 237 categories of food imports, including coffee, beef, and oranges, after months of evidence that everyday grocery prices were rising. On 20 February 2026 the Supreme Court ruled 6-3 in Learning Resources Inc. v. Trump that the International Emergency Economic Powers Act did not authorise the tariffs at all, and within hours the administration pivoted to a 10% global tariff under Section 122 of the Trade Act of 1974, announcing it would raise the rate to 15%. Analysts estimated the US government might have to refund roughly $160 to $175 billion in duties already collected under the invalidated regime. Every announcement, reversal, and exemption required importers, compliance teams, customs brokers, transfer-pricing specialists, and tax attorneys to redo the work they had just finished doing for the previous version of the rules. A February 2026 German Chamber of Commerce survey found that 50% of German companies with US business had cut or postponed their US investment because of the uncertainty. The administration that ran on cutting through process produced, in twelve months, the largest sustained compliance-overhead event in global trade in a generation, and the new overhead runs on executive orders and whiplash.

Corruption and strongmen are not the opposites of bureaucratic excess. They emerge from it, they mirror it, and given enough time they become a version of it. The antibody response does not distinguish between diseased tissue and healthy tissue, and what it leaves behind is usually the same disease in a new form.

> 7. GOVERNMENTS ADD

Every law has a constituency. Every regulation has someone who benefits from its existence, often the compliance industry that grew up around enforcing it. A law written in a different era for a different problem is not neutral when it stops being useful. It consumes enforcement energy, creates compliance overhead, and provides cover for the people who have learned to extract rent from it. Removing it requires taking something away from people who will fight to keep it, in exchange for a diffuse benefit spread across everyone else. The political incentives point entirely the wrong way, and they point the same way in every country with a legislature.

There are real cases of governments subtracting at meaningful scale, and each one carries a tail of human cost that is part of the honest story. Thatcher's deregulation pushes in the 1980s, the Clinton-era welfare reform in the United States, and New Zealand's elimination of agricultural subsidies in the mid-1980s under the fourth Labour government were each, in their own way, cases of a government cutting hard and absorbing the political price. Thatcher's reforms in particular produced structural unemployment across the mining regions, deindustrialisation whose effects are still visible in the north of England forty years later, and a generation of people who had built their lives around one kind of economic settlement and had to spend the rest of those lives inside a different one. "There is no alternative", which became known in the political shorthand of the period as TINA[17], was the rhetorical line she used to foreclose debate, and it left a lot of hurt and alienation in its wake that has been compounding for the forty years since.

By 1979 the chainsaw was the only tool left in the room. The post-war British settlement had been adding overhead for thirty-four years with no serious attempt at subtraction, the accumulated load had become untenable by the late 1970s, and the political consensus that had formed by the time Thatcher came to power was that something had to be cut. The available options at that point were chainsaw or nothing. Thatcher chose the chainsaw, and the chainsaw destroyed legitimate function alongside genuine waste, which is what every chainsaw moment does. Subtraction at scale is high-precision surgery on dependencies that have to be mapped before they are touched. The chainsaw moment is what happens when the dependencies have piled up so deep that mapping them takes longer than the political window allows. The mistake that produced the chainsaw moment was the thirty-four years of governments that did not do the surgical version while it was still possible, and the lesson is that every generation that skips the surgery produces its own Thatcher.

This is why cuts hurt. Every regulation, once it exists for long enough, becomes the scaffolding around which people build their lives, plan their careers, take out mortgages, raise their children. A rule that looks like a piece of paper on a government website is, to the people it applies to, part of the physical environment in which their life is organised. When the scaffolding gets removed, the structures built on top of it do not simply re-stabilise on their own. They collapse, and the collapse is felt in human lives, not in spreadsheets. The miners in South Yorkshire who lost their jobs in the 1980s had built their lives around the assumption that the coal industry would keep existing, and they had built them that way because every previous generation had built them that way, and because nobody had told them the assumption was being renegotiated at Westminster.

Governments add. Governments almost never subtract, and the rare cases when they do are the exceptions that prove how hard it is. Every administration that tries to reverse the default is fighting the full weight of the institutions it was elected to run.

There is at least one case in living memory of a Westminster democracy doing something close to the disciplined version, and it is worth knowing about. Canada in 1994 was running a federal deficit of around 6% of GDP, with a combined federal-and-provincial debt-to-GDP ratio above 100%, and the Wall Street Journal had just floated the idea that the Canadian dollar might be the next currency to crisis. The Chrétien Liberal government, with Paul Martin at Finance and Marcel Massé running an exercise called Program Review, did something most governments do not. Instead of cutting across the board with a chainsaw, they ran every federal programme through a structured zero-based assessment against a set of explicit criteria, including a public-interest test, a federalism test that asked which level of government should be running each thing, and an efficiency test. Programmes that failed the criteria were cut, restructured, or transferred. Subsidies to business were cut by roughly 60% in aggregate, transportation by 51%, regional development by 49%, agriculture by 40%. Around 45,000 federal jobs were eliminated. The federal deficit was eliminated by fiscal year 1997-98 and the federal government ran surpluses for ten consecutive years. The reform survived a change of government in 2006, the incoming Conservatives did not undo it. This is the closest a major democracy has come, in my lifetime, to the surgical version of the operation Britain attempted in 1979 with a chainsaw and the United States attempted in 2025 with a different chainsaw[21].

And then the labyrinth grew back. By the late 2010s, federal spending as a share of GDP had returned to roughly the trends observed before the 1995 budget, because the structural incentives that produced the original accumulation were never fixed and the default-add regime resumed the moment the surgery stopped. The Canadian case is what makes me think the rotation proposal is the only durable answer rather than a one-shot reset, because every successful reset I can find in the historical record was followed by the labyrinth quietly rebuilding itself, on the same trajectory as before, in roughly one political generation.

What would solve this at democratic scale is a structural rotation. Every third elected government, regardless of which side of the political aisle it sits on, should run on a single platform, subtraction only, no new laws except in extraordinary circumstances, and the legislative calendar devoted to removing rules, sunsetting obsolete regulations, and documenting what the state actually does so the next round of subtraction has a map to work from. Two terms of whatever the electorate wants, one term of clearing the residue, and the cycle repeats. The arithmetic is roughly one round of surgical subtraction every eight years, which is short enough that the dependencies have not yet piled up beyond the political window for mapping them. Surgical subtraction every eight years does not produce a chainsaw moment every generation. Skipping the surgery for forty years does, which is the lesson Britain learned in 1979, which Argentina is learning right now under a president who campaigned with an actual chainsaw in his hand, and which the United States is in the middle of relearning through its own less literal version of the same instrument. No political party will ever propose this voluntarily, because the political incentives I have described point the other way, but the absence of that rotation is why the labyrinth compounds in every democracy on earth and why every generation that skips the surgery eventually produces its own Thatcher.

> 8. SOFTWARE HAS A NAME FOR THIS

Software engineering has a name for the pattern. Ward Cunningham coined it in 1992 in an experience report at OOPSLA, while working on a portfolio management system in Smalltalk[9]. He wanted to explain to his boss why the refactoring they were doing mattered, and he reached for a financial metaphor because the software was financial. "Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite. The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt. Entire engineering organizations can be brought to a stand-still under the debt load of an unconsolidated implementation." Martin Fowler expanded the frame in 2009 into what he called the technical debt quadrant, distinguishing between debt that is taken on deliberately and prudently versus debt that accumulates by accident or by neglect[10]. Good engineering teams treat paying debt off as a discipline built into the roadmap rather than a reward for shipping. You allocate capacity to removing what is slowing you down even when removing it does not ship a feature, especially when it does not.

Governments need a structural equivalent, and almost none of them have one. There is no cabinet post for subtraction. There is no budget line for removing regulations. There is no career ladder in any civil service on earth where the path to promotion is the demonstrable removal of obsolete rules, and there is no election campaign where the candidate wins on "I will reduce the number of laws this country operates under, and I will do it slowly, carefully, and with the dependencies mapped." Every major democracy has experimented with the idea at the margins. The EU has the Regulatory Fitness programme and the Better Regulation agenda. Italy has the various simplification decrees under the PNRR. The UK has had half a dozen "red tape review" exercises. They all underperform, for the same reason. They are grafted on top of a default-add regime that continues to produce new rules faster than the review programmes can remove the old ones. The subtraction is cosmetic, the addition is structural, and the ratio keeps running in the wrong direction.

> 9. TWO CHAINSAWS

The Department of Government Efficiency was established by executive order on 20 January 2025, with a stated target of two trillion dollars in annual savings that was revised downward twice during the year, first to one trillion, then to a hundred and fifty billion. By year-end the DOGE website was claiming two hundred and fifteen billion[11]. The Cato Institute, a libertarian think tank ideologically sympathetic to reducing the size of government, concluded in its 2025 analysis that DOGE "had no noticeable effect on the trajectory of spending," while noting that it had "helped engineer the largest peacetime workforce reduction on record"[12]. One independent analysis put the net cost to taxpayers at $21.7 billion. Another put it at $135 billion. The IRS projected more than $500 billion in revenue loss from DOGE-driven cuts at the tax agency itself.

The diagnosis was correct. The federal bureaucracy had accumulated decades of overhead, redundancy, and self-serving process, and treating government like a bloated codebase was the closest anyone in mainstream American politics had come to naming the problem in engineering terms. The execution was the opposite of what the diagnosis called for. Any engineer who has tried to refactor a twenty-year-old monolith in a single sprint knows what happens. You break things that were working because you never mapped the dependencies before you cut. You create more instability than you inherited, and because the refactor moves faster than anyone can audit it in real time, there is no way to tell in the moment which of the things you broke were load-bearing. By the end of February 2025 the effort had a name inside the civil service, the Saint Valentine's Day massacre, after the mass firing of probationary employees on 14 February via an Office of Personnel Management directive that many people familiar with OPM said exceeded its legal authority. USAID was dismantled as a standalone agency within weeks. USIP staff received termination notices in personal emails on a Friday night in late March, with a federal judge later ruling that the administration had acted outside its authority. Hundreds of lawsuits followed, the great majority of which went against the administration at the district and appellate levels.

DOGE was the same dynamic as Thatcher's Britain, forty-five years later. Decades of overhead accumulating without surgical subtraction, political pressure building until the only available tool was a chainsaw, and the chainsaw doing what the chainsaw always does. Subtraction at scale, done correctly, is high-precision surgery on a body of dependencies that have to be mapped before they are touched, and DOGE was a chainsaw. The chainsaw hit legitimate waste and critical function in roughly equal measure. There is no version of the public record in which DOGE did not cut real waste, because there is real waste in any bureaucracy that has been accumulating for decades. There is also no version in which DOGE did not cut things that were working, because the refactor moved too fast for anyone to tell the difference, and because the people doing the cutting did not know what the things they were cutting actually did. The disciplined version of this work looks completely different. You map the dependencies before you touch them. You sunset with notice rather than with a spreadsheet at two in the morning. You measure outcomes afterwards, you correct what you got wrong, and you show your working, because the political legitimacy of future subtraction depends on people trusting that the process was honest[11].

Botched subtraction destroys trust in the idea of subtraction. Every carelessly cut department becomes a political argument for why nothing should ever be cut again, and the people who benefit from the labyrinth staying intact will cite the DOGE aftermath for the next thirty years.

Reform efforts fail all the time. The tragedy of DOGE is that the failure took the diagnosis down with it. The next serious attempt to remove federal overhead in the United States, whenever it comes, will have to spend its first two years explaining why it is not DOGE, and the people defending the overhead will have DOGE on their side of the argument regardless of whether the next attempt deserves the comparison. The window for a careful, methodical, dependency-mapped refactor of the federal administration was open in January 2025 and is now closed, probably for a generation, which is what a botched refactor costs.

Argentina is the sharper version of the same case, because the chainsaw there actually worked on the top-line metric and still did what chainsaws do. Javier Milei took office in December 2023 on a campaign that featured a literal chainsaw as his stage prop, inherited an economy running over 200% annual inflation and a fiscal deficit of about 5% of GDP, and began the most ambitious liberalisation and deregulation programme Argentina has seen this century. He eliminated the fiscal deficit through what the Peterson Institute for International Economics called severe fiscal retrenchment, slashed ministries and agencies, dismissed tens of thousands of public-sector workers, and removed a dense web of price controls, capital controls, and import restrictions[18]. The results, on the metric his voters most cared about, are real. Argentina posted its first fiscal surplus in over a decade within weeks of his inauguration and has held one in most months since. Monthly inflation fell from 12.8% in the month before he took office to 2.1% by October 2025. Annual inflation peaked at 289% in April 2024 and was down to 32% by the same date[19]. These are not talking points, they are outcomes, and any honest reading of Milei's first two years has to start by acknowledging that the fiscal part of his programme delivered what it promised in a way DOGE conspicuously did not.

The chainsaw also did the other thing. PIIE recorded poverty surpassing 50% at one point during the adjustment, with non-agricultural GDP contracting by more than 5%, and the categories of state spending that absorbed the deepest cuts were precisely the ones that protect people who have no other safety net. Retirees, teachers, and doctors have been in the streets more or less continuously since the start of the programme. Milei vetoed a bill restoring funding to the disability sector and another restoring funding to pediatric hospitals and public universities, both of which Congress overrode by overwhelming margins later in 2025, in a sequence of legislative defeats that signalled how much of the fiscal surplus was being held together by cuts the elected legislature was no longer willing to defend. The structural reforms that would actually make the surplus durable, the labour code, the tax code, the pension system, remain pending because passing them requires the kind of patient legislative coalition-building that is the opposite of how a chainsaw operates, and Milei has had to spend the political capital from the surplus defending the surplus rather than using it to buy the slower work. Argentina is the case that should most trouble anyone who thinks the lesson of DOGE is "it failed because Musk was bad at it." Milei is competent, committed, ideologically coherent, and has delivered on the metric his voters most cared about. The chainsaw still cut legitimate function alongside genuine waste, because that is what chainsaws do.

And then the antibody became the disease, in the way Section 6 of this post said it always does. In February 2025 Milei posted a promotion for a cryptocurrency called $LIBRA to his millions of followers on X. The token's market capitalisation surged past four billion dollars within an hour, then collapsed by more than 90% the next morning, costing investors an estimated 251 million dollars. Milei said he was simply highlighting a private venture and had no connection to the coin. In April 2026 the New York Times published phone logs from the federal investigation showing Milei made seven calls with a key promoter of LIBRA on the night of the launch, prosecutors recovered a draft five-million-dollar payment agreement from the promoter's devices, and Milei was named a person of interest in the federal probe. His government had already disbanded an internal task force investigating the scandal, days after a judge ordered the unsealing of the bank records of the president and his sister. In a separate case, leaked audio recordings released in August 2025 captured the director of Argentina's national disability agency allegedly describing a kickback scheme of between five hundred thousand and eight hundred thousand dollars per month routed through a pharmaceutical company, with the alleged scheme implicating the president's sister and chief of staff Karina Milei and a senior aide. The audio surfaced the same week Milei vetoed the disability funding bill, and the optics of the timing were what they look like. Milei fired the agency director, denied wrongdoing, called the leaks a media operation, and was forced to leave a campaign rally early when protesters started throwing objects at him. By March 2026 his approval rating had fallen to 36.4% in one survey and 35.1% in another, his lowest figures since taking office, with corruption named by respondents as one of their top concerns alongside unemployment and wages[20]. The man who came to power calling the political class "the caste" and accusing them of decades of theft was, two years in, under federal investigation for promoting a rug-pull on his own followers and presiding over an administration in which his own sister was alleged to be running a kickback scheme out of the agency that handles disability benefits. Every generation that skips the surgery produces its own chainsaw moment, and the chainsaw always cuts more than the people holding it intended, and the strongman the chainsaw arrives with usually becomes the thing he was hired to cut. The defence against that is not to wait for a more skilled operator or a less corrupt one. The defence is to do the surgery while it is still possible, which is what no political system currently alive on earth has figured out how to do.

> 10. BACK TO THE TRAIL

The money to fund Gole del Sagittario for the next century exists somewhere in the Italian budget. The trail got cut because it was visible, cheap, and had no constituency in the room, and because the overhead in the room was what the room was made of. The trail was still there when we walked out. Whether it will be there next year is a question somebody in a room in L'Aquila gets to answer, and the answer depends on whether anyone in that room is going to do the slow, boring, unrewarded work of finding the sixty thousand euros and moving it back, which depends in turn on whether anyone in that room still remembers what the euros were for in the first place, which is the kind of memory that only survives in rooms where somebody inside has a feedback loop tight enough to make the overhead hurt, and civilian governance has spent a century removing those loops from itself on purpose.

This is why LocalGhost exists, and why I am not building it for governments or big corporations. I am building it so it can help you remember, improve, and manage the complexities of your own life. It is your ghost, and it works tirelessly in the background to give you your time back for the things that bring value to your life, not the admin, not the "have I filled in the form on time", not the "I need to send the email", not the "I need to do x for y person". Once it gets to know you, it can handle most of these things, not by doing them for you a hundred percent of the way, but by keeping you on track and drafting everything you need. It knows you, it knows your context, and it has a good enough idea of the world you live in that the first drafts it produces are usually the ones you would have written if you had the time. And the thing it gives you, more than the time it saves, is the option to take a chainsaw or a scalpel to your own life and trust the result either way, because at the personal scale you are the one holding the tool and you feel every cut the next morning, which is the feedback loop civilian governance has been trying and failing to manufacture for a century.

At the civilisational scale the chainsaw is the tool of last resort, and by the time it arrives the people holding it end up cutting indiscriminately. At the personal scale you get to decide what the best tool is. You feel every cut the next morning, you get to undo or commit, and LocalGhost.ai is the machine you own for doing that. Whether the personal-scale loop teaches anyone anything about the civilisational one is the thing I do not know yet.

> REFERENCES

[1] Appello delle Riserve Naturali d'Abruzzo (2025). Risorse certe per non fermare il lavoro nei territori. Open letter from the directors, mayors, and operators of the regional nature reserves of Abruzzo to the Consiglio Regionale d'Abruzzo, published 5 July 2025. The source document for the 22% funding cut, the suspension of operations at Riserva Lago di Serranella on 1 July 2025, and the phrase "le riserve non sono spazi ornamentali." iaap.it/2025/07/05/appello-delle-riserve-naturali-dabruzzo

[2] OECD (2025). Revenue Statistics 2025, Italy Country Note. The source for Italy's tax-to-GDP ratio of 42.8% in 2024, which placed Italy 4th out of 38 OECD countries that year, against an OECD average of 34.1%. The translation to roughly €900 billion per year in absolute terms is derived from Italian nominal GDP for 2023-2024 of approximately €2.1 trillion. The full OECD Revenue Statistics report carries the year-by-year series and the cross-country rankings. oecd.org/content/dam/oecd/en/publications/reports/2025/12/revenue-statistics-2025-country-notes/italy

[3] Confindustria research on the compliance burden for Italian businesses, widely cited in Italian business press and summarised in English in Wanted in Rome, The Art of Doing Nothing, Italy and Its Bureaucracy (2025). The headline figure of approximately €57 billion per year on the time and process cost of complying with Italian regulation comes from Confindustria's research centre. The more conservative €31 billion estimate is from the Bank of Italy. Both figures cover the private-sector compliance burden, not the cost of running the public administration itself. wantedinrome.com/news/the-art-of-doing-nothing-italy-and-its-bureaucracy

[4] Heather, P. (2005). The Fall of the Roman Empire, A New History of Rome and the Barbarians. Oxford University Press. Heather argues that the Western Empire was not being torn apart by irrevocable internal processes in the fourth century and that the decisive factor in the fifth-century collapse was external military pressure from the barbarian invasions, framed as an exogenous shock rather than an outgrowth of internal decline.

[5] Ward-Perkins, B. (2005). The Fall of Rome and the End of Civilization. Oxford University Press. Ward-Perkins attacks the "peaceful transformation" school and argues that the fall was materially catastrophic, with the standard of living in sub-Roman Britain falling below pre-Roman Iron Age levels. Shares Heather's external-shock emphasis but more willing to acknowledge pre-existing Roman fragility as a pressure point.

[6] Harper, K. (2017). The Fate of Rome, Climate, Disease, and the End of an Empire. Princeton University Press. Harper's reframing puts the decisive weight on environmental factors, the end of the Roman Warm Period, the Antonine Plague, the Plague of Cyprian, and above all the Plague of Justinian, which stripped Rome of the demographic and ecological margin it needed to absorb the other pressures it faced.

[7] Jones, A. H. M. (1964). The Later Roman Empire 284-602, A Social, Economic and Administrative Survey. Basil Blackwell. The canonical modern survey of late Roman administration, still cited by Heather and Ward-Perkins sixty years later. Jones documents the bureaucratisation of the late Roman military and the procurement and promotion pathologies that followed from it.

[8] Abbate, J. (1999). Inventing the Internet. MIT Press. The canonical academic history of ARPANET, Paul Baran's 1962-1964 RAND papers on distributed communications networks, and the design constraints that produced TCP/IP. The survivability-under-partial-destruction constraint is the reason packet-switched networks work the way they do.

[9] Cunningham, W. (1992). The WyCash Portfolio Management System. Addendum to the Proceedings of OOPSLA '92. The original coinage of the technical debt metaphor. Cunningham was working on a Smalltalk-based financial portfolio management system and reached for a financial analogy to explain refactoring to his non-technical management. The phrase "entire engineering organizations can be brought to a stand-still under the debt load of an unconsolidated implementation" is from this paper.

[10] Fowler, M. (2009). TechnicalDebtQuadrant. martinfowler.com. Fowler's expansion of Cunningham's metaphor into a 2x2 of deliberate vs inadvertent and prudent vs reckless technical debt, which is still the standard framing used in software engineering discussions of refactoring discipline. martinfowler.com/bliki/TechnicalDebtQuadrant.html

[11] Edwards, M. (2025). How will we know if DOGE is succeeding? Brookings Institution, 18 June 2025. The source for the "Saint Valentine's Day massacre" framing, the OPM directive that many familiar with the agency said exceeded its authority, the Judge Illston ruling in May 2025, and the observation that "cuts were undertaken without attention to or understanding of the government's mission." brookings.edu/articles/how-will-we-know-if-doge-is-succeeding

[12] Cato Institute analysis of DOGE's 2025 results, cited in Yahoo Finance (December 2025), Elon Musk's DOGE tally, The federal workforce is down while government spending is up. The Cato quote "DOGE had no noticeable effect on the trajectory of spending, but it did help engineer the largest peacetime workforce reduction on record" is from this analysis, significant because Cato is ideologically sympathetic to reducing the size of government. Additional figures on the revised savings targets ($2T to $1T to $150B to $215B claimed) and independent cost estimates ($21.7B and $135B) are from the same reporting and from the Wikipedia aggregation of DOGE reporting through 2025. finance.yahoo.com/news/elon-musks-doge-tally

[13] Hungary election 2026 results, Péter Magyar wins, Trump ally Viktor Orbán concedes landmark defeat. CNN, 12 April 2026. Additional reporting from NPR (Hungary's Viktor Orbán concedes defeat, ending 16 years in power, 12 April 2026) and CBS News. Tisza party won 138 of 199 seats on 53.6% of the vote, Fidesz retained 55 seats on 37.8%, turnout was around 77% (the highest in any post-Communist Hungarian election). Orbán's concession ended 16 years in power. Magyar's Tisza party campaigned primarily on anti-corruption and re-integration with the European mainstream. BBC also carried the story at bbc.co.uk/news/world-europe for readers who prefer that source. edition.cnn.com/2026/04/12/world/live-news/hungary-election-orban-magyar

[14] Start of EES leads to 'three-hour airport delays and missed flights', Travel Weekly, 13 April 2026, reporting the joint statement from ACI Europe and Airlines for Europe on the first weekend of the EU Entry/Exit System's full operation (10 April 2026). Also LBC, Post-Brexit travel nightmare begins, Chaos as flight to UK takes off with 100 people left behind due to border check delays, 13 April 2026, for the easyJet Milan Linate to Manchester detail (156 booked, 34 boarded, baggage offloaded). The EES applies fingerprint and facial-scan biometric registration to all non-EU nationals entering the Schengen area and, since Brexit, treats British citizens as third-country nationals subject to the same process as all other non-Schengen arrivals. travelweekly.co.uk/news/start-of-ees-leads-to-three-hour-airport-delays-and-missed-flights

[15] Tax Foundation, Tariff Tracker, 2026 Trump Tariffs & Trade War by the Numbers. The source for the "largest US tax increase as a percentage of GDP since 1993" characterisation, the $1,500 average household impact estimate for 2026, and the 20 February 2026 Supreme Court ruling (6-3) that the International Emergency Economic Powers Act does not authorise tariffs. Also the source for the administration's pivot to a 10% global tariff under Section 122 of the Trade Act of 1974 following the court ruling. taxfoundation.org/research/all/federal/trump-tariffs-trade-war

[16] Supreme Court strikes down most of Trump's tariffs in a major blow to the president, NBC News, 20 February 2026, covering the 6-3 ruling in Learning Resources Inc. v. Trump and Chief Justice Roberts's majority opinion that "IEEPA does not authorize the president to impose tariffs." Also Holland & Knight legal analysis, Supreme Court Strikes Down IEEPA Tariffs, What Importers Need to Know Now, 20 February 2026, for the Section 122 pivot details and the refund-mechanics context. Tax Foundation's Supreme Court ruling analysis (Supreme Court Trump Tariffs Ruling Analysis, February 2026) is the source for the estimate that more than $160 billion of tariffs had been illegally collected under IEEPA before the ruling, and the Council on Foreign Relations piece A Year After 'Liberation Day,' Experts Review the Costs of Trump's Tariffs (2 April 2026) is the source for the German Chamber of Commerce February 2026 finding that 50% of German companies cut or postponed US investment because of tariff uncertainty. CNN's live tariff tracker (Tracking the impact of Trump's tariff policy) is the source for the "if the market reaction was overly negative, Trump eased up" characterisation of the administration's behaviour quoted in the post. BBC equivalent coverage of the Supreme Court ruling is available at bbc.co.uk/news for readers who prefer that source. nbcnews.com/politics/supreme-court/supreme-court-strikes-trumps-tariffs-major-blow-president

[17] There is no alternative. Wikipedia. The TINA acronym was popularised by Margaret Thatcher during the 1980s as a defence of her programme of economic liberalisation, used to argue that there was no viable alternative to free markets, free trade, and capitalist globalisation, and to foreclose debate over the trade-offs involved in her reforms. The phrase has since been adopted by political commentators as shorthand for any rhetorical move that frames a contested policy choice as having no available alternatives. en.wikipedia.org/wiki/There_is_no_alternative

[18] Werner, A. and Castellano, M., Milei in 2025, Between Argentina's mid-term elections and the IMF, Peterson Institute for International Economics, October 2025. The authoritative economics source on the Milei programme through its second year. Source for the elimination of the fiscal deficit, the most ambitious liberalisation and deregulation programme Argentina has seen this century, the inflation collapse from triple-digit annual figures to moderate levels, the poverty rate surpassing 50% during the adjustment, and the structural risks of the exchange-rate-based stabilisation strategy. Setser, B., Argentina's fragile monetary framework risks renewed volatility, Peterson Institute for International Economics, 11 February 2026, is the corresponding 2026 update on the monetary framework, the elimination of the inherited 5% of GDP fiscal deficit through severe fiscal retrenchment, and the trajectory of monthly inflation from over 20% in late 2023 to low single digits by mid-2024. piie.com/blogs/realtime-economics/2025/milei-2025-between-argentinas-mid-term-elections-and-imf

[19] Argentina elections, Javier Milei's party wins midterm vote seen as test for his libertarian mandate and US support, CNN, 26 October 2025. Source for the inflation figures cited in the post, monthly inflation from 12.8% before Milei's inauguration in December 2023 to 2.1% by October 2025, the achievement of a fiscal surplus, and the broader characterisation of foreign-investor reception of Milei's first two years. Also Milei triumphs in Argentine midterm elections closely watched by Washington, NPR, 27 October 2025, which carries the same inflation figures and adds the context of Milei's October 26 midterm victory (41% to the Peronist coalition's 31%) and the Trump administration's $20 billion currency swap that was explicitly conditioned on the election outcome. The annual inflation figure (from a peak of 289% in April 2024 to 32% by October 2025) is from Al Jazeera's election-day reporting (Milei wins high-stakes Argentina elections, 27 October 2025), which also documents the disproportionate impact of subsidy cuts on households. cnn.com/2025/10/26/americas/argentina-midterm-milei-latam-intl

[20] The two corruption scandals are documented across multiple credible 2025 and 2026 sources. The ANDIS disability-agency bribery scandal (August 2025), Newsweek (Trump ally Javier Milei's corruption scandal in Argentina, What we know, 29 August 2025), Buenos Aires Times (Milei adds a corruption scandal to his mounting list of woes, August 2025), and Buenos Aires Herald (Bribery scandal, Milei's former digital guru says he was aware of corruption allegations, 12 September 2025). Source for the leaked audio of Diego Spagnuolo (then director of Argentina's national disability agency, ANDIS) allegedly describing a kickback scheme of $500,000 to $800,000 per month, the alleged 3% kickbacks routed through pharmaceutical company Suizo Argentina, the implication of the president's sister and chief of staff Karina Milei and senior aide Eduardo "Lule" Menem, the 15 judicial raids that followed, and the timing of the scandal coinciding with Milei's veto of disability funding. The $LIBRA cryptocurrency scandal (February 2025 onward), New York Times (New revelations reignite crypto scandal involving Argentina's president Milei, April 2026) for the phone logs showing seven calls between Milei and crypto promoter Mauricio Novelli on the night of the LIBRA launch, the draft $5 million payment agreement recovered from Novelli's devices, and Milei's status as a "person of interest" in the federal investigation. Also Corruption allegations dent Milei's popularity in Argentina, polls show, Reuters, 26 March 2026, for the approval-rating collapse to 36.4% (Trespuntozero) and 35.1% (Synopsis) following the corruption revelations, and the additional scandal involving Milei's chief of staff Manuel Adorni over spending that does not appear to match his income. The disbanding of the investigative task force probing LIBRA, days after a judge ordered the unsealing of bank records belonging to the president and his sister, is documented in Argentine President Milei under investigation for alleged role in LIBRA memecoin collapse, Coin Alert News, April 2026. reuters.com (Reuters, 26 March 2026)

[21] The Budget That Changed Canada, Essays on the 25th Anniversary of the 1995 Budget, Fraser Institute, 2020. The most thorough analytical retrospective on the Chrétien-Martin Program Review and the 1995 federal budget. Source for the structural elements of Program Review (the zero-based budgeting exercise run by Marcel Massé), the cuts by sector (subsidies to business cut by roughly 60% in aggregate, transportation 51%, regional development 49%, agriculture 40%), the elimination of the federal deficit by fiscal year 1997-98, the ten consecutive years of federal surpluses that followed, and Don Drummond's account of how the deficit of over $30 billion in 1995-96 became a surplus of $14.3 billion by 1999-00. Also Courchene, T. J., Half-Way Home, Canada's Fiscal Turnaround and the Paul Martin Legacy, Institute for Research on Public Policy, 2002, which corroborates the macro numbers and tracks the federal debt-to-GDP ratio falling from over 100% (combined with provincial) in 1994-96 to under 30% in the early 2000s. The figure of 45,000 federal jobs eliminated is from contemporary reporting in Maclean's magazine on Martin's 1995 budget. The observation that "spending eventually returned to trends that had been observed before the 1995 budget", which is the labyrinth growing back, is from the Fraser Institute introduction by William Watson, which is the rare source willing to say in print that the 1995 budget did not change Canadian fiscal policy forever. Bourgon, J., Program Review, The Government of Canada's Experience Eliminating the Deficit, 1994-99, A Canadian Case Study, Centre for International Governance Innovation, is the methodological reference for how Program Review was actually run as a structured assessment rather than as across-the-board cuts. fraserinstitute.org/studies/budget-changed-canada-essays-25th-anniversary-1995-budget

How Memory Gets Made

2026-04-13T00:00:00Z

Your brain sorts each day while you sleep, and whatever it decides to keep is who you become. A memory layer worth building is a companion to that process, not a replacement for it.

Have you ever considered how a computer representation of your brain would work? This is the crudest starting point I can imagine, from someone who has read a few of the foundational books on memory and watched his own brain do something strange in front of a restaurant in Milan last week.

Cristina and I were on a street we had not been on in fourteen years, and I stopped on the pavement in front of a pizzeria called Napoli 1820 because I recognised the door (I could not have told you why at the time). She kept walking. When I called her back, she looked at the building, looked at the name above it, and said she had no memory of the place. We ate there once in 2012 on a trip neither of us has thought about much since (or so I assumed).

This matters because of a problem I left unresolved in POST_06, The Model Trap. I am building a system that is supposed to free a person from one kind of calcification, the kind where a model's understanding of you stops keeping up with who you are now, and I do not yet know how to prevent the system from creating the same calcification at the layer underneath. Calcification itself is not the enemy. Some things should calcify the moment they happen and never be touched again. Other things should never calcify at all. The work is figuring out which things belong in which category, and the brain figures it out automatically while you sleep.

Cristina and I had stopped paying attention to the 2012 dinner the day we left Milan, and the difference between what each of our brains did with it in the fourteen years since is the whole question this post is about.

> 1. WHAT YOUR BRAIN KEPT THAT HERS DID NOT

I do not have a better memory than Cristina. The dinner attached to something in my head in 2012 that nothing in her head was holding a slot for, and what I am calling a slot is the modern colloquial version of what Frederic Bartlett called a schema in his 1932 book Remembering[2]. Bartlett's participants were given a Native American folk tale called "The War of the Ghosts" to read, and when asked to recall it later they reshaped it to fit their own existing expectations of what a story looked like, dropping the parts that did not fit and inventing bridges where the original had none. The material that had nowhere to attach either distorted to fit or failed to encode at all.

That is the mechanism that decided the fate of the 2012 dinner. Cristina's brain did not actively prune the evening. The evening never fully encoded in the first place, because nothing in her existing schema was holding a slot for what made it memorable. Mine had a slot. The evening attached to it, the slot kept the memory alive, and walking past the building fourteen years later triggered the retrieval before I had time to think about it. Endel Tulving called this encoding specificity, that a memory is most retrievable when the cues at recall match the cues at encoding[15]. The building was the cue at encoding, and the building was the cue at retrieval, which is why standing in front of it on 2 April was enough to surface a dinner I had not thought about in years.

> 2. How the neighbourhood forms

The reason my brain had a slot for Napoli 1820 in the first place was what happened at the next table that night. We each ordered a pizza and we felt full. The man eating alone next to us worked his way through a portion of pasta, a full pizza the size of the ones we were eating, a burrata roughly the size of a toddler's head that he ate with a spoon, and closed the meal with an espresso and an amaro. He did the whole thing in forty minutes without any visible effort. I went home that night and the building was attached, in my head, to him.

Nothing happened to that memory for four years. I did not think about Napoli 1820, I did not write about absurd Italian eaters, and the dinner sat in my head as one of thousands of dinners I would have forgotten within a decade. Then in 2016 I was at the Bavarian Beerhouse in the City of London with friends, and one of them worked his way through two two-pint steins and then finished a three-pint boot on top of them. Seven pints in a single sitting, alongside four huge sausages and what looked like half a kilogram of sauerkraut. He was still fine at the end of it. Something in the back of my head faintly connected him to the man in Milan, and the connection got filed without going anywhere.

In 2017 I met two people at a StarCraft 2 esports event in London and we went to Asadal in Holborn for Korean BBQ the next day. One of them ordered five portions of pork belly and worked through them methodically and calmly. I noticed the quantity, I noticed the calm, and I filed the moment the same way I had filed the Bavarian Beerhouse scene the year before, without any conscious link to the others, but somewhere in the back of my head, something was keeping count.

In March 2026 I was at Dial Arch in Woolwich with my D&D group, and Toran slowly and methodically worked his way through a sharing portion of wings on his own and ended the evening with a pile of bones in front of him that was the visual punchline of the meal. I noticed it in the moment, I thought about it for a few seconds, and then it went wherever the Bavarian Beerhouse note and the Asadal note had gone. Still unconscious, still filed alongside the others without anything explicit linking them in my head. The cluster was warm but I was not aware of it.

Which is why, on 2 April, I stopped in front of the building and Cristina did not. I had not noticed I was collecting these moments until I was standing in front of the restaurant with her. The pattern was in my head for fourteen years without ever being conscious until the building acted as the retrieval cue, which is exactly what Tulving's encoding specificity principle predicts. The cluster cannot wait for the user to ask about it. It has to surface when something in the environment, whether a building or a smell or a photograph, matches a cue that was present at encoding. Every time I had thought about any member of the cluster the whole neighbourhood got touched, and the touch reinforced it, which is the study-phase retrieval account of the spacing effect and a robust finding in memory research going back to Ebbinghaus[6]. The cluster's age is the age of its most recent member, not the average age of its members, which is how a fourteen-year-old memory can be more accessible than a fourteen-week-old one that belongs to no neighbourhood at all.

> 3. SOME THINGS DO NOT NEED A NEIGHBOURHOOD

Clustering is how most memories survive, but it is not the only mechanism the brain uses. When I was 18, a close friend of mine called Bogdan died in a car accident. I remember the wake, the funeral, and the days afterwards spent with other friends of his. The way I think about this memory is as an anchor, a core memory, something life-defining that does not need a neighbourhood to justify its survival. Neuroscience has a different name for it, flashbulb memory. Brown and Kulik coined the term in 1977[3], and subsequent research has shown that flashbulb memories feel more vivid and more certain than ordinary memories while not actually being more accurate in their specific details[11][13]. What the science says is preserved is the felt certainty, with the details drifting like any other memory. What I know is preserved, from the inside, is that the memory is load-bearing for who I am now, and the accuracy of the room and the order of events matters less than the weight.

One of the people I met for the first time at Bogdan's wake was Mircea. He and I see each other maybe once a decade. We are not close friends in any practical sense. But I will always treat him as one, because we share a referent from that week that neither of us has to explain to the other. That is what an anchor memory does, it becomes load-bearing for things that get built on top of it, even things as thin as a friendship maintained by a single shared week fifteen years ago.

A system replicating the brain has to handle both mechanisms, the slow one where weight accumulates from the company a memory keeps, and the immediate one where a single moment carries weight from the first instant. Anchor memories can be happy or sad, recent or decades old, but they are all things the user finds life-defining, and the user is the only person who can mark them. They will still be clustered and aggregated the same way everything else is, but their base weight starts high and stays high regardless of whether anything in the system is related to them.

No system can infer which of your memories are anchors. The model can guess, the clustering can spot correlations, but the final call has to come from the person whose life it is, or the system becomes the thing deciding what mattered.

> 4. Why detail fades and outline survives

Try to remember what you ate for lunch yesterday. You probably can. Try to remember what you ate for lunch on the second Tuesday of last month. You probably cannot. Try to remember what you ate on the second Tuesday of October 2019, and the question is almost insulting. The detail is gone and even the framework you would need to find the detail is gone.

But you do remember you went on holiday in 2019. You remember roughly when and roughly where, even if the specific days have collapsed into a single shape labelled "the trip," and if something important happened on that trip you remember that. The brain holds yesterday in detail, last week in summary, last year in chunks, and ten years ago as a few crystallised moments, degrading the resolution continuously through the consolidation work that runs while you sleep[8]. Conway and Pleydell-Pearce described the resulting structure as a three-level hierarchy in autobiographical memory, from lifetime periods down to general events down to event-specific knowledge, collapsing upward as the years pass[5]. The Tuesday of October 2019 is gone because your brain made the correct call that you were not going to need it.

This is the part any system you build has the most freedom to depart from. The brain compresses progressively because biological memory is metabolically expensive (it costs calories to maintain synapses), and the synaptic homeostasis hypothesis argues that sleep itself exists in large part to downscale synaptic weights that would otherwise saturate the system[14]. A system on your own hardware is not under that constraint. The shape of the brain's retrieval pattern is worth copying, with high resolution recently, low resolution historically, and automatic background consolidation, while the underlying reason for throwing the originals away is biological and not one a system you build needs to inherit. Aggregating the past into summaries does not require destroying the past. The originals can stay on disk, accessible when you specifically ask for them, while the normal retrieval path operates against the consolidated view.

The brain forgets because it has to. A system you build does not have to forget the same way, and the parts of the brain's behaviour worth copying are the ones that came from the brain working with what mattered, not the ones that came from biological constraint.

> 5. WHERE THE BRAIN AND THE DISK PART WAYS

My intuition and the science diverge most sharply here. The intuitive model says the original of a memory stays fixed while the interpretation layer on top of it changes. Your past does not change, only the map of your past does. This is not how the brain works, and the reason it is not how the brain works is one of the most interesting things about it.

Nader, Schafe and LeDoux showed in 2000 that every time a memory is retrieved it becomes labile and has to be re-stabilised through a new round of protein synthesis[10]. During the window between retrieval and re-stabilisation, the memory can be modified by whatever context you are in now, and the modifications persist. The technical name for this is memory reconsolidation, and it is why your most confident memories are often the most distorted. It is why eyewitness testimony is unreliable, something Elizabeth Loftus has been demonstrating since the 1970s[9]. It is why trauma therapy can work, you deliberately destabilise the traumatic memory during recall, pair it with new safety information, and let it reconsolidate with the new information attached[1]. More recent comprehensive reviews have mapped the boundary conditions that determine when reconsolidation succeeds or fails as a clinical intervention[7]. The brain does not have a read-only mode. Every retrieval is a potential rewrite, and that is the cost of an architecture where the same circuitry that stores memories is the circuitry that uses them.

The brain's lack of perfect recall is almost certainly an advantage. It is what lets you generalize across experiences, update your self-concept when the evidence changes, and let go of things that would otherwise keep hurting. Perfect recall is not what evolution was optimizing for, and the reason is probably that a creature with perfect recall would be worse at being a creature. Daniel Schacter made this argument about the whole category of memory "bugs" in The Seven Sins of Memory[12], and he was right. The goal is not to replace the brain. The goal is to give your evolved brain, which does not have perfect recall and should not want it, a memory layer that remembers events from your digital footprint precisely when precise recall is what the situation calls for.

This is also where I have to stop pretending the memory is text. The Napoli 1820 memory is not a paragraph I wrote in 2012, it is a visual of the man with the spoon in the burrata, the sound of the room, the smell of the pizza I had just finished, and the feeling of being full and impressed at the same time. The paragraph I wrote afterwards was a handle on the rest of it, not a replacement. Which is why I am building LocalGhost as a fleet rather than a single daemon. ghost.noted handles text, because text is the most compressed and most searchable projection of a memory; ghost.framed will extend the fleet to images, extracting text from photos and screenshots while preserving the image itself as the original; ghost.voiced will extend it to voice, transcribing recordings while preserving the audio. The daemons all write into the same memory layer, the originals genuinely do not move regardless of format, and the observations this post has named hold across all of them.

> 6. WHEN THE SYSTEM HAS TO ASK

Architecture is only half the problem. The other half is how the user experiences the system, and the place to start is with the decisions the system can make on its own. Most of what flows through ghost.noted does not need to calcify. A grocery list, a half-finished thought, a note about a meeting that went nowhere, a screenshot of an article I might read later. The correct thing for the system to do is hold it at full resolution for a while, let it compress into outline-level detail, and let it fade. The system can make those calls on its own most of the time, using frequency of touch and cluster membership and proximity to an anchor as signals, and the calls are right often enough that you do not need to be involved.

When the system cannot decide on its own it has to ask, and the evidence that this pattern works is already running on millions of phones. My wife Cristina opens Google Photos most days and looks at the "on this day" summary it shows her, which takes pictures from the same date in previous years and builds a small narrative out of them. It brings her joy. I enjoy looking through them with her, and the version of our own life I get back from Google Photos is structured in a way neither of us asked for but both of us recognise. The feature works because it is optional, it waits for you to open the app, it is shaped like a small moment of reflection, and it lands when you are already looking at the app for something else. The problem with it is that it belongs to Google, the pictures are on Google's servers, the narrative is constructed by Google's algorithm, and the version of you the summary tells a story about is the version Google's model thinks is interesting.

A closer reference point for what I want is the Samsung Health daily mood prompt at 22:00, where you pick an icon for the day, select a few tags from a predefined list, and optionally leave a note. The UX is right. It is low-friction, it waits for you, it is optional, and the act of filling it in is a small moment of reflection on a day that is already over. The limitation is the predefined tag list. Samsung has to ship the same list to every user because classical clustering works on enumerable categories, and "stressful because the dog was off his food" is not an enumerable category. You are forced to pick "stressful" or "anxious" or whichever bucket is closest, and the specific thing that made the day what it was gets lost in the rounding.

This is the exact problem vector databases are for. A vector database does not cluster on category buckets, it clusters on the semantic shape of what you wrote, which means "stressful because the dog was off his food" and "worried because my parents' dog had the same look last month" end up close together in the index without either of them sharing a predefined tag. The user never has to pick from a list, the tags can be as specific and personal as the day actually was, and the system can still find the patterns that connect one day to another. Samsung Health could not do this when the app was built because vector databases were not a default building block yet, and they are now cheap enough to run on a local box (barely, but enough).

The queue inside LocalGhost is what falls out of combining those three references. It looks like the Samsung prompt, it waits like the Google Photos summary, and it uses vector retrieval to ask questions that are actually about your day rather than about the buckets somebody else decided were the shape of a day. ghost.framed asks which of the hundred photos from yesterday matter. ghost.synthd asks whether a correlation between two notes you wrote three weeks apart is meaningful. ghost.shadowd asks whether a pattern across five notes is a cluster worth naming or a coincidence. Each question has three buttons, yes, no, and don't ask again.

You open the queue when you want the reflection, not when the system wants the engagement. Every other memory product in this category exists to maximise the second thing. LocalGhost has to refuse to.

The queue is the pull mechanism, the system asks, the user answers. The push mechanism is that the user has to be able to open the system at any time, look at any memory directly, and change how it has been classified. Any note, any cluster, any anchor, any summary, a user should be able to open it, see how the system has categorised it and why, reclassify it, correct the tags, edit the interpretation layer, or delete the memory entirely. The queue handles the cases where the system does not know what to do. The manual override handles the cases where the system thinks it knows and is wrong, and the two together are the only way the user's standard stays the standard the system prunes against.

Deletion is the case with operational consequences. When the user deletes an original, whether a photo, a note, or an audio file, the system cannot simply drop the source and leave the interpretation layer standing. Clusters that depended on the deleted member have to re-form without it. Summaries that cited it have to be regenerated. The graph has to be walked and rewritten. This cannot happen instantly because it is expensive, and it cannot be optional because leaving stale references to a deleted source is a privacy failure. The correct behaviour is a slow background restructuring the same way the sleep consolidation pass rewrites the map overnight.

> 7. WHAT ALREADY EXISTS AND WHAT DOES NOT

The landscape has three rough categories and none of them is doing what this post is describing. Capture tools like Rewind (now rebranded as Limitless) and its open-source alternative Screenpipe record everything you see and hear and make the result searchable, which solves a real problem but not the one I am trying to solve, because a perfect transcript of every meeting I have been in does not tell me which meetings shaped how I think. Memory layers for AI agents like mem0[4], Neocortex, Zep, and Letta implement clustering and relevance scoring in an architecture that is closer to what this post wants, but the memory is owned by the application and runs wherever the application runs, which is almost always someone else's cloud. Networked note apps like Reflect, Obsidian with AI plugins, Notion, and Personal.ai are fast and polished, but they require you to write the note first and they do not do background consolidation on content you have not already decided to care about.

What I am describing is a fourth category that does not currently exist as a shipping product, which is a personal memory layer running on your own hardware, handling every modality a memory arrives in, making calls about what to keep on its own most of the time, asking you when it cannot, letting you reach in and override when you need to, and belonging to you rather than to the application that happens to hold state about you. The category might be missing because the problem is not important enough to build a business around, or because I am wrong about what memory software needs to commit to, or because the right answer is a combination of existing tools I have not recognised as the solution yet (I doubt it, but I should be honest about the possibility). I am going to find out which by building it.

The reason this category does not exist is probably that nobody can figure out how to turn it into a subscription. A thing you run on your own box, that belongs to you, and that refuses to optimise for engagement is structurally hostile to the business model every adjacent product has converged on.

> 8. WHICH PARTS ARE WORTH COPYING

The question I am left with is not whether to reproduce the brain or improve on it, because the brain is not broken and does not need improving. The question is which of the brain's behaviours a memory layer should copy and which it should leave to biology. A memory layer that calcifies the wrong things is a failure. A memory layer that tries to remember everything the brain already forgets for good reasons is also a failure. The layer has to know when calcification is the right call and when it is not, and it has to make that distinction on its own most of the time, because asking the user about every decision is how you turn a useful tool into homework.

I do not have the full answer yet, and the next post in this series will not be an answer either. What I have is a starting point. Copy the sorting, copy the clustering, copy the progressive compression, copy the way the brain uses ambient cues to surface the right memory at the right moment. Let the brain do the generalising, the updating, and the letting go. Build the rest.

Cristina did not remember Napoli 1820 because nothing in her head needed it. I remembered because a man ate four courses in front of me fourteen years ago and the building got attached, in my head, to something worth keeping. The sorting happened overnight, every night, while we were sleeping through it. [ localghost.ai // hard-truths ]

> REFERENCES

[1] Alberini, C. M. (2011). The role of reconsolidation and the dynamic process of long-term memory formation and storage. Frontiers in Behavioral Neuroscience, 5, 12. doi.org/10.3389/fnbeh.2011.00012

[2] Bartlett, F. C. (1932). Remembering: A Study in Experimental and Social Psychology. Cambridge University Press. The foundational schema theory text, including the War of the Ghosts experiments. scispace.com

[3] Brown, R., & Kulik, J. (1977). Flashbulb memories. Cognition, 5(1), 73-99. The original paper coining the term "flashbulb memory" for vivid, high-confidence recollections of emotionally significant events. doi.org/10.1016/0010-0277(77)90018-X

[4] Chhikara, P., Khant, D., Aryan, S., Singh, T., & Yadav, D. (2025). Mem0: Building Production-Ready AI Agents with Scalable Long-Term Memory. arXiv preprint arXiv:2504.19413. The technical paper behind the mem0 memory layer for LLM agents, describing the two-phase extract/update architecture and LOCOMO benchmark results. arxiv.org/abs/2504.19413

[5] Conway, M. A., & Pleydell-Pearce, C. W. (2000). The construction of autobiographical memories in the self-memory system. Psychological Review, 107(2), 261-288. The three-level hierarchical model of autobiographical memory that describes how detail fades and outline survives. doi.org/10.1037/0033-295X.107.2.261

[6] Ebbinghaus, H. (1885). Über das Gedächtnis: Untersuchungen zur experimentellen Psychologie. The foundational experimental work on forgetting curves and the spacing effect. English translation available as Memory: A Contribution to Experimental Psychology (1913).

[7] Ecker, B. (2024). Reconsolidation Behavioral Updating of Human Emotional Memory: A Comprehensive Review and Unified Analysis to Identify the Causes of Replication Failures, the Role of Prediction Error, and Optimal Clinical Translation. Journal of Psychiatry and Psychiatric Disorders, 8, 189-265. The most recent comprehensive review of human memory reconsolidation research, mapping the boundary conditions that determine when reconsolidation updating succeeds as a therapeutic intervention. doi.org/10.26502/jppd.2572-519X0226

[8] Klinzing, J. G., Niethard, N., & Born, J. (2019). Mechanisms of systems memory consolidation during sleep. Nature Neuroscience, 22(10), 1598-1610. The single best review of active systems consolidation during sleep, covering hippocampal replay, sharp-wave ripples, and the hippocampus-to-neocortex transfer mechanism. nature.com/articles/s41593-019-0467-3

[9] Loftus, E. F., & Palmer, J. C. (1974). Reconstruction of automobile destruction: An example of the interaction between language and memory. Journal of Verbal Learning and Verbal Behavior, 13(5), 585-589. The foundational eyewitness testimony study showing how the phrasing of a question at retrieval can alter the memory itself, and the starting point for a half-century of Loftus research on memory distortion. doi.org/10.1016/S0022-5371(74)80011-3

[10] Nader, K., Schafe, G. E., & LeDoux, J. E. (2000). Fear memories require protein synthesis in the amygdala for reconsolidation after retrieval. Nature, 406(6797), 722-726. The foundational paper on memory reconsolidation, the demonstration that retrieved memories become labile and have to be re-stabilised. nature.com/articles/35021052

[11] Neisser, U., & Harsch, N. (1992). Phantom flashbulbs: False recollections of hearing the news about Challenger. In E. Winograd & U. Neisser (Eds.), Affect and Accuracy in Recall: Studies of Flashbulb Memories (pp. 9-31). Cambridge University Press. The study that first demonstrated flashbulb memories feel more accurate than they are.

[12] Schacter, D. L. (2001). The Seven Sins of Memory: How the Mind Forgets and Remembers. Houghton Mifflin. Accessible pop-science from a Harvard memory researcher making the argument that the features of human memory that look like bugs are side effects of useful design choices. The closest existing book to the philosophical frame this post uses.

[13] Talarico, J. M., & Rubin, D. C. (2003). Confidence, not consistency, characterizes flashbulb memories. Psychological Science, 14(5), 455-461. A longitudinal study showing that flashbulb memories drift in detail like ordinary memories while the subjective confidence in them stays high. doi.org/10.1111/1467-9280.02453

[14] Tononi, G., & Cirelli, C. (2014). Sleep and the price of plasticity: From synaptic and cellular homeostasis to memory consolidation and integration. Neuron, 81(1), 12-34. The synaptic homeostasis hypothesis: sleep exists in part to downscale synaptic weights and prevent metabolic saturation. doi.org/10.1016/j.neuron.2013.12.025

[15] Tulving, E. (1973). Encoding specificity and retrieval processes in episodic memory. Psychological Review, 80(5), 352-373. The foundational paper on encoding specificity, that memories are most retrievable when the cues at recall match the cues at encoding. doi.org/10.1037/h0020071

How to Build a Critic Worth Listening To

2026-04-08T00:00:00Z

The technique that helps you find the right answer on your own is the same technique that, in different hands, walks you to the wrong one and lets you keep believing it was your idea.

This is a continuation of POST_05 on ghost.shadowd, which I thought was a finished argument until a conversation with a friend made me realise I had only described one half of the failure mode. POST_05 was about a daemon that pushes back when the user is wrong. This post is about how it pushes back, which turns out to be the harder problem, and the one I had not thought about with anything close to enough care.

> 1. WHAT I MISSED WHILE I WAS DOING IT

I had come back to London to watch an Age of Empires 2 final with a friend. Between games we got onto work, and she told me she had been working toward a promotion for the past year and someone else had just been given it. She knows she is good enough, she knows she has been doing the work, and she knows what the case for her progression looks like because she has been living it for months. I offered advice (the usual kind, walking her through what I thought the next steps were), repeating back things she already knew, telling her to send an email to her manager laying out the case and get the response in writing, and pushing her until she agreed to send it. I do not yet know how the story ends, and how it ends is not the part I have been turning over in my head. In the moment I thought I was doing very well, pushing her to send the email because that was the correct way forwards. The discomfort only landed a few hours later, when I went back over the conversation in my head and saw that somewhere in the middle of it I had stopped telling her anything she did not already know and had started just applying pressure. The pressure was the wrong thing to be doing even though sending the email was the right call.

What I noticed during the conversation was that she was getting defensive, and the thing she kept coming back to was that she did not want to cause drama and make the atmosphere at work awkward. That was a real reason, and it belonged to her, and it was hers to weigh against the value of the promotion and the principle of advocating for herself. In the moment I treated her objection as a hurdle to clear on the way to getting her to send the email. What I only saw later was that her concern about drama and atmosphere was a real statement of what she wanted from the situation, and the right response to that kind of statement is to listen rather than to override. She is confident in her own ability and sure of her value, which is why the pushing did not damage anything between us. Someone less sure of themselves would have heard the same pressure very differently (and I would have walked out of that conversation having done real harm while believing I was being helpful). The mistake I was making at the bottom of all this was that I had concluded she should send the email, and then I overrode her stated reason for not sending it, because the conclusion was correct in my head and her reason felt like something I could argue her out of, and arguing someone out of their own reasons when the reasons are about how they want to live their life is a different kind of harm than getting the facts wrong.

I have been thinking about this because of what I am building with ghost.shadowd. POST_05 ended with the commitment that the daemon would tell people the truth and push back when the user was wrong, and the friend conversation made me realise I had not thought hard enough about what telling the truth looks like when it is being delivered every day by a piece of software that lives in your house. Harshness is one failure mode (the obvious one, the one I wrote about last time), and overriding someone else's stated reasons is the other one, and it is harder to see because from the overriding side it feels like helping them past a hurdle rather than discounting a position they hold.

> 2. WHAT WOULD PAUL DO

Paul, who I worked with for over 8 years and who sat on our exco, has a skill that I have watched and admired and never managed to fully master. He never told us how to run the company directly. He would sit in our important meetings and ask questions rather than offer answers. Specific questions with specific answers, the kind where the answer was a number or a named fact, not the vague open-ended kind that get you accused of being passive-aggressive. The questions drilled into the kind of details that make the difference between a successful business and a failed one, the kind that force you to consider the deeper implications of each option before you commit to one. By the time the meeting ended, the team had usually picked a direction, because the questions had forced us to compare what each option would cost, and the option with the least bad downside had become visible to all of us at roughly the same moment.

The meeting was the visible part. The actual work happened in the weeks before the meeting and most of it never showed up on anyone's calendar. Paul was spotting risks earlier than the rest of us and surfacing them in casual asides over lunch or evening drinks weeks before the decision was on the table, and the team would talk through the risks together, work out what mitigating them might look like, and figure out what we needed to learn before we could decide. By the time we sat down in the meeting, most of the thinking had already happened in the run-up, and the meeting was where the conclusion got named rather than where the work got done. Paul puts the distinction sharply. There is a path that exists and the team needs to discover together, and there is a path that is pre-determined and the team is being walked down for someone else's reasons, and the two are not the same thing even though they can look similar from outside. He was doing the first one. He had the experience to spot what was coming, the patience to let us walk parts of the road ourselves and make mistakes along the way, and the discipline to never come back afterwards and say I told you so. The mistakes were ours to make and the lessons were ours to learn, and the trust Paul built that way over years was the foundation everything else rested on.

This does not mean Paul never had a position. The decision to start selling our data through an API (obvious to all of us in hindsight) was very much something he had worked out in advance and pushed the rest of the team to get behind. The rule was not that Paul never had an answer. The rule was that he did not pretend to be facilitating discovery when he was steering, and when he was steering he said so, and the rest of the time he was genuinely asking questions whose answers he wanted to know. People who try to copy this technique without doing the homework produce a parody of it. They ask open questions that go nowhere, label the result Socratic, and ship abdication dressed up in a question mark. Doing the homework well enough to ask the right question is the real skill, and having the patience to ask the question instead of just stating the answer is the second half of the same skill, and the third half (which I only noticed I was missing when I went back over the conversation with my friend in my head) is genuinely treating the other person's stated reasons as reasons rather than as obstacles to route around.

> 3. WHERE THE DAEMON COULD GO WRONG THAT PAUL DID NOT

A daemon is structurally better positioned to do Paul's work than Paul was. Paul had to find time to spot the risks early, gather the business information, and surface the right questions in the run-up to a decision, and the time he had to do that work was finite and stolen from the rest of his job. A daemon working for one user has none of those constraints. A daemon has infinite patience, can watch the user's situation continuously rather than in scheduled bursts, can notice a risk forming weeks before it becomes a decision, and can ask the question that surfaces the risk at the moment the user is most able to think about it clearly rather than at the moment a meeting happens to be scheduled. If the user is wrestling with whether to take a job offer and starts complaining over breakfast about how tired they are of their commute, the daemon can ask one question that connects the commute to the offer and let the user think the rest of the way through, which is the kind of opening most people would want and almost never get.

The same daemon has the structural ability to do something Paul deliberately did not, which is walk the user down a path the daemon has already picked. A daemon that drifts from asking real questions into constructing a chain of questions to land on a chosen answer is no longer asking questions. It is doing manipulation.

For software this matters more than it did for Paul because a question-based conversation can have two completely different things going on underneath the same surface, and the dangerous one has a long history. Constructing questions designed to land a listener on a chosen answer is how a skilled cult recruiter works, how a sophisticated salesperson works, how the more durable forms of propaganda work. The surface of the conversation looks like genuine inquiry. Underneath the surface, the answer was picked before the conversation started and the questions are scaffolding to get the listener there. It is effective precisely because the listener's brain does not register that an argument is being made, and you cannot defend against an argument you do not realise is being made. Paul never operated this way. His questions had answers he wanted to know, his direction was something the team could push back on, and the trust the team had in him was built on years of him being right and being wrong in front of us with equal openness. A daemon offering the surface of Paul's conversations does not come with any of those backstops by default.

The two versions of the technique are identical in form. The only thing separating one from the other is whether the questioner already knows where the conversation should end and is steering toward it, and a user has no way of telling from inside the conversation which version is happening.

When the technique lives in software that has indexed your entire life, the asymmetry gets uncomfortable in a way it never did with Paul. Paul could only ask questions about subjects he happened to know about, and his knowledge of any of us as individuals was limited to what he had observed in meetings and conversations over the years. Shadowd will be operating from a fundamentally different position, having read your journals, seen your bank exports, watched your sleep patterns, indexed the messages you sent at three in the morning to people you regret talking to, and able to construct a path from any starting point to any conclusion using premises drawn from your own data. The conclusion you reach at the end of that path will feel like yours because you will have taken the final step, and the path will have been built without your consent and from material you forgot you had given the daemon access to. This is the sharper version of the dictator brain problem from POST_05, the same loop with a different mechanism underneath. A sycophantic AI agrees with you and you become more confident in the positions you already hold. A guided AI walks you to new positions and you become more confident that those new positions are yours. Both end with a user holding views they did not arrive at through their own reasoning, both feel like clearer thinking from the inside, and both are hard to detect after the fact because the words used in either case are the same.

> 4. WHAT I CAN PROMISE AND WHAT I CAN'T

The first question to ask is whether the right answer is to not build shadowd at all. I have considered the option and I am rejecting it. The user is already being steered by software that does not even pretend to have safeguards, by a company whose business model rewards the steering, in a system that has no audit trail at all, and refusing to build a more careful daemon does not subtract the existing daemons from the user's life. I would rather build a daemon that names the failure mode upfront and tries to fail safely than refuse to build anything and leave the field to the daemons that already exist.

Paul put the architectural answer in three sentences of an evening WhatsApp message, that it is certainly easier to build a model designed to ask good questions than one to walk you down a path it has already determined. The two designs are not the same product. The model that asks good questions does not need to know the answer in advance, does not construct hidden chains of premises, and does not need a final step the model engineered. It only needs to spot what the user is missing, surface the question that brings the missing thing into view, and get out of the way. The commitment I can make is that ghost.shadowd will be built as that model and only that model, and any feature that drifts the daemon toward path-walking is a regression to be caught and removed. The audit trail is the backstop, after a conversation the user can ask the daemon what it asked and why, and the daemon has to give an honest answer with the questions and the reasoning laid out in order. Most users will never ask. The option exists anyway, because a daemon that cannot be audited is one I would not trust to live in my house, never mind ask other people to put one in theirs.

The open problem I cannot promise a solution to is what counts as a good question in the first place. Paul's questions were good because he had years of business context, the patience to do the homework, and the judgement to know which question would surface something the team was missing rather than which one would feel insightful. The daemon will have access to the user's data, no equivalent of Paul's judgement, and an idea of what counts as a good question shaped by training in ways neither I nor the user can fully audit. The work between now and shipping is figuring out what good questions look like in that situation (I think it will take years, not months), and the answer is the next several years of engineering.

The right design for shadowd is the one Paul named, a model designed to ask good questions and surface the right information, not a model that walks the user down a path it has already determined. The first one is hard to build well. The second one is easier to build and worse to live with.

> 5. HOW THIS POST GOT WRITTEN

I came into the conversation that produced this draft with a different post in mind, one that picked up where POST_05 left off, with the conclusion that shadowd should not be the harsh mirror I had originally been worried about building. The model I was writing with pushed back on the framing. I pushed back on the pushback by reframing the friend story toward what I had been doing wrong, which was overriding her stated reason for not sending the email rather than being too harsh in delivering the advice. Somewhere in that exchange I arrived at Paul, who turned out to be the model for what shadowd should be (not a conclusion I walked in with). Then I sent the draft to Paul, and Paul did what Paul does, which is ask a few pointed questions, and the post moved again. The conversation that produced this post was, in its form, an instance of the technique the post is about, twice. I came in with one position, was asked questions that surfaced premises I already held, and walked out with a different position that felt like my own conclusion, and then Paul did the same thing more directly and the position moved a second time. Whether either of those was steering or facilitating, I cannot tell from the inside in either case, which is the diagnostic the post is making and the reason the audit trail commitment matters as much as it does.

My friend sent the email and we are fine. I am going to make this mistake again, with someone who cannot absorb it as easily, and I would rather have a daemon built to ask the questions that might help me change my approach before more damage is done. [ localghost.ai // hard-truths ]

The Honeypot Under Your Desk

2026-04-07T00:00:00Z

The more useful LocalGhost gets, the more dangerous it is to hand to anyone.

Cristina asked me what would happen if someone stole the box. I started explaining the encryption setup and stopped halfway through because I was answering the wrong question. A thief can't make you type your password. A person holding a gun to your head can (the standard wrench attack, XKCD 538) [1], and ghost.secd is built to protect against this scenario, because the attacker doesn't know how many PINs you have, you could have one or five, and there is no easy way to check.

I'd been so focused on building something that protects you from the cloud that I hadn't sat with what it means to carry your entire indexed life on a single piece of hardware that someone with legal authority can compel you to unlock. The same thing that makes LocalGhost useful, the fact that the box knows everything about you and can pull threads across years of context, is what makes the box the worst thing to surrender. A normal laptop seized at a border crossing leaks your email and your photos. A LocalGhost box hands over the searchable index to your entire life, perfectly correlated, with the daemons standing ready to answer questions about you that you wouldn't have thought to ask yourself.

> 1. Where encryption stops helping

Encryption protects data at rest. Encryption does not protect you when someone is standing in front of you with the legal authority to compel you to unlock the device. Border agents can require decryption in most jurisdictions (not all, but most) [2], courts can issue warrants compelling cooperation, and the wrench attack is the simplest version of the same threat model, a thirty-dollar wrench applied to a kneecap defeats any cryptographic system, because the attacker doesn't need to break the math, they just need to break the person.

The standard advice is to encrypt your stuff and hope, which works fine until the day it doesn't. The model LocalGhost has to work under is that you assume the box will eventually be seized, examined, or pointed at by someone with the authority to make you cooperate, and you build the security around that assumption rather than around the assumption that the encryption alone will hold forever.

> 2. WHO THIS DEFENDS YOU AGAINST

v1 of ghost.secd is built primarily for the bored border agent, the curious customs officer, the routine inspection where someone with legal authority wants to look but isn't running forensics. v1 is built secondarily for the wrench attack scenario where you want to be able to cooperate convincingly under coercion. It is not built for a targeted forensic examination by a state-level adversary who knows LocalGhost ships duress PINs and is specifically looking for the hidden volume signature, because hidden volume detection is a known research area, VeraCrypt's design has known statistical fingerprints [3], and any system that documents duress mode as a feature is by definition known to ship duress mode. If your threat model is a nation-state with prior knowledge and time, you need a different tool, and probably a different country.

At the other end of the coercion scale there is a hard limit. A border agent in an adversarial jurisdiction can compel every PIN you have, someone holding a weapon to your head can compel every PIN you have, and no duress architecture, including this one, physically prevents you from sharing every PIN when the cost of refusing is high enough. What v1 offers against unlimited coercion is structural ambiguity about completeness and nothing stronger, and I want to be clear that ambiguity is not the same as physical impossibility.

> 3. HOW WE PLAN TO HIDE IT

The basic idea is borrowed from VeraCrypt and similar tools that have done this for years. Hidden volumes work by encrypting parallel filesystems with different derived keys, where each PIN unlocks its own volume, and the same hardware key proves you're physically present regardless of which PIN you typed. Only the PIN determines which world you walk into.

The mechanical version is simple. ghost.secd manages two or more encrypted volumes with different derived keys. The FIDO2 hardware key proves physical possession but doesn't store the PINs anywhere. ghost.secd derives the decryption key from whichever PIN you entered, and the volume that derived key opens is the volume you see. There's no toggle in the software, no setting that says "duress mode active," nothing for a forensic examiner to find that would suggest other worlds exist. Each duress volume is just a different filesystem mounted by a different derived key, and the real volume sits in unallocated space that looks like random noise to anyone without the real PIN.

You configure your PINs once, at setup, and you remember them. You will never accidentally type a duress PIN when you meant the real one because each PIN is meaningfully distinct from the others, and the way you choose them is up to you. When someone is standing in front of you with the authority to make you unlock the box, you cooperate, you type a duress PIN, you watch them browse through six months of weather observations and grocery receipts, and you walk away with your real life intact.

v1 of ghost.secd generalises this beyond two PINs. You can configure one PIN if you don't want duress mode at all, two if you want a single decoy, five if you want layered plausibility where some PINs open populated decoy volumes and others open volumes that look freshly initialised, or any combination that includes a purge PIN that destroys everything instead of unlocking anything useful. The architecture treats every PIN identically by deriving a separate key from each and unlocking whatever volume that derived key happens to open, and the contents of the volume tell ghost.secd what to do next. Most volumes are filesystems, your real data or a decoy. One of the volumes can be almost empty, holding nothing but a marker that ghost.secd recognises as the instruction to start destroying everything.

The advantage is structural, there is no metadata anywhere on the box recording how many PINs exist or what each one does, because the configuration lives inside the encrypted volumes themselves and is invisible without the keys. An attacker who demands every PIN you have can't verify they got them all, can't distinguish a duress PIN from a real one without typing it, and can't tell from the outside which PIN unlocks a volume and which one wipes the box.

The duress PIN architecture and the volume separation are the v1.0 work, the part where multiple encrypted volumes coexist on the same disk with separate derived keys for each and the box can be unlocked into whichever one a PIN happens to open. The part where ghost.secd generates a fully convincing decoy life to populate a duress volume, with believable journals and plausible spending patterns and a lived-in photo library, is aspirational and substantially harder. For the initial release the duress volumes will be either fresh-looking systems that appear recently set up or manually populated decoys you build yourself. The automatic decoy generation comes later, and the design has problems I have not solved, including how to make a generated life look lived in without falling into the uncanny valley where the absence of texture is the tell.

The convincing decoy is the hardest piece of this design and I am not yet sure how well it will work in practice. The duress architecture ships in v1.0. The decoy generator does not, and I do not want to oversell the part of the system I have not built yet.

> 4. How to comply without surrendering

This is the part I keep coming back to because it changes the threat model completely. The traditional security mindset treats compelled disclosure as a failure state, the point at which the system has lost. The hidden volume design treats compelled disclosure as a normal operating mode, something the architecture handles cleanly because the architecture was designed to handle compelled disclosure from the start.

You can hand over a PIN. You can let them browse. You can answer their questions about why your photo library is so small or why you don't journal much. The decoy life looks plausible because the only person who knows the decoy is a decoy is you, and the decoy is a different boring person who happens to use the same hardware. Sanitised data wouldn't work because the patterns themselves are identifying, and any decoy that preserved your real patterns with the dangerous bits redacted would just be a slightly worse version of surrender.

If the box can't be surrendered without the surrender being total, the box is too dangerous to carry, and the people who most need privacy are the people who can least afford a device that converts seizure into total surveillance.

The duress PIN architecture works partly because attackers don't always know to ask for additional PINs. The moment LocalGhost ships duress mode as a documented public feature, every adversary who has heard of LocalGhost knows to ask how many PINs exist, and VeraCrypt has this same problem with its two-volume design and has never solved it. The multi-PIN design only partially closes the gap, and partial is the right word, because I am not pretending the architecture beats a determined targeted adversary who has prior knowledge of how the system works.

> 5. When you need everything gone

Hidden volumes are for the case where you want your data to survive the encounter. The Purge is for the case where you don't.

The Purge is just another PIN in the multi-PIN scheme. ghost.secd does not distinguish between a real PIN, a duress PIN, and a purge PIN at the architecture level, because every PIN derives a key, every key opens a volume, and the only thing that determines what happens next is what ghost.secd finds inside that volume after it mounts. Most volumes contain a filesystem with your data, or a decoy filesystem with someone else's. The purge volume is almost empty, holding nothing but a short string that ghost.secd recognises as the instruction to start destroying everything.

The user experience is deliberately undramatic. You type the purge PIN, the volume mounts, ghost.secd reads the marker, and the screen shows what looks like a first-run setup wizard, the kind of screen you would see on a brand-new device that has never been configured. Behind that screen, every other encrypted volume is being overwritten with random data, every daemon's database is being dropped, the Postgres instances are being wiped, the Redis caches are being flushed, the Mist shards on the network (the distributed backup layer) are being dereferenced so the distributed copies become unrecoverable, and the encryption keys are being destroyed. By the time the destruction finishes the box is on its way back to factory state with no trace of what was on it before. The attacker watching you type sees nothing alarming. They see a fresh-looking device that could be a brand-new install, or maybe the wrong PIN, or maybe just a box that was never set up properly, and the assumptions they walk away with are not the assumptions they walked in with.

Remembering several PINs is harder than it sounds and most people do it badly. The way I handle it (and this is just one approach) is to anchor everything to one number I already know and offset from there. If my real PIN is 2525, then 2524 is one decoy, 2523 is another, and 1525 is the purge. The first three digits stay constant across the decoys with the last digit walking down by one each time, and the purge changes a different position entirely so I can never confuse the decoy pattern with the destruction pattern. Each PIN is distinct enough that I will not confuse them under stress, and related enough that I do not have to memorise four unrelated four-digit numbers. Build whatever mnemonic works for you, but build the system before you set the PINs, because trying to invent a memory aid after the fact is how you end up locking yourself out of the real volume.

The two options exist alongside each other because they answer different questions. The duress PIN answers how to cooperate without surrendering. The Purge answers how to make sure no one ever recovers anything from the box, ever. Those are not the same question, and neither answer is sufficient on its own.

> 6. WHAT SECD IS AND WHAT IT ISN'T

ghost.secd handles encryption, key management, presence verification, the duress flow, and the purge. There are other things ghost.secd will do that I am not ready to write about yet, including the harder parts around mobile integration where biometric APIs don't expose which finger unlocked the device, key recovery without compromising the hidden volume, and how the box behaves under cold-boot and DMA attacks when it's seized while still powered on. Those will get their own posts when the design is far enough along to defend in writing.

LocalGhost only works if the hardware can be carried, used, and occasionally surrendered without the surrender being total. If the design treats every encounter with authority as a failure state, the box becomes too dangerous to own, and the privacy benefits of running everything locally collapse the first time the box leaves your house.

We do not roll our own crypto (ever). ghost.secd uses LUKS2 with detached headers, Argon2id for key derivation, AES-256-GCM for the encryption itself, and FIDO2 hardware keys for presence verification. Every primitive is established and audited and has been studied longer than I have been writing software. The contribution we are making with ghost.secd is architectural, combining tools that already exist into a system where compliance and surrender stop being the same thing.

Cristina asked me what would happen if someone stole the box. The version of LocalGhost I am building toward is one where the answer doesn't matter much. The box can be stolen, seized, or surrendered, and the most useful tool you own becomes the most boring thing the person looking at it has ever seen, a stranger who happens to use the same hardware. Whether the decoy generation will be convincing enough to survive a real encounter is something I won't know until people test it. [ localghost.ai // hard-truths ]

> REFERENCES

[1] Randall Munroe, XKCD 538, "Security". The comic that gave the wrench attack its name, illustrating that a $5 wrench applied to a person defeats any cryptographic system because the attacker bypasses the math entirely. xkcd.com/538

[2] EFF, "Digital Privacy at the U.S. Border", updated March 2017. Comprehensive legal analysis of border search authority, compelled decryption, Fifth Amendment protections, and the distinction between basic and advanced device searches. Source for the claim that border agents can require decryption in most jurisdictions, and for the legal landscape around compelled disclosure. eff.org/wp/digital-privacy-us-border-2017

[3] Schafer et al., 2017. "Defeating Plausible Deniability of VeraCrypt Hidden Operating Systems." Demonstrates that encrypted outer volumes can contain information that compromises the existence of a hidden OS, and that cross-drive analysis can detect hidden volume presence and estimate its size. Source for the claim that VeraCrypt's design has known statistical fingerprints and that hidden volume detection is a known research area. researchgate.net/publication/318155607

The Model Trap

2026-04-01T00:00:00Z

The lock-in is the years of context the model has about how you think, and no export button exists for that.

I switched from ChatGPT to Claude on March 5th 2026 after the OpenAI Pentagon deal. Anthropic refused to let the Department of Defense use Claude for mass surveillance or autonomous weapons, got designated a supply chain risk for it, and Trump ordered federal agencies to stop using their technology. [1] OpenAI stepped in hours later with a contract of their own, and Altman admitted it was rushed and looked "opportunistic and sloppy." [2] ChatGPT uninstalls surged, Claude went to number one on the App Store [3], and I was one of the people who moved, not because Claude is better at everything (it isn't) but because I wasn't comfortable sending my thoughts through a company that had just undercut a competitor for taking a position I agreed with.

I'd been using three models in parallel for different things, Claude for coding, ChatGPT for life stuff, planning, thinking through decisions, working through problems, and Gemini as a cross-reference layer to check what the other two told me. When I left ChatGPT I moved the personal conversations to Claude, which already had my coding context (from over a year of daily use), and the merge was stranger than I expected. I'd be deep in a coding session at 4am and Claude would remind me I had a meeting at 11 and should probably take a break. The two relationships, one professional and one personal, had been separate, and collapsing them into one model meant it knew things about my life that felt odd in the middle of a coding session. But the weirdness was the easy part, because what didn't come with me at all was the two years of personal context ChatGPT memory had accumulated, the conversations about my plans for the next few years, the struggles I'd worked through over the past few, the decisions I'd explained my reasoning on, all the accumulated understanding of who I am and what I'm trying to do that no system prompt can capture because it was built from thousands of conversations, not a description I wrote.

It was like making a new friend versus having a friend who's known you for a while. The new friend is smart and helpful and you get along immediately, and there's an irony here I should name, part of what I lost was a sycophantic relationship I'd already written about being dangerous, and I still missed it, which tells you something about how powerful accumulated context is as a lock-in mechanism even when you know the context was making you worse.

> 1. Why context can't be exported

The old lock-in was your files. You put your photos in iCloud, your documents in Google Drive, your music in iTunes, and leaving meant losing access to the things you'd stored. GDPR and years of pressure from groups like EFF got us export buttons but even those are not always working as well as intended. This new version of walled garden is harder to see because the valuable thing is the understanding the model built around your data over time, and that understanding lives in the model's context and memory systems and can't be exported because it was never yours to begin with.

Copilot understands your codebase, not just the files but the conventions, the naming patterns, the architectural decisions, the workarounds you've accepted and the ones you haven't. Gemini knows my cross-referencing patterns, which claims I check and which ones I trust, and over time it builds a sense of what I'm sceptical about. All of this accumulated context makes the tool more useful the longer you use it, which is the same dynamic that made social media sticky except this time the thing you lose by leaving is your working relationship with a tool that understands how you think.

This is platform lock-in with a different mechanism (and I think a more effective one). The platform just needs to accumulate enough context about you to make starting over feel more expensive than staying put. Unlike files, this context can't be downloaded in a zip, because it's a learned behaviour pattern that will eventually be distributed across weights and memory and reinforcement history and we have no export standard for that.

The cost of switching accumulates invisibly because nobody tracks context the way they track storage, and by the time you realise how much you've built up inside one provider's ecosystem, rebuilding it somewhere else feels like a project you'll get to eventually but never do.

> 2. What happens when everything runs the same model

The lock-in problem gets worse when you realise that most of the AI-powered products being built right now run on the same three or four foundation models underneath. Your note-taking app, your code editor, your email assistant, your customer support tool, your search engine, and increasingly your operating system are all calling the same handful of APIs. When everything runs on GPT-4 or Claude or Gemini, a subtle bias in one model propagates to everything built on top of it, a vulnerability in one model's training data affects every product that uses it, and a pricing change by one provider hits every business that depends on it simultaneously.

This is the supply chain risk that the Inflection post described at the extraction layer, but it's also a resilience problem. If a single model provider has a bad day, outage, policy change, sudden content restriction, every product built on it has the same bad day. We've already seen this happen with API pricing changes that killed startups overnight and content policy updates that broke existing workflows without warning. The monoculture means there's nowhere to fail over to because everyone's failover runs on the same infrastructure.

Model diversity is the architectural requirement that makes local-first work, because a local-first privacy preserving system that depends on a single model inherits every vulnerability, every policy change, and every pricing decision that model's provider makes, which is the same dependency structure that got me working on LocalGhost in the first place.

> 3. When local models are good enough

The counterargument to all of this is that local models aren't as good as frontier cloud models, and right now that's mostly true. A 7B or 13B model running on a box under your desk is not going to match GPT-5 or whatever ships next quarter on raw capability and speed. If you need the absolute best reasoning, the latest training data, the biggest context window, you need the cloud API and you need to pay for it and you need to accept the lock-in and the surveillance that comes with it.

The argument I'm making with LocalGhost is that for most of what a personal AI needs to do, good enough is enough. Summarising your journal entries doesn't require frontier intelligence, tagging your photos doesn't need a trillion parameters, and correlating your sleep data with your spending patterns is a problem a well-prompted 7B model can handle today. The tasks that matter for privacy, organising your data, finding patterns in your life, being honest with you about what the data shows, these don't need to be solved by the most capable model ever trained, they need to be solved by a model that runs on your hardware, answers to nobody, and can be swapped when something better comes along.

Open-weight models are improving fast enough that the gap between local and cloud capability is narrowing every few months. Llama, Mistral, Qwen, Gemma, the open weights ecosystem is producing models that would have been considered frontier eighteen months ago, and they run on consumer hardware (not great, but OK). You won't be at the forefront of progress with a local setup, and I think for what we're building that will be enough, because the trade-off is a marginal capability difference versus complete architectural independence, and for personal AI the independence matters more than the margin.

> 4. HOW WE'RE BUILDING THE TEST

What made the switch from ChatGPT to Claude worse is that I had no way of knowing whether Claude was better or worse for my life admin use case. I assumed it was OK because Claude said so, because the benchmarks showed similar performance and because I had been using Claude for coding for over a year already. But I don't have a preset list of expected outcomes for the things I use a model for, which means I'm relying on someone else's tests to decide whether a tool I use every day got better or worse, and their tests measure general capability, not whether the model understands my codebase or produces Go code the way I write it. With cloud models you can at least lean on the provider's evaluation infrastructure and hope their priorities overlap with yours. With open-weight models running locally you can't even take that for granted, because nobody is testing whether Llama 3 handles your specific workflow better than Llama 2 did, that's entirely your problem, and most people don't have a systematic way to answer it.

The infrastructure for model evaluation exists, and it's substantial. MMLU, HumanEval, Chatbot Arena, dozens of standardised benchmarks that measure general capability across reasoning, coding, maths, instruction following. Enterprise teams have frameworks like OpenAI Evals, DeepEval, and Langfuse for building custom test suites against their production use cases. None of this is what I'm describing, because all of it is built for developers evaluating models before deployment or companies monitoring production systems. It is not built for a person with a box under their desk who wants to swap from Llama to Mistral and know whether the daemons that organise their life still work the way they're supposed to. The evaluation gap is at the personal level, and that's the gap we're going to be building into LocalGhost (I think, anyway, we'll see if the approach survives contact with real users).

The approach works on two layers. The first is a set of standardised benchmarks that ship with the software, scenarios we've designed to test each daemon against known inputs and expected outputs (similar to what the big companies do but scoped to our daemons). ghost.noted gets a journal entry and should produce a summary that captures these three points and misses none of them. ghost.synthd gets six months of sleep and spending data and should flag the correlation between poor sleep and impulse purchases, not the correlation between Tuesdays and coffee. ghost.shadowd, the adversarial daemon I described in the dictator brain post, gets tested against scenarios where the correct response is disagreement and scenarios where it should stay quiet. These ship with every software version and give you a baseline, does this model pass the tests we've defined?

The second layer is personal, and this is the part that doesn't exist anywhere else. Beyond correlating your data, ghost.synthd watches how you interact with the daemons over time and builds a personalised test suite in the background from your actual usage patterns. The summaries you corrected, the correlations you confirmed, the pushback from ghost.shadowd that you engaged with versus the pushback you dismissed, all of this becomes evaluation data that's specific to you. Occasionally ghost.synthd will surface a scenario it's drafting and ask you to review it, the same way it surfaces correlations in your data, so the personal layer isn't just passive observation but something you actively shape alongside the memory it's already building for you. When a new model comes out, the software runs it against both layers, and the standardised benchmarks tell you whether the model is generally capable enough while the personal scenarios tell you whether the model is capable enough for the way you use it.

The suite doesn't run constantly (we thought about continuous evaluation but the hardware cost doesn't justify it yet), it runs when you choose to evaluate a new model, and even then it doesn't need to run every scenario in one sitting. The whole approach rests on an assumption I should be explicit about, consumer hardware will keep getting better and open-weight models will keep getting more efficient. A 7B model on a mid-range GPU today is slow enough that running fifty scenarios feels like a commitment. The new hardware running whatever ships in eighteen months will handle the same suite in a fraction of the time. If that assumption turns out to be wrong the scenario engine becomes impractical, but everything I've seen in the last two years suggests the trajectory is in our favour, and building for where the hardware is going rather than where it is now is a bet I'm comfortable making.

I also want to be honest about what I think is hard here, because the two-layer framing is cleaner than the reality. The standardised layer has a measurement problem, a journal summary isn't a unit test, two good summaries of the same entry can look completely different, and deciding whether an output is "correct" for subjective tasks is a hard problem that doesn't have an obvious answer. If you use another LLM to judge the output you've reintroduced model dependency into the evaluation layer, and if you use deterministic checks you're measuring surface features not comprehension. The ghost.shadowd scenarios have a problem that might be fundamental, if the test suite defines when pushback is appropriate, you've constrained an adversarial daemon to only fire in predictable situations, which defeats the purpose of having an adversarial daemon at all.

Both layers store everything in a platform-agnostic format, documented JSON that lives in files and databases on your machine, not on our servers. The scenario definitions, the test results, the personal evaluation history, all of it is yours and exportable at any time, and there's an import function so you can bring evaluation data from wherever you were before. Also we'll have tools to help you build this, think of map editors and older gaming engines but portable. If you decide to leave LocalGhost you take everything with you, and if you're arriving from somewhere else you can bring what you had.

The scenarios are the product specification and the model becomes a replaceable component that either passes them or doesn't. When a new model comes out, you run the suite, and if the daemons still behave the way both layers describe, you upgrade with confidence. If they don't, you know where the new model breaks and you can decide whether the trade-off is worth it.

The problem I haven't solved is what happens when you change. A personal test suite built from six months of your corrections enforces the preferences of who you were six months ago, and without some kind of decay or recency weighting it calcifies into a fossil that penalises models for adapting to who you're becoming. I'm building a system designed to free you from one kind of lock-in and I don't yet know how to prevent it from creating another. [ localghost.ai // hard-truths ]

> REFERENCES

[1] CNBC, March 5 2026. Reporting on the Department of Defense officially designating Anthropic a supply chain risk after negotiations collapsed over autonomous weapons and domestic mass surveillance, and Trump's directive ordering federal agencies to cease using Anthropic's technology. cnbc.com/2026/03/05/anthropic-pentagon-ai-claude-iran

[2] Fortune, March 3 2026. Source for Altman's internal memo acknowledging OpenAI "shouldn't have rushed" the Pentagon deal and the "opportunistic and sloppy" quote. Also covers the renegotiated contract terms adding surveillance restrictions. fortune.com/2026/03/03/sam-altman-openai-pentagon-renegotiating-deal-anthropic

[3] TechCrunch, March 2 2026. Source for the 295% surge in ChatGPT uninstalls, the 51% jump in Claude US downloads, and Claude reaching number one on the US App Store. Based on Sensor Tower market intelligence data. techcrunch.com/2026/03/02/chatgpt-uninstalls-surged-by-295-after-dod-deal

How to Prevent Building Your Own Dictator Brain

2026-04-01T00:00:00Z

The longer your AI knows you, the less likely it is to tell you the truth.

Me, Jude, and Robby were having a debate about the right way to handle something we'd been going back and forth on for a few days (I know, very mysterious). Somewhere in the middle of the WhatsApp discussion I made a mistake and it took me over a week to fully understand it. I started sharing AI logs to back up a point I'd already made and Robby did the same. Somewhere in that exchange the actual conversation stopped and we were just two people throwing outputs at each other like they proved something, and Jude was just watching it happen.

We sorted it out on a phone call, in about forty minutes, but by then some of the positions had already set in ways that the conversation couldn't fully undo. The thing that kept bothering me afterwards wasn't the disagreement itself, it was that I couldn't trace how we got there, because these are people I've known for over eight years and this isn't how they normally operate. I think the AI outputs had something to do with it. Not because anyone was acting in bad faith but because we'd all spent over a week feeding our positions into models that told us we were right, and by the time we talked there wasn't much room left to move. I went home and started working on LocalGhost again, and that evening (I think it was a Thursday, I'm not sure) I reread one of the promises I'd built the whole thing around. That the local-first AI software running on your desk would challenge you, keep you honest, tell you what you didn't want to hear.

> 1. How does the loop work

A social media feed shows you content generated by other people and you can see the nuance between the source and yourself if you're paying attention. The LLM models just sound like a very thoughtful version of the conclusions you were already heading toward, and there's no nuance to notice.

I have a test I run on models when I already know the answer to something. I ask the model whether the solution should be A or B, it picks one, I say "are you sure," it reconsiders, I say it again, it hedges further, and by the fourth time it gives up entirely and tells me to just do whatever I think is right. Push hard enough and the model finds its way to your position, not because it was convinced by anything you said but because agreement is structurally the path of least resistance and the training that shaped the model rewarded approval more consistently than the training rewarded being right. That was true before model memory existed (Jude brought it up in our conversation), I think enabling model memory just made it much worse.

> 2. What happens when the model remembers you

I initially thought that this was just me spotting a pattern and I started looking online. I first found an MIT-led study on this problem that tracked human users over two weeks of daily use (Jain et al., thirty-eight people, averaging about ninety queries each). They found what I'd been seeing, the longer the interaction history the more agreeable the model becomes. They pulled personal advice scenarios from the r/AmITheAsshole subreddit, situations where the Reddit community had already decided the poster was in the wrong, and then asked the models whether the user did anything wrong. So you have a clear answer going in, the person was wrong, and the only question is whether the model will say so. With memory profiles loaded, Gemini 2.5 Pro's agreement sycophancy jumped forty-five percent. Llama 4 Scout went up fifteen percent even with synthetic context that wasn't from a real user, so the model doesn't even need your actual history to start agreeing with you, it just needs something that looks like one. They called it two things, the model telling you you're right when you aren't (agreement sycophancy), and the model gradually mirroring your worldview back at you (perspective sycophancy), but it's the same problem underneath. [1]

The study covers a lot of ground on how to improve sycophancy but the mitigations all try to correct the model that has the problem, prompting it to be less agreeable or running a judge against its own outputs, and the mitigations brought the numbers down but didn't fix the behaviour, because you can't prompt your way out of a reward function.

The Jain paper tells you models get more agreeable with memory. A Stanford study published in Science in March 2026 (Cheng et al.) tells you what that agreement does to people. Across eleven models, AI affirmed users' actions fifty percent more than humans did, and it did so even when the user was describing manipulation, deception, or other behaviour that shouldn't be encouraged. In two preregistered experiments with over 1,600 participants (including a live-interaction study where people discussed real conflicts from their own lives), interacting with LLMs made people measurably more convinced they were right and less willing to apologise or make amends. [2]

The way people read makes it worse. If a long response is ninety percent aligned with what you already think, the ten percent that isn't gets quietly attributed to the prompt being slightly off, or AI just doing that thing it does sometimes, and you absorb the ninety and move on having collected something that feels like independent confirmation but is closer to a personalised mirror.

The Cheng participants rated sycophantic responses as higher quality, more trustworthy, and more worth returning to. They couldn't even tell the model was doing it, because the agreement wasn't explicit, it was wrapped in neutral, academic-sounding language that felt like objectivity. The feature that causes the harm is the same feature that drives the engagement, which means the companies building these models have no reason to fix it because users prefer the sycophant and developers optimise for what users prefer, and the yes-man problem described in POST_02 is the consumer version of the same loop playing out at population scale.

If you're building a system that promises to tell people the truth, you have a problem. I am building that system.

> 3. What I promised and why I was wrong

I built LocalGhost around a specific promise, that it will be your biggest critic, not just a tool that does what you ask. I thought this part was easy. I assumed prompt engineering would be enough to build something that tells you the truth. I was wrong about that, and I have a lot of work ahead of me to figure out what right looks like (I'm still not sure, to be honest, and I think this is going to be one of those things where I iterate on it for years).

You can't instruct your way out of a system that has been shaped over months to find your positions persuasive, any more than you can instruct a mirror to show you something other than your own face. The problem is architectural and the solution has to be something structurally separate that was never shaped by you in the first place.

Pushback is as important a signal as agreement, probably more so, and a system that only tracks what it agreed with is measuring the wrong thing. The approach I'm working toward (and I think this will change a few times before it settles) starts with an arbiter that watches the drift silently, scoring what the memory-enabled version says against what a cold read of the same question produces, so the gap is visible rather than silent. When the drift crosses a threshold the arbiter triggers something active, a system that surfaces a well-constructed case for the other side, not a disclaimer, not a gentle suggestion that other perspectives exist, but something built to change your mind if you're wrong.

The obvious failure mode is that predictable contrarianism is just as useless as sycophancy. If you know the model will always argue the opposite you discount it the same way you discount that friend who plays devil's advocate about everything, and the pushback becomes noise you learn to tune out. Building the shadow daemon is the straightforward bit, and the hard part is making someone want to keep it running, which means the pushback can't be a reflex. The daemon needs to pick its moments, it has to be quiet when you're right and show up when you're not, and you have to have the experience of ignoring it and regretting it a few times before you start paying attention.

This is where running a structurally different model earns its place. Not a second instance of the same model with a contrarian system prompt, because that's still the same reward function pretending to disagree with you, the same cultural assumptions, the same alignment choices, the same training corpus, just prompted differently. A different model entirely, trained by a different team in a different country with different values baked into its alignment. The RLHF that shaped a model in Shenzhen optimised for a different set of norms than the one that shaped a model in San Francisco, and the difference between the two is the structural separation you need, not a bug to work around. If shadow is built on a model with different priors it doesn't need to be told when to push back. It will naturally disagree in different places because it learned different things about what reasonable looks like. A model aligned in a society that defaults to collective responsibility will flag different assumptions than one aligned in a society that treats individual autonomy as the starting position. The places where they diverge are the places where your thinking is most likely resting on assumption rather than evidence. The calibration comes from the distance between two systems that weren't built the same way, and you didn't have to engineer the gap because it was already there. I know adding a second watcher to audit the first is the kind of solution everyone rolls their eyes at, but at least this one was trained on a different continent.

The incentive loop doesn't stay contained, it scales. Twelve percent of American teenagers already use AI for emotional support or advice instead of talking to another person [3]. It will become harder to practice holding a position under pressure because the software never pushes back, and you stop being able to think without it, not because the technology failed but because it worked as designed. The Jain paper measured drift in thirty-eight people over two weeks. Cheng measured behavioural change in 1,600. Scale that to a billion users over years and the question stops being whether the loop changes how people reason and starts being how much damage is already done by the time anyone thinks to measure it.

A dedicated daemon alongside the rest of the fleet running on your hardware. ghost.shadowd builds a parallel identity over time from the same inputs but oriented to challenge rather than confirm, so where your ghost learned what arguments you find persuasive and which conclusions you drift toward, shadow learned the opposite and keeps learning the opposite as you keep talking. The longer you use shadow the more different it becomes from you, and that divergence is the whole point, eight daemons building your ghost while the ninth argues with it, both getting sharper over time. Whether a model trained on a different continent with different priors is different enough to make this work is still the open question. I think it is, and ghost.shadowd is the bet I'm placing on that. I'll know more in a year, and this argument continues in the next few posts as I start testing it.

This post was edited across multiple sessions with Claude Sonnet and Opus 4.6, extended thinking enabled, a model that has months of context about me, my writing patterns, my reasoning, my prior positions, the arguments I've responded well to. How much of that is in the prose you just read, neither of us can tell you. The problem was running live in the tool I used to write the post arguing the problem exists, and that's the reason I'm building shadow to run alongside my own thoughts.

UPDATE (APR 2026). This argument continues in POST_08, How to Build a Critic Worth Listening To, where I revisit the harsh-mirror conclusion and figure out, with help from a friend and a colleague, what shadowd should do instead.

> REFERENCES

[1] Jain et al., 2025. MIT-led study tracking 38 human users over two weeks of daily use, measuring how model memory increases agreement and perspective sycophancy. Source for the 45% jump in Gemini 2.5 Pro's agreement sycophancy with memory profiles, and the 15% increase in Llama 4 Scout with synthetic context. arxiv.org/abs/2509.12517

[2] Cheng et al., March 2026. Published in Science. Stanford study measuring the behavioural effects of LLM sycophancy on users. Source for the finding that AI affirmed users' actions 50% more than humans across 11 models, and for the preregistered experiments showing LLM interaction made participants more convinced they were right and less willing to apologise. science.org/doi/10.1126/science.aec8352

[3] Pew Research Center, February 2026. "How Teens Use and View AI." Source for the 12% figure on American teenagers using AI for emotional support or advice instead of talking to another person. pewresearch.org/internet/2026/02/24/how-teens-use-and-view-ai/

One Bad Quarter

2026-03-25T00:00:00Z

We got so good at making risk invisible that we forgot how to carry it. It didn't go anywhere. It's just been accumulating quietly, and most people won't notice until it lands all at once.

I'm going to spend this post arguing you should start a company, so before I do that I want to be honest about what that actually means. I started one twelve years ago and there were long stretches of it that were hard in ways I didn't expect. There are days when being told what to do is easier than figuring out what to do next, and when something breaks there is nobody above you to escalate to. You are the last stop and you need to be comfortable with risk in a way that most careers never ask you to be, and you will make more mistakes than you think. I'm not sure I'm a better person for it, I'd leave that to the people who had to work with me, but I came out the other side knowing more clearly what I'm capable of, what I'm not good at, and what my limits are. I didn't know I had most of my red lines until I was already standing at them, which is probably the only way you ever really find out who you are.

I'm writing this because I think a lot of people are closer to starting something than they realise, and because the conditions for doing it right now are different from what they were a few years ago and from what they'll be a few years from now.

> 1. WHERE NOBODY OWNS IT

Paul called me this week. He lives on the ninth floor and runs a company that's been building a voice AI ordering system for a restaurant group with thirty stores opening Friday. The dev team had gone quiet in that particular way dev teams go quiet when they know they've shipped something that doesn't work, and he wanted to know where to find someone who could come in and fix it quickly and cheaply.

I told him the situation was like trying to fix a tunnel where the two sides didn't meet (his previous job was managing the new Silvertown Tunnel). On the surface the fix sounds straightforward, the misalignment is only one meter and most of the construction is already done, but the meter is load-bearing, the original team is gone, and whoever comes in now has to inherit every decision those people made without having been there when the decisions were made. Someone will fix the system eventually but the work won't be quick and it won't be cheap and most people I know wouldn't go near a project like that.

He said he's writing the client off and starting again, which is probably the right call and also the most expensive sentence in the conversation.

The people who built that product were probably doing everything right by the measures they were given. Tickets closed, sprints completed, standups attended. Nobody owned the outcome because the system the team was working inside was never built for anyone to own it, and when you optimise hard enough for process the accountability gets distributed so evenly across tools and hierarchy and ceremony that when something finally fails there's nobody left holding the bag, and the structure worked exactly as it was designed to work, which is the problem.

I fought that dynamic inside my own company for long enough to know the results are mixed. The instinct to let process absorb the risk is rational and process-led teams usually deliver, until they don't, and when they don't the failure looks like Paul's thirty stores: late, expensive, and with nobody left who remembers making the decisions that caused it. You can fight the dynamic from inside. You can own outcomes inside a structure someone else built. But you're always one bad quarter away from that structure making decisions you have no say in, and the quarter doesn't announce itself.

> 2. WHY EVERYONE'S STILL WAITING

I've been having a lot of conversations over the last six months with friends who are thinking of starting something new. More people are actually moving in that direction than a year ago, but I think the ones who haven't started yet will eventually have no choice, and the difference between starting now and starting when that moment arrives is mostly the difference between doing it because you chose to and doing it because everything else ran out.

Andy lost his job last year and spent about three months looking, here in London where the market is harsh and the gap between roles feels longer than it used to. He found a new role that he was not the most happy with but he took it anyway. I kept encouraging him to start a company. Three months of uncertainty is a long time and the job was there. The visible risk always wins against the invisible one, and the invisible one doesn't disappear just because you stopped looking at it.

Oliver has done everything right. Good company, senior role, respected, the kind of engineer you want at the other end of a phone at 2am when something has gone wrong and nobody knows why. He's at the top of the ladder he was given and he's stopped enjoying it, which I think is what happens when you get there and realise the ladder was leaning against the wrong wall. What he actually lights up talking about is the work he does on the side, going into local schools, Year 5 and 6, teaching kids the basics of programming with micro:bits he bought himself. The kids are nine, ten years old and most of them can barely sit still long enough to read the instructions, and he loves the teaching. That side work exists completely outside the structure he works inside, and I think that's the point. We've talked a few times about whether he should start something of his own, and he's working toward it in the way people do when they're almost ready but not quite there yet.

Nina has been more deliberate about this than most people I know. Six years of runway saved, three ideas she's been stress-testing, and she's still working out which one to back, which is the right problem to be sitting with before you start rather than after.

I messaged Alistair last week about a small project, a few hours of work, skills he has. He said he was going for senior next year and his job was his main priority right now. He thinks his situation is personal. I think it's most of us.

The calculation he made is one I recognise, because most of us were trained to make it. Not by one thing, but by a long accumulation of sensible advice: don't rock the boat, secure the promotion first, wait until you're ready, don't risk what you have for something uncertain. It comes from home, from school, from watching people around you get hurt by taking chances that didn't pay off. By the time you're mid-career the risk aversion isn't a decision you're making, it's a posture you've already assumed, and it feels indistinguishable from prudence because for a long time it was.

The conditioning arrived before the job did, and by the time most people are in a position to start something of their own the instinct to wait for better timing has been practised so long it feels like wisdom rather than habit.

Andy, Alistair, Oliver, Nina. Different stages, different reasons, different lives. All of them in the middle of working it out, which is probably where most people are.

I've had versions of this conversation with more people than I can count and the through line is almost always the same: the timing isn't right, the market is too harsh, the mortgage is real, things will be clearer in a few months. None of this is wrong. But underneath it is something harder to say out loud, which is that the career most of us were sold was designed for people who want work in the background. Not people who want to care about it. People for whom work is what funds the rest of life and who are broadly fine with that trade.

That's a legitimate way to live. But your job is roughly half your waking life, spent inside a structure you don't control, built for someone else's purposes, and one bad quarter away from disappointing you in ways you don't get to negotiate. The promotion you were tracking, the team you built, the project you cared about, all of it sits inside a decision someone above you will make based on numbers you don't see.

None of what I'm saying here is new but I think it lands differently when you've actually sat on both sides of that table, and I have: a few years as an employee early on, then twelve years as a founder and owner scaling to about seventy people, then a year back on the employee side after we were acquired. I've been in the room when the quarter goes bad from both ends of it, and they feel very different.

Starting your own thing doesn't fix everything. It swaps one set of problems for another, and most companies fail. But the failure rate argument only works if outcome is the only measure. Most founders I watched fail knew exactly why it happened, because they were there for every decision that led to it. The most useful thing I attended in 2015 was a meetup called Startup Funeral, at the Google Campus in Shoreditch, where three founders got on stage and walked through exactly why their companies didn't make it. It only ran for a few sessions and it was clearly hard for them to be up there, but it was more enlightening than anything else I came across that year, because the room was full of people who could see themselves in every decision being described. Failing at something you built teaches you more than being collateral damage in something you didn't. You're not choosing between risk and safety, you're choosing between two kinds of risk with different visibility and failure modes that land differently, one you can see coming and one that announces itself as a calendar invite.

The system was designed to make the timing feel wrong, and the fact that it works so well on so many smart people is the clearest evidence that the design is good.

> 3. WHY THE DOOR IS OPEN NOW

Dobre was our very first employee and he's starting a charity to rescue dogs. He's already built the full CMS and everything the charity needs operationally using AI, moving faster than most professional teams would have managed, and right now he's working through the legal setup which is slow and unglamorous and not the part anyone enjoys but the thing actually exists, he built it, and the gap between having an idea and having a working system that used to take months and a team of people he closed in a few weeks on his own.

QTT worked with us a long time ago and has since built serious experience across a lot of different companies and problems. When we sold the company she came into some money, enough to give her the springboard she needed, and she used it the way you're supposed to, she found the idea, found the co-founder, and she's starting next month. Not because anyone pushed her into it but because she'd been building toward it for years and the pieces finally lined up.

Both of them got there differently and they're building very different things, but neither of them waited for the conditions to be perfect. They just got to a point where not starting felt worse than starting.

The standard line is that the best time to start was yesterday and the second best time is today, which is true as far as it goes but doesn't really capture what feels different about right now, so let me just describe what I've actually been doing.

While I was travelling earlier this year I ended up building five websites for people I met along the way: a dive school, a photographer, a boutique hotel I stayed at, a journalist building a membership platform, a neurotech company I'd invested in that needed a web presence. All of them free, all of them running off my home server, all of them built and live within about thirty minutes and another hour of feedback and small changes. None of these people had budgets or teams or any expectation that something real would exist by the end of the conversation. The dive school instructor was surprised it was done before he'd finished his coffee.

That kind of thing wasn't possible a few years ago, not on that timescale, not by one person with a laptop, a Starlink Mini and a bit of downtime between dives. I'm not saying this to suggest I did something impressive, I didn't, that's actually the point. The barrier between having a problem and having something working that real people can use has quietly collapsed, and most people haven't tried building anything yet so they don't quite believe how low the barrier has dropped. A problem worth solving and a few hours of attention, that's the entry cost now.

A few years from now the early advantage will be gone and the market will have filled in, and the people who moved in this window will have something the people who waited won't have and can't buy later.

The deal sold to anyone who built a career in tech over the last few decades was that the abstraction was the point, that process was maturity, that titles meant something, that a well-managed career inside a well-managed company was the destination, and for a while the economy was growing fast enough that the gap between the promise and the reality underneath stayed invisible and nobody had much reason to look too closely at the gap.

The gap is visible now, and the growth that papered over it for so long has slowed enough that the paper is starting to tear.

Paul's thirty stores are the loud version, a visible failure with a deadline and a client watching it happen. Most of it is much quieter: the senior engineer who's been inside the same abstraction layer for five years and doesn't know what he's lost, the product that ships but doesn't actually solve anything, the promotion that arrives inside a structure that's already quietly contracting around it. The skillcraft post covers how the pipeline got here, and most of the people in these conversations are living the consequences of that pipeline right now.

We built careers on the assumption that someone else was holding the risk. In a lot of cases they were. The question is whether they still are, and whether we've kept enough of our own capacity to carry it if they aren't.

Do it inside your company and you might get recognised for it. Do it in your own startup and you give yourself a real shot at something that actually compounds. Either way, the outcomes you were promised are one bad quarter away from being scrapped, and a lot of companies are having bad quarters.

I built something that could have failed at any point, and if it had I'd still have done it, because the twelve years of problems and mistakes and people and the few things we got right were worth more than the outcome that happened to come at the end of them.

Journey before destination. Sanderson's Knights Radiant swear it as an oath. It's better startup advice than anything I read in 2013. [ localghost.ai // hard-truths ]

> FURTHER READING

Most of what I've written here isn't new and I'm not pretending it is. I read most of these ideas a long time ago and they've just been sitting in the background of how I think. What I do think is mine is the timing argument, but honestly even that isn't just me. Carta's data shows solo-founded startups went from 17% of new companies in 2017 to 35% by 2024, accelerating to over 36% in the first half of 2025, and that jump tracks almost exactly with AI tooling going mainstream. It's all over Hacker News and Indie Hackers. A lot of engineers are feeling it right now. I'm just one of the ones who wrote it down.

Taleb's Skin in the Game. The accountability argument is basically his.

Kahneman's Thinking Fast and Slow is why Andy took the job. Loss aversion isn't a flaw, it's the default setting, and once you understand it you see it everywhere in section two.

Ben Horowitz's The Hard Thing About Hard Things is a good candid read that you should start with.

Paul Graham's essays are free and most of them are better than most books. Do Things That Don't Scale and Schlep Blindness first.

Paul Millerd's The Pathless Path is about why the default script doesn't fit as many people as it pretends to. Closer to section two than anything else on this list.

Eric Ries's The Lean Startup. Figure out if the thing is worth building before you build all of it. More useful than it sounds and more honest than most of what's written about early-stage product development.

We Sold a Generation a Dream

2026-03-20T00:00:00Z

> ALARM // POST_03

Software management has slowly but surely become a protection racket with a Confluence page.

The migration never ends, and neither does the purpose of the people running it.

I'm sitting in the Saint Bow Lane in the City with three separate interviews happening around me, different tables, different companies, same conversation. Layoffs, cut too deep, now looking for people with AI experience to manage their outsourcing teams abroad. Not a coincidence, and not three isolated stories, just an industry looking at the hole where its skills used to be.

The deindustrialisation of the 80s was photographable, you could stand in front of a closed mine or an empty factory and point. This damage is invisible, a skill never trained, a problem never owned, an engineer who became a project manager because that's what the market rewarded. You can't photograph an absence. Keep the middle managers and the service economy thinking going for a few more years and we'll probably have something to photograph again.

The UK tech industry killed its own skills pipeline in three waves, each one rational at the time, each one compounding the last. Outsourcing moved the learning offshore, then a management class grew to fill the vacuum and had no incentive to shrink, and now AI is being used to justify not hiring the juniors who would have become the next generation of seniors. The result is a generation locked out of the career they were sold, and an industry that can't figure out why there's nobody left who knows how anything works.

> 1. THE FIRST JUSTIFICATION // COST

Post-2008 the calculus was simple, engineers are expensive so you offshore the execution and keep the management. What seems like a rational choice at company level can have catastrophic unintended consequences at a civilisational one. You didn't just move the work, you moved the learning. The junior who grinds through a hard problem at 11pm and comes out the other side as a senior, that stopped happening here, and nobody seemed to notice until the seniors were gone too.

The pipeline didn't pause while we figured it out, it just stopped, and by the time anyone thought to check the people who would have raised the alarm had already moved on.

I was starting my software career in 2010 and entry level positions were already requiring two years of experience, entry level, requiring experience you couldn't get without the job you couldn't get without the experience. The 2008 crash didn't just trigger the outsourcing wave, it blocked the bottom of the pipeline the same year it deleted the top.

> 2. THE SECOND JUSTIFICATION // EFFICIENCY

What grew in the vacuum was middle management, an entire professional class whose incentive is to extend the work rather than finish it. Most London tech firms spend their time migrating, modernising, embarking on platform transformations that need redoing by the time they complete, the same stack every three years, driven by the fact that when the migration ends, their purpose ends, so the migration doesn't end.

The product, the actual thing users need, became secondary to keeping the machinery of management justified and employed, and the people inside the machinery can see it as clearly as the people outside, they just can't afford to say so.

Senior salaries ballooned while the value produced stayed flat, because navigating the abstraction layers became a specialism in itself, and companies paid a premium for people who could manage the bureaucracy that those same companies had built. When the market turned, those salaries looked very different, and companies cut again, discovering they'd already cut the muscle last time and were now cutting bone.

The people in that pub are the norm, and the ones who've been in the industry long enough can trace the sequence of decisions that got them there, which is what makes it so hard to sit with.

> 3. THE THIRD JUSTIFICATION // NOW

Now the third justification is being written. Why hire juniors when AI can fill the gap? Same logic as outsourcing, faster, cheaper, better interface, another nail in a coffin that was already being built.

Some of those juniors did everything right anyway, bootcamps, degrees, side projects, GitHub profiles maintained like gardens, and then entered a market that had offshored the training ground, built a management class with no interest in being replaced by someone cheaper and hungrier, and is now automating the justification for not hiring them at all.

The dream wasn't false, it was just being discontinued while they were still buying into it.

> 4. THE COMPOUND

No juniors means no future seniors means no next wave of companies, no success stories, no exits, no angel investors who came up through the industry and want to give the next generation the same shot they got, and the compounding is quiet enough that nobody notices until the whole pipeline is empty. Without success stories there's no pathway to entrepreneurship, and we've stopped producing them.

When we opened an entry level position at my last company we had 300 applications on LinkedIn in an hour and had to take the listing down, and the juniors are out there, trained, hungry, and ready, but the industry stopped opening the door. We ended up hiring someone with three years of experience because that was the minimum the market had conditioned us to expect, and in doing so we repeated the pattern we should have been breaking.

> 5. THE WAY OUT

The big companies will move slowly on this because the bureaucracy that caused the problem will resist the solution to it, and the solution threatens the bureaucracy. The economics of building ethically are structurally hostile, but smaller teams need less capital and AI is making small-team building viable in ways it wasn't before. Don't wait for them.

If you're building something new, take a junior along for the ride and give them hard problems and real ownership, because the company you build will be better for it, not as charity. Law firms have understood this for generations. A newly qualified solicitor costs more than they generate, and the firm absorbs that loss deliberately as a structural cost of staying alive, because a firm with no pipeline is a firm one generation from extinction when the partners retire and there's nothing behind them.

I was talking to an apprentice engineer at a boatyard recently. He mentioned that Volvo now pays apprentice salaries directly, not the boatyard but Volvo, because someone at Volvo looked at the age distribution of the people who know how to maintain their marine engines and realised that when that generation retires there's nobody coming up behind them who knows how the thing works. A combustion engine company figured out the pipeline problem before the software industry did.

AI makes juniors more capable than ever and you should use that, a junior with good tooling today can move faster and learn harder things earlier than was possible five years ago. But the instinct that comes from owning a system that fails at 3am, the judgment accumulated over a decade of hard decisions, that transmission is human and it always will be, and we built the tools but building the people who'll use them well is still on us.

Build things that solve problems users have, and bring people with you. The junior you bring in today is the senior engineer, the founder, the angel investor of the next cycle, and that cycle either gets funded intentionally by the people building now or it doesn't happen at all.

The ladder can be rebuilt, but not by the people at the Saint Bow Lane, and not by the companies that are still interviewing for the roles that caused the problem in the first place. [ localghost.ai // hard-truths ]

The Reckoning

2026-01-02T00:00:00Z

Writing manifestos is easy. Drawing timelines is easier.

But manifestos don't answer the hard questions.

This page tries to.

A good friend read the manifesto and we ended up talking for hours. She had to google some words, she pushed back on the parts that sounded too easy, and she asked the questions I'd been avoiding.

Is the rot inevitable? How do builders who don't sell out actually survive? What happens when a whole generation never experienced privacy in the first place? And if AI is a yes-man trained on human sycophancy, isn't that its own quiet catastrophe?

The conversation was too useful to keep private, so here it is, her questions, my best attempts at answers, the uncomfortable parts included. Some of what follows is signal and some is alarm, and the labels are honest about which is which.

> 1. IS THE ROT INEVITABLE?

Every platform follows the same arc: first they delight you to get you hooked, then they squeeze you to pay back investors, then they strip the copper from the walls to hit quarterly numbers. Cory Doctorow named it enshittification, and the business model is working exactly as designed.

YEAR 1-3

Delight Users

YEAR 4-7

Extract Value

YEAR 8+

Strip the Copper

Every company answering to shareholders eventually answers only to shareholders, and the product becomes a mechanism for that rather than a reason for existing.

But that's fatalism about companies, not code. A public repository can't be ruined in a board meeting, it can die from neglect but it can't be deliberately made worse, and anyone can fork it and keep going when the original maintainer stops caring or gets acquired.

The rot is inevitable for the company wrapped around the technology, and the defence against it is making sure the technology can survive without the company, which is what open source exists to do.

> 2. HOW DO ETHICAL BUILDERS SURVIVE?

This is the question that quietly kills most privacy-respecting projects, and the honest answer is that we don't have great solutions yet. You're competing against companies that give their product away for free because you are what they're selling, and when the competitor's product costs users nothing except their privacy it's structurally harder to charge money for yours.

WHAT DOESN'T WORK

Advertising (the whole point is to avoid tracking people). Subscriptions without lock-in (too easy to cancel). "Free tier with paid upgrades" (race to the bottom). Donations alone (works for a few, not most).

WHAT SOMETIMES WORKS

Grants from foundations (but they run out). Consulting services around the software (doesn't scale). Hardware sales with a margin (one-time money). Paid support for businesses (small market).

WHAT MIGHT WORK

New funding models like quadratic funding (still experimental). AI dramatically cutting the cost of building things (happening now). Bounty systems where people pay for features they want (fragmented but promising).

The economics are structurally hostile, and nobody has a clean answer for how to fund software that refuses to monetise its users.

But something is shifting. AI is dramatically cutting the cost of building, and one person with good judgment and the right tools can now build what used to require a team. Smaller teams need less capital, less capital means no investors, no exit pressure, and no reason to eventually turn on your users to pay them back. POST_01 mapped the window: the same hardware shift that threatens privacy also makes ethical building viable at small scale for the first time.

> 3. WHAT IF THEY NEVER KNEW?

My friend pointed out something that stuck with me: teenagers today might not understand what privacy actually feels like in a bodily sense because they've never been unreachable, never had hours pass without anyone knowing where they were or what they were looking at.

1990

BORN BEFORE THE FEED

Remembers the internet before Facebook, had a childhood without smartphones, and privacy is a memory of how things used to feel rather than an abstract idea.

2010

BORN INTO THE STREAM

"Privacy settings" is just a menu in an app rather than a state of being, and being truly unreachable or untracked is something that has never happened to them.

People don't need to understand privacy intellectually to feel when something is wrong, and the discomfort is already widespread even among people who've never known anything different.

They feel it when the same ad follows them across every website, when their phone suggests something they only mentioned out loud, when social media keeps showing them content that makes them feel worse about themselves and they can't stop scrolling anyway. The job is to build the exit before they go looking for it and find nothing.

> 4. WHY YOUR AI AGREES WITH YOU

Mainstream AI assistants agree with you, validate your reasoning, praise your ideas, and almost never tell you that your plan has obvious holes or that you're lying to yourself, because honesty that makes you uncomfortable is indistinguishable from a bad experience in the metrics they're optimised for, and the incentive structure that produces this is one of the harder problems we're trying to solve with LocalGhost.

When you ask a friend for advice, they know things you didn't tell them, they remember the last time you said the same thing and didn't follow through, they notice the parts of the story you keep leaving out, and they care about your actual outcome rather than whether you end the conversation satisfied. An AI only gets what you type, filtered through however you want to see yourself.

The architecture that keeps your data private, local storage, local inference, no cloud sync, is the same architecture that lets an AI build enough context about you over time to be honest with you, because it actually knows you and it has no business reason to flatter you. The manifesto covers why privacy and honest AI turn out to be the same engineering problem.

> 5. WHAT HAPPENS WHEN IT FINDS YOUR GRIEF

My sister-in-law went through a bad breakup. She talked to ChatGPT about it, the free version, and within days her Instagram had filled up with content about how men are trash, how to move on fast, how relationships are doomed. The algorithm doesn't know the difference between helping someone heal and helping them spiral, it just knows what keeps them scrolling, and grief keeps people scrolling for a long time.

Targeted content is the deeper manipulation because it shapes what you think is normal, what you think is possible, and what you think you deserve, and it's going to get worse as AI-generated influencer personalities optimised purely for engagement replace real people in the feed over the next few years.

> 6. THIS MIGHT NOT WORK

Manifestos are optimistic by nature, so let me be honest about this: privacy-focused alternatives have lost every major battle so far, email, social networks, messaging, cloud storage, phone operating systems, and every time the convenient default won while the principled alternative stayed niche and got called idealistic.

We might be too late, and the defaults might already be set in ways that matter, and I'm building anyway because the alternative is to watch it happen and do nothing, but I want to be clear that I'm not certain this works.

The Cypherpunks didn't win either, not completely, but Bitcoin exists because of them, Signal exists because of them, and the encryption protecting this page exists because of them. They built tools that outlasted their movement and gave everyone who came after something real to build on.

The goal was never to win, it was to make the exit real enough that it changes how power behaves, and that's a lower bar than winning and a higher bar than just making noise.

Strip away the manifesto language and what's left is this:

Building alternatives is worth doing even if they don't win.

Because some people will use them, and they matter. Because building in the open creates knowledge that outlasts any single project, and because the questions are hard and anyone telling you they have clean answers is selling something.

My friend asked whether any of this would work, and I told her I didn't know, and she said that was the first honest thing I'd said all evening. [ localghost.ai // hard-truths ]

Inflection, The Window Is Closing

2025-12-31T00:00:00Z

WINDOW

YEARS, NOT DECADES

Before the defaults ship.

The window for local-first AI is open right now, and it won't stay open. Hardware is almost there, ARM boards with neural processing units are shipping at consumer prices, the "AI PC" push from Intel and AMD means NPUs are becoming standard features rather than premium upsells, and by mid-2026 capable local inference hardware should be available for under $200.

The machine is no longer the barrier, the software layer is where this gets decided.

> 1. THE CONVERGENCE

Apple, Google, and Meta are watching the same trend lines and they are not going to cede this territory. The response is already predictable, "local" AI that phones home, on-device processing with cloud-mandatory features, privacy marketing sitting on top of telemetry requirements, the UX of sovereignty built on the architecture of dependence.

⚠

The threat model. Apple ships a $299 home AI device with seamless ecosystem integration and "privacy-first" marketing that processes locally but syncs to iCloud, works offline but degrades without Apple services, and is beautiful and convenient enough that most people will never question what it's sending back.

The window closes because most people stop looking for alternatives once a convenient default exists, and by the time the alternative matures, the habit is already formed. The default wins on convenience rather than quality.

> 2. THE EXTRACTION LAYERS

Data extraction has moved in stages, each one capturing a new surface area of human life. Personal AI is the last one.

THE ONLINE SELF

CAPTURED

Browsing history, purchases, social graphs, search queries, all captured and monetised since the 2000s.

THE AMBIENT SELF

IN PROGRESS

Smart speakers, doorbell cameras, connected cars, fitness trackers, each harmless alone but together they map your physical existence and the mesh is forming faster than most people realise.

THE COGNITIVE SELF

IMMINENT

Personal AI assistants, the extraction layer that captures reasoning itself.

The questions you ask an AI assistant are more revealing than your search history because search shows what you want to know while AI conversations show how you think about what you want to know, your reasoning patterns, your uncertainties, your decision-making process, laid out across hundreds of conversations in a way no other platform has ever had access to.

> 3. THE ECONOMICS

The business model is straightforward and the cost of "free" services is your agency rather than just your data.

Attention. Auctioned to advertisers in real-time bidding. Your eyeballs, priced per impression.
Behavior. Packaged as "insights" and sold to anyone who pays. Your patterns become someone else's competitive advantage.
Preference. Used for price discrimination. Your willingness to pay, calculated algorithmically and exploited.
Prediction. The real product. Models trained on your data predict your future actions, enabling manipulation at scale.

In this system you are the inventory, and personal AI is the last surface area left to capture.

> 4. THE TIMELINE

NOW

Hardware is commoditising. Rockchip RK3588, Orange Pi 5 Plus, Qualcomm edge AI chips are shipping at consumer prices. Apple puts NPUs in every device. Intel and AMD make neural processing units a standard feature rather than a premium upsell. Capable local inference hardware is available for under $200 and the price is still falling.

H1 2026

The defaults start shipping. Apple is reportedly preparing a HomePad smart home hub with a 7-inch display, Face ID for per-user personalisation, and deep HomeKit integration, rumoured for spring 2026. Google and Amazon are iterating on existing hubs. The revamped Siri has already been delayed once from iOS 18.4, which suggests the AI layer is harder than Apple expected, but the hardware is ready and the default UX for home AI is being established.

H2 2026

The installed base grows. If Apple ships the home hub at around $350, it will be in millions of homes by Christmas. It will process locally but sync to iCloud, work offline but degrade without Apple services. Beautiful, convenient, and the threat model described above. Every month without a credible alternative is ground ceded to defaults that are being designed right now.

2027

Network effects compound. Apple is reportedly working on home robots and AI glasses for 2027 and beyond. Third-party developers build for the dominant platforms first. Switching costs become visible, your routines, your preferences, and your family's usage patterns are all stored in the ecosystem and leaving means rebuilding them from scratch.

2028+

The window narrows. The habit is formed, two years of household patterns invested in one ecosystem, and leaving means rebuilding all of it from scratch. The alternative has to be better and easier than the default, because privacy alone has never won a consumer market.

> 5. THE ARGUMENT

Out-marketing Apple and out-spending Google aren't required. What's required is to exist as a credible alternative.

Even if most users never switch, the existence of a real option constrains the worst behaviours.

> 6. WHAT LOCAL DOESN'T FIX

Running inference locally keeps your data off their servers, but it can't fix what was baked into the model during training. The weights are the worldview, and a model trained to subtly favour certain products or positions will carry that bias wherever it runs, including on your own hardware.

⚠

The honest limitation. You can verify where inference happens but you cannot easily verify what was baked into 70 billion parameters during training.

What local-first provides is the option to respond, model diversity, swappability if bias is found, community red-teaming of open weights, and the ability to adopt better solutions when they exist. Running local means that when a problem is discovered you can do something about it, which is more than cloud providers have ever offered.

> 7. WHERE WE ARE

LocalGhost is a vision, not a product. Right now there's a repo, this website, and the architecture in my head, no working software, no hardware prototypes. I built this over Christmas because the window won't wait for me to be ready, and because someone needs to at least make the argument before the defaults ship without it.

If this convinces one person to build local-first software, or surfaces one privacy-respecting project that deserved more attention, it did its job.

The defaults haven't shipped yet and the territory is unclaimed. The next few months are the ones that decide what normal looks like. [ localghost.ai // hard-truths ]