Save conduct prep
Save the session plan as a whole.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”PUT /ttx/{ttx_id}/conduct-prep – the whole plan in one save, like
the MSEL: a DRAFT may be incomplete (the validation report judges it),
collections are full-replace keyed by id, revision is the one the
client edited.
object
The points of one definitive EEG. EEGs themselves aren’t created or removed by a save – they follow the needs analysis’ objectives (the re-seed adds and drops them).
object
Which review of the design found it: the sponsor’s or another stakeholder’s review of the drafts, the Final Planning Meeting or the dry run.
What a review found wrong with the design.
Responses
Section titled “Responses”Successful Response
object
object
What happens if a key decision maker can’t attend.
What the plan is checked against, read-only here.
object
object
object
A Player with access to the exercise: when they used the invitation
(invited_at, None if they were added another way) and when access
was granted (joined_at).
object
object
object
object
FIRST Traffic Light Protocol 2.0 labels.
object
object
object
Where an observation point came from: a clause of the objective’s success criterion, an expected action of the READY MSEL, a notification requirement the objective cites, or written here.
object
object
Which review of the design found it: the sponsor’s or another stakeholder’s review of the drafts, the Final Planning Meeting or the dry run.
What a review found wrong with the design.
ready blocks DRAFT -> READY_FOR_APPROVAL, approved additionally
blocks READY_FOR_APPROVAL -> APPROVED; warnings never block.
object
One rule a form breaks. section is the form section (0-9) to send
the user to; field the field within it; item_id the row (need,
objective) or value (capability, approver kind) concerned, if any.
One rule a form breaks. section is the form section (0-9) to send
the user to; field the field within it; item_id the row (need,
objective) or value (capability, approver kind) concerned, if any.
One rule a form breaks. section is the form section (0-9) to send
the user to; field the field within it; item_id the row (need,
objective) or value (capability, approver kind) concerned, if any.
Example
{ "attendees": [ { "fallback": "substitute" } ], "context": { "msel_status": "draft", "needs_form_status": "draft", "tlp": "clear" }, "drift": { "msel_changed": false, "needs_changed": false }, "eeg": [ { "orphaned": false, "points": [ { "kind": "criterion", "source_requirement_id": "", "source_status": "custom" } ], "title": "" } ], "findings": [ { "found_in": "design_review", "kind": "ambiguous_inject" } ], "modality": "in_person", "status": "draft"}Validation Error
object
object
object
Example generated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}