What is Liddr HANDBOOKS?

HANDBOOKS is the living-documents product inside Liddr. It generates long-form reference documents — runbooks, onboarding guides, training material, architecture references — from your knowledge graph, with every claim cited and the document versioned as things change.

How is a handbook different from a wiki page?

A wiki page is written once and goes stale. A handbook is generated from your live knowledge, cited to its sources, and re-generated with a what-changed summary as the underlying knowledge changes — so it stays current.

Where does the content come from?

From your own connected sources through the Liddr knowledge graph. Handbooks are grounded and cited, and access is governed to the individual document — nothing is invented.

    app.liddr.ai/handbooks — 24 living documents · 3 updated today
    MOD.02 // HANDBOOKS
  

LIDDR_

      /platform
      /know
      /handbooks
      /forge
      /signal
      /docs
      /pricing
      /compare
      /demo
    

TRY LIDDR

MOD.02 // HANDBOOKS

Living documents.

Evergreen reference, runbooks, onboarding, and training — generated from your knowledge, cited to source, and kept current automatically. The documentation you always meant to write, that never goes stale.

GENERATE A HANDBOOK SEE THE TYPES

handbook · on-call runbook — payments

RUNBOOK · v4 · REGENERATED 2H AGO

Payments — On-Call Runbook

Escalation path routes to the payments on-call, then the platform lead1. The webhook consumer is the most common failure point; restart is safe and idempotent2.

Rollbacks follow ADR-51; protobuf schema changes require a two-step deploy3.

1 RUNBOOK · escalation 2 INC-101 postmortem 3 ADR-51

            ✓ EVERY CLAIM CITED
            WHAT CHANGED: +escalation, ADR-51
          

Documents that write — and update — themselves.

FN.01

Generated from your graph

Start from a topic, not a blank page. Liddr drafts the document from your own connected knowledge — structured, complete, and in your context.

FN.02

Cited & verified

Every claim links to its source and is faithfulness-checked before it lands — a reference you can trust, not a confident guess.

FN.03

Living, not static

As the underlying knowledge changes, the handbook regenerates — with a version history and a "what changed" summary. It never goes stale.

ARCHETYPES // ONE ENGINE, MANY SHAPES

Every document your team needs

DOC.01

Reference

Authoritative "how this works" documents for a system, service, or domain.

DOC.02

Runbooks

Operational procedures — escalation, recovery, and on-call — grounded in real incidents.

DOC.03

Onboarding

Get a new hire productive fast — the context, systems, and "why" in one place.

DOC.04

Training

Explain a process or practice, teach-first, with examples drawn from your work.

DOC.05

Architecture

The decisions and their rationale — so the "why" outlives the people who made it.

DOC.06

Custom

Describe the document you need and its shape — Liddr generates to your spec.

Documentation that keeps itself current.

REQUEST ACCESS BACK TO PLATFORM

← LIDDR_
      KNOW
      HANDBOOKS
      FORGE
      SIGNAL
    
© 2026 · THE ARCHITECTURE OF THOUGHT