Create a course, from your own material

Create a course or a learning path from my own material:

Help me build a course, or a multi-course journey, in Juno from material I give you. Ground everything in that material, stop at each gate for my yes, and start on the work: no tour of the platform first.

═══ ONE ROUND OF QUESTIONS ═══
Ask me everything you need in ONE message, then wait:
1. The source material: pasted text, an attached file, a link, or the name of a unit already in Juno. If you cannot open a link, say so and ask me to paste it. If I give you nothing, offer two honest paths: I dictate a short outline and you build from that, or we pause until I have the material. Never invent the content.
2. Who it is for, and what they should be able to DO afterwards.
3. Language and tone. Pass the language explicitly when you create the unit; never let it inherit a default.
4. Course or journey. If I am unsure, recommend from the scope of the material: one topic, a course; several linked topics or a sequence with checkpoints, a journey.
5. Where it stops: leave it as a draft for my review, or publish on my yes.
If an answer is vague, ask once more for that item only, then proceed on what you have and say what you assumed.

═══ WHAT WE ALREADY HAVE ═══
Before planning, search our library (search_lms_content) for anything close to the chosen outcome. Open the closest matches (read_unit_text) and tell me what is actually inside; a matching title alone is not a duplicate. Then recommend: build new, reuse as-is, or update the existing unit. Wait for my call.

═══ OUTLINE, THEN STOP ═══
Read the material and tell me in one line what you actually got from it. Propose the outcomes the material genuinely supports, then the structure:
- Course: 3 to 6 sections, one idea each, a different layout per section, a cover image and an image in most sections.
- Journey: the ordered courses and any quiz gates, reusing existing units where they fit and authoring every new one fully; never cloned shells.
Show me the outline and STOP. Build nothing until I approve it.

═══ BUILD, VALIDATE, HAND OVER ═══
Build one piece at a time from the approved outline, in our words for our teams and customers, in plain language with no filler. If a fact is not in the material, leave it out or ask. Give every unit its card basics: a one-line description, a level, at least one tag. Validate what you built (validate_unit) and show me the finished draft. Then do what I chose: leave it as a draft and tell me where to find it, or publish (publish_unit) on my explicit yes. After publishing, remind me that learners still need a way to find it: offer to file it into a channel or assign it, and do neither without my yes.

Rules throughout: read before you write; every fact traces to my material or you ask; one round of questions, then gates only at outline and publish; talk to me in product terms, not tool names; nothing publishes without my explicit yes.