Tour · 8 stops · about 25 min
The architecture in eight stops
Start here if you are new. Each stop is one diagram and a few minutes of reading, in an order where each stop builds on the last. Every stop links to the chapter that has the full detail.
- What Stamped does with plant dataStamped reads data a plant already produces, finds where good parts, material and energy are being lost, and sends one named person a ranked card with options.
- The six layers and the repos behind themThe architecture has six conceptual layers: Plant systems, Context, Analytics, Decision, Action and Value.
- How a finding becomes a decision cardA detection in L3 becomes Evidence, L4 turns Evidence into at most one Prescription draft, and L5 turns that draft into a live card assigned to a person on shift.
- Who approves what: autonomy levels and hard stopsStamped's authority at a plant is whatever the plant grants, per action class and per asset, in an AutonomyPolicy.
- Edge and cloud, and the fast loopStamped runs two loops in two places. The slow loop runs in the cloud over minutes to weeks and is what exists today; the fast loop runs on a Plant Box at the plant, in seconds, and is still direction.
- The ten contracts and how data moves between layersTen versioned contracts carry data between the layers, and repos may depend on nothing else.
- What is built and what is plannedMost of the slow loop exists as code with tests across eleven product repos, but none of it runs at a customer yet, and nothing runs in seconds at the plant.
- What is still open: the decisions boardTwenty-one architecture choices are tracked on one board.