> ## Content Index
> Fetch the complete content index at: https://cryenx.com/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# What we write about here
- URL: https://cryenx.com/blog/about-this-blog/
- Published: 2026-09-30T09:00:00.000Z
- Updated: 2026-09-30T13:55:15.000Z
- Description: Engineering notes from the systems we build and run. Agents, retrieval, evals, guardrails and data pipelines. What we measured, what broke, and what it cost.
- Author: Cryenx Labs
- Tags: Announcements, Lab Notes

This is where the lab writes things down.

Not launch posts. Not "the future of AI is..." takes. The notes we would want to read ourselves before putting a model on work that costs money.

## What you will find

**Tests with numbers.** We take a new model or method and put it on a real kind of work, with our own test set, our own labels and every number we got. Including the ones that did not go our way. The first one: [Jev on a freight desk](https://cryenx.com/blog/jev-for-logistics/).

**Production notes.** Most of running AI in production is boring infrastructure. Evals, guardrails, stop rules, what happens when a model is confidently wrong at 3am. Nobody posts about it because it does not go viral. We will.

**Industry desks.** What AI actually does on a logistics exception desk, a plant floor, a finance back office. One industry at a time, each with its own cases, not a template with the name swapped.

## How we write

Plain language, so a buyer can follow it. The engineering shown, so a builder can check it. Method and limits in every post. If a claim can be a chart, it is one.

If your team is stuck between an AI pilot and AI in production, [talk to us](https://cryenx.com/blog/contact). That is the work.