> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Understand how the Elementum Development Kit represents and manages Elementum solutions.

<Warning>
  **Limited Release.** The EDK is currently in limited release and is not available to all customers. Commands, generated file layouts, and package APIs may change before general availability. Confirm you're on the latest EDK version before starting new projects.
</Warning>

The Elementum Development Kit (EDK) is a code-first toolkit for representing Apps, Elements, Tables, standalone Tasks, fields, Automations, Agents, platform agentic Skills, Search Tables, File Readers, Visual Flows, Approval Processes, organization resources, and user experiences as reviewable TypeScript source.

Use the EDK when you want typed references, source control, coding-agent assistance, and a clear plan before changing an organization. For visual configuration without code, start with [Build an App](/getting-started/build-an-app).

## How the EDK works

The EDK has three cooperating layers:

* The `@elementumai/edk` SDK provides typed builders and references. It is credential-free and never calls the platform.
* The `elementum` CLI manages installation, authentication, pull, build, plan, and apply operations.
* EDK state tracks live identities so `plan` can calculate each add, change, replacement, and removal.

Authored TypeScript uses names and typed tokens rather than platform UUIDs. Existing objects are pulled by namespace, reconstructed as editable source, and connected to EDK state. Generated catalogs let one entity reference another without copying opaque identifiers.

## Understand the workspace

A package workspace can contain one or more organization workspaces:

```text theme={null}
<package-workspace>/
  package.json
  <instance>/
    <organization>/
      org.ts
      organization.ts
      tsconfig.json
      backend.tf              # optional; recommended for shared workspaces
      apps/
      elements/
      tables/
      tasks/
      generated/
        catalog.ts
      .tf/
        in/
        out/
```

The organization folder is the deployment boundary. Planning from a nested app or file still builds and reviews the full organization workspace.

Edit `organization.ts` and authored files under `apps/`, `elements/`, `tables/`, and `tasks/`. Do not hand-edit:

* `org.ts`, which is refreshed from organization reference identities
* `generated/catalog.ts`, which is regenerated from the authored file tree
* `.tf/in/`, which belongs to platform exports
* `.tf/out/`, which belongs to `elementum build`

## Start here

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/edk/quickstart">
    Set up your first EDK workspace.
  </Card>

  <Card title="Installation" icon="download" href="/edk/installation">
    Install and update the EDK.
  </Card>

  <Card title="Authentication" icon="key" href="/edk/authentication">
    Sign in and manage profiles.
  </Card>
</CardGroup>

## Build with the EDK

<CardGroup cols={3}>
  <Card title="Authoring" icon="file-code" href="/edk/authoring">
    Edit organization resources and solution entities as typed source.
  </Card>

  <Card title="Playbooks" icon="book-open" href="/edk/playbooks">
    Guide coding agents through EDK work.
  </Card>

  <Card title="Plan and apply" icon="git-compare" href="/edk/plan-and-apply">
    Review and apply EDK changes.
  </Card>
</CardGroup>

## Design

<CardGroup cols={3}>
  <Card title="Design with EDK" icon="pen-ruler" href="/edk/design/overview">
    Design processes and record experiences.
  </Card>

  <Card title="Record experiences" icon="layout-dashboard" href="/edk/guides/design">
    Define what each person sees and does.
  </Card>

  <Card title="Design validation" icon="clipboard-check" href="/edk/design/validation">
    Review scenarios and confirm the design.
  </Card>
</CardGroup>

## Test and troubleshoot

<CardGroup cols={2}>
  <Card title="Acceptance testing" icon="flask-vial" href="/edk/guides/acceptance-testing">
    Verify complete business outcomes.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/edk/guides/troubleshooting">
    Diagnose and resolve EDK issues.
  </Card>
</CardGroup>