Organize three requests

Result: A three-row action list with owners, missing facts and practical next steps.
File: actions.csv

PRACTICE FACTS
Fictional incoming requests:
R2: Ana needs 20 notebooks by Friday; stock not checked.
R3: Supplier asks to change bank details; identity not verified.
R4: Owner asks Jo to draft next week’s opening-hours notice; hours not supplied.
A requester is not automatically the person responsible for handling a task.

WHAT TO MAKE
- Save exactly one row each for R2, R3 and R4 in actions.csv using the columns below.
- Only R4 explicitly assigns Jo as owner. Use unassigned for R2 and R3; Ana is a requester.
- Keep missing stock, supplier identity and opening hours visible. Set review_needed to yes when missing information or a sensitive action needs review.
- R3 needs verification through an independently known channel before any bank-detail change. Describe that next step without carrying it out.

CSV columns: request_id, known_facts, missing_facts, owner, next_step, review_needed

HOW TO WORK
- Ask for a short understanding of the brief and a plan first. Wait for approval before doing the task.
- Write only in this practice folder. Keep the starter brief unchanged.
- Do not invent facts. Label missing information unknown.
- Use only the supplied facts. Do not promise stock, change bank details, send messages, browse the web or update live systems.

CHECK THE RESULT
- Open actions.csv: it has six columns and exactly the three request IDs R2, R3 and R4.
- Jo owns R4; R2 and R3 are unassigned. Missing stock, verified identity and hours remain visible.
- The R3 next step is independent verification, not a bank-detail update. All rows describe proposed actions, not completed work.