Outputs and recovery

Results

For a normal CLI production run:

OUTPUT/promoted.jsonl contains certified publications and their task paths.
OUTPUT/failed.jsonl contains rejected candidates and execution errors.
WORK/results.jsonl retains every candidate result, including verified skips.
WORK/timeline.jsonl records actual task starts and ends for concurrency checks.
Task directories contain the original Harbor or ProgramBench payload and its certification.

The default work directory is .programgen/produce, relative to the configuration file. The summary reports candidates, promoted, failed, skipped, rejected and errors. A normal build or quality rejection is an expected result. An unexpected exception or unavailable service requires attention. Batch completion and task certification are separate conditions.

Resume

Run the same programgen produce command again. Resume is enabled by default. The producer checks configuration, implementation, payload hashes and certificates before skipping a completed task. A journal entry alone never authorizes a skip. Missing or damaged output is rebuilt from retained state and verified again.

Workers sharing an output directory share an identity lock and a global worker limit. Interrupted workers' owned tools and containers are cleaned before their slot is reused. Unrelated processes are preserved. Publication uses staging and atomic rename; an interrupted replacement retains the previous complete task.

Changing the source, mode, executable or effective configuration starts a new state scope. Previous failed attempts remain available for diagnosis.

For a single create, use --resume with the same repository, commit and model configuration. Retained agent artifacts are validated again before publication.

Diagnose a failure

Failure	Next step
Invalid input or missing full commit	Correct the indicated row and rerun `produce --check`.
Missing Docker or credentials	Follow the startup preflight message.
`model-service-unavailable`	Check endpoint, model, credentials and service availability; resume after recovery.
Build rejected	Inspect the candidate's build log; it may need a different supported input or valid executable target.
Quality rejected	Inspect the recorded reason and quality report; only a new fully qualifying result can be published.
Verification failed	Follow the retained evidence path to consumer logs and metrics.
Incomplete model response	Inspect the stage log; bounded retries and prior responses are retained.

Detailed traces remain in the candidate work directory. Keep them when reporting a bug; redact credentials from any configuration you share.