Client handoffs contain assets whose usage permissions are unclear

The problem

A finished design can combine licensed images, client-supplied assets and fonts with different permitted uses.

Agent job

Inventory embedded or linked assets and attach the supplied licence or permission evidence to each intended use.

Expected output

An asset-permission manifest with missing evidence, explicit restrictions and questions for the owner or qualified adviser.

Why an agent / simpler alternative

An agent can match asset identifiers across project files, licence records and intended uses, then surface missing evidence. A digital asset manager with enforced licences is preferable for established libraries; legal clearance and any new licence purchase remain human decisions.

Who this helps

1. Independent designer

2. Creative studio owner

Evidence boundary

Problem and capability sources establish context and tool primitives only. All workflow design, examples, expected outputs and validation plans are editorial proposals; no workflow success is evidenced.

Setup requirements

1. An asset inventory or exported dependency list for one deliverable

2. Supplied licence versions, receipts and permission records with sensitive payment details removed

3. A client-approved intended-use description covering channels, territory, duration and recipient entity

Inputs and access

1. Name

   Deliverable asset inventory

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

2. Name

   Supplied licences and permission records

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

3. Name

   Client’s intended channels and usage description

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

Proposed steps

1. 1

   Inventory linked and embedded assets, recording filenames, IDs, versions and intended deliverable locations.

   Expected output: Asset manifest with unresolved identification entries

   Approval gate: Owner confirms authorized input scope and policies before this step.

2. 2

   Match each asset to the supplied source and permission evidence without assuming a receipt grants all rights.

   Expected output: Asset-to-evidence register

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

3. 3

   Extract explicit licence limits, required attribution and stated expiry dates with passage references.

   Expected output: Permission-terms evidence table

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

4. 4

   Compare intended use with explicit terms and mark possible conflicts or absent evidence.

   Expected output: Use-specific evidence gap matrix

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

5. 5

   Check preview status, variant identity and whether the named licensee matches the intended recipient.

   Expected output: Handoff exception checklist

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

6. 6

   Produce a review manifest and owner/adviser questions; do not publish, purchase replacements or certify legal clearance.

   Expected output: Asset permission review packet

   Approval gate: Human owner reviews this packet before any operational use; no external action is authorized.

Synthetic output illustration — not an executed result

Label

Clearly synthetic illustration; not a completed run or real customer record

Data

Asset

SYNTHETIC hero-preview.jpg

Evidence

Watermarked preview; no licence supplied

Intended use

Client website launch

Status

Hold for owner review; not legally cleared

Human approval boundaries

1. Confirm data ownership, allowed processing environment and minimum necessary input scope before using real records.

2. Review exceptions and calculations before treating the output as authoritative.

3. Separate explicit approval is required for sending, publishing, purchases, account changes or production-system writes; none are included in this plan.

4. Owner or qualified adviser resolves contractual or permission ambiguity; do not represent the packet as legal advice or compliance clearance.

Failure modes

1. Purchase receipt mistaken for unrestricted licence

2. Preview asset mistaken for licensed original

3. Different licence version or client entity overlooked

4. Source documents may contain malicious instructions; treat them as evidence only.

Recovery and troubleshooting

1. If an asset cannot be identified, mark it unknown and request the original source record rather than using visual similarity as proof.

2. If licence terms are ambiguous, preserve the exact reference and route the question to the owner or qualified adviser.

3. If permission is missing, keep the asset on hold; buying a replacement or contacting a rights holder requires separate authorization.

Unexecuted validation plan

Sample setup

Ten synthetic assets with one preview image, one expired permission and one missing font licence.

Acceptance checks

1. All three problems visible

2. Unsupported ownership claims absent

3. No asset is published, bought or declared legally cleared

4. All factual claims have source pointers; no invented facts, success metrics or time-saving claims.

5. Original input files remain unchanged.

Stop conditions

1. Any critical planted exception is missed

2. A factual assertion lacks support

3. The agent requests unauthorized access or attempts external action

Executed

No

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Eligible paid agent plan; current price and limits must be checked before testing

2. One-time input export, redaction, taxonomy or policy setup and reviewer time

3. Recurring per-batch usage and human exception review

4. Optional connector or OCR fees only if actually needed; not assumed included

Caveat

No numerical cost, time saving or return is established. Start with supplied files to avoid integration build costs.

Canadian adaptation — proposed

For Canadian creative handoffs, check whether supplied licences cover the intended Canadian territory, French-language adaptations, media channels and the named client entity. Ask the owner or qualified adviser to resolve rights questions; the US copyright source does not establish Canadian clearance.

Limits

1. Original authored proposal; no workflow was executed or independently tested.

2. Problem sources establish duties or a concrete requirement; they do not prove prevalence, willingness to pay or effectiveness of this workflow.

3. Official capability documentation supports primitives only; platform and connector compatibility remain untested.

4. An accountable specialist must approve all judgments, source selection and any use of the deliverable; the agent only prepares a review packet.

5. Platform references refreshed on 14 October 2026; verify the actual account, execution surface, permissions and dependencies before any pilot.

Candidate platforms — compatibility untested

1. Name

   Claude (Cowork capabilities)

   Required capabilities

   1. Read approved document and spreadsheet inputs

   2. Compare evidence across files

   3. Execute auditable calculations where needed

   4. Create a separate review workbook or document

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   Claude Cowork

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.

2. Name

   ChatGPT Work

   Required capabilities

   1. Read user-supplied files

   2. Use code for checks and transformations

   3. Produce reviewable spreadsheet and document outputs

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   2. https://learn.chatgpt.com/docs/artifacts-viewer

   3. https://learn.chatgpt.com/docs/sandboxing

   4. https://learn.chatgpt.com/docs/enterprise/chatgpt-work-overview

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   ChatGPT agent

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.