### Platforms

The platforms and their architecture modules are:

#### Core automation platform

This is a general-purpose automation platform which takes care of the efficient definition and execution of work, such as tasks.
This platform is agnostic to what exactly the purpose of the work is.
It might be creating an application, setting up development environments, orchestrating deployments, running simulations, etc.

```

## Platforms

### Core automation platform

This is a general-purpose automation platform which takes care of the efficient definition and execution of work, such as tasks.
This platform is agnostic to what exactly the purpose of the work is.
It might be creating an application, setting up development environments, orchestrating deployments, running simulations, etc.

There are several different types of requests, such as a request to run a set of tasks, or to query a tooling model, or to stop.
Some requests will require that the build is configured and maybe some work executed, and other requests might not.

See [Build execution model](build-execution-model.md) for more details.

### Build state model

As Gradle executes, it acts on various pieces of the build definition, such as each project in the build.

- Tooling API client. This a library that is embedded into applications, such as IDEs or CI agents, that allows them to act as a Gradle client.
- Worker processes. Long-running daemon processes that the Gradle daemon starts to run specific kinds of work, such as compilation or test execution.

The diagram below shows the relationships between the different processes:

```mermaid
    graph LR

    name = "Warmup EC2 Agent"
    id("Util_WarmupEc2Agent")

    vcs.useAbsoluteVcs(VersionedSettingsBranch.fromDslContext().vcsRootId())

    features {
        freeDiskSpace {
            // Lower the limit such that the agent work directories aren't cleaned during the AMI baking process
            requiredSpace = "100mb"
        }
    }

    params {
        param("defaultBranchName", "master")

a
an
and
are
as
at
be
but
by
for
if
in
into
is
it
no
not
of
on
or
such
that
the
their
then
there
these
they
this
to
was
will

 * This form extends CreateForm to include fields necessary for updating existing scheduler entries,
 * including tracking information for optimistic locking.
 * Schedulers define automated jobs such as crawling and system maintenance tasks.
 *
 */
public class EditForm extends CreateForm {

    /**
     * Creates a new EditForm instance.
     */
    public EditForm() {
        super();
    }

import java.util.Arrays;

/**
 * Entity class representing a request parameter with a name and associated values.
 * This class encapsulates HTTP request parameters that can have multiple values,
 * such as query parameters, form parameters, or other request-related data.
 *
 * <p>This class is immutable and thread-safe. Once created, the parameter name
 * and values cannot be modified.</p>
 *
 */

 * of SSO authentication and authorization processes. It extends FessSystemException
 * to provide consistent error handling within the Fess system for SSO-related
 * processing failures such as token validation errors, communication failures
 * with SSO providers, or configuration issues.
 */
public class SsoProcessException extends FessSystemException {

    private static final long serialVersionUID = 1L;

 */
package org.codelibs.fess.dict;

/**
 * Abstract base class for all dictionary items in the Fess search system.
 * Dictionary items are used to store entries in various dictionaries such as
 * synonyms, kuromoji, protwords, and stopwords dictionaries.
 *
 */
public abstract class DictionaryItem {
    /** The unique identifier for this dictionary item */
    protected long id;

    /**