Gergely Sipos

A useful coding agent needs more than good answers. Something has to call the model, expose tools, retain task state, and make the resulting work reviewable. That surrounding machinery is the harness.

CodeAF is an early-preview harness worth a bounded experiment, not a migration. Do its task handoff and checking loop help with your work? Start with one disposable repository and an unambitious request. This is early triage, not an endorsement or an Aliz adoption recommendation.

Ask an agent how Aliz approaches infrastructure reviews, and a well-written Markdown page is a good starting point. Ask which repositories had the most indexed agent sessions updated this week, and the problem changes. Now you need consistent records, a time window, and a count, not another document explaining the conventions.

SQLite can help with that second question. But putting information in a database does not automatically make an agent smarter, safer, or cheaper to run. Someone still has to expose the right capabilities and teach the agent how to interpret the results.

The useful distinction is not "Markdown versus databases." It is knowledge versus records, tools versus skills, and retrieval versus evidence. The Dev Hub can remain human-readable while structured workloads get a better interface.

We've been talking about it for a while, and now it's real: the Aliz Dev Hub is live. It's our collective engineering handbook — a single place where we capture what actually works at Aliz, from GCP patterns to frontend conventions to infrastructure decisions.

It's not a wiki. It's not a Confluence space. It's a Docusaurus site backed by Git, reviewed through pull requests, and deployed like any other piece of software we ship.