The future, painted.

Scenarios by Balane. The images are concept images by Bria.

The state as an interface (2038, State)

Today, files pile up under a stamp. The day after tomorrow, administration is an interface that checks the application while you file it. Then what counts is who writes the rule, and what happens when it stops running.

Today

  • Digital offices: Estonia handles almost all dealings with authorities online. The country shows it can be done.
  • Promised is not delivered: Germany's Online Access Act was meant to bring hundreds of public services online by the end of 2022. Three years after the deadline, only part of them were there. There were hardly any consequences.
  • When the network falls, the service falls: After the attack on two Berlin senate departments in August 2026, housing benefit payments for tens of thousands of households were at risk.

What changes

  • The application files itself. The state knows what you are entitled to and offers it before you ask.
  • Law becomes code. Laws are written so that machines can check them. Whoever translates them writes along, and every default becomes procedural law.
  • A person for the rest. A person remains for the cases that need empathy. And for the day the system goes down.

The story, step by step

  1. A government corridor, today. Door after door, and someone waiting outside each one.
  2. The display changes. Nobody can tell you when your turn will come.
  3. The same form for every door, filled in once more. Files travel from stamp to stamp.
  4. Then the paper folds into itself. What the state needs to know sits in one place. Once.
  5. A woman walks in. Before she reaches a door, the offer comes to her.
  6. The application files itself. She says yes and walks past every door.
  7. The law on the wall becomes a rule a machine can check. Whoever translates it writes along.
  8. The stamp becomes an interface. Decisions flow without anyone touching them.
  9. The chairs are no longer needed. There are no waiting numbers anymore.
  10. The walls fall. The corridor becomes an open space where everything runs quietly. An error now runs quietly too, the same in every decision.
  11. One person remains. For the cases that need empathy, and for the day the system goes down.
  12. Whom do you turn to when the interface says no?

Whom do you turn to when the interface says no?

The objection: A state that delivers wins twice: once in results, once in trust. The risk lies less in the machine than in nobody practicing how to work without it.

The future,
painted.

N° 01 · Software · 2029

Nobody builds apps

01 · Today · Signs that it has begun

  • Code by description

    Developers let AI assistants write functions and only review them. Cursor, Copilot and Claude Code are part of everyday work in many teams.

  • Prototypes the same day

    What used to be a sprint now stands as a clickable draft the same afternoon. Whether it holds up in operation shows later.

  • Experts build for themselves

    People without a computer science degree build their own internal tools without waiting for IT. Who maintains them once they leave is usually written down nowhere.

Draft. Sources to follow.

02 · Tomorrow · 2029 · Concept image

Today, teams write code for months. The day after tomorrow, software takes shape in conversation, in minutes. The machine takes over the typing. Not the deciding, and running it does not get cheaper.

03 · What changes

  1. 01

    You describe instead of build.

    An app emerges from a conversation about the problem. The software asks back, proposes, builds and tests itself.

  2. 02

    Being wrong gets cheap.

    A tool for one week pays off because it costs almost nothing. Whatever does not fit is regenerated. What has to keep running stays expensive: maintenance, security, liability.

  3. 03

    Deciding becomes the bottleneck.

    No machine can automate a decision nobody ever made. Whoever does not know what they want gets the wrong thing very quickly.

04 · The question

Who still understands your software when the machine that built it fails?

The objection Maybe running software becomes as cheap as building it. Then the only bottleneck left is knowing what you want. That was always the most expensive part.

Keep scrolling: N° 02 · Your colleague is an agent

DE/EN

// Vision · 2026
Scenarios, continuously rethought.

////// Manifest

6 scenarios on how software, work, markets and the state will change. Painted with concept images, thought through from 2026 to 2045.

Scroll to enter the valley

Imprint · Privacy

Imprint · Privacy · Deutsch

[························]   0