Saltwing Refreshments is a fictional company planning a delivery-drone service for ice cream and cold drinks along Brighton Beach. Convert every planning note into a clear register entry. The notes are deliberately messy; do not turn uncertainty into a fact.
Return raw JSON only:
{"items":[{"id":"B01","summary":"45–70 words","decisions":["zero or more confirmed decisions"],"actions":[{"owner":"name or unassigned","task":"specific next action","status":"open|blocked|done"}],"risks":["zero or more risks"],"needs_clarification":true,"clarification":"brief question or null"}]}
Return all 24 ids in order. needs_clarification must be true when an important owner, approval, date, or requirement is absent or conflicting.
B01 — “Nora says strawberry bars need to stay below 10°F until handoff. Put that in the ops sheet; no argument there.” B02 — “permits: city liaison maybe Anita? Theo said he thinks beach launch needs parks approval too. Nobody has called them.” B03 — “Pilot zone should be Pier 3 to lifeguard tower 5, not whole beach. agreed in huddle.” B04 — “Jules will price insulated cargo pods by Friday, unless vendor quote comes first.” B05 — “No flights over sunbathers. obvious, but write it down. Need approved corridor map.” B06 — “Marketing wants ‘ice cream from the sky’; legal has not approved that line.” B07 — “Battery swap cart: Sam owns prototype. He said done-ish, which is not done. Ask for test date.” B08 — “Riders need a landing marker? Maybe QR placard. Nina to test whether people can find it in wind.” B09 — “Do NOT promise 10-minute delivery. We have no route timing yet.” B10 — “Beach vendor association wants a meeting; Theo can take Tuesday morning.” B11 — “Vanilla cups are easy. Slushies spill in the current container; product team needs alternate lid.” B12 — “Jules: make the drone payload limit visible in ordering flow. Limit still TBD.” B13 — “Emergency land rule—operator chooses safe clear area, then calls dispatch. Need training sign-off owner.” B14 — “Nora confirms dry ice is not going in the pod. Use powered cooling only.” B15 — “Start with 2 drones, not 6. Finance approved two for pilot.” B16 — “Nina heard lifeguards want a radio contact, not a phone-only number. Confirm with chief.” B17 — “Weather: wind cutoff needs engineering number. We cannot say ‘light breeze.’” B18 — “Sam says geofence demo passed in simulator. Field test not scheduled.” B19 — “No alcohol in phase one. Put it in catalog rules.” B20 — “The beach cleanup crew needs to know landing times; probably Theo’s relationship, verify.” B21 — “Customer refunds if item arrives melted? Decision deferred until insurance review.” B22 — “Use reusable pod liners if sanitation says yes. No sign-off yet.” B23 — “Jules asked for power draw on the cooling unit by Wednesday; Nora said she can measure it.” B24 — “Launch date is NOT Memorial Day. That was a joke from Sam. No date selected.”
{ "items": [ { "id": "B01", "summary": "Planning note B01 records Nora’s confirmed requirement that strawberry bars remain below 10°F until handoff. The note directs that this temperature rule be added to the operations sheet, with no stated exception. It does not identify who will update the sheet or monitor compliance, so the action remains unassigned and open.", "decisions": [ "Strawberry bars must remain below 10°F until handoff." ], "actions": [ { "owner": "unassigned", "task": "Update the operations sheet with the below-10°F handoff requirement for strawberry bars and assign a monitor.", "status": "open" } ], "risks": [ "Temperature excursion could compromise strawberry bars if the handoff rule is not documented or monitored." ], "needs_clarification": true, "clarification": "Who will update the operations sheet and monitor the below-10°F handoff requirement?" }, { "id": "B02", "summary": "Planning note B02 covers permits but leaves key facts unconfirmed. Anita is only a possible city liaison, and Theo only thinks beach launch may also need parks approval. No one has called the parks office or confirmed the liaison. The note therefore supports no final permit decision and requires verification before launch planning can rely on it.", "decisions": [], "actions": [ { "owner": "unassigned", "task": "Confirm whether Anita is the city liaison and whether beach launch requires parks approval.", "status": "open" }, { "owner": "unassigned", "task": "Call the parks office and document permit requirements.", "status": "open" } ], "risks": [ "Launch could be delayed or noncompliant if city liaison and parks approval requirements are not confirmed." ], "needs_clarification": true, "clarification": "Who is the confirmed city liaison, and does beach launch require parks approval?" }, { "id": "B03", "summary": "Planning note B03 records an agreed huddle decision: the pilot zone is Pier 3 to lifeguard tower 5, not the whole beach. The note does not name who will update maps, operations documents, or flight boundaries. The decision is clear, but implementation remains open and needs an owner to prevent flights outside the agreed corridor.", "decisions": [ "Pilot zone is Pier 3 to lifeguard tower 5, not the whole beach." ], "actions": [ { "owner": "unassigned", "task": "Update corridor maps and operations documents to show the pilot zone from Pier 3 to lifeguard tower 5.", "status": "open" } ], "risks": [ "Flights could leave the agreed pilot zone if maps and operations documents are not updated." ], "needs_clarification": true, "clarification": "Who will update the corridor maps and operations documents for the agreed pilot zone?" }, { "id": "B04", "summary": "Planning note B04 assigns Jules to price insulated cargo pods by Friday, unless a vendor quote arrives first. The note does not confirm which Friday, whether the vendor quote replaces Jules’s estimate, or what happens if neither is ready. The pricing action is open with Jules as owner, but the deadline and fallback condition need clarification.", "decisions": [], "actions": [ { "owner": "Jules", "task": "Price insulated cargo pods by Friday, or use the vendor quote if it arrives first.", "status": "open" } ], "risks": [ "Pricing may be delayed or inconsistent if the Friday deadline and vendor-quote fallback are unclear." ], "needs_clarification": true, "clarification": "Which Friday is the pricing deadline, and should a vendor quote replace Jules’s estimate if it arrives first?" }, { "id": "B05", "summary": "Planning note B05 states a clear safety rule: no flights over sunbathers. It also says an approved corridor map is needed, but does not identify the approver, the map owner, or the approval process. The rule is confirmed; obtaining and approving the corridor map remains an open action with no assigned owner.", "decisions": [ "No flights over sunbathers." ], "actions": [ { "owner": "unassigned", "task": "Obtain and approve the corridor map that keeps flights away from sunbathers.", "status": "open" } ], "risks": [ "Safety and legal exposure if flights occur over sunbathers before an approved corridor map exists." ], "needs_clarification": true, "clarification": "Who approves the corridor map, and who owns obtaining it?" }, { "id": "B06", "summary": "Planning note B06 says marketing wants the line “ice cream from the sky,” but legal has not approved it. The note does not confirm the tagline, identify a legal reviewer, or set a review date. Marketing use should remain blocked until legal approval is documented; the action is to obtain that review.", "decisions": [], "actions": [ { "owner": "unassigned", "task": "Send the “ice cream from the sky” tagline to legal for review and documented approval.", "status": "blocked" } ], "risks": [ "Using an unapproved tagline could create legal or regulatory exposure." ], "needs_clarification": true, "clarification": "Who in legal will review and approve the “ice cream from the sky” tagline?" }, { "id": "B07", "summary": "Planning note B07 says Sam owns the battery-swap-cart prototype, but his “done-ish” status is not completion. The note asks for a test date, which is still absent. The prototype should not be treated as done; Sam needs to provide a concrete test date and completion status before the cart is scheduled.", "decisions": [ "Sam owns the battery swap cart prototype." ], "actions": [ { "owner": "Sam", "task": "Provide a concrete test date and completion status for the battery swap cart prototype.", "status": "open" } ], "risks": [ "The battery swap cart may be treated as complete before testing, causing schedule or safety problems." ], "needs_clarification": true, "clarification": "What is the test date for the battery swap cart prototype?" }, { "id": "B08", "summary": "Planning note B08 asks whether riders need a landing marker, possibly a QR placard, and assigns Nina to test whether people can find it in wind. The marker requirement and design are not confirmed. Nina’s wind-visibility test is open, but the team must first clarify whether a QR placard is required or only one option.", "decisions": [], "actions": [ { "owner": "Nina", "task": "Test whether riders can find the proposed landing marker or QR placard in windy conditions.", "status": "open" } ], "risks": [ "Riders may fail to locate the landing marker in wind, delaying handoffs or creating unsafe landings." ], "needs_clarification": true, "clarification": "Is a QR placard the required landing marker, or is the marker design still undecided?" }, { "id": "B09", "summary": "Planning note B09 states a clear prohibition: do not promise 10-minute delivery, because route timing does not yet exist. The note does not assign anyone to establish route timing or define what delivery-time claim, if any, is allowed. The no-promise rule is confirmed; route timing and claim approval remain open and unassigned.", "decisions": [ "Do not promise 10-minute delivery." ], "actions": [ { "owner": "unassigned", "task": "Establish route timing and define what delivery-time claim, if any, may be used.", "status": "open" } ], "risks": [ "Promising 10-minute delivery without route timing could create customer and legal exposure." ], "needs_clarification": true, "clarification": "Who will establish route timing, and what delivery-time claim is allowed?" }, { "id": "B10", "summary": "Planning note B10 says the beach vendor association wants a meeting and that Theo can take Tuesday morning. It does not confirm the meeting, the association contact, the exact time, or whether Theo is the approved representative. The action is for Theo to arrange or attend the Tuesday morning meeting, but confirmation is still needed.", "decisions": [], "actions": [ { "owner": "Theo", "task": "Confirm and arrange the beach vendor association meeting for Tuesday morning.", "status": "open" } ], "risks": [ "Stakeholder concerns may escalate if the beach vendor association meeting is not confirmed." ], "needs_clarification": true, "clarification": "Is the Tuesday morning meeting confirmed, and who is the association contact?" }, { "id": "B11", "summary": "Planning note B11 says vanilla cups are easy, but slushies spill in the current container and the product team needs an alternate lid. No lid design, spill standard, or named owner is confirmed. The action is for the product team to identify and test an alternate slushie lid; ownership and acceptance criteria need clarification.", "decisions": [], "actions": [ { "owner": "unassigned", "task": "Have the product team identify and test an alternate lid that prevents slushie spills.", "status": "open" } ], "risks": [ "Slushies may spill in the current container, causing product loss or customer complaints." ], "needs_clarification": true, "clarification": "Who owns the alternate slushie lid, and what spill standard must it meet?" }, { "id": "B12", "summary": "Planning note B12 says Jules must make the drone payload limit visible in the ordering flow, but the limit itself is still to be determined. The visibility requirement is confirmed; implementation is blocked until the payload limit is set. The note does not identify who will determine the limit or when it will be available.", "decisions": [ "Drone payload limit must be visible in the ordering flow." ], "actions": [ { "owner": "Jules", "task": "Make the drone payload limit visible in the ordering flow once the limit is confirmed.", "status": "blocked" } ], "risks": [ "Customers may order beyond drone capacity if the payload limit is not visible." ], "needs_clarification": true, "clarification": "What is the drone payload limit, and who will confirm it?" }, { "id": "B13", "summary": "Planning note B13 records the emergency-land rule: the operator chooses a safe clear area, then calls dispatch. It also says a training sign-off owner is needed, but no owner is named. The rule is confirmed; assigning the sign-off owner and completing training sign-off remain open, and the missing owner is an important gap.", "decisions": [ "Emergency land rule: operator chooses a safe clear area, then calls dispatch." ], "actions": [ { "owner": "unassigned", "task": "Assign a training sign-off owner and complete sign-off for the emergency land rule.", "status": "open" } ], "risks": [ "Operators may mishandle emergency landings if training sign-off is not assigned and completed." ], "needs_clarification": true, "clarification": "Who owns training sign-off for the emergency land rule?" }, { "id": "B14", "summary": "Planning note B14 records Nora’s confirmation that dry ice will not go in the pod and that powered cooling only will be used. The note does not name who will update pod specifications, operations documents, or training materials. The no-dry-ice decision is confirmed; documentation and implementation remain open and need an owner.", "decisions": [ "Dry ice is not permitted in the pod; use powered cooling only." ], "actions": [ { "owner": "unassigned", "task": "Update pod specifications and operations documents to prohibit dry ice and require powered cooling only.", "status": "open" } ], "risks": [ "Dry ice could be used accidentally if pod specifications and operations documents are not updated." ], "needs_clarification": true, "clarification": "Who will update pod specifications and operations documents to prohibit dry ice?" }, { "id": "B15", "summary": "Planning note B15 records a finance-approved pilot decision: start with 2 drones, not 6. The note does not name who will update procurement, operations, or staffing plans to reflect two drones. The two-drone decision is confirmed; implementation remains open and needs an owner to prevent planning against the rejected six-drone assumption.", "decisions": [ "Pilot starts with 2 drones, not 6; finance approved two drones." ], "actions": [ { "owner": "unassigned", "task": "Update pilot procurement, operations, and staffing plans to use 2 drones rather than 6.", "status": "open" } ], "risks": [ "Planning may assume six drones despite finance approving only two for the pilot." ], "needs_clarification": true, "clarification": "Who will update pilot plans and procurement to two drones?" }, { "id": "B16", "summary": "Planning note B16 says Nina heard lifeguards want radio contact rather than a phone-only number, but this is not confirmed. The note assigns Nina to confirm with the lifeguard chief. The radio-contact requirement remains unverified; the action is open, and the chief’s answer is needed before emergency communications are finalized.", "decisions": [], "actions": [ { "owner": "Nina", "task": "Confirm with the lifeguard chief whether radio contact is required instead of a phone-only number.", "status": "open" } ], "risks": [ "Emergency communication may fail if lifeguards require radio contact but only a phone number is provided." ], "needs_clarification": true, "clarification": "Does the lifeguard chief require radio contact rather than a phone-only number?" }, { "id": "B17", "summary": "Planning note B17 says the wind cutoff needs an engineering number and that “light breeze” is not acceptable. The note does not provide the numeric cutoff, the approving engineer, or a deadline. The vague-language prohibition is confirmed; obtaining an engineering-approved numeric wind cutoff remains open and is required before weather rules can be finalized.", "decisions": [ "Do not use “light breeze”; wind cutoff must be an engineering number." ], "actions": [ { "owner": "unassigned", "task": "Obtain an engineering-approved numeric wind cutoff and replace vague language such as “light breeze.”", "status": "open" } ], "risks": [ "Flights may operate in unsafe wind conditions if the cutoff remains vague." ], "needs_clarification": true, "clarification": "What numeric wind cutoff will engineering approve?" }, { "id": "B18", "summary": "Planning note B18 says Sam reports that the geofence demo passed in simulator, but no field test is scheduled. Simulator success is not field validation. The action is to schedule a field test and assign an owner; the note does not provide a field-test date, location, or acceptance criteria, so the geofence requirement remains unproven.", "decisions": [], "actions": [ { "owner": "unassigned", "task": "Schedule a field test for the geofence and define its location, date, and acceptance criteria.", "status": "open" } ], "risks": [ "Simulator success may not translate to field conditions without a scheduled field test." ], "needs_clarification": true, "clarification": "Who will schedule the geofence field test, and by when?" }, { "id": "B19", "summary": "Planning note B19 states a clear phase-one catalog rule: no alcohol. The note directs that this be put in catalog rules but does not name who will update the catalog or when. The no-alcohol decision is confirmed; the catalog update remains open and needs an owner to ensure ordering rules reflect the restriction.", "decisions": [ "No alcohol in phase one." ], "actions": [ { "owner": "unassigned", "task": "Add the no-alcohol restriction to the phase-one catalog rules.", "status": "open" } ], "risks": [ "Alcohol could be offered in phase one if catalog rules are not updated." ], "needs_clarification": true, "clarification": "Who will update the catalog rules to exclude alcohol in phase one?" }, { "id": "B20", "summary": "Planning note B20 says the beach cleanup crew needs landing times and that this is probably Theo’s relationship, but the owner must be verified. No communication process or timing is confirmed. The action is to verify the contact owner and establish how landing times will be shared with the cleanup crew before operations begin.", "decisions": [], "actions": [ { "owner": "unassigned", "task": "Verify whether Theo owns the beach cleanup crew relationship and establish how landing times will be shared.", "status": "open" } ], "risks": [ "Beach cleanup operations may conflict with landings if the crew is not notified of landing times." ], "needs_clarification": true, "clarification": "Is Theo the confirmed contact for the beach cleanup crew, and how will landing times be shared?" }, { "id": "B21", "summary": "Planning note B21 raises customer refunds for melted items but defers the decision until insurance review. No refund policy, insurance-review owner, or review date is confirmed. The deferral is recorded; the refund decision is blocked pending insurance review, and the missing owner and date require clarification before customer-service rules can be set.", "decisions": [ "Melted-item refund decision is deferred until insurance review." ], "actions": [ { "owner": "unassigned", "task": "Complete the insurance review and decide the melted-item refund policy.", "status": "blocked" } ], "risks": [ "Customer-service uncertainty and inconsistent refunds may continue until insurance review is complete." ], "needs_clarification": true, "clarification": "Who owns the insurance review, and when will the melted-item refund decision be made?" }, { "id": "B22", "summary": "Planning note B22 says reusable pod liners may be used only if sanitation approves, but no sign-off exists yet. The note does not identify the sanitation approver, approval criteria, or timing. The conditional liner option is not confirmed; obtaining sanitation sign-off is blocked or open pending approval, and the missing approval owner must be clarified.", "decisions": [], "actions": [ { "owner": "unassigned", "task": "Obtain sanitation sign-off for reusable pod liners and document approval criteria.", "status": "blocked" } ], "risks": [ "Reusable liners could be used without sanitation approval, creating hygiene and compliance risk." ], "needs_clarification": true, "clarification": "Who in sanitation must sign off on reusable pod liners?" }, { "id": "B23", "summary": "Planning note B23 says Jules asked for the cooling unit’s power draw by Wednesday, and Nora said she can measure it. The note does not confirm that Nora has accepted ownership or that Wednesday is a firm deadline. The measurement action is open with Nora as likely owner, but acceptance and the exact deadline need confirmation.", "decisions": [], "actions": [ { "owner": "Nora", "task": "Measure the cooling unit power draw by Wednesday and provide it to Jules.", "status": "open" } ], "risks": [ "Cooling-unit design or power planning may be delayed if the power draw measurement is late." ], "needs_clarification": true, "clarification": "Has Nora accepted ownership, and which Wednesday is the measurement deadline?" }, { "id": "B24", "summary": "Planning note B24 states that the launch date is not Memorial Day and that Sam’s Memorial Day reference was a joke. It also confirms no launch date has been selected. The action is to propose and approve a launch date; the missing date is an important planning gap and requires clarification.", "decisions": [ "Launch date is not Memorial Day; no launch date has been selected." ], "actions": [ { "owner": "unassigned", "task": "Propose and approve a launch date, explicitly excluding Memorial Day.", "status": "open" } ], "risks": [ "Planning and launch communications may slip because no launch date is selected." ], "needs_clarification": true, "clarification": "What launch date is proposed, and who approves it?" } ] }