Purpose
Registries are the operational reference layer that connects curated source inputs, runtime caches, prompt synchronization, and auditability across HASMaster pipelines.
Registry Scope
- published source URL registries used as auditable reference material
- runtime prompt registries used by assistant and journey behavior
- supporting draft registries for device, domain, guide, infrastructure, and software workflows
Primary Control Points
- Admin surface: WordPress Admin -> Tools -> HASMaster Tools -> Runtime Registries
- Published reference: /use-case-source-url-registry/
- Assistant runtime cache:
/mnt/nas_docker_apps/wordpress-staging/wp_data/wp-content/hasmaster-runtime-cache/
When To Use Registries
- after prompt updates
- after assistant-nudge publish or validation
- after source-taxonomy changes that affect runtime resolution
- when inspecting whether a published runtime artifact matches its source
Operational Workflow
- Update the source-controlled registry or prompt source.
- Run the publish step for that source family.
- Validate synchronization from source to WordPress/runtime cache.
- Inspect the public or admin registry surface before closing the change.
Safety Rules
- Do not hand-edit generated runtime cache artifacts.
- Keep registry metadata aligned with the source files that publish into it.
- Use validation tooling after every publish step to catch drift early.