Describe the bug

As an OSCAL tool developer, in order to understand when and how to annotate a control implementation with a property to indicate the control implementation requirement is fulfilled in whole or in part by control implementations from a leveraged authorization, I want clear documentation of the intended value for that prop.

Who is the bug affecting

OSCAL tool developers implementing SSPs leveraging a leveraged authorization, specifically @telosBA and their colleagues as reported on a feedback call.

What is affected by this bug

Documentation

How do we replicate this issue

1. Read the current documentation on the implemented-requirement/prop[@name='leveraged-authorization'].
2. Review the source code definition for the prop in this context of the SSP model.
3. Observe the kind of value (boolean? UUID?), recommended values, or constraints, are unclear.

Expected behavior (i.e. solution)

Documentation clearly explains what the intended value of this prop in this particular context of the SSP model.

Other comments

Thanks to @telosBA and company for the verbal report when providing feedback to us.