E11 Alloy
Knowledge as a build artifact.
Alloy is a versioned library of markdown documents that teach AI agents how to build software a particular way, plus the pipeline that produces, validates, measures, and distributes those documents. The thesis is simple: treat knowledge the way a compiler treats code. Every doc is machine-validated before it can merge, stamped with the exact commit it was derived from, mechanically declared stale when that commit's files change, and served to agents through a versioned contract they pin like a dependency.
🚀 New here? Start with Why Alloy - what it is, and why a docs folder is not enough. Two minutes.
This guide is for a team standing Alloy up on their own repo: onboarding a codebase Alloy has never seen, establishing a corpus specific to it, and keeping that corpus honest as the code moves. You consume the tooling as published packages - you do not need access to Alloy's own source to follow along.
Start here
Adopting Alloy on your repo? This is the path. → The tutorial - survey your repo, review the draft, adjust it, commit, run a campaign to establish the corpus, and add curated docs. Seven runnable steps, end to end.
Never installed the tooling? → Installation - the registry prerequisite and the consumer paths.
Want the vocabulary first? → Glossary - source, unit, kind, view, provenance, drift, coverage, spoke, curated.
Want the mechanism, not the how-to? → Concepts - the two loops, discovery, extraction and the gate, provenance and drift, views and coverage.
Table of contents
Getting started
The tutorial - stand up Alloy on your repo
- Overview
- 1 - Survey your repo
- 2 - Review the draft
- 3 - Understand the draft
- 4 - Adjust
- 5 - Commit and install
- 6 - Run a campaign
- 7 - Add curated docs