An architecture group moves a technology from assess to adopt on its internal radar. In their scheme adopt means the paved road will support it and teams may use it without a waiver. The evidence is one production use - a six-week internal tool built by the two engineers who proposed it. What has the group committed to and what has it given up?

What is being tested

Whether you can read a ring label as a commitment made by somebody other than the proposer. On a radar that is only a published opinion, promotion costs nothing. On a radar wired to a paved road and a waiver process, promotion transfers cost from the team that wanted the technology to the group that has to support it.

The mechanism

Adopt, in this scheme, means three concrete obligations land on the platform group: the technology gets a supported build, an upgrade owner, and a place in the on-call rotation's mental model. None of those were created by the promotion vote; they were created by the promise the ring makes.

The evidence does not support any of them. A six-week internal tool exercises the happy path at low volume with its authors present. It says nothing about the questions that determine support cost: how the thing behaves on upgrade, what its failure modes look like at 02:00 to somebody who did not choose it, whether it has a patching story, and whether anyone besides the two proposers can operate it.

What is given up is reversibility. Demoting from adopt is a far harder act than declining to promote, because by then services depend on it. The asymmetry is the whole reason promotion needs evidence: promotion is cheap and reversal is not.

What evidence would have justified it

• Two or more teams who did not propose it, in production, past one upgrade. The second team is the signal - it tests whether the technology is adoptable without its champions in the room.
• One incident, handled by somebody else. A technology nobody outside the proposing team has debugged under pressure is unassessed on the dimension that costs the most.
• A named upgrade owner and a stated support window, so the obligation has a person attached before the ring changes.
• A stated exit: what the estate does if this is demoted in two years. Cheap to write now, impossible to write later.

A workable rule: assess needs curiosity, trial needs one team's production experience with a time box and a named owner, adopt needs two independent teams and one survived upgrade.

Why the other options fail

• "Nothing material because adopt is guidance." True of a radar that is purely advisory, and that is the common case - but the stem says adopt removes the waiver requirement and puts the technology on the paved road. Once a ring is wired to a mechanism, it is a decision, not advice. People make this mistake by reading the artefact's genre rather than its wiring.
• "A faster path for the proposing team." This is the benefit, correctly identified, and it is what the proposers are optimising for. It is not what the organisation gave up, and the question asks for both sides. A trade-off answer that names only the gain is the most common weak answer in architecture reviews.
• "An exception-register entry." This confuses the two instruments. An exception register records a deliberate, time-limited departure from a standard - it is what you use when a team needs something the radar holds. Promotion to adopt is the opposite move: it makes the thing standard for everyone, with no expiry and no owner-of-record.

When this is the wrong answer

When the radar is genuinely only a publication - no paved road behind it, no waiver gate, no platform group committing anything. Then promotion on thin evidence costs a little credibility and nothing else, and demanding two independent production users before you will even write a technology down turns the radar into a lagging record of what the estate already runs. That artefact has its own value, but it is an inventory, not a radar.