STE
Explain DNS to a new office employee. Use writing inspired by ASD-STE100: short sentences, one idea per sentence, active voice where possible, and one term for each concept. Define DNS, resolver and cache. Keep the distinction between finding an address and loading a website. Show a dense before paragraph and a clearer rewrite. Label this STE-inspired, not verified ASD-STE100 compliance. Use Cloudflare's DNS explainer as the factual source: https://www.cloudflare.com/learning/dns/what-is-dns/. Create a readable one-page PDF with the source link and a two-question comprehension check with answers. Render the PDF and inspect it for clipping.

DIAGRAM
Create an editable SVG diagram that teaches a new engineer a simplified retrieval-augmented generation (RAG) workflow. Show two lanes: document preparation (documents -> chunks -> searchable index) and answering (question -> retrieve passages -> enough evidence?). A yes branch gives the question and passages to a model, which drafts an answer with citations; a no branch asks for better evidence. Connect the index to retrieval. Treat the evidence check as our proposed design, not a guarantee built into every RAG system. Use at most ten nodes, labelled arrows and large text. State that citations still need checking. Include an accessible text description. Export the SVG and an HTML page that displays it. Ground retrieval in https://developers.openai.com/api/docs/guides/retrieval.

WEBPAGE
Build a self-contained HTML page that explains a support-review bottleneck. Use synthetic data. Start with 40 incoming tickets/hour, two AI workers at 20 tickets/hour each, one human reviewer, and three minutes of review per ticket. Let me vary arrivals, workers, reviewers and review time. Show agent capacity, review capacity, completed tickets/hour and backlog growth/hour, with the formulas visible. Assume a continuous, steady flow, no starting backlog, no breaks and no rework. Ask me to predict what happens when workers double before revealing the result. Include reset and two example scenarios. Make the page work offline, with keyboard-accessible controls and a mobile layout. Check the baseline, doubled workers and doubled reviewers against hand calculations. Save the complete HTML file.

VIDEO
Create a 35-45 second narrated mathematical explainer for team leads: why more AI workers may not speed up approvals. Use this synthetic example: 40 tickets arrive per hour; two workers can draft 20 each; one reviewer takes three minutes per ticket. Animate the flow, show the 20/hour review ceiling, then double workers without changing completed throughput. Finish by doubling reviewers, which raises the idealised completed rate to 40/hour. Label this a simplified steady-flow model with no breaks or rework. Use clear geometric animation and original visual design, English narration, captions, no music, and a readable 16:9 layout. Use an available local speech engine if no voice service is connected. Produce an MP4, an English VTT caption file and representative stills. Check every number and inspect the rendered clip.