> Markdown twin of https://adna.network/how/
> Index: https://adna.network/llms.txt · Full corpus: https://adna.network/llms-full.txt
> State is a build-time snapshot generated 2026-08-30 (UTC); nothing here is live.
> Derived from the rendered page — this route has no markdown source.

*[image: Bird's-eye pixel-art desk with glowing module-boxes wired into a left-to-right pipeline of light — aDNA operations]*

# How

The **how/** leg of the aDNA triad covers operational processes — the repeatable workflows that turn knowledge into outcomes. Where [what/](/learn/) holds what a project knows and [who/](/community/) holds who decides, **how/** holds the procedures: the things a person or an agent runs.

## What belongs in how/

The test is whether the document tells someone *to do something*, in an order, repeatably. A description of the publishing pipeline is how/; an explanation of what a lattice *is* is what/. The distinction matters because it decides where an agent looks: an agent asked to publish this site reads how/ and does not need to load the concept library to do it.

In practice that means three kinds of document — a pipeline (a sequence a machine can run), a kit (a sequence a person runs, with materials), and a lattice definition (a sequence written as a graph, so it can be executed or inspected).

## The three areas

[Publishing How vault content becomes a live documentation site — the transform pipeline, content mapping, and social sharing system.](/how/publishing/)[Workshops Structured workshop kits for teaching aDNA — from beginner vault exploration to advanced lattice design.](/how/workshops/)[Lattice Examples Self-referential lattice definitions that model the processes used to build this vault and site.](/how/lattice-examples/)

## Where to start

If you want to see how this site is produced from a vault, read [Publishing](/how/publishing/) — it is the pipeline running behind the page you are reading. If you are teaching aDNA to a group, start with [Workshops](/how/workshops/). If you want to see a process written as a graph rather than as prose, [Lattice Examples](/how/lattice-examples/) models this vault's own workflows.

## In this vault

Everything in this section is a working example rather than a description of one. The publishing pipeline documented here is the pipeline that built this page; the lattice examples model the campaigns that wrote it. That is the aDNA structure doing its own job — `how/` in a vault holds the procedures that produced the vault, so the documentation and the mechanism cannot drift apart without one of them visibly breaking.