Hardware evidence, matrix and scheduler

What it covers

• Evidence channels can use lsblk, lspci, ip, dmidecode, SMART/NVMe, RAID tools, BMC/IPMI/Redfish, sensors, ECC/EDAC, rasdaemon/mcelog and kernel logs.
• The evidence matrix shows available/success/missing/not-applicable, freshness, coverage and confidence by component type.
• The hardware worker performs policy-controlled collection; the scheduler defines tasks, interval, timeout and load restrictions.
• An evidence-packet export contains snapshot, findings, summaries, identities and checksums.

How to use it

1. Check the matrix.
2. Distinguish missing from failed.
3. Schedule by host load.
4. Run a heavy manual check only when approved.
5. Export a packet.

Important rules

• A missing SMART tool does not mean a healthy disk.
• Vendor lookup does not replace local evidence.
• Do not transmit sensitive identifiers without policy.