Add Patterns regularly as "products"

[ ] Tracking Windows events via Event Viewer (read and follow New Research Reveals Windows Event Logs Key to Identifying Ransomware Attacks).
[ ] Create osv-scanner-based Pattern called Vulnerability Explorer which can be used via capturable executables.
[ ] See https://github.com/qe-collaborative-services/quality-system for starting point of TAP-based quality reporting. @shah designed this to work without surveilr but perhaps it makes more sense to have it as a surveilr Universal Pattern.
[ ] Read Why did we need to build our own SIEM? and add a surveilr SIEM pattern.
[ ] See Open-source ConfigOps infrastructure to understand "Configuration as Code" (CaC) and see if we can create a simple surveilr CaC pattern that would allow all configurations in XML, YAML, JSON, etc. be easily queryable, viewable, etc. privately.
[ ] See Middleware for DORA Metrics and add DORA Metrics Pattern for software engineering teams' productivity.
[ ] Start preparing a similar article for Opsfolio: “Why did we need to build our own Evidence Warehouse?” article referencing surveilr.
[ ] See Marketecture Examples as good approaches for how to create Pattern diagrams / visuals.
[ ] NCQA does many "scorecards" for healthcare including quality metrics aggregation, etc. This is an ideal use case for surveilr Service Patterns as well as Industry Patterns.

surveilr / www.surveilr.com