Register of futures Optimism, practiced Open filing

Futures worth building The long list of good futures, taken seriously enough to plan for.

Twelve entries filed

Revised continuously

On the method

Pessimism is easy to make rigorous. You list what breaks, and you are usually right, because most things do break. Optimism gets treated as the soft option: a mood, a temperament, something you either have or you do not.

This register treats it as paperwork instead. Every good future below is filed the way a serious plan is filed: with the conditions it depends on, the things already true, and the one next action that is small enough to actually start. If a future cannot survive that treatment, it was a wish. If it can, it was a plan all along and nobody had written it down.

None of these are predictions. They are open files. Open a row to read the docket.

Depends on

  • Licenses that survive an acquisition
  • Formats a stranger can read without permission
  • Funding that does not require growth to continue
  • Maintainers paid before the crisis, not during it

Already true

Some of the most load-bearing code in the world is older than most of the companies using it, and is maintained by people who were never anyone's employee. The proof exists. What is missing is the habit of building that way on purpose.

First step

Pick one tool you rely on daily. Find out who maintains it and how they are paid. That answer is the future arriving early or late.

Depends on

  • Parts sold to whoever asks
  • Schematics that are not a trade secret
  • Glue used where screws would do the job
  • Repair taught somewhere before it is needed

What is blocking it

Nothing technical. A repairable device costs slightly more to design and considerably less to own. The blockage is that the person choosing the design and the person living with it are never the same person.

First step

Fix one thing you were told to replace. The knowledge that it was possible is the part that spreads.

Depends on

  • Hardware cheap enough for a street to buy
  • Working examples in more than one country
  • Municipal rules that permit rather than forbid
  • Someone in the neighbourhood who enjoys the wiring

Already true

Community networks already serve towns that no carrier considered worth the trench. They tend to be cheaper, and they tend to be repaired faster, because the person fixing the line also lives on it.

First step

Learn who physically owns the cable into your building. Almost nobody knows. It is the first fact any of this depends on.

Depends on

  • Teams small enough to see the whole shape
  • Outcomes reported back to the people who made them
  • Metrics that describe the work instead of replacing it
  • Permission to say a task was pointless

Why it is on the list

A surprising share of skilled people cannot say what their work changed. Not because it changed nothing, but because nobody closed the loop. This is one of the cheapest futures here and one of the least attempted.

First step

Tell one person exactly what their work made possible. Be specific enough that it could not apply to anyone else.

Depends on

  • Engines that were the loudest thing becoming optional
  • Surfaces chosen for sound, not only for cost
  • Streets where walking is the default, not the concession
  • Noise treated as a health measure rather than a nuisance

Already true

This one is arriving as a side effect of decisions made for other reasons, which is how most good futures actually arrive. The work is noticing it in time to keep it, instead of filling the quiet back up.

First step

Stand on your street and count what you can hear. Do it once a year. You are now holding a dataset nobody else has.

Depends on

  • Copies in more than one jurisdiction
  • Open formats with published specifications
  • Endowments rather than annual grants
  • An agreed answer to who inherits it

What is blocking it

Archives die of budget cycles, not of fire. The technical problem was solved decades ago. The institutional problem, which is that most organizations cannot credibly promise anything beyond their next funding round, was not.

First step

Keep your own copy of something you would miss. Distributed redundancy starts as a personal habit before it is ever a policy.

Depends on

  • Corrections that reach the audience the claim reached
  • Careers that survive an honest retraction
  • Predictions kept on record with dates attached
  • A culture that reads a reversal as competence

Why it is on the list

Almost every other future here gets cheaper if this one lands, because the main cost of a mistake is the time spent defending it. This is the load-bearing entry in the register and the one with the least visible progress.

First step

Write down a prediction with a date on it. Check it when the date arrives, out loud, whichever way it went.

Depends on

  • Export that returns everything, not a summary
  • Interfaces that reward the practised hand
  • Changes that respect what you already learned
  • Business models that do not need your attention daily

Why it is on the list

Most software is designed for the first week of use and then optimised against the tenth year of it. A tool built for the long user looks different at every level: fewer prompts, more depth, no urgency.

First step

Try to export everything from the app you use most. Whatever comes back is what you actually own.

Depends on

  • Publicly funded work published publicly
  • Mirrors run by people with no stake in the traffic
  • Citations that survive the link rotting
  • Translation treated as part of the work

Already true

The default has genuinely shifted within one working lifetime. A student anywhere can now read most of the frontier. That was not true recently and is not guaranteed to stay true.

First step

When you cite something, link the version that will still resolve in twenty years. Prefer the archive to the announcement.

Depends on

  • Systems run below capacity on purpose
  • Savings that are normal rather than exceptional
  • Schedules with recovery time already in them
  • Institutions that hold reserve without being asked why

What is blocking it

Slack looks identical to waste right up until the moment it is the only thing that saved you. Every efficiency drive removes it, and every crisis proves it was the point. The blockage is that the removal is measurable and the rescue is not.

First step

Leave one thing in your week deliberately unbooked and defend it as though it were a meeting. It is the smallest possible version of this entire file.

Depends on

  • Nothing anyone has to invent
  • Staying in one place long enough, or trying anyway
  • Repeating occasions that need no organiser
  • Contact that is not mediated by a company's roadmap

Why it is on the list

This is the only entry that requires no funding, no policy, and no technology, and it is the one most reliably left undone. It belongs in a register of futures because it decays silently when it is not scheduled.

First step

Send the message you have been meaning to send. There is no version of this plan that starts later and goes better.

Depends on

  • Someone noticing a good future nobody filed
  • Taking it seriously enough to write down what it needs
  • Being willing to be wrong in public about the timing

Why the file stays open

A closed list of good futures would be the most pessimistic document here. This row is left deliberately empty so the register cannot pretend to be finished, and so the next person to read it has somewhere to put something.

First step

Name one. Give it a horizon and one honest precondition. That is the whole method, and it fits on the back of anything.

On the horizon column

The dates are the least reliable part of every file and the most important thing on it. A future without a horizon cannot be planned for, only hoped at.

Being wrong about when is a normal cost of taking something seriously. Refusing to guess is how a good future stays permanently ten years away. Everything here is filed with the expectation that some of it will be revised, some of it will arrive early by accident, and at least one entry will turn out to have been finished while nobody was watching the row.