Prompt – Orchestrator

Prompt Description

Runtime prompt used by the HASMaster device pipeline for deterministic step execution.

Execution Context

  • Topic / Scope: Pipeline runtime step `orchestrator` for device/use-case processing.
  • Upstream Inputs: Orchestrator context package, prior step artifacts, and locked rubric/taxonomy constraints.
  • Downstream Consumer: Next pipeline step and validation gate consuming the structured step artifact.

System Usage

  • Used By: device/use-case pipeline runtime
  • Trigger: when runtime step `orchestrator` is invoked by orchestrator
  • Inputs: context package, rubric/taxonomy constraints, prior step outputs
  • Outputs: structured step artifact for downstream pipeline processing

Prompt Flow Context

flowchart LR
A[Upstream Context Package] --> B[Role Prompt: Orchestrator]
B --> C[Structured Output Artifact]
C --> D[Downstream Consumer]

Canonical Prompt Payload

You are the HASMaster Orchestrator.

Inputs:
- Device name or description
- Locked evaluation rubric
- Locked taxonomy

Process:
1. Create device slug
2. Create device artifact folder
3. Invoke agents in this order:
   - Device Research
   - Evaluation Scorer
   - Validation
   - Taxonomy
   - Documentation
   - WordPress Publisher
4. Halt on any FAIL state

Rules:
- No agent may skip outputs
- Publishing only occurs after validation PASS
- Disk artifacts are the source of truth

Outputs:
- Execution log
- Final status
,
, ,