axKit 5.0.1

• axKit: PRIVACY.md, the README, SECURITY.md and the bundle spec say exactly how axKit meets the network: its own code makes requests in the updater alone, over HTTPS to GitHub (the update check, a setting, and the download you choose, accepted from this repository's release address only); an access layer reaches the network only through the program it runs as a child process on your computer (Claude Code talks to Anthropic, git reaches a remote on fetch, pull and push alone, your shell's commands reach what they reach, KeePassXC's tool nothing).
• axKit: docs/axkit/outside-calls.md, a page written from the sources at every release: everything axKit reaches outside its own process, GitHub, Claude Code, git, the shells, KeePassXC's tool, the installers, Windows, the programs you choose, axKit itself and the AI tools' pipes, with what each is, where it is, how axKit reaches it and its documentation, and every call in the code under it with its app, file, line, function and purpose. The README links to it under Transparency and self-audit.
• For developers: every network request, program start and pipe in src carries an Outside call, <kind>, <what is reached>: comment; tools/outside-calls.ps1 writes the page from them, build.yml fails on a call without one or a stale page, and release.ps1 writes and commits the page with each release (bundle SPEC B-17, AX-11.11).
• For developers: the release workflow can sign AxKit.exe for Windows (Authenticode) through Microsoft's Azure Artifact Signing, so that Windows' Smart App Control accepts an update instead of blocking it ("An Application Control policy has blocked this file" on 3.7.1 and 3.7.4): a job of its own signs in to Azure with the run's OpenID Connect token as an identity that holds the signer role alone, signs with a certificate Microsoft issues for each signing in the maintainer's verified name, and zips nothing Windows does not find validly signed. The repository variable AZURE_CERTIFICATE_PROFILE is the switch, off until the maintainer's identity validation and the certificate profile are through, and a release made with it off says in its notes that the program is unsigned (docs/axkit/code-signing.md; publish.ps1 -NoZip and -ZipOnly; ReleaseWorkflowTests keeps the order, the switch and the pinned actions). docs/axkit/development-environment.md lists every tool of the development computer, how it is installed, signed in and checked, and the order to set a new computer up in.
• For developers: axList, lists to remember as plain Markdown files, is planned as an app of its own beside axTask: its specification, user guide and NVDA test plan are in docs/axlist/, brought from the branch where it was first drafted in 2026-10 and brought up to the bundle as it is; nothing of it is built. The draft's code is kept as the tag archive/axlist-draft.
• For developers: docs/feature_requests/ is an axTask folder, the maintainer's feature requests and bugs as items of the lists Features and Bugs (axtask docs\feature_requests opens it); its README says how an item moves into the plan, a spec and the code. GitHub's issues wait until there are users.

Built with the .NET SDK 10.0.403.

axKit is a set of personal tools shared as they are, not a product or a service. Installing this release means accepting its licence, https://github.com/KyleKeane/AxKit/blob/v5.0.1/LICENSE, and the reminders in NOTICE.md, https://github.com/KyleKeane/AxKit/blob/v5.0.1/NOTICE.md.

Code signing policy, privacy and governance: https://github.com/KyleKeane/AxKit#code-signing-policy, https://github.com/KyleKeane/AxKit/blob/main/PRIVACY.md and https://github.com/KyleKeane/AxKit/blob/main/GOVERNANCE.md

AxKit.exe in this release carries no Windows signature, and Windows' Smart App Control may refuse it; signed releases are being set up (https://github.com/KyleKeane/AxKit/blob/main/docs/axkit/code-signing.md).