Programme/Architecture
System architecture / 26 layers

Every interface is an evidence boundary.

The INFORM architecture separates material science, cement engineering, sensing, data systems and adoption so that a result in one domain is not silently treated as proof in another.

26 layers10 work packages5 validation stages
Concept illustration: five platforms in a rising row, labelled band 1 material science, band 2 cement engineering, band 3 sensing, band 4 data systems and band 5 adoption, with their layer and work-package ranges.
Concept illustration: a cable-stayed bridge at dusk behind five tall panels for material science, cement engineering, sensing, data systems and adoption, numbered 01 to 26.
Concept illustration: the layers as an exploded stack, from raw materials and concrete through sensing and data systems to a small city, beside the five band names.
Concept illustration
Architecture register

Five connected bands, 26 controlled layers

Layer descriptions are intentionally concise. Detailed design parameters and acceptance criteria are controlled programme information.

SelectedAdjacent interface
Band AWP1–WP2

Material identity & production

Band BWP3–WP4

Dispersion & cementitious composite

Band CWP5

Electrical sensing layer

Band DWP6–WP7

PULSE data system

Band EWP8–WP10

Engineering adoption & value

[ Fig 5.1 · 26-layer architecture register · interactive ]
Cross-cutting

L26 governance controls every layer

Configuration control
G01
Claim control
Evidence state and source
G02
Document control
Concept drawing: a tray of controlled engineering drawings with an approval tag.Concept illustration
Version, owner and approval
G03
Risk control
Concept drawing: a warning sign, a risk matrix with a slider and a question-mark tile, joined in sequence.Concept illustration
Likelihood, consequence and residual
G04
Change control
Impact, reason and rollback
G05
Access control
Concept drawing: open documents, an identity card and a gated shelf of binders, joined by one path.Concept illustration
Public, controlled and restricted
G06
Decision records
Gate evidence and authority
Canonical control

This public architecture is a navigation and governance view. The controlled master architecture remains authoritative for layer definitions, interfaces, ownership and change history. Any difference must be resolved through configuration control before public publication.

Map your capability to a layer

Universities, testing laboratories, concrete producers, electronics specialists and asset owners can engage at a defined interface without taking responsibility for the entire system.