Book · Mateusz Chrzanowski
THE LAYER
ABOVE
A book about the architecture that becomes visible when separate systems stop being analysed separately.
Technology, organisations, markets, infrastructure, people and decisions are usually divided into categories because categories make complexity manageable. Reality is under no obligation to respect those boundaries. The Layer Above is about what appears when those fragments are reconstructed as one system.
“I do not intend to teach you anything in this book. I intend to show you a different perspective, and I hope it stays with you.”
01 · The visible event
The problem is often older than the event.
A factory stops. A customer leaves. A company enters insolvency. A grid cannot meet demand. A cyberattack interrupts production. The visible event immediately takes over the conversation because it is concrete. It has a date. It can be measured, reported and assigned to someone.
But serious system failures rarely begin where they become visible. By the time a crisis reaches the board, the operator, the regulator or the public, the architecture may have been producing that result for years.
The event is real. It is not necessarily the beginning of the problem.02 · System boundary
The visible system is not the whole system.
A factory is not only production. A hospital is not only medicine. A transport company is not only vehicles. An energy system is not only generation. A business is not the sum of the departments shown on its organisational chart.
Specialists are necessary because individual layers can contain enormous depth. The mistake begins when depth inside one layer is mistaken for visibility of the whole.
03 · Accumulated architecture
Architecture accumulates.
A small organisation can begin with a structure somebody genuinely understands. Then it grows. New systems are added. Procedures solve local problems. Spreadsheets appear around software that does not quite fit. Departments optimise their own results. Temporary solutions survive. New technology is connected to old technology.
Years later the organisation still has an architecture, but much of it may no longer have been designed as a whole.
Most of it was simply never designed.
It accumulated.
04 · Two systems
Different systems. Same function.
The book begins with two systems that should have almost nothing in common. One was a fragmented transport labour market. Drivers existed. Companies existed. Routes, rates and demand existed. What was missing was the organising layer capable of connecting them.
The other was an industrial power plant. The equipment had been designed. The documentation existed. The technical destination was known. What was missing was a structure capable of turning that complexity into executable work.
Different domain. Different material. Same function.Architecture / execution
Architecture has to survive contact with execution.
Japojade could not remain a diagram of how a labour market should work. The power plant could not remain a technically correct set of drawings. Eventually real people had to use one system and physically build the other.
The output of architecture is not the elegance of the model.
The output is a system that can exist.
Inside the book
The book moves across scale.
Markets, companies, products, infrastructure, technology, organisations, industrial systems and public systems. Not because they are interchangeable, but because the architectural questions repeat.
“The place where the system screamed
is not necessarily the place where it was wounded.”
The final event gives the system a voice. It does not give you its architecture.
Read the sample
Start with the book itself.
The sample contains the complete Prologue — Two Systems. One Function. — and Chapter One —The Problem Started Before You Saw It.
No registration. No email gate. Just read it.
The complete book
THE LAYER ABOVE
328 pages · 14 chapters · 3 interludes · First Edition 2026
The argument continues through system reconstruction, boundaries, accumulated architecture, fragility, products, organisations, execution and finally the role of the System of Systems Architect.
Departments have boundaries. Professions have boundaries. Companies have boundaries. Industries have boundaries.
Reality does not have to respect any of them.
From inside one domain, the effects may look disconnected. From above, they may be one structure. When separate systems stop being analysed separately, they begin to form one model.
THAT IS THE LAYER ABOVE.