Purpose
The HASMaster structure layer is the control plane that keeps taxonomy, prompts, icon assets, runtime registries, and rendering behavior aligned. Use this guide when you need the big-picture map before editing one specific subsystem.
Structure Map
| Layer | What It Governs | Where To Inspect It |
|---|---|---|
| Taxonomy | content modeling, journey task naming, directory filters, relationships | /taxonomy/ |
| Orchestration | multi-step prompt execution and validation flow | /orchestrator/ |
| Prompt Library | source prompt organization and operator-facing publish/validate control | /prompts/ |
| Icon Library | canonical SVG/icon mapping for taxonomy and cards | HASMaster Tools → Icon Library |
| Registries | runtime prompt artifacts, source-url registries, synchronization state | HASMaster Tools → Runtime Registries |
How The Pieces Interact
- taxonomy gives the system a shared vocabulary for categories, journey steps, and discovery filters
- orchestration and prompts transform that vocabulary into repeatable content-generation and assistant behavior
- icon and registry layers keep the runtime presentation and operator tooling synchronized with source decisions
Practical Usage Pattern
- start with taxonomy when a content or journey concept is not modeled correctly
- move to orchestration when the system is modeled correctly but generating poor results
- use prompt-library and registry tools when the source/runtime contract is drifting
- use icon-library controls only after the taxonomy and naming contract is stable