Harnesses by architecture
A series of base harnesses for software architectures. They all wrap the same small app: only the architecture and the harness change.
The key idea: the harness is the main character; the architecture is the context. Each page explains the architecture briefly and spends the rest on the harness.
The series is complete: four base harnesses, three reusable pieces, the starting point they are compared with, and a guide. If you do not know where to start, readHow to choose a harness.
What a base harness is
A base harness is the starting kit you give an agent to work on a project with a specific architecture. Each harness in the series brings an AGENTS.md that explains where each thing goes, permissions, hooks, and, when it helps, a Skill for frequent tasks. One hook checks the main rule of the architecture. If the agent breaks that rule, the hook catches it and the agent cannot finish the task.
The harnesses are not tied to one agent. The instructions go in AGENTS.md, and the hooks, skills, and permissions go in an .agents/ folder. Each page explains how to connect them to some agents, such as Claude Code or Codex.
Some parts work for any architecture: security, quality, and clean code. They are taken out of the first harness and reused in the next ones as pieces.
The mini app
Every harness wraps the same app: a small REST API for a library, with books, members, and loans. It has two business rules: a loaned book cannot be loaned again, and a member can have at most three active loans. Data lives in memory, with no database.
All harnesses use the same language, TypeScript with Node, and pass the same eleven acceptance tests. Since only the architecture changes, they can be compared fairly.
How to read the explorer
Each page has a file explorer like the one in VS Code. The folders are on the left (above, on a phone); select a file to see its content. Folders open and close with a click or with Enter. Hidden folders such as .agents/ are shown too, because that is where hooks, skills, and permissions live. Dependencies and lockfiles are left out.
The files are in English, like the code. Without JavaScript, the explorer shows every file one after another.