Service Register Three states, not one list.

Delivered.

Marketed, scoped and delivered as standard work. A client can expect a quote against a defined scope and a committed date.

Quoted on enquiry.

Listed capability, scoped per project rather than sold as a standard offer, usually because it depends on knowing how a particular shop already works. It is not a lesser service; it is one that cannot be scoped honestly from a distance.

Recorded as direction.

On the capability map, not offered. Listing it here rather than omitting it is deliberate: a reader assessing scope needs to know what is not available as much as what is.

Sub-service lines within each are set out on the service pages themselves.

Adjacent areas that appear on the capability map and are not offered. They are set out in full on horizon practices, and the direction attached to them is on the Track B roadmap.

Two boundaries are permanent rather than developmental, and worth stating here: structural steel, curtain wall and architectural aluminium detailing are not offered, and machine post-processors and G-code are partner-delivered and are not offered. Neither is on a roadmap.

A capability moves from direction to enquiry, and from enquiry to delivered, when the conditions attached to it are met rather than when demand appears. Those conditions are recorded on the roadmap.

The register reflects the current state. It is not a forecast, and a line's presence in a lower tier is not an indication that it will move.