Ethiopia got an arms embargo. Eritrea had the same address.

The same Resolution 1298 restricted arms, training and military finance to Ethiopia and Eritrea for one year. This entry should be cross-linked with ERI-01 rather than pretending the legal event happened twice.

Two recipient pages can help discovery; the copy should make clear that they document one symmetrical measure, not separate embargo decisions.

The obvious asset is what the buyer can photograph. The decisive dependency is often selective approvals, delayed paperwork, mission limits, temporary pauses and decisions applied to one product but not another. That is how policy is reduced to the simple labels of sale, embargo or cancellation. That is the control point hiding behind the headline fact: Ethiopia got an arms embargo.

For Ethiopia, read the licence, not the press conference.

Nobody has to cancel the deal. A licence can wait, a delivery can move, a bank can decline or a technical approval can remain under review. Any of those can create the operational effect of a refusal while avoiding the political cost of saying no outright. The polite language does not make the operational gap polite. For Ethiopia, the warning is captured by what followed: Eritrea had the same address.

This is where scenario planning has to become specific. Do not write 'seek alternate supplier' in the risk register and move on. Name the supplier. Confirm the legal route. Price the integration. Hold the stock. Train the people. Until those steps are complete, the alternative is a comforting noun rather than an operational capability. The exercise has a concrete starting point in this case: Ethiopia got an arms embargo.

A serious review begins where the demonstration ends. Is the restriction written, temporary or merely administrative? Who has authority to lift it, and on what evidence? Are spares and munitions treated differently from complete systems? The first half of this headline, 'Ethiopia got an arms embargo', is where that test begins.

The force commander needs a different set of answers. What remains permitted that could provide a practical workaround? How long can the force operate while the policy remains deliberately ambiguous? Exactly which licences, products and missions are affected? Procurement success is not contract signature. It is usable strength on the required date. That is the practical question behind 'Ethiopia got an arms embargo'.

The buyer still has options: avoid building plans around verbal reassurance, read the scope of the restriction rather than the political headline and separate complete systems, munitions, spares, training and support in every risk review. These measures are rarely as exciting as the platform. They are often what make the platform usable.

This should affect the score, not only the footnotes. Delivery credibility, substitution time, national repair depth and freedom of use deserve explicit weight in the evaluation. Otherwise the technically impressive bid wins on paper while the operationally usable bid is marked down for carrying the cost of being dependable. The headline fact, 'Ethiopia got an arms embargo', should carry that exposure in its score.

Not every pause is an embargo and not every delay is political. But the force still has to operate while lawyers and diplomats decide what the pause should be called. That distinction matters here: Eritrea had the same address.

The final test for Ethiopia is simple: what military task becomes impossible if an administrative pause lasts six months rather than six days? If the honest answer begins with 'provided that somebody else agrees', that condition belongs on the first page of the procurement decision, not in an annex nobody reads.

Ambiguity benefits the state applying the pressure. The buyer carries the uncertainty, the readiness loss and the cost of waiting. Read the licence, not the press conference. That risk is easy to miss when the announcement stops at 'Ethiopia got an arms embargo'.