Ideas · Builder Notes
Starter policy packs and a private-banking pack
Kognita alpha 0.4 ships five starter packs and a private-banking pack, with user overlays and integrity pins.
Why did this need fixing?
Nobody wants to write governance from a blank page.
What did I do about it?
Five starter packs (role-based access, geo-fencing, data classification, time-gated access and two-signature approval chains) plus a private-banking pack with scenarios such as cross-border solicitation and booking-centre denials. A user overlay shadows the built-in pack and is never overwritten by an update.
kognita serve --pack compiles a pack and passes it to the gateway.
Which detail mattered?
A pack cannot skip a tripped circuit breaker or an open revocation, even if the pack says it does not apply.
Where are the limits?
Pack updates fetch only from the Kognita repository over HTTPS, and pins.toml is an integrity pin, not a catalogue.
If you're building something similar?
Ship opinionated defaults, and make overrides explicit and local.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #44 in the Kognita repository.