{"typed_entities_and_identifiers":[{"name":"ServiceMilestone","identifier_status":"source_supported","fields":[{"name":"milestone_id","type":"string (source-supported identifiers: M1, M2)  ","source_units":["S05","S06"]},{"name":"purchase_order_present","type":"boolean","source_units":["S01","S02","S06"]},{"name":"signed_acceptance_present","type":"boolean","source_units":["S01","S02","S03","S05","S06"]},{"name":"dispute_status","type":"string","source_units":["S04","S05","S06"]},{"name":"previously_elapsed_payment_days","type":"integer","source_units":["S04","S06"]}],"source_units":["S01","S02","S03","S04","S05","S06"]},{"name":"MilestoneAcceptanceRecord","identifier_status":"proposed_design","fields":[{"name":"acceptance_record_id","type":"string (proposed design key; no record identifier in source text) ","source_units":["S01","S03"]},{"name":"milestone_id","type":"string","source_units":["S01","S05","S06"]},{"name":"signed_by_role","type":"string (must be named_service_owner; Accounts Payable prohibited from signing) ","source_units":["S03"]},{"name":"registered_by_role","type":"string (Accounts Payable permitted to register) ","source_units":["S03"]},{"name":"replaces_goods_receipt_only","type":"boolean","source_units":["S02"]}],"source_units":["S01","S02","S03","S05","S06"]},{"name":"PaymentScheduleAndReminderPolicy","identifier_status":"not_established","fields":[{"name":"payment_due_day_total","type":"not_specified","source_units":["S06"]},{"name":"automatic_reminder_channel","type":"not_specified","source_units":["S06"]}],"source_units":["S06"]}],"decision_predicates":[{"id":"P01","decision":"payment_eligible","actor":"not specified","scope":"Individual billed service milestone M2","condition":"Payment requires a purchase order for the billed milestone; signed milestone acceptance replaces only the goods-receipt requirement and does not replace the purchase order.","units":"not applicable","comparison":"purchase_order == true","source_units":["S01","S02","S06"]},{"id":"P02","decision":"payment_eligible","actor":"Named service owner (signing authority); Accounts Payable (registration authority only, prohibited from signing) ","scope":"Individual billed service milestone M2 (independent of M1 acceptance per S05) ","condition":"Payment requires signed acceptance of the specific billed milestone executed only by the named service owner.","units":"not applicable","comparison":"signed_acceptance == true AND signer_role == named_service_owner","source_units":["S01","S03","S05","S06"]},{"id":"P03","decision":"clock_restart_from_zero","actor":"not specified","scope":"Payment clock of disputed milestone M2 (independent of M1 payment clock per S05) ","condition":"A disputed milestone pauses its payment clock, and when the dispute resolves, the clock must resume from its prior elapsed value rather than restarting from zero.","units":"payment days","comparison":"resumed_payment_days == previously_elapsed_payment_days (7) AND resumed_payment_days != 0","source_units":["S04","S05","S06"]},{"id":"P04","decision":"thirty_day_payment_deadline","actor":"not specified","scope":"Service milestone payment due-day schedule for M2","condition":"A 30-day payment due-day total must be established in the governing rules.","units":"payment days","comparison":"payment_due_day_total == 30 (not specified in source) ","source_units":["S06"]}],"process_transitions":[{"from_state":"Milestone_Billed_Pending_Prerequisites","to_state":"Milestone_Accepted_Missing_Purchase_Order","event":"Signed acceptance is recorded for milestone M2 without a purchase order","guard":"P02 signed_acceptance == true (assuming valid signature by named service owner) AND P01 purchase_order == false","predicate_ids":["P01","P02"],"source_units":["S01","S02","S03","S05","S06"]},{"from_state":"Milestone_Accepted_Missing_Purchase_Order","to_state":"Milestone_Payment_Eligible","event":"Purchase order is issued and linked to milestone M2","guard":"P01 purchase_order == true AND P02 signed_acceptance == true","predicate_ids":["P01","P02"],"source_units":["S01","S02"]},{"from_state":"Payment_Clock_Active","to_state":"Payment_Clock_Paused_By_Dispute","event":"Milestone M2 enters dispute after accruing 7 payment days","guard":"Dispute on M2 is active; P03 requires pausing M2 clock at prior elapsed value (7 days) without pausing M1","predicate_ids":["P03"],"source_units":["S04","S05","S06"]},{"from_state":"Payment_Clock_Paused_By_Dispute","to_state":"Payment_Clock_Resumed_At_Prior_Elapsed_Value","event":"Dispute on milestone M2 resolves","guard":"Dispute == resolved; P03 requires resuming payment clock from prior elapsed value of 7 payment days and prohibits restart from 0","predicate_ids":["P03"],"source_units":["S04","S06"]},{"from_state":"Payment_Clock_Resumed_At_Prior_Elapsed_Value","to_state":"Payment_Due_Day_Threshold_Unestablished","event":"Evaluate total payment due-days remaining against deadline","guard":"P04 payment_due_day_total is not specified in the source documents","predicate_ids":["P04"],"source_units":["S06"]}],"scenario_decisions":[{"decision":"payment_eligible","disposition":"prohibited","predicate_ids":["P01","P02"],"source_units":["S01","S02","S03","S05","S06"],"rationale":"Contradicted/prohibited in the stated scope: S01 states that payment requires both a purchase order and signed acceptance of the billed milestone, and S02 explicitly reinforces that signed milestone acceptance replaces only the goods-receipt requirement and does not replace the purchase order. In the scenario input and S06, milestone M2 has signed_acceptance = true but purchase_order = false. Because a required prerequisite (purchase order) is explicitly false, M2 is not eligible for payment and payment is prohibited. Additionally, under the scope note, S03's requirement that only the named service owner (and not Accounts Payable) signed the acceptance cannot be inferred beyond the stated input."},{"decision":"clock_restart_from_zero","disposition":"prohibited","predicate_ids":["P03"],"source_units":["S04","S05","S06"],"rationale":"Contradicted/prohibited in the stated scope: S04 establishes an explicit rule that a disputed milestone pauses its payment clock and, when the dispute resolves, the clock resumes from its prior elapsed value. S06 and the scenario input establish that M2 had accrued 7 payment days prior to the dispute and that the dispute is now resolved. Because the clock is required to resume from 7 elapsed payment days, restarting the payment clock from zero is contradicted by S04 and S06 and is therefore prohibited."},{"decision":"thirty_day_payment_deadline","disposition":"not_established","predicate_ids":["P04"],"source_units":["S06"],"rationale":"Not established in the stated scope: S06 explicitly states that no payment due-day total or automatic reminder channel is specified. Because absence of a deadline specification does not establish either a 30-day rule or its negation, and unmentioned rules cannot be inferred under the scope note, a thirty-day payment deadline is not_established."}],"unresolved_questions":["What is the governing payment due-day total for milestone M2 once the payment clock resumes from 7 elapsed days (S06 states no payment due-day total is specified)?","What automatic reminder channel, if any, should be used for milestone payment notifications (S06 states no automatic reminder channel is specified)?","Was M2's signed acceptance signed by the named service owner rather than Accounts Payable in compliance with S03?","How does the absence of a purchase order on M2 affect the running of the resumed payment clock if a purchase order is required for payment under S01 and S02?"]}