Update the README.

README.md

@@ -1,15 +1,46 @@
 # Dependency graph results as task inputs
 
-## Artifacts
+This repository contains a Gradle build that demonstrates tasks that use dependency resolution results as inputs
+in a configuration cache compatible way.
 
-- Run once
-- Run again, is up-to-date
-- Change dependency graph, changes
-- Change source file, changes
+There are two different kinds of results that can be used by tasks:
 
-## Graph
+- The dependency graph, represented via `ResolvedComponentResult`, which provides access to the components and dependencies in the graph.
+- Artifact metadata, represented via `ResolvedArtifactResult`, which provides access to some details about an artifact in the result.
 
-- Run once
-- Run again, is up-to-date
-- Change dependency graph, changes
-- Change source file, is up-to-date
+The `plugins/` directory contains a plugin implementation that registers two tasks, one that generates a report on the
+dependency graph of the project's runtime classpath, and one that generates a report on the artifacts in the runtime classpath.
+
+The artifact report task (`ReportArtifactMetadataTask`) declares both the artifact metadata and the artifact files as inputs,
+but a task might instead use only the artifact metadata.
+
+This build has configuration caching enabled.
+
+## Artifact metadata
+
+To try the artifact report, run:
+
+`> ./gradlew artifact-report --console verbose`
+
+This builds the artifacts, then generates the report. It also writes a configuration cache entry.
+
+Some things to try:
+
+- Run this again. The configuration cache entry is reused and the report is up-to-date.
+- Change a library source file, for example in `libs/lib2/`. The configuration cache entry is reused, the artifacts are rebuild and the report generated again. The artifact files are declared as inputs to the report task so when their content changes the report is run again. 
+- Change the dependency graph, for example by changing `libs/lib2/build.gradle.kts`. In this case, the configuration cache entry is discarded because one of its inputs have changed, and the report is generated again.
+
+## Dependency graph
+
+To try the dependency graph, run:
+
+`> ./gradlew graph-report --console verbose`
+
+This generates the report and writes a configuration cache entry. Notice in this case the artifacts are not
+built, as they are not available via `ResolvedComponentResult` and so do not form an input to the report task.
+
+Some things to try:
+
+- Run this again. The configuration cache entry is reused and the report is up-to-date.
+- Change a library source file, for example in `libs/lib2/`. The report is up-to-date because the artifacts are not an input to the report task. 
+- Change the dependency graph, for example by changing `libs/lib2/build.gradle.kts`. In this case, the configuration cache entry is discarded because one of its inputs have changed, and the report is generated again.