# LinkedIn ad file handoff

## Decision: Needs file details

Technical state: `DRAFT`  
Record: `Unknown`  
Owner: Unassigned  
Next action: Assign one stable record ID.

## Asset checked

- Format / placement: `Unknown` / `Not applicable`
- File: `Not attached`
- SHA-256: `Unknown`
- Detected MIME / bytes: `Unknown` / Unknown

## Rule source

- URL: Unknown
- Observed: Unknown
- Captured text SHA-256: `Unknown`

## Local checks

| Check | Result | Expected | Supplied |
| --- | --- | --- | --- |
| Decode | Hold | Final bytes and complete decoded facts | Missing |

## Recommendations

No recommendation result is available yet.

## Open requests

### req-record-id
Owner: Unassigned  
Field: `record_id`  
Reason: The handoff needs a stable identity.  
Expected: `"Stable nonblank record ID"`  
Supplied: `""`  
Next: Assign one stable record ID.

### req-format
Owner: Unassigned  
Field: `format_id`  
Reason: The selected format is missing or reference-only.  
Expected: `["single_image","video","document_pdf"]`  
Supplied: `""`  
Next: Choose single_image, video or document_pdf. Use the reference table for other formats.

### req-final-asset
Owner: Unassigned  
Field: `asset`  
Reason: The final asset bytes are not bound to the record.  
Expected: `{"file_name":"final file","sha256":"64 lowercase hex"}`  
Supplied: `{"asset_id":"","owner":"","expected_file_name":"","file_name":"","sha256":"","byte_count":null}`  
Next: Attach the final file and compute its SHA-256 before review.


## Native checks


## Evidence boundary

`LOCAL_READY` means the decoded file fits every local requirement encoded for the selected supported format and source version. It does not mean LinkedIn approval, copyright clearance, delivery or performance.