Philosophy
TAS is a practical application of the whose.world framework.
This page is a bridge, not a substitute. If the ideas below resonate, read the original.
The core question
Whose are you?
Every digital environment is built by someone. Every interface has an architect. The question is not whether you’re inside an architecture — you always are. The question is whether you can see it, stop it, and leave it.
Two modes of building
An open‑mode architecture contains pauses, allows exit, and is recoverable. If someone inside it sees how it works — that’s a success, not a threat.
A closed‑mode architecture removes pauses, makes exit costly, and depends on the user not noticing. If someone inside it sees how it works — that’s a risk to the system.
The difference is not intent. The difference is structure.
Three criteria — and five more
The structural foundation is three tests: Pause, Exit, Recoverability. They determine whether a system is open‑mode or closed‑mode.
But whose.world goes deeper. Its diagnostic toolkit identifies five additional forces that erode autonomy even when the structural criteria are met:
Personalisation — a designed flow that looks like your own choice. Urgency — artificial time pressure that disables evaluation. Hidden cost — the price you pay without knowing you’re paying. Transparency fragility — a system that depends on your ignorance to function. Trajectory — the direction a project is heading: toward openness or away from it.
TAS translates all eight into the Infrastructure Audit — a practical checklist for evaluating any technology.
How this relates to TAS
TAS translates whose.world into infrastructure decisions:
- The Infrastructure Audit applies all eight questions to your stack.
- The catalog evaluates each technology against the three structural criteria and assigns Autonomy (A0–A3) and Transparency (T0–T2) levels.
- The recipes combine technologies to build open‑mode systems.
- Selected catalog cards include a Trajectory assessment — not just where a project stands, but where it’s heading.
By using TAS, you become an architect who builds in open mode — creating digital infrastructure that respects the autonomy of whoever uses it.
Further reading
- whose.world — the full philosophical system
- Infrastructure Audit — apply the three criteria to your stack
- Assessment Scale — how Autonomy and Transparency levels are defined