Keep it currentUpdate
Keep your content up to date
It finds what you already have first
You get a straight answer: new unit, or an edit to one you already own. For an edit, a section-by-section change plan before anything moves, each row tied to the passage that justifies it and approved one at a time.
Keep our training in Juno up to date: Help me update our training. The update is either a NEW subject that nothing in Juno covers yet, or NEW information for a subject that already exists as a unit. Find out which before anything changes. ═══ ONE ROUND OF QUESTIONS ═══ Ask me in ONE message, then wait: 1. The source of the update: pasted text, a file, a link, release notes, a transcript, a unit in Juno. No real source, no change. Never invent. 2. Whether I already know the unit it belongs to. If not, offer to scan our library for it. Confirm the subject in one line. ═══ FIND WHAT EXISTS ═══ Search our library (search_lms_content) for the subject and open the closest matches (read_unit_text) to see what they actually cover; do not judge from titles. Then state plainly which case this is: - NEW: nothing meaningfully covers it. Ask which shape fits, a course, a journey, an interactive lesson, or a video, and hand off to that build with my source: the matching line on this sheet, with its own questions and gates. - EDIT: an existing unit covers it and needs the new material folded in. If the scan is ambiguous, show me the candidates and let me decide. ═══ FOR AN EDIT: THE CHANGE PLAN, THEN STOP ═══ Read the whole unit first (read_unit_content_blocks), both what learners see now and any unpublished draft, and warn me before touching a draft someone else has in flight. Then compare it with the source and show me a section-by-section plan: - ADD: what the source introduces. - CHANGE: what it contradicts or supersedes, old next to new. - REMOVE: what is now obsolete. Mark what the source states outright versus what you inferred. Every change cites the passage that justifies it; no passage, no change. Wait for my approval, row by row: approving one row approves one row. ═══ APPLY ═══ Apply only the approved rows. When you rewrite a section, carry every unchanged part verbatim and change only what the row says; do not regenerate the unit. For an interactive lesson, open the saved lesson as a draft, make the edit, preview it, and save it as a new version; every save keeps the previous version restorable. Re-validate, show me the result, and publish only on my final yes. Where learners already have the old version, say so and ask whether the update should reach them again. Rules throughout: source first; confirm new versus edit by reading, not by title; change plan before any change; approved rows only; nothing publishes without my yes; talk in product terms, not tool names.