Handbooks

Learn · handbook

▶Start here

You are here: Learn → Handbooks This type is for you if: you need a whole domain — multi-page reference you return to (not a single how-to). Not this? Guides = one topic · Reference = this site’s authoring stack · Playbooks = phased execution.

Handbooks are durable, multi-page reference — framework primitives, architecture, and how to ship.

Start here

Laravel · CodeCanyon Mental models for vendor-safe customizations — ZajModules, three-tier admin, schema, and version management.

AI agents · Agent framework TypeScript agent framework — overview → concepts → architecture → agents → workflows → deployment.

Note

Handbooks vs. Reference. Reference documents this site’s authoring stack. Handbooks document third-party frameworks and domains your products run on.

Handbook spine

Every engine handbook follows the same spine — read top to bottom the first time, or jump to the page you need:

1. 1

   Overview

   What it is, who it’s for, when to reach for it, and the mental model.

2. 2

   Concepts

   Each core primitive defined crisply — the vocabulary you’ll reuse everywhere.

3. 3

   Architecture

   How the pieces fit and how a request flows end to end.

4. 4

   Building agents

   The minimal end-to-end path to a working agent.

5. 5

   Workflows

   Multi-step orchestration, branching, and human-in-the-loop.

6. 6

   Deployment

   Dev → build → ship, deployer targets, and production concerns.

The same six-page spine for every engine, so you always know where to look.