Outputs & Auditability

Every Forge job produces an output file and a manifest. The manifest is the audit trail.

Output Structure

A completed job writes two things:

  1. The output file — the transcoded or proxied media.
  2. The manifest — a structured record of the job.

Both are written to the output directory. The manifest uses the same base filename as the output, with a .manifest.json extension.

What the Manifest Contains

The manifest records:

  • Input file path and hash
  • Job specification (all parameters)
  • Start and end timestamps
  • Exit status (success or failure)
  • Failure reason, if applicable

The manifest is written atomically. If the job fails, the manifest still records the attempt and the failure reason.

Verifying Results

To verify a job, compare the manifest against your expectations:

  • Does the input path match the file you intended?
  • Does the spec match your preset?
  • Is the exit status success?

For batch workflows, manifests can be parsed programmatically. They are standard JSON.

No Silent Partial Output

If a job fails mid-process, Forge removes any partial output file. The output directory contains only complete, verified results or nothing at all. The manifest is the only record of a failed job.