### Application Discovery { #application-discovery }

The build cache has anonymous read access, so you don't need to authenticate in order to use it. You can use a different build cache node by specifying `-Ddevelocity.edge.discovery=false -DcacheNode=us` for a build cache node in the US or `-Ddevelocity.edge.discovery=false -DcacheNode=au` for a build cache node in Australia.

    "crossVersionTests": false
  },
  {
    "name": "build-discovery",
    "path": "platforms/core-runtime/build-discovery",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "build-discovery-impl",
    "path": "platforms/core-runtime/build-discovery-impl",
    "unitTests": false,
    "functionalTests": false,

### Descoberta da Aplicação { #application-discovery }

### Виявлення застосунку { #application-discovery }

### Anwendungserkennung { #application-discovery }

### Обнаружение приложения { #application-discovery }

### Descubrimiento de la aplicación { #application-discovery }

### Uygulama Keşfi { #application-discovery }

- ACCEPTED on 2023-12-01

## Context

In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.

We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:

* They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made