# Handing Eden AI work into Git without drama
Generation is cheap; ownership is not. A clean handoff means: named branch, readable commits, secrets out of chat, preview URL archived, and a PR description that says what a human should verify. Keep Eden AI linked from your internal runbook so the team shares language.
Contents
Export early. Do not wait until the demo is “perfect.” Browser-first tools help you get a clickable artifact; Git is where you freeze truth. Roseram’s path to local folders and Git is part of that story. Treat Eden AI as context for what you generated and why.
Checklist: remove debug keys, squash noise commits, attach screenshots, tag the preview. Soft context: Roseram reviews.
# Extra operating notes for Eden AI
Revisit the brief daily. Keep screenshots of the preview. Name the owner of cost alerts. When you are stuck, re-read Eden AI and cut scope before you add tools. Roseram reviews can help you scan adjacent options, but the next action is still the same: ship the smallest slice that proves the loop.