Ideas · Builder Notes
Kognita 0.5.1: the last egress gaps, and a migration guide
Just after midnight on 20 October: Kognita alpha refuses attachments it can't inspect, screens message-shaped responses input and JSON keys, closes the library path, and ships 0.5.1.
Review was still finding ways content could reach a provider unscreened. Image, audio and file parts are now refused, because the gateway can't inspect them. Message-shaped input on the /v1/responses endpoint is screened like chat. JSON object keys are classified and redacted as well as their values.
The library path was weaker than the gateway. It now requires a live workload credential every time, and tier 2 and above use cases are refused in library mode at runtime as well as at registration.
Many of the fixes since 0.5.0 were breaking. 0.5.1 shipped at 1:11 am with the breaking changes, a migration section and the known issues in the changelog.
What I'd do differently
I'd audit every entry point against the same checklist before the first 0.5 release. The library path should never have lagged the gateway.
Worth stealing
If you can't inspect it, don't forward it.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #109, Kognita PR #110, Kognita PR #111, Kognita PR #112, Kognita PR #113 in the Kognita repository.
