Releases — Contextual Agentic

Reader Toolkit 0.1.0 — v0.1.0

The first Reader Toolkit release: the pattern catalogue, the Zero Trust checklist, the governance assessment, the maturity model and the three templates. Free to anyone, with no purchase and no email address.

Works with: Applies to every edition. Nothing in this release depends on a specific printing, because nothing in it is printed.

Artefact	Licence	Size	SHA-256
Enterprise Agentic Pattern Catalogue (Markdown)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	6.3 KB	`4761ba4504e1bf64…`
Enterprise Agentic Pattern Catalogue (CSV)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	4.9 KB	`9ba7953b862bcafd…`
Zero Trust Agentic Security Checklist (Markdown)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	6.2 KB	`a6240b4d4b530374…`
Zero Trust Agentic Security Checklist (CSV)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	4.2 KB	`990ff7170439e39e…`
AI Governance Assessment (Markdown)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	3.7 KB	`662f8b4e381c08ed…`
AI Governance Assessment (CSV)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	2.4 KB	`2cfe82efaa7e20c2…`
Executive Maturity Model (Markdown)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	3.1 KB	`27fe9ffcccea69c2…`
Executive Maturity Model (CSV)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	1.6 KB	`f71cb4b23e21641a…`
Context, authority and evidence templates	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	3.1 KB	`83500800cd90c0f9…`
Deterministic envelope diagram (SVG)	CC BY-NC 4.0 — attribute to Hanif Karimi, contextualagentic.com	3.3 KB	`19bebd98797d0cc4…`

What is in it

The complete Reader Toolkit as it stands: ten patterns, twenty-four security checks, eighteen governance questions, a six-dimension maturity model and three one-page templates. Each artefact comes as Markdown to read and CSV to work with, generated from a single source so the two cannot drift apart.

What is deliberately not in it

No code. The companion code is released separately and against a specific printing, because code and a printed book age at different rates. This release applies to every edition precisely because nothing in it is tied to a page number.

Verifying it

Every artefact carries a SHA-256. python3 tools/release.py --verify 0.1.0 recomputes each one from the file and fails if it differs. The catalogue shows “Checksums verified” only after that has passed.

Conditions

None. The toolkit is not gated on a purchase, an email address, a review or a rating.

How releases are handled

Versions

Releases are semantic. A patch fixes something without changing how you call it; a minor adds something without breaking what you had; a major changes something you will have to edit. A release that breaks a listing printed in the book is a major, no matter how small the diff looks.

Every release names the printing it belongs to

The book is a fixed artefact and the code is not. A release therefore says which printing and which edition it works with, and older releases stay published for as long as copies of that printing are in circulation. Removing a release because a newer one exists would break the book for whoever bought it last year.

Checksums are checked, not asserted

Every artefact carries a SHA-256. tools/release.py --verify recomputes it from the file and fails if it differs, and the catalogue shows “Checksums verified” only for releases that have passed that check. An unverified release says so on the page.

Deprecation

Something being deprecated means it still works and will stop working in a stated future release. A deprecation without a migration note is not allowed — the build refuses it — because the note is the entire point of announcing it early.

Withdrawal

A withdrawn release is one that should not be used: a defect serious enough that running it is worse than not having it. It stays listed, marked withdrawn, with the reason. Deleting it would only mean people keep using the copy they already downloaded without ever learning why they should not.

Rollback

Rolling back is publishing the previous release as current again and marking the bad one withdrawn. The history is not rewritten. tools/release.py --rollback <version> does this and refuses if the target was never published.

Companion code releases