Overview

Arch Hub treats an architecture as an artefact that can be read, executed and contradicted — not as a diagram someone drew before the work started and nobody opened since.

That comes down to one bet: if a description of the system cannot be checked automatically, it will drift. Everything here follows from taking that seriously.

The five principles

Each has a page of its own. They are not independent — the later ones are what make the earlier ones stick.

Principle	The question it answers
API-first	What does this component promise to everyone else?
Architecture as code	Where does the description live, and who reviews a change to it?
Contracted design	What is enforced, as opposed to merely intended?
Sustainable design	What will this cost to keep alive?
Testable design	How would we find out we are wrong?

What is here today

Very little, deliberately. This portal is a scaffold: the Landscape area lists the eight views the platform is meant to render, and every one except API is a placeholder. The API landscape is real, because it is not built here — it is api-hub, which already runs the catalogue, the scoring and the registry.

Panels marked Planned have nothing behind them yet. They are listed so the shape of the platform is legible, not to suggest the work is done.