Control note for the generated !gloss companion notes. This is a draft canonical vocabulary; source notes remain authoritative. Companion notes may use an alias, but retrieval should converge on a preferred concept ID.
| Preferred concept | Known aliases | Status |
|---|---|---|
| exception handling | exception handling; error handling; exceptions | draft |
| WebDAV | webdav notes; webdav vhost; webdav head; webdav transport | draft |
| stunnel | existing stunnel; stunnel TLS; stunnel PKI | draft |
| JSONHTL | jsonhtl notes; jsonhtl note; jsonhtl documents; jsonhtl spec | draft |
| GPS/location | GPS; gps fixes; location database; gazetteer comparisons | draft |
| exercise coaching | exercise; demonstrating; functional exercise; gym instructor blueprint | draft |
| solar eclipse | solar eclipse; total solar eclipse; path of totality | draft |
| certificate integration | certificate configuration; CertHub; cert path; cert deployment | draft |
| host migration | gravlax and kelp; deployed to gravlax; remote host | draft |
| notes/indexing | notes key; index notes; project notes; avoiding orphaned notes | draft |
Do not merge concepts merely because they are near neighbours in embedding space. A merge needs a shared meaning, an alias decision and at least one reviewed source example. Keep the old label as an alias so companion history remains readable.
Next curation pass: review the highest-frequency labels and all labels marked unsupported or related by the source-reranker. Promote a concept only after source-grounded review.
This note is deliberately a control vocabulary, not a claim that the seed aliases are all equivalent.