Disclosure

Disclosure

This page sets out what the project claims, the limit of each claim, and the evidence for both. Each entry covers 1 thing the project does: the claim and its limitation stand side by side, each pointing to the evidence.

Entry 1

How the guides are sourced

Claim: The contribution rules require every configuration line, flag, or variable name in a guide to come from the vendor's documentation, with that page linked in the guide's dated Sources section. Where a tool has no native control, the guide says so and gives a fronting-layer pattern instead of inventing an option.

Limitation: Tracing each line to its source is an authoring and review duty. The guide-shape gate checks that a guide has a Verify section and dated Sources; it cannot check that a line matches the page it cites.

Evidence: What a guide needs (opens in a new tab) The guide-shape gate (opens in a new tab)

Entry 2

What a Verify step rests on

Claim: Verify steps declare DEMONSTRATED, meaning the check ran against both the exposed and the fixed state, or REASONED, meaning it is derived from cited vendor behaviour. A reasoned step is never presented as verified.

Limitation: The marking gate checks that a declaration exists, not that the demonstration occurred or that the reasoning holds; that is checked in review. Older steps still being brought in line are listed in a baseline file.

Evidence: The gap and the standard (opens in a new tab) The marking baseline (opens in a new tab)

Entry 3

The verification checklist

Claim: The checklist sets out 11 checks to run before reporting completion, with each result recorded as pass, fail, untested, or not applicable, and a control reported as verified only for the checks that passed.

Limitation: Every item is REASONED and records that it was not run against a deployment. Items 1 to 4 record local syntax checks and stub runs only, and item 8 names tools without a command or a pass threshold.

Evidence: The checklist Its sources (opens in a new tab)

Entry 4

Versions and dates

Claim: Most guides carry machine-readable front matter recording the sources checked and, where known, the exact versions. Guides date their sources in a section titled with the month and year they were checked; common-mistakes.md, a checklist that links to the fixes, carries none of its own.

Limitation: Versions are recorded where known; 100 of the 102 guides are listed for the version-basis check. Vendor behaviour can change after the checked date.

Evidence: The version-basis list (opens in a new tab) The version-basis check (opens in a new tab)

Entry 5

Scope

Claim: The guides cover deployment exposure: TLS, human and machine authentication, MFA, access restrictions, secrets, and inbound and outbound network access, from first deployment through teardown.

Limitation: General application security, such as injection, deserialization, and business logic flaws, is out of scope and left to the OWASP resources the guides link; LLM application risks such as prompt injection are covered by the OWASP Top 10 for LLM Applications.

Evidence: Scope and currency (opens in a new tab) Contribution scope (opens in a new tab)

Entry 6

What the site loads

Claim: These pages load only files from this site: 3 stylesheets, the template's fonts, logos and marks, and 3 scripts: 1 reveals the copy buttons on 2 pages, 1 marks the section the reader is on in the contents list on 2 pages, and 1, on every page, shows the light and dark switch and applies the reader's choice. That script keeps the choice in the browser's local storage under the name scheme, only once the reader presses the switch, and sends nothing. The pages' own code sets no cookies, and the site's gates refuse inline script, inline style, and event-handler attributes in its pages.

Limitation: Cloudflare, which serves the site, can add its own scripts. The site's Content-Security-Policy allows Cloudflare's script and analytics hosts and inline scripts for its JavaScript Detections, by the owner's decision of 3 November 2026.

Evidence: The headers file (opens in a new tab) The page gate (opens in a new tab)

Entry 7

What ships as code

Claim: The guides are documentation. The code that ships is the Agent Plugin under plugin/ and the helper scripts under tools/ and scripts/; the site adds the template's copy, rail and scheme scripts.

Limitation: A correction lands on main through the normal pull-request and gate process, so an installed plugin bundle or a copied guide must be refreshed against main to pick it up.

Evidence: The security policy (opens in a new tab) The plugin (opens in a new tab)

Entry 8

Automated checks

Claim: Every gate in the suite is deterministic and offline, and the suite is the required status check on main. Every non-draft pull request runs the gates its changes affect, and a change to a guide, the code, the checks, a requirements file, a served script, the _headers file, a _redirects file or any site file of a type not on the content list runs the whole suite, so no change merges with a failing gate among those its changes affect. The whole suite also runs weekly.

Limitation: A change to a site file of a type on the content list (.html, .css, .json, .svg, .png, .jpg, .jpeg, .webp, .ico, .woff2, .txt and .xml: pages, page sources, stylesheets, fonts, images, text and XML files) that is not a requirements file, or to a project record, runs only the gates that read it; a requirements file runs the whole suite even with a listed suffix, and a gate a change does not run is checked in the next whole-suite run. The gates check the structure of the guides; whether a demonstration ran or a reasoned step is justified is checked in review. External links are swept weekly by an advisory job that does not block a merge.

Evidence: The gate suite (opens in a new tab) The gate selector (opens in a new tab) The CI workflow (opens in a new tab)

Entry 9

Licence

Claim: The guides, the configuration samples, and the site are dedicated to the public domain under CC0 1.0 Universal.

Limitation: The AIQT Guardrails material listed in .aiqt/PIN is under the Apache License 2.0. The site template's fonts are under the SIL Open Font License 1.1, and the GitHub, LinkedIn and ORCID marks are their owners' trademarks, used under their owners' terms.

Evidence: The licence page The notice file (opens in a new tab)

Your browser

If you use the light and dark switch, your choice is kept in your browser's local storage under the name scheme, so the site opens in that scheme next time. It is not sent to this site, and nothing is stored until you press the switch.

Security

To report a security vulnerability, see the vulnerability disclosure policy (opens in a new tab). The privacy policy that covers this site and the other 5 is at posluns.ca/privacy (opens in a new tab).