Registries#
Registries define portable vocabulary, not permission to extend a closed object. An unknown action is denied; an unknown document field is rejected. Capability extensions are separately described by the posture specification.
Published inventory#
| Registry | Download | Role |
|---|---|---|
| action-types | YAML | Closed portable vocabulary |
| capabilities | YAML | Registered identifiers and compatibility rules |
| condition-types | YAML | Closed portable vocabulary |
| detectors | YAML | Registered identifiers and compatibility rules |
| error-codes | YAML | Registered identifiers and compatibility rules |
| frameworks | YAML | Registered identifiers and compatibility rules |
| media-types | YAML | Closed portable vocabulary |
| rule-blocks | YAML | Closed portable vocabulary |
| rule-paths | YAML | Closed portable vocabulary |
Version and ownership#
A registry can retain its original registry version while shipping in HushSpec v1. Read the registry header for its extension policy. Do not infer that an arbitrary capability, detector or framework is supported merely because a string fits its identifier grammar. Conformance is a separate claim about behavior against a named corpus.