Ideas · Builder Notes

Releasing Kognita 0.3.0

Kognita alpha 0.3.0 shipped the AI gateway, the MCP proxy, run budgets and replay. The release commit changed the version and the changelog, and nothing else.

What was in it?

Everything from the 4 and 5 October work: the OpenAI-compatible gateway, the MCP proxy, run budgets and approval holds, classifier envelopes, pinned evidence and the reconstruction report.

Why keep the release commit so small?

A release that also changes behaviour is hard to review and hard to roll back. The bump touched the version number and the changelog section and nothing else, so anyone reading it could see exactly what 0.3.0 claimed.

What was left for later?

The README still described 0.2. I fixed that in a separate docs pass the next day, so the release and the description could each be reviewed on their own.

What would I tell another builder?

Cut the release from a main branch that is already done. If the release commit needs code, the work wasn't finished.

Sources

Kognita is an open-source alpha. This note comes from Kognita PR #28 in the Kognita repository.

All ideasEmail Ahmed