May 1, 2026 — Overlock team
Welcome to the Overlock blog
A short note on why we are starting this blog and what to expect: engineering posts, network updates, and field notes from building a verifiable control plane.
[ Read ]
Why a blog
We have been writing a lot of code, drawing a lot of diagrams, and shipping a lot of small experiments. This blog is where we slow down long enough to explain the reasoning behind those decisions.
You can expect three kinds of posts:
- Engineering deep-dives on how reconciliation, capability tokens, and on-chain audit trails are implemented under the hood.
- Network updates covering what just shipped, what is in review, and what is blocked. Honest status of the work in flight.
- Field notes from running providers and integrating real workloads.
Every post is here to help a developer or a provider build something.
How writers can contribute
Posts live as plain markdown files in content/blog/. Add a file, add the
frontmatter at the top, write the body in regular markdown, and open a PR.
The site rebuilds and the post appears under /blog/<slug>/.
---
title: "Your post title"
description: "One or two sentences shown on the index page."
date: "2026-05-06"
author: "Your name"
tags: ["topic-one", "topic-two"]
---
That is the whole pipeline. No CMS, no database, no preview environment to spin up. Just a file in a repo.