Fictional AI lifestyle ad — independent portfolio concept.
A 23.5-second vertical concept for an invented bottle and an original fictional AI character, with four lifestyle scenes, English narration and post-production. Grok-generated source clips, vidIQ voiceover and FFmpeg editing; the 1080×1920 presentation is resampled from lower-resolution source footage.
This is self-directed concept work, not a paid client campaign, authentic customer endorsement or proof of advertising performance. Six hook/format exports are variations of this same campaign.
Product hero companion: https://drive.google.com/file/d/1GNHLX_OKbwL94dZQpj9lJF8-3EKEpEFR/view
(https://drive.google.com/file/d/1GNHLX_OKbwL94dZQpj9lJF8-3EKEpEFR/view)Lifestyle master: https://drive.google.com/file/d/1JD39kiyyfzcak_q5XPBEDGSZ95-wDuaM/view
0
3
Captioned creator video with Ozzy
0
3
Fictional workflow QA demo — five failure cases
Invented input, created with AI assistance and reviewed before publication. This is not paid client work. The expected outcomes below are proposed acceptance criteria, not executed test results.
The six-step example: receive a request → validate fields → classify it → log it → email an acknowledgement → notify the owner. In this deliberately flawed version, invalid input has no route, the log continues after failure, acknowledgement is recorded before sending, and IDs come from timestamps.
Five checks:
Missing email: retain a NEEDS_REVIEW record and alert the owner; send no acknowledgement.
Logging failure: stop before emailing a reference that was never stored.
Uncertain email send: mark UNCERTAIN and reconcile delivery status. Never blindly retry after a timeout.
Repeated event: use a stable provider event ID or explicit idempotency key. A matching email/text hash only flags a possible duplicate; it must not silently merge valid new requests.
Unknown category: route to owner review instead of silently guessing support/normal.
The correction: explicit request and acknowledgement states, success-only transitions, and one review path with reason codes. Agree retention and collision handling before implementation.
Static review only: no n8n execution, production-system testing or measured delivery-time claim.
My small offline review service covers one redacted export, up to 10 steps, five failure-case instructions and a findings report. Start with invented or redacted data and an intended outcome:
https://contra.com/s/E2XARkom-offline-workflow-review-five-failure-cases
0
18
Synthetic CSV QA demonstration - not paid client work. This 10-record example preserves the original and identifiers, checks agreed rules and logs one approved title-whitespace change. Input and output both contain 10 records. The candidate is ready for human QA, not guaranteed import-ready data. URL checks cover syntax only. For a scoped review, send headers and a few invented or redacted rows first. Rules, record cap, timing and quote are agreed before accepting work. No live-store access or confidential files in messages.
0
13