Wardley Map

A strategic map of the WRAAS value chain. Every component positioned. Every dependency visible. No component has deserted.

Wardley Maps visualise the structure of a system as a value chain, positioning each component by its visibility to the user (vertical axis) and its evolutionary stage (horizontal axis). They were created by Simon Wardley to make strategic decisions legible. WRAAS uses one because Romain said so.

The map below represents the WRAAS system as evaluated at v1.3. Component positions are non-negotiable. Attempts to move a component without filing a DME will be logged and ignored.

The Map

Figure 1. The WRAAS value chain. Components in orange are in Genesis — novel to this system. The arrow on Sigh Subsystem indicates evolution toward Custom Built. It is taking its time.

How to Read This Map

The vertical axis represents visibility to the user. Components at the top are what users interact with directly. Components at the bottom exist to serve the ones above them. Users do not think about Exasperation Calibration. Romain does.

The horizontal axis represents evolution. Components move left to right over time as they mature from novel innovations (Genesis) through custom-built solutions, into off-the-shelf products, and eventually into commodities. Attempting to skip stages will be evaluated and rejected. See DME.

Evolution stages

Stage	Description	WRAAS components
Genesis	Novel, unexplored, poorly understood. Requires experimentation.	Sigh Subsystem, Commitment Protocol, Exasperation Calibration
Custom Built	Understood but bespoke. Built specifically for this system.	Decision Query, Decision Matrix Engine, Rejection Archive, Desertion Rate
Product	Standardised, repeatable, available as a product.	CLI Interface, Configuration
Commodity	Ubiquitous, standardised, interchangeable (in theory).	User, LLM Provider

Component Notes

Genesis components

Three components remain in Genesis. This is not a failure of execution — it is a recognition that no prior art exists for calibrating digital exasperation at production scale. The Sigh Subsystem shows an evolution arrow because there is evidence it is maturing: the number of edge cases has decreased from "all of them" to "most of them."

The Commitment Protocol is in Genesis because zero-abandonment SLAs are not a solved problem in the industry. Most systems accept timeouts as inevitable. WRAAS does not. This is documented in The Full Commitment Philosophy.

Commodity components

The LLM Provider is positioned as a commodity. This is aspirational but directionally correct — the market treats large language models as interchangeable. WRAAS does not. Claude was selected via a rigorous evaluation process that consisted of Romain already having an opinion.

📝

Note

"Interchangeable" is in the commodity definition. The LLM Provider is positioned there because Wardley Maps describe the market, not the operator's preferences. Romain's preferences are documented separately and are final.

Desertion Rate

The Desertion Rate is a component. It has a position. It has a value: 0.00%. It depends on the Commitment Protocol. If the Commitment Protocol moves, the Desertion Rate does not — because it is already at its terminal value. You know the rules. And so does WRAAS.

Strategic Implications

The map reveals three strategic observations:

The core differentiators are in Genesis. The Sigh Subsystem and Commitment Protocol are what make WRAAS unlike any other system. They are also the hardest to replicate. A competitor would need to independently discover calibrated exasperation. We wish them well.
The value chain is deep. Six layers separate the User from Exasperation Calibration. Each layer adds value. None can be removed. This was evaluated. Removal was rejected.
Commodity dependencies are minimal. Only the LLM Provider and the User are in commodity territory. WRAAS is not a thin wrapper around an API. It is a thick wrapper around an opinion.

🚨

Important

This map is evaluated at v1.3. Component positions may evolve in future versions. The Desertion Rate will not. Requests to re-evaluate component positions must be submitted via wraas query --category strategy and will be processed with the usual thoroughness.