Goal: Make
python3resolve to a real interpreter across PowerShell, cmd, Git Bash, and other shells used by agent tooling on Windows 11, without requiring WSL.Common symptom:
python3 --version→ “Python was not found; run without arguments to install from the Microsoft Store…”Root cause (often): Windows “App execution aliases” stub
python3.exein...\WindowsAppsshadows the real Python.
ATTRIBUTION: thanks to Martin Cleaver https://github.com/mrjcleaver and the Agentics-Foundation https://agentics.org/ -- I took chat notes, and restructured for future reference below.
A lightweight, durable way to capture why an architectural decision was made (not just what was built), so teams can revisit decisions with context instead of re-litigating from scratch.
Tip
ADR = one decision, one file. Keep it durable, searchable, and easy to supersede.
Search for articles...
A role-based, actionable guide for executives, platform maintainers, and delivery teams to move from fragmented tooling to a coherent API lifecycle.
Version: 1.1
Date: 2025-12-23
Source inspiration: A vendor whitepaper on unifying the API lifecycle (adapted and generalized).
Note: Quantitative examples are reproduced as illustrative benchmarks and may not generalize.
graph TD
subgraph G0["Repo controls - Maintainer and Admin"]
G0A["Set roles and permissions<br/>Admin: merge to main<br/>Contributors: no direct push to main"] --> G0B["Protect main branch<br/>Require PRs<br/>Block force-push<br/>Restrict who can push"]
G0B --> G0C["Require reviews<br/>Minimum reviewers<br/>CODEOWNERS optional"]
G0C --> G0D["Require CI checks<br/>Tests, lint, build, security optional"]
G0D --> G0E["Define merge method<br/>Squash or merge-commit or rebase-merge"]DO YOUR OWN DUE DILIGENCE, and... if privacy matters to YOU, then, read below, and choose how you wish to further engage in usage of KIMI, (and derivatives thereof, and/or other MoonshotAI products/services.) -- THIS CONTENT was analyzed straight from their platform/site. (via Claude.)
The complete, systematic breakdown of Unix/Linux permission modes requires enumerating every valid combination, and grouping them into mutually exclusive, collectively exhaustive categories — across all axes:
- Axis 1: File type (1st char)
- Axis 2: Owner / Group / Others permission triplets
- Axis 3: Permission levels (r/w/x combinations)
- Axis 4: Special bits (setuid, setgid, sticky)
- Axis 5: Numerical representation (octal)