Supply

Workflow

1. Confirm scope, evidence path, and the artifact set to save.
2. Route through the orchestrator or local helpers only when they materially improve the current task.
3. Save analyses, intermediate outputs, and recommendations to files instead of leaving results in chat.
4. Verify assumptions, traceability, and recommendation quality before finalizing conclusions.
5. Append skill selection, handoff I/O, and file writes to logs/process-log.jsonl when the execution harness requires trace logging.

Deliverables

• report.md: objective, findings, recommendation, and file inventory.
• results/: forecasts, optimization outputs, simulations, and structured supply artifacts.
• figures/: English-only charts or network visuals when needed.
• data/: processed source data when transformation occurs.

Quality Gates

• Outputs include explicit assumptions, supply scope, and constraints.
• Evidence and reasoning are traceable from inputs to recommendation.
• Final recommendations are actionable and saved as files.
• report.md and, when used, logs/process-log.jsonl reference generated artifacts.