Explanation
Explanation pages teach why. Start with architecture if you are building a product; infrastructure if you are shaping the environment.
Windows
-
ClearType — subpixel font smoothing; GDI vs Avalon/DirectWrite setting planes; multi-monitor as a corollary
-
Windows color management pipeline — ICM/WCS, VCGT/MHC2, ACM, and why calibration vendors ship their own loaders
Languages
-
Language recommendations — a small set that culls the ecosystem (D, Rust, TypeScript, Julia, Lisp/Haskell)
Internet Architecture
-
Internet Architecture — systems altitude for public reference identity
-
Internet Reliability — usability + reference durability (not packet uptime alone); peer to product SPE Architecture on the docs hub
Architecture
-
Software Product Essentials — shared framework for shippable software
-
Auxiliary features — Help, updates, diagnostics, connectivity templates
-
Delivery classes — desktop / web / mobile matrices
Infrastructure
Toolchain management, shells, WSL, IaC, MCP/studio install strategies, abstract playbooks (PlayTime / Scriptbook / Equivalence Engine), OS install concurrency, Git’s file-shaped change model, API key vs token, Google Cloud projects as OAuth boundaries, Access in front of static sites (including how GitHub org membership is checked), and related topics live under Explanation → Infrastructure in the nav.
Featured agent / studio topics:
AI literacy
-
Curated watching (AI) — mandatory / high-signal videos (Sophontic geometric reasoning interview and later entries)
Programming
-
Curated watching (programming) — Armstrong, WordPress governance study, Postgres history, …
Open source / licensing posture
-
Ecosystem failures and successes — history book for CSL (xkcd Dependency, Heartbleed, left-pad, WordPress, Postgres)
Web publishing
-
What SEO does for a public website — how rendered content, metadata, links, sitemap and robots rules, structured data, performance, sitelinks, and Search Console support discoverability