PROPOSAL
Auto Engine prepares
SEE can prepare selects and proposed work for the Review Queue without silently executing the final action.
Operational trust, stated precisely
Protect the Source
Keep control of the process
SEE separates verified copying, local processing, optional provider-backed actions, and human approval so the operator can see what is happening and decide what happens next.
01 · VERIFIED SAFE COPY
Evidence before
safe to eject
Safe Copy protects everything inside the selected Source Folder. SEE copies that content and checksum-verifies the protected copy before heavier archive processing begins. After successful verification, SEE reports the verified state and says when it is safe to eject.
Additive source handling
Safe Copy does not modify original Source media. Processing continues from the protected copy according to the selected workflow.
02 · LOCAL-FIRST BOUNDARIES
Local-first does not mean
vague promises
The data path depends on the action. SEE distinguishes local workflow data from optional providers, website collection, licensing, and support.
| Footage and archives | Designed to remain on storage controlled by the user. SEE works with local paths, project destinations, and archive records. |
|---|---|
| Local transcription | Speech-to-text processing for supported workflows runs on the workstation. |
| Technical index | Camera, frame rate, resolution, timecode, duration, and file-path cataloging does not require a paid AI key. |
| Optional providers | Supported semantic or generative actions may send the specific input required for that action to the provider selected by the user, using credentials the user supplies. |
| Provider cost | SEE identifies paid actions, surfaces provider-cost context, and supports spend controls. Provider terms and retention still apply. |
| Website and support | The public website uses Meta Pixel and collects reservation/support information submitted by the visitor. The Privacy Policy describes this separately from desktop workflow data. |
| Licensing and updates | Activation, entitlement, and updater requests may contact the services described in the Privacy Policy and Terms. |
03 · HUMAN CONTROL
Preparation can run
Consequences stay gated
Human approval is part of the product architecture, not a missing automation step.
REVIEW
The operator inspects
Job context, controls, and next actions remain visible before the proposal advances.
APPROVAL
Approval creates the next job
Approving a proposal queues the corresponding Creative Build work. It is not the same as running it.
DELIBERATE RUN
Consequential work is explicit
The operator reviews and deliberately runs builds, renders, publishes, uploads, or deletions where supported.
04 · HONEST LIMITS
Verification is evidence
Not a guarantee of everything
SEE can verify a copy operation and preserve workflow receipts, but every production environment still requires operator review, healthy storage, tested backups, and appropriate delivery checks.
Keep independent backups
Checksum verification establishes that the protected copy matches the selected source at that operation. It does not replace a broader backup strategy, storage-health monitoring, client-delivery QC, or professional judgment.
SEE IT IN CONTEXT
Watch the safety model
inside the real workflow
Book a walkthrough or join the Windows launch list.