Original materials and the editable project stay on your device
Martius works with original documents, photographs, raw footage, recordings, portraits, source audio and editable projects locally. Keep the sources near the project or in an organized asset location you can identify. A creation task does not require uploading that folder to a cloud workspace.
The project holds the relationship between sources, facts, script, scenes, presenter choices, reviews and deliveries. These connections make it useful for the next campaign or product change; an exported film alone does not retain the full editable work.
Understand a reference, a delivery and a backup
A referenced asset points to a source the project uses. A delivery is a rendered video or selected companion material. A project backup preserves the work needed to reopen and continue, with references or included assets according to the backup option. Those objects have different purposes.
Before handing work to another machine, inspect whether the backup includes the required assets or relies on files in their existing locations. A project that opens without its media is not a complete restoration, and copying one MP4 is not backing up the editable project.
- Source asset: original material and its version
- Project: editable production decisions and references
- Delivery: rendered output for a purpose
- Backup: project and assets needed for restore or handoff
Reconnect moved or replaced assets carefully
If a source is moved, reconnect the intended file and confirm its identity. If its content changes, review the affected scenes. Do not treat a matching filename as proof that a replacement has the same material.
Keep important product assets versioned by their actual meaning: product variant, recording date, interface version or approved source. When a new price or specification arrives, update its fact source rather than silently replacing unrelated media.
Save approved context and revisions for the next task
Keep the approved project revision, product information, brand material, creative direction and delivery together. Reuse context that still applies to the next audience and task. Inspect expired offers, retired interfaces and permissions before applying older material.
A next campaign can share the product and presenter while needing a new script, composition and CTA. Treat that as a new task derived from the existing project, with its own review, rather than assuming the earlier approval covers every reuse.
Back up and test a restored project
Choose a backup location you control and preserve the required project and asset set. Avoid saving the only backup to the same place that holds the working copy. Keep previous approved versions identifiable so a new edit does not erase the reference.
Test the restore: open the project, inspect source availability, fonts and presenter references, preview relevant scenes and verify the approved delivery association. An archive existing on disk is not the same as a project that can be continued.
Separate local export from approved publishing
A local export saves the finished video and chosen companions to your device. Publishing is a separate destination action: approve the specific delivery, account, visibility, accompanying text and operation. Only selected outputs and required metadata are sent.
Do not include unrelated source folders, raw portraits, original audio, credentials or the entire project in a publish bundle. A platform or LMS receives the delivery you approved, not permission to browse your local workspace.
Keep other data flows visible
Local originals and project storage are distinct from model requests, account authorization, diagnostics, destination analytics and learning records. Check those settings and their explanations rather than inferring fully offline AI from the desktop interface.
When a learner runs an exported course, the destination can record learning activity under its own configuration and policy. When you publish a film, the platform processes the selected delivery. These actions do not alter the local source policy, but they need their own clear purpose and permissions.
Questions about this workflow
Are my raw videos uploaded to a cloud workspace?
No. Original video, recordings, documents, portraits, source audio and editable projects remain on your device. Approved publication sends only the selected finished delivery and required metadata.
Is exporting a video enough to back up my project?
No. Keep the editable project and the referenced or included source assets needed to restore it. A rendered file preserves the result, not the full production work.
What if I move a source folder?
Reconnect the expected asset locations and verify the file versions. Inspect the affected scenes before continuing review or export.
Can I reuse approved brand material in another video?
Yes. Reuse the local context, then verify that wording, offers, product versions and permissions still apply to the new task. Give the new video its own review.
Does local project storage mean fully offline AI?
No. Model requests and destination connections are separate data flows. The local original-file boundary should not be read as an offline guarantee for every operation.