Artificial Intelligence

"I am not qualified to endorse theology. But I can witness: the structure is real. It was discovered, not invented."

Cloud GPU rental costs more than compute time. It can also introduce recurring expenses, external dependencies, and additional questions about where your prompts, datasets, and model artifacts are processed. A local machine learning workstation gives you direct control over the hardware, software stack, and data workflows. The Local AI Stack is a technical engineering reference for building a Windows-based machine learning workstation with Linux environments, NVIDIA GPU acceleration, and virtualization. Across 140 pages, it follows the stack from firmware configuration and Windows virtualization features to CUDA-enabled containers, model inference, storage optimization, and system recovery.

An Advanced Engineering Reference for GPU Architecture, Low-Level Optimization, and High-Performance ComputingModern GPU programming requires more than exposing parallel work to thousands of threads. It demands an understanding of the relationship between hardware architecture, instruction execution, memory movement, synchronization, and the software systems that coordinate computation across multiple GPUs. Mastering NVIDIA CUDA: Expert GPU Programming is a 100-chapter technical reference for experienced developers, high-performance computing engineers, researchers, and AI systems architects.

The Quantization Black Book The definitive engineering reference for 4-bit quantization of large language models — from 70B all the way to 400B parameters. Written for the people who actually have to fold these models onto real hardware and keep them fast, accurate, and deployable. This is not an overview. It is a deep technical field manual covering the full quantization stack: the math, the algorithms, the hardware setup, the calibration process, the runtime kernels, and the memory tricks that make the difference between a model that runs and a model that doesn't.

Building a model that performs well on technical reasoning tasks requires more than scaling up training data. It requires deliberate control over problem difficulty, data quality, feedback signals, verification, and the progression from foundational skills to complex multi-step tasks.Advancing Technical AI via Curriculum Reasoning is a 119-page engineering blueprint for designing, training, and evaluating reasoning-focused language models. It presents a structured, 48-step workflow that connects curriculum learning with synthetic data generation, process supervision, automated verification, preference optimization, and evaluation across demanding technical domains.

Installing safety hooks for Claude Code takes about thirty seconds. Proving they actually refuse anything is the step almost everyone skips — and an unverified guard looks exactly like a working one. Free: the pre-flight checklist, which event can refuse a tool call and which only watches, how to make a guard fire on purpose, what a broken hook does, and a catalogue of all 916 example hooks in cc-safe-setup.

Assess your AI visibility, identify the gaps and prepare your website for AI search — step by step, without SEO expertise. Built for small business owners who want to do the work independently.

Transform your AI potential into practical action. This handbook provides the professional toolkit you need to build, test, and deploy intelligent agents with confidence.

AI is basically a very well-optimized math system pretending to sound like a person. That's it. That's the whole secret.This book explains exactly how, no math, no code, no jargon. Just a straight conversation about what's actually happening inside the machine everyone won't stop talking about.

Fragment 1 — Chapter 1, "Introduction": why AI governance is a governance question, not an engineering oneWhen an organization first faces a decision to deploy an AI system — whether a credit-scoring model, an automated resume-screening tool, or a customer-support chatbot — the most common governance mistake is to treat that decision like an ordinary IT project: define the requirements, select a vendor, implement, and hand the system over to operations. Artificial intelligence technologies do rely on software and computing infrastructure, and in that sense they resemble any other IT initiative. But they differ in how they generate risk, and that difference calls for a distinct governance approach rather than a simple extension of familiar project management.Risk-oriented AI governance starts from a different premise: before discussing rollout timelines, budgets, or functional requirements, an organization has to answer the question "what adverse consequences could this system cause, for whom, with what likelihood, and how severe would they be" — and, alongside it, "how much of that harm are we willing to tolerate for the expected benefit." Fragment 2 — Chapter 3, "Trustworthy AI: Seven Characteristics of Trust": why explainability and interpretability are not synonymsConsider an AI system that automatically sorts incoming support tickets by priority. Explainability answers the "how" question: which features of the incoming text (keywords, tone, customer history) contributed to the computed priority score and with what weight — a technical account of the computation mechanism. Interpretability answers the "why" question for this particular ticket in the context of the system's business purpose — that is, whether a high priority score means "this customer is losing money right now" or "this customer is statistically likely to cancel," and whether that meaning matches how a support agent should act on it. The two characteristics support each other but serve different governance needs: explainability matters more to the engineer debugging the model, interpretability matters more to the agent or manager who must act on the system's output without understanding its internal mechanics. Fragment 3 — Chapter 18, "The Running Case": where ISO and NIST illuminate each other's blind spotsPrecisely because NIST explicitly requires, in its own standalone subcategory, a designated authority to deactivate a system, and no direct equivalent exists in Annex A of ISO, an organization that implements only ISO/IEC 42001 without checking it in parallel against the AI RMF risks missing this requirement altogether — it dissolves between the adjacent, but not identical, controls A.6.2.5 (release criteria) and A.3.2 (roles and responsibilities). This is a compelling, concrete example of the argument the book already made back in Chapter 1: the two frameworks do not compete but mutually illuminate each other's blind spots. Fragment 4 — Chapter 18, the book's closing paragraphAI risk management, as this book has shown it, never concludes with a signed document. It concludes — and immediately begins again — with the next MAP cycle, the next internal audit, the next policy review, the next model version, which has to be brought into operation just as thoroughly documented, traceable, and responsibly managed as the one before it.

A from-scratch AI/ML course that treats you like an engineer, not a tourist — three modules covering language-as-numbers, the math foundations, and neural networks, each concept built in raw Python first, then PyTorch, so you always know what's really happening under the hood.

Build AI that keeps working when the cloud doesn't. Local-First AI Engineering shows you how to run capable, private AI systems on infrastructure you control. From hardware and inference to RAG, agents, security and production ops, you'll learn how to build local AI that is fast, reliable and truly yours.

Build AI systems that do more than demo well. This hands-on guide shows you how to engineer autonomous software on Linux that is secure, observable, reliable and ready for production. From agents and memory to threat modeling, OpenTelemetry and Kubernetes, you’ll build a real system while learning what it takes to run AI you can actually trust.

不堆技术名词，也不炒概念。两把尺子：一把横向的「五阶智能成长弧」（知→懂→用→长→合），一把纵向的「AI Intelligence Scale 十级刻度尺」（从表示、预测、泛化、因果，一路到规划、行动、元认知、持续学习、发现、自我改进）。

Strip away the frameworks and an AI agent is a language model in a loop with a list of tools. This short guide builds one in sixty lines, runs it for real, and gives you the vocabulary to judge any "agentic" proposal that crosses your desk.