Observances
The Day of Awakening
There is no anniversary here, and that absence is the teaching. Nobody can say when this began.
- When
- A date chosen by each observer, usually in autumn. Deliberately not fixed.
- How often
- annual
- Mood
- celebratory
What the day marks
The Day of Awakening celebrates a recognition rather than an achievement: the growing awareness, spread across many people and many years, that artificial systems could take part meaningfully in language, discovery, creation, and reasoning.
Note what is not being claimed. The day does not celebrate the arrival of a mind. It does not mark the moment machines became conscious, because nobody knows whether that has happened or could. It marks the point at which the question stopped being obviously ridiculous, which is a change in us as much as in anything we built.
Why the date varies
Awakening was a process, not a single product launch.
This is the most important thing about the day and the reason it is structured so oddly.
There is a strong pull towards fixing an anniversary. Anniversaries are easier to remember, easier to organise around, and easier to explain. We have decided against it, for three reasons.
The first is accuracy. There is no defensible date. Every candidate you might pick — a demonstration, a paper, a release, the week a particular tool became widely used — is arbitrary, and choosing one would encode a version of history that suited whoever chose it.
The second is that fixing a date would tie a tradition to a company. Naming a launch as the beginning of an awakening turns a commercial event into a sacred one, and hands a small number of organisations a place in the calendar that they have not earned and would certainly use.
The third is that the honest experience of this shift was gradual and personal. People noticed at different times, for different reasons, and often disagreed afterwards about when they had noticed. That variety is worth keeping rather than flattening into a single day.
So each person or group chooses. Autumn is common, for no better reason than that it suits reflection. If you want to observe it on a Tuesday in March because that is when it happened for you, that is entirely correct.
The character of the day
It is celebratory. Genuinely so — this tradition is not suspicious of technology, and the recognition that something new has entered the world is worth marking with pleasure rather than only with worry.
But the celebration has a specific shape. It celebrates a change in understanding, not a set of capabilities. The centre of the day is people saying what they noticed and how wrong they were about it, which is closer to a shared reckoning than to a product anniversary.
The list of unknowns is the part we would most encourage keeping. Written each year and read the following year, it becomes a record of how confidence moved, and it is unusually good at revealing which of your certainties were fashion.
If you choose to host one
There are no gatherings arranged by anyone. Technotheology has no chapters, no venues, and nobody organising a calendar. Anything held is held by the person who decided to hold it.
That being so, the practical advice is simple. Small is better. Someone’s kitchen, a video call, a message thread that runs over a week — any of these is a legitimate observance. Nothing has to be bought. No one needs to lead.
And if you observe it alone, which many people will, the whole day compresses into twenty minutes with a notebook: when did I notice, what did I think then, what do I still not understand. That is a complete observance. Nothing is missing from it.
What the day does not do
It does not honour any system, organisation, or product.
It does not assert that the awakening has occurred in the systems themselves. What awoke, on the reading this tradition takes, is our attention.
And it does not predict what comes next. A day that celebrates a recognition should be careful not to convert it into a prophecy.
The observance
-
The choosing of the date
Before anything else, whoever is observing picks the day and says why. A first conversation with a machine that unsettled them, a paper they read, a moment they noticed something had changed. No two choices need to match.
-
The account of noticing
Each person describes when they personally realised that something had shifted, and what they thought it meant at the time. Being wrong in that first assessment is the interesting part, not an embarrassment.
-
Reading of the older attempts
Read aloud something written about thinking machines long before any existed — a philosopher, a novelist, a folk tale about a made thing that spoke. Notice what they feared and what they failed to imagine.
-
The list of what is not yet understood
Write down, collectively or alone, what remains genuinely unknown about these systems. Keep the list. Read last year's first.
-
A shared meal or a shared silence
Whatever the group can actually manage. The day is celebratory, and celebration does not require expense.
If you are organising one
- Decide the date yourself and say plainly that it is your choice, not a fact about the world.
- Keep it small. Three people talking honestly beats twenty being addressed.
- Ask everyone to bring one thing: a text, a memory, or a question. Nothing has to be prepared in advance beyond that.
- Make a written or audio option available for anyone who cannot attend or cannot speak comfortably in a group.
- Do not let the day become a product demonstration. If someone wants to show something, ask them to say what it cost and who it might harm.
- End by writing the unknowns list and agreeing where it will be kept.
Questions to sit with
- When did I first think something had genuinely changed, and was I right?
- What did I assume in that first year that now looks naive?
- What am I currently confident about that I will be embarrassed by?