What we write here, and what we won't.

This journal exists because Vendric Labs ships software that handles consequential records — OSHA logs, incident reports, cryptographic audit chains. The people who depend on those records deserve a clearer view of what we’re doing, what we’re not, and why.

That’s the whole job of this page. There is no posting calendar, no content strategy doc, no SEO target keyword in the title. When something is worth writing down for the record, it lands here.

What you can expect to find

• i.OSHA explainers. Plain-language walk-throughs of the rules behind Forms 300, 300A, and 301 — and the 29 CFR 1926 paragraphs that decide whether a citation has teeth. Useful if you’re a GC, a broker, or an investor who wants to understand the regulatory surface.
• ii.Status notes. What shipped this month, what slipped, and what we decided not to do. If a posture or a date moves backwards, that move shows up here before it shows up on /trust.
• iii.Anti-pattern posts. The occasional manifesto in the same key as the homepage Posture section: things we refuse to do, and why.

What you won’t find

Equally important. We don’t publish anything that wouldn’t belong in a court filing of the company’s record.

• i.“AI is transforming X” takes. No trend posts. If we can’t point to a specific output we built, we don’t write about the category in the abstract.
• ii.Anonymous customer stories. A “case study” without a named customer who consented in writing isn’t a case study. We’ll publish those if a customer wants to be named; otherwise we won’t.
• iii.SOC 2 promises that aren’t in audit. The trust page already says SOC 2 Type II is planned for H2 2026. We won’t soften that here, and we won’t name an auditor before one is engaged.
• iv.Hype. No “revolutionary,” no “game-changing,” no “AI-powered.” If a post needs those words to land, it’s the wrong post.

If you want to write back

Every post will have a contact path at the bottom — usually a direct email to me. If something we publish here is wrong, late, or missing context, tell me. I read everything. Material corrections will get a dated note at the top of the post, not a quiet edit.

For one-off questions, the structured contact form is the fastest way through. For a real conversation, book a slot on the calendar. For a vulnerability report, security@vendriclabs.net.

Welcome. There’s a lot of substrate to talk about.