The four-discipline operating cycle that connects all six modules into a continuous, repeatable practice. Read → Extract → Design → Deliver. Non-linear. Runs continuously throughout the engagement. New information triggers a return to the appropriate discipline, not a restart of the full cycle.

The first discipline in the Velocity Loop. Establishing situational awareness before first stakeholder contact. Engagement archetype identification. Document inventory. Stakeholder mapping. Environment diagnostic. Read is complete when the practitioner knows what kind of engagement they are in and what posture it requires.

The second discipline. Obtaining the information required for accurate design from stakeholders who may not volunteer it. The ten-question protocol. Vendor interrogation. Information gap mapping. Extract is complete when the intelligence base is sufficient to begin design — not when every question has been answered perfectly.

The third discipline. Selecting the right instrument, at the right level, for the right audience. Current state mapping. Target state definition. Gap analysis. Heat map completion. Assumption register. Risk register. Technical debt register. Design is complete when the Architecture on a Page can be produced without further information gathering.

The fourth discipline. Producing the five artefacts and presenting them to every audience who must act on them. Raising concerns in writing. Holding positions under pressure. Escalating through the three-layer protocol when required. Deliver is complete when the delivery team can operate without the solution architect in the room.

The level at which a decision belongs. Business decisions belong at business altitude — with the executive audience who funds and approves. Technical decisions belong at solution architecture altitude — with the architects and technical leads who design and build. Delivery decisions belong at delivery altitude — with the project and operations teams who execute. A decision made at the wrong altitude produces outcomes that the correct altitude must spend time and resource correcting.

The condition in which decisions are made at the wrong altitude — typically EA-level decisions made at SA level, or business decisions made in technical forums. Altitude collapse is the structural cause of most re-work in complex engagements. When the wrong audience makes the wrong decision, the consequences compound at every subsequent altitude.

The measurable cost of governance processes that produce compliance output without producing governance outcomes. Documents are produced. Reviews are conducted. Decisions are not made. The engagement moves through process stages without advancing toward a result. Governance drag is not the result of too much governance — it is the result of governance that is structured around process completion rather than decision production.

The discipline of declaring a design decision closed and defending that closure against re-litigation that is not driven by new information. A pattern is locked when the decision has been documented in an ADR, confirmed in a workshop, and accepted by named decision makers. It is unlocked only by new technical information, a changed regulatory obligation, or a confirmed change in business requirements — not by stakeholder preference or vendor commercial interest.

The condition in which one party to an engagement holds relevant information that another party does not. Information asymmetry is present in every engagement to some degree. In the Obfuscation Engagement it is deliberate. In the Negligent Void it is structural. In the Institutional Paralysis it is historical. Naming the asymmetry is the first step to resolving it.

An unanswered cell in the heat map. In the context of VAF·SA, a blank cell is not an absence of information — it is evidence. A blank cell produced by a vendor or stakeholder in a structured engagement, where the question has been asked and no response provided, is treated as a deliberate withholding until evidence demonstrates otherwise. Blank cells drive escalation. They are never closed by promise — only by documented confirmation.

The decision to end workshop-level resolution and escalate to a formal governance mechanism. The E-Stop is triggered when a conflict has been reframed twice without resolution, when the required decision-maker is not in the room, when new issues are surfacing faster than existing ones are being closed, or when a vendor has deferred the same commitment twice. The E-Stop is not a failure — it is the workshop doing its job by identifying the limit of what workshop-level engagement can resolve.

An engagement in which information critical to the solution is being deliberately withheld by a vendor, internal party, or stakeholder with a vested interest in preventing full disclosure. The defining characteristic is intent — the withholding is purposeful. Operating posture: forensic. Every response is a hypothesis until independently verified.

An engagement in which no architectural foundation exists. No documentation. No data classification. No vendor alignment. The engagement exists as a requirement but has never been given the architectural attention it requires. The defining characteristic is absence — not deliberate, but structural. Operating posture: constructive.

An engagement that has been attempted multiple times by different parties, with no ownership, no delivery, and a history being withheld or denied. Significant budget has been consumed. Nothing has been produced. The defining characteristic is accumulated inertia — each failed attempt adds political weight against the next one. Operating posture: immersive.

An engagement in which the solution is achievable and the capability exists — but the parties who need to collaborate have never been in the same room. The problem is human and structural, not technical. The defining characteristic is proximity — the answer is present in the organisation, distributed across people who have not been connected. Operating posture: facilitative.

A formal written statement that defines precisely what the solution architect can confirm the design satisfies and what remains unconfirmed pending an outstanding decision or unresolved risk. Issued when escalation has been exhausted and a decision to proceed has been made over the architect's documented objection. The boundary statement is not a resignation from the engagement. It is a precise assignment of accountability.

The Stakeholder Concern Register in its function as a mutual accountability instrument. When every stakeholder sees their concern recorded in their own words alongside a named commitment, the document becomes a contract — not legal, but social and professional. It removes the ability for any party to claim their concern was not raised or addressed, and it converts private political agendas into formal work items.

Working days from engagement start to the first signed Customer Impact Statement. The primary velocity measure. Measures how quickly the engagement produces its first decision-enabling output. Activity is not velocity. A signed artefact is. Target: 10–20 days standard, up to 30 for Institutional Paralysis engagements.

The percentage of heat map cells moved from red or amber to confirmed green per week. Measures decision production, not document production. A cell moves to green only when the relevant information is confirmed and independently verified. Target: 15–25% of open cells per active week.

Architecture Decision Records reaching Accepted status per engagement week. The direct measure of architectural progress. Each accepted ADR is a locked pattern, a confirmed decision, and a piece of design that will not be re-litigated. Target: 1–3 ADRs accepted per active week in Design and Deliver phases.