diff --git a/spec/LOCKFILE.md b/spec/LOCKFILE.md
new file mode 100644
index 0000000..a3fce32
--- /dev/null
+++ b/spec/LOCKFILE.md
@@ -0,0 +1,56 @@
+# Lockfile
+
+In order to get consistent installs across machines, package managers need more information than the dependencies configured in `package.json`. Package managers need to store exactly which versions of each dependency were installed.
+
+For storing this information, the `dependencies-lock.yaml` file is used in the root of the project. A simple lockfile looks like this:
+
+```yaml
+checksums:
+  package-1:
+    1.0.3: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0
+  package-2:
+    2.0.1: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0
+  package-3:
+    3.1.9: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0
+  package-4:
+    4.5.1: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0
+registry: https://registry.npmjs.org
+resolutions:
+  ied:
+    alexanderGugel/ied#2.3.4: alexanderGugel/ied#373c7fa787e486438a998b4b4574ac5684d42e5f
+  package-1:
+    ^1.0.0: 1.0.3
+  package-2:
+    ^2.0.0: 2.0.1
+  package-3:
+    ^3.0.0: 3.1.9
+  package-4:
+    ^4.0.0: 4.5.1
+    ^4.5.0: 4.5.1
+```
+
+## `dependencies-lock.yaml` structure
+
+The lockfile is a YAML file with sorted keys.
+
+### `resolutions`
+
+The resolutions property maps fuzzy dependencies to exact ones.
+
+### `checksums`
+
+Optional. Contains checksums of packages.
+
+### `registry`
+
+Contains the registry that was used to resolve the dependencies.
+
+## Current package only
+
+During install package managers only use the top-level dependencies lockfile and ignore any lockfiles that exist within dependencies. The top-level `dependencies-lock.yaml` file includes everything package managers need to lock the versions of all packages in the entire dependency tree.
+
+## Check into source control 
+
+All `dependencies-lock.yaml` files should be checked into source control (e.g. git or mercurial). This allows package managers to install the same exact dependency tree across all machines.
+
+Framework and library authors should also check `dependencies-lock.yaml` into source control. Even when published, `dependencies-lock.yaml` file won’t have any effect on users of the library.