# J4 · Adopt a shared component and roll back

Scenario specification, revision 1. Two independent teams need a supported interface. One tries the next release while the other stays on its existing pin.

[I17 · Find the same answer as a designer, engineer or agent](../../intents/guidance/I17-find-design-guidance/intent.md) · [I15 · Use the same web component in each web host](../../intents/renderers/I15-use-the-web-adapter/intent.md) · [I16 · Operate the same task through native controls](../../intents/renderers/I16-use-native-controls/intent.md) · [I18 · Judge a component while it is moving](../../intents/quality/I18-review-interaction-quality/intent.md) · [I19 · Adopt and roll back the shared system per project](../../intents/adoption/I19-adopt-a-release/intent.md)

| Step | Required observation | Reject this substitute |
| --- | --- | --- |
| Resolve the same task from the guide and an agent entry. | Both identify the same contract, revision and target support. | The authoring tool silently reads latest. |
| Render a real candidate on its declared host and rehearse interaction. | The observed keys, focus, motion and action count belong to the candidate renderer. | A web recording is used as a native result. |
| Upgrade one recipient and rehearse reverting it. | Both recipients resolve the expected contract and the earlier pin can reproduce its screen. | The upgraded product silently changes its sibling. |

Each recipient owns its adoption decision and production settings. A missing platform capability is visible even when the design for the task exists.

[Design portfolio](../../README.md)
