Penanganan aset
Dokumen ini dalam bahasa Inggris.
How Denver Creative OS handles product references and project assets
DCO is built around one principle:
The reference remains the source of truth.
This page explains what happens to project assets from upload through generation, QA, delivery, and expiry.
1. What counts as a project asset
A project asset may include product cutouts and catalogue images, brand references, room or campaign references, documents and creative briefs, 3D files such as GLB or glTF, generated images and videos, prompts and approved creative direction, QA artifacts, metadata, lineage records, and final delivery files.
2. Source assets remain authoritative
An original client reference is not treated as disposable input.
DCO uses the source asset as the primary reference against which derived work is planned and evaluated.
When a generated result conflicts with an observed product fact in the source, the source should take priority.
3. 2D references and generated 3D proxies
When DCO creates a 3D model from a single 2D product image, that model is a 3D geometry proxy.
The proxy can help with spatial inspection, camera planning, multi-angle preview, silhouette reference, scene blocking, and downstream creative exploration.
It is not automatically authoritative geometry.
Visible source-facing surfaces can usually be treated with higher confidence. Partially visible surfaces have lower confidence. Hidden, rear, underside, or occluded surfaces may be inferred by the generation system.
A generated proxy must not be presented as manufacturing-grade CAD unless separately validated.
4. Native client 3D assets
If a client provides a native GLB, glTF, CAD-derived model, or other validated 3D asset, DCO may treat that asset as a stronger geometry reference than an AI-generated proxy.
The exact authority of the model depends on what the client confirms about its origin and accuracy.
5. Processing workflow
A typical DCO asset flow may include:
Upload → Analysis → Identity Lock → Creative Direction → Generation → QA → Lineage → Release
Not every project uses every stage.
During processing, DCO may create working derivatives such as resized previews, thumbnails, temporary renders, masks, metadata, 3D proxies, reference packs, QA comparisons, and final delivery versions.
These derivatives exist to complete the project workflow.
6. Third-party processing
Some project operations may use external AI, rendering, storage, or infrastructure providers.
Only the assets reasonably required for a particular operation should be sent to the provider performing that operation.
Provider behavior, retention, and data-use terms can differ. If a project requires specific provider restrictions or zero-retention handling, those requirements should be agreed before sensitive assets are uploaded.
7. No unrelated reuse
DCO does not intentionally reuse private client assets for unrelated client work, public marketing, portfolio publication, or proprietary model training without permission.
Permission to showcase a final result does not automatically mean permission to publish every source file, internal artifact, or project record.
8. Lineage and traceability
Where supported by the workflow, DCO may associate outputs with their source references, generation stage, QA state, or project identifiers.
The purpose is to keep creative work traceable rather than treating every generated file as an isolated image.
Lineage records are operational metadata; they do not by themselves prove legal ownership, authenticity, or manufacturing accuracy.
9. Downloads
Delivery files may be shared through temporary or project-scoped links.
Clients should download approved deliverables within the communicated access period.
A project workspace or temporary delivery link is not intended to replace the client’s permanent archive or digital-asset-management system.
10. Retention and deletion
Retention can vary by project, provider, and operational requirement.
Project assets may remain available while a project is active and for a limited period afterward for delivery, troubleshooting, recovery, QA, security, or legal obligations.
A client may request deletion of eligible project data, subject to contractual, legal, security, backup, and third-party-provider constraints.
Requests can be sent to:
11. Before uploading sensitive assets
If the material is confidential, embargoed, regulated, unreleased, or subject to strict contractual controls, contact the studio operator before upload.
The project can then be reviewed for appropriate provider, retention, and access requirements.
12. Questions
Questions about asset handling can be sent to: