# Build state model

The Gradle daemon tracks state for various elements. These are arranged in a hierarchy:

```mermaid
  graph TD

  process["build process"]
  
  session["build session"]
  process --> session
  
  build_tree["build tree"]
  session --> build_tree
  
  build1["root build"]
  build_tree --> build1
  
  project1["root project"]
  build1 --> project1
  
  project2["project"]
  build1 --> project2

Most source code in Gradle is arranged by which part(s) of the build state model it acts on.
This affects the lifecycle of the code and the set of services available for dependency injection.
When working on some source code it is important to be aware of the model it acts on.  

					"jvm-services",
					"kotlin-dsl",
					"kotlin-dsl-integ-tests",
					"language-java",
					"language-jvm",
					"logging",
					"maven",
					"messaging",
					"model-core",
					"model-groovy",
					"persistent-cache",
					"platform-base",
					"platform-jvm",
					"plugin-development",
					"plugin-use",
					"plugins-application",
					"plugins-distribution",

The platforms and modules are defined using a DSL in [settings.gradle.kts](../settings.gradle.kts)

    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "model-core",
    "path": "platforms/core-configuration/model-core",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "model-groovy",
    "path": "platforms/core-configuration/model-groovy",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false

    "testId" : "org.gradle.performance.regression.java.JavaIDEModelPerformanceTest.get IDE model for Eclipse",
    "groups" : [ {
      "testProject" : "largeJavaMultiProject",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.java.JavaIDEModelPerformanceTest.get IDE model for IDEA",
    "groups" : [ {
      "testProject" : "largeJavaMultiProject",