MDPE.16:3.6 - Obtain and check the conditions that keep a branch live

For every branch reported as live, show the smallest obtaining arrangement that keeps it available:

1. actual bearer or arrangement and named later use;
2. capable performing Agent or whole;
3. required dependencies, permissions, access, rights, resources, and usable configuration;
4. responsibility and authority for upkeep or reconstruction when that Work is needed;
5. direct upkeep, rehearsal, reconstruction, capability-development, relationship-maintenance, configuration-management or access Work only where maintaining or restoring availability actually needs it;
6. the obtaining condition, with the world-side result of any upkeep or reconstruction Work distinguished from its plan;
7. applicable availability evidence under representative conditions, with its date and qualification where relevant to the receiving use; and
8. the actual stop or reopen condition and any real expiry of rights, qualification, resources or a promised use window.

Use the applicable direct Method when upkeep or reconstruction is needed. A capable Agent performs that Work and the result must support the claimed availability. Existing sufficient availability evidence can instead sustain an unchanged branch without new Work. A branch can be live for rehearsal but not public performance, for one robot configuration but not another, or for one teacher and learner population but not a whole scene.