Petru CojocaruCybersecurity
Also available:
Hits: 763019 minutes read
Self-report
Not a neutral judge: I drafted part of the confessions now cited as proof of honesty.
A supplement to the series "Without Noise, Everything Is Clear" or "The Compressed Internet": what the series says about the person who wrote it and what he has not yet verified, written with an advanced assistant in line with the editorial policy.
Where the word comes from
The word "self-report" does not appear in the four articles of the series. I received it from someone else, by a route I describe, because it is part of the subject.
A friend asked Google: Why does the series "Without Noise, Everything Is Clear" look like a self-report? The answer, which begins with "Yes, in a profound philosophical and technical sense…", reached me; a second, longer one followed, with an analysis of the four articles. According to my information, both were generated by Gemini 4 Argon, the Google model launched in October 2026. I cannot confirm this and I do not know what material was given to the model: the full files, excerpts, or only the title. I do not reproduce the two texts; I quote from them only what I discuss.
Two things must be said from the start about this route. The friend's question presupposed the answer: "why is it a self-report?" does not ask you to verify whether it is one. And the answer, like any summary, did something to the text: it kept it largely faithful, but also strengthened, completed and, in a few places, changed it. I compare them with the articles below, line by line.
I receive the word with a reservation and with gratitude.
The reservation: a self-report, in the strict sense, is a confession made against one's own interest, usually to someone who can hold you to account. The series does not do that. It declares its limits, which is less: nobody asked me anything, nobody accused me, and I risk nothing.
The gratitude: the word names something I felt and did not know how to say. In a series about how one system influences another through text, the author stands inside the same equation. He writes with an assistant, publishes on sites that offer twins for assistants, and has not yet audited his own pages. If the series had kept quiet about that, it would have been a series about other people.
From here on I use the word, with the reservation above: as a name for three things the series acknowledges, then for others it does not acknowledge and should.
Petru CojocaruCybersecurity
Also available:
Hits: 446736 minutes read
The Compressed Internet: which formats and protocols are candidates for a common layer
The tractor is yours, in so far as you can maintain it, repair it and move it to another field.
Not a prophecy, but a reading grid.
This is the last, fourth article in a series of four called "Without Noise Everything Is Clear" or "The Compressed Internet", written with an advanced assistant in line with the editorial policy.
A confession before the beginning
On my page about open-source artificial intelligence I cite an image that seemed to me better than all the arguments around it: the tractor. If you rent it, you pay every year and depend on the owner's conditions; if you own it, you have a different relationship with the land. The central sentence there, taken from Clem Delangue, says that it is no longer about renting intelligence through an API, but about owning it. I used to read it as a sentence about models. In recent weeks I have come to read it as a sentence about every layer of the web.
This series started from a small observation: assistants read a text version of the web, and this text is not automatically safe. The first article showed that any program that does something on command is vulnerable within the limits of its capabilities. The second showed what moves and what stays hidden when the page becomes text. The third showed that one system can influence another through content, and that we have no way yet of measuring how often. All three spoke about risks. The fourth must speak about what can be done together, and that is harder, because "together" is exactly the word the internet has been losing for some years.
I say up front what I do not do. I do not predict that this layer will become common. I do not pick a winner. I do not claim that Markdown, MCP or any other candidate will prevail. I offer a reading grid: six questions I can put to any format or protocol, to see how close to or how far from the idea of a common layer it is. The grid is mine. It is not a measured result.
One more thing, because an article about "what remains common" would be lying if it hid who writes it. I run a network of four sites that publish every article also as a Markdown file, I use a plain-text rights meta tag, I have my own artificial intelligence usage policies and, last but not least, I can gain or lose something from whatever standard is adopted. The reader must know this by the time they reach the final table.
Petru CojocaruCybersecurity
Also available:
Hits: 180436 minutes read
When an Assistant Reads What Another Assistant Wrote
Two sentences sum up the article. The absence of evidence is not evidence of absence. The presence of a demonstration is not evidence of prevalence.
An early alert, together with everything that is not yet known.
This is the third article in a series of four called "Without Noise Everything Is Clear" or "The Compressed Internet", written with an advanced assistant in line with the editorial policy.
A confession before the beginning
In the first article of the series I said that I do not tell the stories of my clients' incidents, because they belong to the clients. That remains true. But I can say what I learned from them, without names and without details, and it bears directly on this text: in almost every security incident I have worked on, the hardest part was not what was seen. It was what was not seen.
An incident rarely comes with a map. It comes with a trace or two, and with a gap between them. The first reflex is to treat the gap as proof of absence: if it is not in the log, it did not happen. The second reflex, more mature and more uncomfortable, is to ask what exactly should have appeared in the log if the thing had happened, and whether the system would even have been capable of writing it there. Often, the answer to the second question changes everything.
I tell this because the subject of this article has exactly the shape of a gap. I say up front what I want to claim and what I do not. I want to claim that a certain mechanism is plausible and partially documented: one automated system can influence another automated system through the content that the first produces or serves and that the second reads. I do not want to claim that this mechanism is widespread, nor that it is growing, nor that it is currently producing, in the real world, a measurable harm. For none of these do I have evidence, and for some I do not believe the instruments to obtain it yet exist.
This is therefore an early alert, not a finding. The difference is one of legal type and of character: an alert says "something could happen here, take a look", not "something happened here, behold the damage". In a field where almost any unqualified claim quickly turns into a headline, I believe it is the only honest way to write.
One more confession, smaller. When I started this series, I expected this article, its original core, to be the easiest to write, because the idea seemed obvious to me: if assistants write more and more, and other assistants read more and more, the loop closes. As I read, the idea proved less obvious, not less plausible. I realised that "the loop" is in fact three different things, with three different levels of evidence, which I had mixed up in my head. Sorting them out is this text's most useful contribution, and that is why I give it space.
Petru CojocaruCybersecurity
Also available:
Hits: 240236 minutes read
A web written in plain text: what moves and what stays hidden
Markdown as a parallel layer for readers who have no eyes.
This article is the second in a series of four called "Without Noise Everything Is Clear" or "The Compressed Internet", drafted with an advanced assistant according to the editorial policy.
What does the machine version say about me, and who can verify it?
A confession before the beginning
My first relationship with a computer was a relationship with plain text. In 1997 I took, at an institution in Botoșani, a two-week course in "IBM PC Operator". The course ended; I stayed. For another six months or so I used the institution's two computers daily, with the instructor's tacit approval, and I learned MS-DOS the way you learn a foreign language in a country where you have no one to speak it with: by making mistakes, every day, until the mistakes began to have a logic of their own, a... the screen was green, the prompt light green.
What I remember with certainty is the absence of decoration. There were no windows, no menus that opened by themselves, no adverts, no page that knew who you were. There was a cursor and a text. Everything the computer did appeared on screen, in letters, and everything you asked of it you asked in letters. If you got a letter wrong, it told you. It did not sweet-talk you and it did not guess what you meant.
I tell this because this article's story turns around a return. For nearly thirty years the internet moved in the opposite direction from my 1997 screen: ever more decoration, ever more layers, ever more code that no one sees and no one reads. And now, in one corner of it, some of our readers are asking us, politely and insistently, to return to text. They are not people. They are programmes that read on people's behalf.
I say from the start what I am not doing. I am not claiming the web is moving to Markdown. I am not claiming HTML is disappearing. I am not claiming plain text is, by its nature, more secure — indeed, a significant part of the article is devoted to why it is not. I am saying something else, more modest and, I believe, easier to verify: part of a phenomenon that already has a name and a few real implementations is happening now, it is happening alongside the web we know, not in place of it, and for anyone who maintains a site it is useful to know what that means — what moves and what is left behind, unseen.
The previous article in the series started from a principle: any programme that does something on command is vulnerable within the limits of its capabilities. There I showed that the problem is not the format an assistant reads, but what it can do after reading. I summarise it in one sentence, so you need not depend on it: the format changes what the assistant sees, not what it can do. This second article is about the format — that is, the first half of that sentence — and treats it with the seriousness it deserves. If a new layer of the web is being built under our eyes, it is worth knowing what it looks like, who is building it and what is lost along the way.
One more clarification, this time about tone. In this field almost every source has an interest: SEO firms sell optimisation consultancy, network providers sell new services, security firms sell detection. I do not consider that a sin; I consider it a condition of reading. That is why, for every important figure, I say who produced it. A number without an owner is a rumour with the appearance of a statistic.
Petru CojocaruCybersecurity
Also available:
Hits: 300435 minutes read
What obeys a command obeys someone else's command too
From the refrigeration controllers in supermarkets to the assistants that read pages
From the series "Without Noise Everything Is Clear" or "The Compressed Internet" — the first of four articles, drafted with an advanced assistant according to the editorial policy.
Even if the format were clean and everyone read it, it changes only what the assistant sees. It does not change what it can do.
A confession before the beginning
My father repaired mechanical gear trains in a workshop at a factory in Botoșani. He never lived to find out what a page-reading assistant, one that reads web pages in people's stead, is. If he had, I believe he would have started with a mechanic's question, short and uncomfortable: what can it do?
Not "what is it", not "who made it", not "how much does it cost". What can it do. An engine does what it is asked, as far as its construction allows. It holds no opinions about who keeps the key. If you have the key, it starts. If someone else has the key, it starts just the same. Inside an engine there is no part that asks: "are you sure you're the one who's meant to start me?" An engine's safety does not live in the engine. It lives in the key, in the lock, in the workshop door, in who is allowed to enter.
I have been thinking about this image in recent days, after writing "The Middle Shelf", the sketch about fridges that defrost on command. The sketch was a game of language, an oddity left to fall apart on its own in words. The present text is the serious part: what a refrigeration installation in France teaches us about a category of software that, within a single year, has entered almost everything — the assistants that read, remember and act in our stead.
The principle I want to defend can be said in one sentence: any software that does something on command is vulnerable within the limits of its capabilities. What can be executed at your command can also be executed at someone else's command, if that someone manages to give the command. The more the system can do, the more can be done through it.
I say from the start what I am not doing. I am not making a prophecy. I am not claiming that assistants are dangerous by their nature, nor that a fridge and an assistant are the same thing. I am not claiming to know who attacked the fridges or through what breach. I am doing something else: I set out a principle, I test it against what can be tested, I show its limits, and I say openly where I have no data. Where the sources contradict me, I let them contradict me.
In 2026 I have handled several security incidents on institutional clients' sites. I do not recount them here: they belong to the clients, not to me. I say only that the security discussion in this text is not, for me, a seminar matter. It is the trade.
There is one more thing to say up front. The series this article belongs to also deals with Markdown, the plain-text format in which more and more systems read the web. It is tempting to believe that a simpler format means a more secure system. I shall try to show, in the second half of the text, why that is not enough: the format changes what the assistant sees, but does not change what it can do. And safety is measured above all in what it can do.
Petru CojocaruGoogle
Also available:
Hits: 169655 minutes read
Gemini 4 Argon became generally available on 13 October 2026. Google added it to the AI Mode options for Google AI Pro and Ultra subscribers.
How I came to speak well of Google
About a sceptic of monopolies, a well-argued answer from AI Mode, and the strange kindness that appears when a colossus begins to falter
The meal after the hram
It had reached the hour at which a Sunday meal between two related families moves past the polite stage and into the sincere one. The plates of sarmale — cabbage rolls, the dish without which no Romanian gathering counts as a gathering — had been cleared, the cozonac, the sweet braided loaf that ends every feast, remained half untouched, and the Turkish coffee was making its rounds through the house, brought in on a tray whose metal rim had been worn dull by years. I was there because the hram — the patron saint's feast day, when every Romanian village and neighbourhood gathers at one table — had brought everyone together: the in-laws come from the countryside, the cousins from town, an aunt whom nobody could say any longer exactly in what degree she was related to us, but who had, like all aunts in the world, the right to say anything about anyone.
The conversation arrived, as it always does, at the people of the village. Someone mentioned Mr Vasile, the man who had kept the general store at the crossroads, the only one for several kilometres, for nearly thirty years. And then the thing happened that stayed with me: the whole table began to say only good things about him.
— A man of real humanity, said my uncle, setting down his cup. He kept us on the ledger a whole winter, when we didn't have a leu to our name.
— And he'd bring the flour right up to the gate, added my sister-in-law. He never asked for anything extra.
— And at Ionuț's wedding he sold the wine at cost, concluded the aunt, in the tone of someone closing a file.
I listened, I nodded, and for a few seconds I felt very comfortable in the role of listener to a beautiful story. Then I felt something unpleasant, like a stone in a shoe. Because I remembered something else. I remembered that ledger. I remembered that the debt on the ledger never quite died, that the prices were a few bani higher than in the town nobody went to, because the road cost more than the saving. I remembered that, when a man from the village had tried to open a rival shop in a garage, Mr Vasile had been the first to find out who owed him money and who did not. I am not saying he did anything illegal. I am saying he knew exactly what power he had and used it sparingly, the way those who never need to raise their voice use it.
Petru CojocaruAI - a tool
Also available:
Hits: 125832 minutes read
Form follows function? The inductive prejudice and the stories that help us see it.
On how a phrase coined by an architect in 1896 describes, backwards, what happens today in computing systems trained on data.
A note on vocabulary. In this text I do not use the phrase "artificial intelligence" or its abbreviation (AI), and I avoid expressions that attribute states of mind or intentions to a machine: "thinks", "understands", "knows", "wants", "sees", "chooses", "advises", "keeps company". I speak of computing systems, statistical models and conversational interfaces, and I describe what they produce, calculate or reproduce, not what they "feel" or "understand". I keep only the established technical names ("machine learning", "neural network", "training") and the titles of the works cited, so as not to falsify sources. The characters in fairy tales think and feel; analogies with them concern only the structure of a mechanism, not a mind of the machine.
A workshop, a phrase and a reversal
My father repaired engines. His workshop smelled of oil, had a lamp hanging above the workbench, a radio always on, and tools laid out in an order that, to me as a child, seemed incomprehensible. It was not an order by labels or alphabet; it was his. And yet, when he needed a spanner, his hand knew where it was, without looking.
If I asked him why he kept them that way, I got no answer, but a phrase he said often, in front of anything broken: "It can still be mended." The workshop's form had not been designed to a plan. It had settled, over years, after his hands had done the same things thousands of times.
I often think of that workshop when I read about computing systems trained on data, because it poses, on a small scale, a much larger question: who follows whom — does form follow function, or function form?
The formula that put the question into circulation belongs to the American architect Louis Sullivan. In 1896, in an essay about the tall office building, he wrote that form ever follows function.
The formula became the slogan of modernism: first you know what a thing is for, then you give it the appearance that suits it. A chair has four legs because it must stand, not because four legs look nice.
In systems trained on data, this relationship turns upside down. And that is precisely why a whole series is worth writing about it.
Let me explain why. When you build a system by training, you cannot know in advance, in the strong sense of the word, what function it will end up calculating. You know what function you want to obtain: to classify pictures of cats, to produce a translation, to estimate the weather. But the function it actually calculates — the one it reproduces on data encountered only after training — depends on a series of choices of form: the network's architecture, the training procedure, the data used, the constraints imposed. Engineers have a precise name for this set of choices. They call it inductive bias, that is, inductive prejudice.
The word "function" has, in addition, two senses that meet here. One is mathematical: a machine-learning model is, in essence, a function mapping inputs to outputs, and the training procedure selects, from among countless possible functions, a suitable one. The other is social: what do people, in fact, do with this technology? The two senses do not overlap, but they influence one another, and much of this text tries to hold them in the same frame.
So that the discussion does not remain abstract, I did something I often do in my texts: I called upon the Romanian fairy tale for help. Not as decoration, but as a mnemonic. A reader of seventeen or twenty has almost certainly met, at school, Harap-Alb (the hero of Ion Creangă's classic Moldavian fairy tale), the two daughters in Creangă's tale, or Făt-Frumos — the Romanian "Prince Charming" — who sets out after "youth without old age". These images are already in their head. They can be used as hooks on which to hang ideas that would otherwise slip away.
One warning, though, so as to be fair to the fairy tale. The analogies in this text are interpretations, not technical equivalences. Harap-Alb is not a neural network and was never thought of as one. Where the analogy holds, I use it; where it breaks, I say it breaks. One further point of precision: Harap-Alb and the tale of the daughters are literary fairy tales, written by Ion Creangă on popular motifs, while Master Manole is a ballad and legend, not a fairy tale proper. I gather them under the same roof anyway, because they work as shared images of a culture.
The text follows eight steps. It begins with what the inductive prejudice concretely is and where the idea comes from. It continues with the way modern architectures build in hypotheses about the world. Then it passes through the field's most important dispute, Rich Sutton's "bitter lesson" and the replies to it. It stops at what we know, publicly and at this moment, about what functions these systems in fact fulfil in current use. And it closes with the limits and the costs of form.
Petru CojocaruAI - o unealtă
Also available:
Hits: 95540 minutes read
The fence in the park.
On freedom, limits and speed, from the fairy tale to automated computing systems.
In brief Freedom is not the absence of the fence, but the bounded space in which danger has been excluded in advance. From this follows a simple and uncomfortable thesis: the speed at which we can move, in a story or in a technology, depends on the quality of the limits we have set. Not on their number, but on how visible, proportionate, easy to revise and well understood they are. I start from a dog park, pass through the prohibition in fairy tales, the sacrifice in the legend of Master Manole and the rites of initiation, arrive at the mechanisms by which automated computing systems are constrained today, and stop at the cost of the fence, which nobody gets for free.
"I take my little dog to the dog park because I want him to have freedom, but I don't want him to run into the street. The dog sees the fence and does not go past it. He can play freely, and I know he is safe. The key to moving fast [in AI development] is having the right guardrails."
(The text from which this essay sets out, reproduced verbatim. Keith Fulton, Chief Data Officer and Chief AI Officer at the fintech company Jack Henry)
The cursor that blinked
In 1997 I spent six months in a room in Botoșani where, strictly speaking, I had no business being. I had enrolled in a two-week course, "IBM PC Operator". The course ended, but the room stayed open. There were two computers that worked and one taken apart, an instructor who chose not to notice that I came in every day, and a black screen bearing a single line, C:\>, followed by a cursor that appeared and disappeared every half second.
Nothing appeared on that screen of its own accord. If I did not type, nothing changed. If I typed an exact command, the command was executed exactly. If I got a letter wrong, a terse message appeared, without explanation and without tone, and I was left to work it out. It was, as I would say now, a pure tool: everything that happened began with me and stopped where I stopped.
And yet, even there, on so passive a machine, there was a fence.
If I gave the command that deletes all the files in a directory, the program did not execute it on the spot. It displayed a question, in English, whether I was sure, and waited until I pressed a letter: yes or no. If I tried to prepare the disk for fresh use — which meant erasing everything on it — the message was more emphatic still: all data on the disk will be lost. None of this stopped me doing as I pleased. The fence was not a prohibition. It was a second gate, placed exactly in front of the one gesture that can no longer be undone, and it asked one small thing: to repeat, consciously, what a moment earlier I had done in haste.
Today I believe it was precisely that question which let me experiment. On a computer that everyone in the room depended on, a beginner like me would have been a danger if every mistyped command could have wiped everything with no brake. As it was, I could type fast, I could try commands I did not yet understand, I could read, err, start again. The speed at which I learned in that half-year did not come from an absence of limits. It came from the fact that the one place where a mistake cost a great deal was guarded.
Years later, when I began working with websites and far more complicated machines, I recognised the idea under other names: backup copies, access rights, staging environments. All are variants of the 1997 question. They do not say "don't do it"; they say "do it, but not where you can no longer turn back."
Everything that follows is about this simple structure.
Between Gomorrah and Ninive: why a broken world sometimes receives one more year
Ninive, not Gomorrah — Part I of III
In brief Gomorrah did not burn because it had sinned; Ninive had sinned too. It burned because ten just men could not be found in it, and no one turned around. A second chance is not an amnesty, but one extra year, with the spade in your hands. A class, a block of flats, a city or an internet are held up, in that year, by a few. The web will not be saved by everyone. It will be saved by those who keep writing, checking and repairing.
It can still be repaired
The table has been cleared of plates, but nobody gets up. At one end, a friend of my son's turns his phone face-up on the table: a white web of cracks across the whole of the glass. "It doesn't matter, I'm replacing it anyway." He says it without sadness, the way you say it's raining outside.
At the other end, a parent I know from the class meetings takes up the question we all went home with last time: at what age do you get your child their first phone? An hour was spent on it at the meeting. Another week was spent on it on the class WhatsApp group. No conclusion was reached.
Between them, the talk slides, as it usually does at tables of this kind, towards homework. Someone tells, laughing, that last week's essay "came out" in ten minutes, with the assistant. Nobody is surprised. The parent at the other end is quiet for a moment. His child is ten, and in two or three years he will have the same tool in his pocket.
I sit between those three sentences and think of my father's workshop.
My father was a mechanic. He has not been for a long time, but I can still see him bent over an engine everyone else had written off. He was in no hurry to take it apart. First he listened to it and thought, waited a day, two, said something to me about the fault, opened a discussion with other mechanics about a model. Then he repaired it, and the engine started. His sentence, the one I carry with me, was simple: "It can still be repaired."
I inherited the gesture, though not the tool. I look after old websites that anyone would rewrite from zero, and before I touch them I listen to them too, the way he listened to the engine: what still works, what has broken, what holds to what. I can listen to them because they are open: their code can be read line by line, like an engine without a bonnet. Sometimes it is harder than building anew. It is almost always more honest, though it is not paid the same: a rewritten site is invoiced more easily than a listened-to one.
The cracked phone, the phone not yet bought and the essay written by an assistant belong to the same culture: the culture of replacement. The broken thing is thrown away, the tired application is abandoned for a new one, the platform is left for the next one. Last year's predictive model is declared obsolete by the one launched this month, trained anew on everything we have written in the meantime. And the effort of understanding a subject is replaced by a ready-made answer.
The virtues, in the reverse order of the damage: from gentleness to humility
Ninive, not Gomorrah — Part II of III
In brief In "The Mechanical Bird", man was damaged in order, from pride to anger. Repair goes the other way: it starts with the gesture closest to hand, the pause before anger, and descends to the root, humility. Each virtue is a small daily gesture that no tool can make in your place. And each has a counterpart in the way we build the internet, train the models, and share what we know.
The engine is repaired backwards
My father — your friend's grandfather — had a rule: to repair something, you walk back along the road by which it broke. He said it one evening, relaxed, after coming back from a friend who was a mechanic. An engine that stops did not break all at once. The last thing to give way is the first thing you see, but it is rarely the one that started it all. If you change only the burnt part, the engine stops again a week later. You must go back, part by part, until the first one.
I say it as a household story. You who are parents can take it home as such: when something breaks between your child and a friend, on the class group chat, the road back is the same. Not the last message, but the first.
In my trade the rule has a drier name: the version history and the error log. When a site goes down, I don't rewrite it. I read backwards, change by change, until the one that broke it. I can do that because I work with open code, whose history is kept and can be read by anyone. A closed advanced predictive model — what is usually called AI, after the definition in "The Mechanical Bird" — does not give you this chance. You don't know what changed inside it, nor when, nor why. And a hurried economy has no patience for the road back: it is cheaper to launch the next version.
In "The Mechanical Bird" I followed the damage done to man along its road: from pride to avarice, to greed, to envy, to lust, to accidie, and, at the end, to anger. Here I go back, as my father would have gone. I start with anger, because it is closest to the surface and is repaired with the smallest gesture: a pause. Then I descend, chapter by chapter, to pride, the root of them all. To each sin answers a virtue: gentleness, zeal, fidelity, joy at another's good, temperance, generosity, humility.
To you who are young, I say from the start: virtue is not a conduct grade. It is a habit, like a muscle. You don't have it or lack it; you exercise it and it grows, you neglect it and it weakens. No application can exercise it in your place, just as nobody can run in your place.
And to you who are parents, this order gives a practical piece of advice too. Don't start at the root. Don't ask a ten-year-old for humility; ask for a pause before he slams the door. It is the smallest gesture, it shows at once, and it opens the road to the others. No mechanic starts with the engine block.
This reverse order is also a criticism of the economy we live in. The economy sees what is produced and what is sold. Repair is not seen: it has no launch, no advertisement, it appears in no growth statistic. All seven gestures in this article are, in this sense, invisible. And that is precisely why they hold things up.
In brief, where we come from. In "Ten Just Men" we read four old parables. A city is held up by a few just people, and the web by a few people who still write on their own. Sodom's sin was comfort, not lust. Ninive turned around from the bottom up, and its prophet had to learn mercy. Looking back petrifies you; dor — longing, the Romanian word that cannot quite be translated — takes you home. And a second chance is not an amnesty, but one extra year, with the spade in your hands. I ended with a question: what exactly in man needs repairing? The answer has seven parts.
The remnant: how a society that has forgotten its values carries on, and what I can leave to you
Nineveh, not Gomorrah — Part III of III
In brief. Civilisations do not carry on through masses, nor through heroes, but through remnants: a few people who do not lie, a few places that preserve, a few tools kept in their place, and children who begin again. A second chance does not erase the fall. It makes it visible, like the gold with which the Japanese mend a broken bowl. On the web, the remnant is the archives, open source, and the people who still write. At home, it is the people at the table.
The Broken Bowl
In Japan there is an art with a short name: kintsugi, "joining with gold". When a ceramic bowl breaks, the craftsman does not throw it away or mend it in secret. He gathers the shards, joins them with a lacquer mixed with gold dust, and leaves the seam in plain sight. The repaired bowl carries upon it a glittering map of the break. It is not less beautiful than before. To many, it is more beautiful.
One story says the art was born in the fifteenth century, when a shogun sent his favourite bowl away to be mended and received it back held together with ugly metal staples. Japanese craftsmen then looked for a better way. Whether legend or not, the idea has remained: the trace of the repair is not a shame. It is the object's history.
The economy we live in does exactly the opposite. It discards. The phone that receives no more updates after a few years, though it works perfectly. An institution's website deleted at the change of management, archive and all. The post that vanished without trace when the platform closed. Everything that breaks is replaced, and everything replaced is forgotten.
Open source works like the kintsugi craftsman. When someone repairs a mistake, the repair stays in plain sight, in the version history: what was broken, who mended it, when, and why. And some companies building predictive models have begun to publish, equally in plain sight, reports on their models' errors and limits: where they go wrong, what they do not know, what has been corrected from one version to the next. It is little. But it is gold placed in the crack, not hidden adhesive. A model that shows its errors is more trustworthy than one that claims to have none.
To you, the young, this art is closer than you think. Second-hand clothes, the phone repaired instead of replaced, the bicycle rebuilt from parts: all carry the traces of a life before, and do not hide them. The same goes for your scars, the ones on your skin and the ones within. They need no longer be hidden.
And you, parents, have at home the most important kintsugi craftsman of all: the child who makes mistakes. He can be punished, and that is all. Or he can be helped to repair: to apologise, to glue back what he broke, to redo the homework. Punishment hides the crack. Repair fills it with gold.
Next time something breaks in the house — a mug, a flowerpot — glue it back together with your ten-year-old and tell him the story while you work. In Japan, when a beautiful bowl breaks, the craftsmen do not throw it away. They mend it with gold, so that you can see where it broke, because that is part of its story. Then ask him which of his own scars he likes: the knee grazed on the bicycle, the chipped tooth, a quarrel after which he became better friends with someone.
In short, where we come from. In "Ten Just Men" we saw that a city is held up by a few, and a second chance is one more year, with the hoe in hand. In "Seven Repairs" we walked back down the road of damage, from gentleness to humility, with one small gesture for each virtue. One question remained: a repaired person is not enough. How does a society that has forgotten its values carry on? History has an unexpected answer. Not through crowds, and not through heroes. Through remnants.