Skip to content

Ulric Book a call

Tagged

Security

2 posts on security.

One engine, three client sites: the fork per client model

Three live sites share one CMS engine and share nothing at runtime: separate repositories, separate keys, separate databases, separate hosting accounts. The bill for that isolation arrives every time I fix something in the engine, because a fix lands in one copy and has to be carried to the rest. Here is the ritual, the path a real security fix took, and the four ways the sweep has quietly failed on me.

Claude Code hooks: the guardrails that never ask the model

A model can be talked out of things: worn down by a long context, swayed by a file it read, or simply wrong at one in the morning. A hook cannot: it is code that runs at a fixed point in the agent loop and returns a decision the model gets no vote on. The hook lifecycle, the exit code that actually blocks, and the two guards I run on every session.

← All insights