Roadmap and Gates Condition-led, not calendar-led.

A gate is a condition attached to a capability. Until it is met, the capability stays where it is in the register, regardless of demand.

Conditions are of three kinds.

Capability conditions.

Something has to be demonstrably deliverable before it is offered. Usually that means it has been done, repeatedly, to a standard that holds.

Partner conditions.

Some capability depends on a delivery partner being in place. Where that partner does not exist, the capability is not offered, and no partnership is implied in the meantime.

Knowledge conditions.

Some work cannot be scoped honestly without knowing how a particular operation runs. That knowledge accumulates over projects rather than arriving with a first package.

Not a date.

No capability on this page carries a delivery date, because a date would be a commitment about work that has not been proven.

Not a forecast of demand.

A gate describes what has to be true, not what is expected to happen.

Not a sales signal.

A capability behind a gate is not available, and reading it here should not be taken as an indication that it can be arranged.

Production readiness assessment as a precondition for production-data scope.

Production data is produced to supplied parameters. Where a shop's parameters are not documented, establishing them is the condition. This is the furthest developed item and it now has a defined route through the Production Readiness Audit.

Deeper value engineering, gated on account knowledge.

Flags come with detailing today. Proposing alternates priced against a shop's own methods requires knowing those methods, which is a knowledge condition rather than a capability one.

Field capture, gated on a delivery partner.

Installation and field drawings are produced from client-supplied measurements. Site capture, laser scanning and point-cloud work depend on a partner arrangement, and until one exists the capability is not offered and no partner is named.

Platform library development, gated on capability demonstration.

Working inside a client's existing environment is delivered today. Building or developing a library within it is not.

Two boundaries are permanent rather than developmental, and stating them here is more useful than leaving them to be inferred.

Structural steel, curtain wall and architectural aluminium detailing.

Different disciplines, different buyers, different obligations. Not offered and not in development.

Machine post-processors and G-code.

These depend on a specific machine, its controller, its tooling and its condition. That work is partner-delivered permanently. It is not a capability being built toward.

When a gate is met, the line moves in the service register and the register becomes the current statement. This page records the condition; the register records the state.

Nothing is described here as imminent, and no line is given a date.