Three tracks, one compatibility overlay
HCB follows the DSH-ENTRY / DSH-FLOW / DSH-BOOST model from dsh-standards. They are three tracks, not three levels.
| Track | Question | Gates | Evidence states | HCB column |
|---|---|---|---|---|
| DSH-ENTRY | can it be recognized, installed, booted? | G0–G5 | runtime / recognized / static / blocked / failed / not-run / stale | standards.entry |
| DSH-FLOW | can a user install, configure, use, recover, uninstall? | J1–J8 | runtime / manual / not-run / failed / stale | standards.flow |
| DSH-BOOST | does it use Cordis natively and efficiently? | LEV-1–8 | measured / not-measured / failed / stale | standards.boost |
Rules HCB enforces
- No total score. HCB never adds ENTRY + FLOW + BOOST into a number.
- No skip-as-pass. Missing declaration =
unknown; a declarednot-runstaysnot-run. - BOOST is not a gate. A measured BOOST never upgrades a failed ENTRY or FLOW.
- Compatibility is separate.
declared-compatibleis a claim by the package author, not a test result.
Evidence levels (v0.5)
A track state says where the package is; row.evidence says how that state was
obtained:
evidence.source |
Meaning |
|---|---|
declared |
read from package metadata; no independent check |
checked |
a checker ran against the published tarball (static ENTRY, no boot) |
tested |
a real host boot ran (ENTRY G0–G3; not produced by v0.5) |
The levels cannot be skipped. A checked pass is recognized, not runtime;
a failed check is still checked; blocked is an evidence gap and blocks the
gate conservatively. See EVIDENCE.md.
What HCB adds
- Compatibility overlay: does the declared
engines.dshrange cover the latest host? - Risk overlay: what capability surface does the plugin request (
subprocess,network:egress,fs:read, ...)? - Gate heuristic (
hcb-gate/1): a review recommendation, not a certification:
| Decision | When |
|---|---|
blocked |
declared range excludes latest host, or ENTRY is failed/blocked |
review |
no declared range, or ENTRY is not-run/unknown/stale, or risk is high/unknown |
pilot |
compatible, but FLOW is not runtime/manual or ENTRY is not runtime |
production-candidate |
compatible + ENTRY runtime + FLOW runtime/manual + risk low/medium |
Gate is not quality. A production-candidate can still be a bad plugin; it only means the checks HCB knows about did not find a blocker.
Source of truth
- Canonical model:
dsh-standards/spec/levels.json(Apache-2.0). - HCB mapping:
spec/tracks.json. - HCB does not relicense the model; see
NOTICE.md.