Purpose
HASMaster orchestration guides explain how prompt source, context planning, validation, and publishing are assembled into multi-step workflows. This is the layer you use when you need to trace why a generated result looks the way it does or when you need to improve pipeline behavior safely.
Core Orchestration Layers
| Layer | Role | Primary Surface |
|---|---|---|
| Planner | Frames scope, constraints, and execution context before generation begins | Guide Context Planner |
| Orchestrator | Sequences prompts, intermediate transformations, and validation gates | Prompt Orchestrator |
| End-to-End Master | Defines the full guide-generation flow from inputs to publishable output | Guide Setup End-to-End Master |
| Runtime Registries | Publishes and validates the prompt/runtime assets the site actually uses | HASMaster Tools → Runtime Registries |
How To Use This Layer
- start with the planner when the subject, taxonomy scope, or audience is still unclear
- use the orchestrator when you need to inspect prompt sequence, routing, or validation checkpoints
- use the end-to-end master when you want the whole content-generation flow in one place
- finish with publish and validation so runtime artifacts stay synchronized with source
What To Verify
- taxonomy assumptions match the target content type and destination
- source references are explicit and preserved through the pipeline
- the rendered post structure includes the required sections, images, and comparison data
- publish-time assets in WordPress and runtime cache reflect the same final prompt source