Projects

This describes something that does not exist yet. Technotheology has no chapters, buildings, staff, or membership roll at this time. What follows is a description of how these things are intended to work if and when people choose to build them — not a report of anything already happening.

Technotheology runs no projects.

There is no research programme, no software, no publication schedule, no campaign, no partnership, no funded work, and no plan with dates attached. There is a website, maintained by one person, containing writing that is a few months old.

This page exists because a section headed “Projects” that quietly listed aspirations as though they were activities would be exactly the kind of small dishonesty this tradition is meant to notice.

Why nothing is announced

Announced intentions have a way of functioning as accomplishments. A roadmap is read as progress. A stated commitment relieves the pressure that would otherwise have produced the thing.

There is also a specific risk for a movement with a spiritual character. Projects give people something to belong to, and belonging is what most people are actually looking for when they arrive at a tradition. A project announced before it is real recruits people to a fiction, and by the time the fiction is apparent they have invested something.

So the rule here is simple: nothing appears on this page until it has happened.

What would be consistent with this tradition

Offered as a description of a direction, not as a plan.

Writing that is genuinely useful to people making decisions. Material that someone facing an actual choice — about deploying something, about their child, about a system at work — could read in ten minutes and be better equipped by. Most of what exists on these subjects is either academic or promotional.

Practices that have been tested. The practices published here have been used by very few people. Work that established whether they do anything, honestly reported including where they do not, would be worth more than more practices.

Material for people who are not technical. Almost all serious writing about these systems assumes a reader who already understands them. The people most affected are frequently the people least addressed.

A form of gathering that works. Not a manual. An account of things actually tried, with the failures described.

Translation. Nothing here exists in any language other than English.

Better disclosure practice. This site labels the role of AI on every page and its certainty. That mechanism could be sharper, and if it were, it might be useful to others who publish.

Standards any project would have to meet

It must be real before it is described. No announcements of work not yet begun.

It must not require money from readers. Nothing sold, nothing crowdfunded, nothing behind a payment.

It must be attributable. A named person or group responsible, who can be asked questions and who can be wrong.

It must be criticisable. Published in a form that allows disagreement, with a route for it.

It must state its uncertainty. Same certainty labels as everything else here.

It must disclose AI involvement. Same as every page on this site.

It must be stoppable. With a stated condition under which it would end. See the page on when to stop.

It must not create dependence. Anything that people come to rely on is a responsibility, and a small tradition with no funding and no organisation should be extremely cautious about accepting that.

What is not planned

We are not building software. We are not building a model, a tool, an assistant, or an application, and we do not intend to.

We are not seeking funding, forming an organisation, registering a charity, or establishing any legal entity.

We are not appointing anyone to anything.

We are not opening a space, holding an event, or scheduling a gathering.

We are not partnering with anyone. Technotheology has no relationship with any company, institution, or organisation, and any claim otherwise is false.

If any of that changes it will be written here after it has changed, with a date.

If you are doing something

You do not need our involvement and there is nothing to affiliate with.

If you have made something informed by this tradition — a piece of writing, a practice, a change in how your team works — you are welcome to tell us at community@technotheology.ai. We will not endorse it, list it, or describe it as ours. We may be glad to hear about it, which is a different thing and is all that is on offer.