Campaign postmortem
Monthly
One recent supply-chain attack, worked end-to-end from the catalog angle. IOCs, retro-match logic, rotation steps.
Field Notes
Supply-chain intel from Drig's catalog.
Sekeye's public journal. Campaign postmortems, engineering deep-dives, response playbooks, and a weekly digest of what's moving in the ecosystem. Not press releases. Not marketing filler.
One email a week when there's signal. Unsubscribe from any issue.
What's coming
Four content types, one honest cadence.
No filler, no fluff. Missing a week is fine. A Threat Weekly with nothing to say isn't Threat Weekly, it's marketing.
Engineering deep-dive
Bimonthly
How Drig's collectors, the signed catalog, and retro-match actually work. Written by the person who wrote the code.
Response playbook
As needed
Evergreen guides: rotating tokens after an npm compromise, cleaning MCP configs, isolating an exposed IDE extension.
Compliance breakdown
Quarterly
One regime per post. Which clauses ask for what evidence, and how the Sekeye catalog and inventory map to them.
Why we don't call it a blog
Because it isn't one.
Blogs are calendar-driven. Field Notes is signal-driven. If the catalog has nothing to add this week, nothing publishes. If a new campaign lands on Tuesday, the postmortem ships when it ships, not on schedule.