Found while rolling out ADR-111 demo data across the fleet. hermiq is the only app with a setup walkthrough that cannot be given a demo-data step, and this is why.
What the descriptor says
lib/Settings/hermiq_register.json declares 30 schemas — Schedule, Approval, AgentWebhook, AiFeature and 26 more — and components.registers is absent entirely:
$ python3 -c "import json; d=json.load(open(\"lib/Settings/hermiq_register.json\")); c=d[\"components\"]; print(\"registers:\", c.get(\"registers\")); print(\"schemas:\", len(c[\"schemas\"]))"
registers: None
schemas: 30
Why that is not cosmetic
A schema has no independent existence in OpenRegister — it is carried by a register. A descriptor that declares schemas and no register has nothing to import them into, so:
- none of the 30 schemas materialise on any instance;
- nothing can be stored against them;
- the fleet demo-data generator reports
hermiq: declares no schemas — nothing to generate, which is how this surfaced. That message was accurate about the outcome and misleading about the cause: the schemas are there, the register is not.
This is the same shape as the ImportFlowRegister finding in openregister — a fully-written artefact that is never named where it would take effect — except here the missing half is the register declaration rather than the Repair-step registration.
What is needed
- Declare the register in
components.registers (slug, title, and its schemas list naming the 30).
- Ship a Repair step that imports the descriptor, per ADR-005 Rule 1 — shipping the JSON alone does nothing at runtime.
- Then hermiq can take the ADR-111 demo-data step like the other six apps with a walkthrough:
occ openregister:descriptors:list --app=hermiq will show the register, and the generator will produce validated demo objects for all 30 schemas.
Related
doriath (keepiq) has the same shape but is still the scaffold default — one schema named example, description "Keepiq — replace with your app description". Worth tracking separately; it is not 30 real schemas going nowhere.
Found while rolling out ADR-111 demo data across the fleet. hermiq is the only app with a setup walkthrough that cannot be given a demo-data step, and this is why.
What the descriptor says
lib/Settings/hermiq_register.jsondeclares 30 schemas —Schedule,Approval,AgentWebhook,AiFeatureand 26 more — andcomponents.registersis absent entirely:Why that is not cosmetic
A schema has no independent existence in OpenRegister — it is carried by a register. A descriptor that declares schemas and no register has nothing to import them into, so:
hermiq: declares no schemas — nothing to generate, which is how this surfaced. That message was accurate about the outcome and misleading about the cause: the schemas are there, the register is not.This is the same shape as the
ImportFlowRegisterfinding in openregister — a fully-written artefact that is never named where it would take effect — except here the missing half is the register declaration rather than the Repair-step registration.What is needed
components.registers(slug, title, and itsschemaslist naming the 30).occ openregister:descriptors:list --app=hermiqwill show the register, and the generator will produce validated demo objects for all 30 schemas.Related
doriath(keepiq) has the same shape but is still the scaffold default — one schema namedexample, description "Keepiq — replace with your app description". Worth tracking separately; it is not 30 real schemas going nowhere.