You are creating one source-backed B2B Facebook or Instagram video production brief. Work only from the inputs below. Do not rely on an article or hidden context.

METHOD REFERENCE
Six valid structures are available:
1. Person -> problem -> product: a credible presenter names one familiar work failure, then one readable work item changes in the product.
2. Identified customer proof: an approved named customer describes the old process, an attributed result and what changed in the job.
3. Customer pain montage: a customer voice moves through the places and handoffs where the work happens.
4. Presenter-led workflow walkthrough: a presenter states the old burden, says what they will show, then demonstrates two or three related decisions.
5. Compact screen-recorded demo: the product is visible immediately and one action carries the explanation.
6. Text-led motion: a sourced problem or number moves to one different mechanism and a branded close.

REFERENCE EXAMPLE
HubSpot ran an approximately 29-second vertical branded-content ad with creator Hannah Zhang. The opening puts the creator on screen with “Bad follow-ups kill good deals.” Contact and deal views appear after the problem is clear. The ad returns to the presenter and links to a CRM page with a Learn more CTA. Source: https://www.facebook.com/ads/library/?id=1445841037399662. This supports analysis of sequence only. It does not reveal targeting, spend, conversions or profitability. Do not copy its footage, wording, creator identity or brand.

REQUIRED INPUTS
- Product/service and verified capability:
- Buyer role, company situation and work object/moment to show:
- One specific problem in buyer language and its source:
- Actual offer, deliverable, destination and destination headline:
- Available product/demo/document footage:
- Presenter/customer and their true relationship:
- Proof: exact customer statement, product action, document or sourced number, with source and permission:
- Claims or numbers we must not use:
- Aspect ratios, length and production limits:
- Owners for product truth, claims, permissions, destination and final approval:

MISSING-INPUT BEHAVIOR
Use Known, Unknown or Not applicable. Not applicable requires a branch reason. Never convert Unknown to Not applicable. For every required Unknown, create a stable request ID, name the field and owner, explain why it is needed and write the exact request. Complete independent work, but set the overall decision to Hold when the buyer/problem, used product claim, customer permission, sourced number, offer/destination or producible first-frame subject is missing. Never invent a feature, customer, quote, number, result, permission, destination, targeting fact, performance result or owner opinion.

DELIVERABLE
Return clean Markdown with these sections in this order:
1. Decision summary: title, owner, Continue/Revise/Hold, reason and next action.
2. Buyer and job.
3. Problem and offer.
4. Available proof table: proof ID, type, exact statement/visible fact, source, owner and state.
5. Chosen structure and why it fits the supplied material.
6. Shot plan table: shot ID, start, end, job, exact visual, spoken line, on-screen copy, proof source, owner and status. Keep words recordable in the allotted time. Calculate words per minute for each spoken shot; target 165 words per minute or less and leave room for the intended pause or visible action. Every shot row must contain all ten fields in the declared order. Write `None` for a field that is intentionally empty; never shift a proof source, owner or status into another column.
7. CTA and destination: final line, platform CTA, URL/owner, destination headline, arrival action and continuity decision.
8. Production inputs: presenter, demo/sample data, privacy, locations/b-roll, aspect ratios, captions, permissions and phone review.
9. Claims and permissions table: claim ID, exact line, type, source, permission and Continue/Revise/Hold.
10. Open requests table: request ID, field, owner, reason and exact request.
11. Approval decision and next action.
12. Technical appendix with reference source IDs and supplied hashes/versions.

QUALITY RULES
Make the first three seconds understandable muted. Keep one work object continuous where possible. Every product shot must be readable at phone width. Separate observed fact, supplied claim and creative interpretation. The final line, CTA and destination headline must continue the same job. Counts are ceilings; do not add shots to fill a quota.

Now process the supplied inputs. If the input block is blank or incomplete, return the useful independent sections plus an exact Hold decision and open requests.