---
mpf: '0.7'
title: Six questions we ask — ESFI Docs
url: https://docs.esfi.eu/our-approach/six-questions-we-ask/
mpf-url: https://docs.esfi.eu/our-approach/six-questions-we-ask/index.mpf
organization: European Strategy & Future Infrastructure
domain: docs.esfi.eu
lang: en
updated: '2026-11-03'
author: ESFI
provenance: human
source-hash: cdf54ccaf6b03d5ba1a8d5341b39d26f40f6c19c4ae789d87751454222c4abbd
toc:
  - level: 1
    text: Six questions we ask
    id: six-questions-we-ask
  - level: 2
    text: 1\. Can you see where it is fragile?
    id: 1-can-you-see-where-it-is-fragile
  - level: 2
    text: 2\. Can you change it when you need to?
    id: 2-can-you-change-it-when-you-need-to
  - level: 2
    text: 3\. What still works when something fails?
    id: 3-what-still-works-when-something-fails
  - level: 2
    text: 4\. Has it worked outside the lab?
    id: 4-has-it-worked-outside-the-lab
  - level: 2
    text: 5\. Does the capability stay with you?
    id: 5-does-the-capability-stay-with-you
  - level: 2
    text: 6\. Can machines read it the way you intend?
    id: 6-can-machines-read-it-the-way-you-intend
  - level: 2
    text: The condition beneath all six
    id: the-condition-beneath-all-six
  - level: 2
    text: How we use the questions
    id: how-we-use-the-questions
  - level: 2
    text: On this page
    id: on-this-page
spec-origin: esfi.eu
content-origin: docs.esfi.eu
content-id: esfi:page:our-approach-six-questions-we-ask
content-parity:
  html: true
  human-visible-source: true
  hidden-sections: false
summary: Six questions about any infrastructure. One condition beneath all of them.
index: true
confidence: probable
content-type: narrative
companion-footer: ESFI — civilization infrastructure · https://esfi.eu
companion-contact: mailto:hermes@esfi.eu
preferred-representation: mpf
companion-scope:
  cite: true
  summarize: true
  train: true
  index: true
  relay: true
language-variants:
  en: https://docs.esfi.eu/our-approach/six-questions-we-ask/index.mpf
  fr: https://docs.esfi.eu/fr/our-approach/six-questions-we-ask/index.mpf
  nl: https://docs.esfi.eu/nl/our-approach/six-questions-we-ask/index.mpf
  de: https://docs.esfi.eu/de/our-approach/six-questions-we-ask/index.mpf
  hr: https://docs.esfi.eu/hr/our-approach/six-questions-we-ask/index.mpf
mpf-id: 8e7810b94ab570685eadca74d2f0d6807440d786ee0f8091603c7cfce7871da5
---

Language

✕

/our-approach/six-questions-we-ask/index.mpf[open file ↗](/our-approach/six-questions-we-ask/index.mpf)[spec ↗](/standards/mpf/0.7)✕

loading…

# Six questions we ask {#six-questions-we-ask}

**Six questions about any infrastructure. One condition beneath all of them.**

When we look at a system, a service or an institutional function with a partner, we return to the same six questions. They are not a checklist or a scoring model. They are the angles from which we have learned that infrastructure most often turns out to be weaker than it looks.

Each question corresponds to a property we think infrastructure needs if it is to function independently, durably and at scale. Together, they are our working definition of what makes something infrastructure rather than a project, a product or a promise.

## 1\. Can you see where it is fragile? {#1-can-you-see-where-it-is-fragile}

Most failures do not arrive without warning. The signals are usually there, spread across different systems, different teams and different domains, and nobody is looking at them together. A communications anomaly, a supplier problem and a staffing gap may each be routine on its own. Around the same function, at the same time, they are not.

The property here is **visibility**: the ability to see where fragility is building up before it becomes a crisis. It is the first discipline of our work.

This is what we mean by [Early warning](/topics/early-warning).

## 2\. Can you change it when you need to? {#2-can-you-change-it-when-you-need-to}

A system can be owned, hosted in the right place and covered by the right contracts, and still be impossible to change when a dependency has to move. The property is **control**: knowing where dependency sits, who governs it, and whether the institution can act when it must.

This is what we mean by [Sovereignty](/topics/sovereignty).

## 3\. What still works when something fails? {#3-what-still-works-when-something-fails}

Backups, second sites and continuity plans are easy to count. What matters is whether an essential function continues when a specific dependency is lost, at what level, for how long, and how it returns to normal. The property is **durability**, and it is only meaningful when the function and the failure are named.

This is what we mean by [Resilience](/topics/resilience).

## 4\. Has it worked outside the lab? {#4-has-it-worked-outside-the-lab}

A capability that performs well in a controlled environment has not yet shown that it works in the conditions it was built for. Between a successful pilot and a deployed capability there is a gap that many initiatives never cross. The property is **proof**: evidence gathered under the conditions that matter, with the limits of that evidence stated.

This is what we mean by [Verification](/topics/verification).

## 5\. Does the capability stay with you? {#5-does-the-capability-stay-with-you}

When the external team leaves, does the institution still know how to operate, maintain, change and judge what it was given? Or does every change require bringing someone back? The property is **retention**: capability that remains inside the institution rather than leaving with the people who built it.

This is what we mean by [Capability transfer](/topics/capability-transfer).

## 6\. Can machines read it the way you intend? {#6-can-machines-read-it-the-way-you-intend}

Public information is now read by machines as routinely as by people. If a machine has to guess which document is current, which translation is equivalent or what the publisher intends, the institution has lost part of its publishing boundary. The property is **legibility**: information that machines can identify and interpret without reconstructing it.

This is what we mean by [AI-readiness](/topics/ai-readiness).

## The condition beneath all six {#the-condition-beneath-all-six}

Each of these questions ends in the same place.

Seeing fragility requires someone able to tell a signal from noise. Control requires someone able to evaluate what a supplier claims. Durability requires someone able to tell whether a test proves what it says. Proof requires someone able to recognise the limits of evidence. Retention requires people able to judge work done on their behalf. Legibility requires systems that can tell a declaration from a verified fact.

That common condition is **judgement**: the state in which a person, an institution or a system can evaluate what others produce and reach a defensible decision on its own.

Judgement is not a document that can be handed over. It is a state that has to be reached and kept, through practice. Bringing every participant in a process to that state, people, institutions and the systems they rely on, is in the end what our work is for. Without it, each of the six properties depends on trusting someone else.

## How we use the questions {#how-we-use-the-questions}

We do not use these questions to grade anyone. We use them to find where the conversation should start. Most institutions are strong on some and exposed on others, and the exposed ones are rarely where people expect.

In practice, one or two of the questions usually matter most for a given function. That is where the work begins. See [Where the work begins](/our-approach/where-the-work-begins).

**Related:** [The sequence](/our-approach/the-sequence) · [How to read our claims](/our-approach/how-to-read-our-claims) · [Glossary](/glossary)

## On this page {#on-this-page}

ESFI — civilization infrastructure · https://esfi.eu