J.1 Complete publication package
The implementation kit contains fourteen original SVG graphics, named fig-01 to fig-14 in the order the figures appear, source and claim ledgers, the 45-practice register, twelve implementation specifications, thirty-six proposed acceptance tests, glossary and metric dictionaries, ten blank templates, two synthetic examples, and a proposed event schema.
Read the complete handbook and individual chapters on The Observability Layer website, or download its PDF and editable Markdown. The implementation kit supplies reusable reference files. File integrity hashes describe file contents; they do not certify research validity or control effectiveness.
J.2 How to cite, license status, and versions
Cite this handbook. Fisher, W. (2026). Agentic Responsible AI: An Enterprise Handbook (Version 1.0.1). The Observability Layer. First published 2 October 2026; version 1.0.1 published 3 October 2026. https://theobservabilitylayer.com/handbook
To cite a chapter or appendix, add its section title and web address. Refer to practices, specifications, tests, explanations and sources by their identifiers in Appendix A.1. Practice, specification, acceptance-test, source and original control identifiers remain stable. The changelog records the regulatory explanation-code migration and its aliases.
License status. Copyright 2026 Dr. William Fisher. The ten original JSON templates in the implementation kit and the original reusable forms in Appendix C.1–C.6 are available under the MIT License, as described in Appendix C.8. The rest of the handbook, including its text, figures and data registers, and any third-party material remain under the publication's current terms, which explain what you may quote, link and cite without asking.
Versions and errata. Version 1.0.1 is a corrections release. It fixes consistency, labeling, navigation and accessibility issues without changing any recommendation, research finding or evidence conclusion. The changelog records every change by version, and the errata list the individual corrections. The files first published on 2 October 2026 remain available, unchanged, at their original addresses.
J.3 Maintain a versioned body of knowledge
For a new edition, record source versions and scope; inspect changed legal or protocol status; update claims, calculations, graphics, and implementation consequences together; retain superseded editions; and explain material changes. Reopen a control recommendation when new evidence contradicts its mechanism or operating assumptions.
Do not update an evidence cutoff merely because the file was rebuilt. A new cutoff should reflect inspected evidence. Enterprise users should version their adopted practices and document which local deployment evidence supports them.
This handbook follows the same rule. A patch release, such as 1.0.1, corrects errors that do not change meaning and keeps the evidence cutoff. A substantive change, such as new evidence or a changed recommendation, requires a new minor edition with its own review date. Every version keeps a permanent address, and earlier files are not replaced.