# There are no Python dependencies. This file exists to say so, and to say it
# in the place a reader looks first.
#
# Every artifact a Training 09 lesson quotes - the nine-call run, the receipt
# chains, the approval cards, the timeline and decision tables, the MCP
# tools/list dump, the compensation proofs, the budget refusal, the ownerless refusal and the kill-switch drill - is produced by the Python standard
# library and nothing else. `pip install -r` on this file installs nothing, and
# the prebuild gate runs green on a machine that has never seen pip.
#
# That is a design constraint, not an accident. A guard is a control; a control
# a learner cannot run because a wheel failed to build is not a control they
# will ever adopt.
#
# TWO OPTIONAL EXTERNAL TOOLS, neither of them a pip package:
#
#   opa   1.20.1, Apache-2.0, linux-amd64, 61,644,271 bytes, pinned by sha256
#         in manifest.lock.json and fetched by `python3 fetch.py bin`. It buys
#         ONE thing: the envelope decided by a second engine, so
#         policy/agree.py can show 22 of 22 cases agreeing over one policy
#         file. The stdlib evaluator in guard/guarded_exec.py is the classroom
#         default and needs no binary. Without OPA the gate skips that tier
#         with a notice and hash-verifies transcripts/opa-test.txt and
#         transcripts/policy-agreement.txt instead.
#
#   curl  used by target/bypass_demo.sh alone, to show that one request at the
#         target's own endpoint does the denied action anyway - and then, with
#         --closed, that the same request is a 403 once the endpoint insists on
#         the gateway's signature. Any HTTP client would do; curl is what a
#         lesson can paste. Without it the gate hash-verifies
#         transcripts/curl-bypass.txt and transcripts/curl-bypass-closed.txt
#         and does not re-run them.
