[docs] - Add Declarative Automation concept page (DOC-321)

docs/content/concepts/automation.mdx

@@ -41,18 +41,16 @@ You can use sensors to run a job or materialize an asset in response to specific
 
 You can also use sensors to act on the status of a job run. Refer to the [Sensors documentation][sensors] to learn more.
 
-### Auto-materialize policies <Experimental />
+### Declarative Automation <Experimental />
 
-If you want a declarative approach to automating your pipelines, Auto-materialize policies (AMP) may be a good fit. AMPs allow you to assign policies to assets and let Dagster determine the best approach to keeping assets up-to-date while adhering to those policies.
+Declarative Automation allows you to automatically materialize assets when specified criteria are met. Using Declarative Automation, you could update assets:
 
-For example, with AMPs, you can update assets based on:
+- When the asset hasn't yet been materialized
+- When an asset's upstream dependency has been updated
+- After an asset's parents have been updated since a cron tick
+- ... based on your own custom conditions
 
-- Whether an upstream dependency has been updated
-- Whether an upstream dependency has the latest data from its dependencies
-- Whether a materialization has occured since the last tick of a cron schedule
-- ... and more
-
-AMPs are declared on an asset-by-asset basis, but can be applied to multiple assets at once. Refer to the [Auto-materializing Assets documentation][auto-materialize-policies] to learn more.
+Materialization conditions are declared on an asset-by-asset basis. Refer to the [Declarative Automation documentation][declarative-automation] to learn more.
 
 ### Asset Sensors <Experimental />
 
@@ -83,7 +81,7 @@ The following cheatsheet contains high-level details about each of the automatio
     <tr>
       <th
         style={{
-          width: "20%",
+          width: "15%",
         }}
       >
         Method
@@ -175,13 +173,13 @@ The following cheatsheet contains high-level details about each of the automatio
     </tr>
     <tr>
       <td>
-        <a href="/concepts/assets/asset-auto-execution">
-          Auto-materialize policies
+        <a href="/concepts/automation/declarative-automation">
+          Declarative Automation
         </a>
       </td>
       <td>
-        Automatically materializes an asset or selection of assets when
-        specified criteria (ex: upstream changes) are met
+        Automatically materializes an asset when specified criteria (ex:
+        upstream changes) are met
       </td>
       <td>
         <ul
@@ -251,4 +249,4 @@ The following cheatsheet contains high-level details about each of the automatio
 
 [asset-sensors]: /concepts/partitions-schedules-sensors/asset-sensors
 
-[auto-materialize-policies]: /concepts/assets/asset-auto-execution
+[declarative-automation]: /concepts/automation/declarative-automation

docs/content/concepts/automation/declarative-automation.mdx

@@ -0,0 +1,182 @@
+---
+title: "Declarative Automation | Dagster Docs"
+description: "Dagster can automatically materialize assets when criteria are met, enabling a declarative approach to asset materialization."
+---
+
+# Declarative Automation
+
+<Note>
+  This feature is currently <strong>experimental</strong>.
+</Note>
+
+Dagster can automatically materialize assets when criteria are met, enabling a declarative approach to asset materialization. Instead of defining explicit workflows to materialize assets, you describe the conditions under which they should be materialized and let the system kick off runs in response.
+
+Declarative Automation includes pre-built conditions to handle common use cases, such as on a periodic schedule or whenever an upstream dependency updates, but conditions can also be customized.
+
+---
+
+## Benefits
+
+Using Declarative Automation helps you:
+
+- Define the precise conditions under which an asset should be materialized
+- Define all logic related to an asset in a single place
+- Avoid thinking about specific workflow boundaries
+
+---
+
+## Prerequisites
+
+Before continuing, you should be familiar with:
+
+- [Asset definitions](/concepts/assets/software-defined-assets)
+- [Sensor definitions](/concepts/partitions-schedules-sensors/sensors)
+- [Code locations](/concepts/code-locations)
+
+---
+
+## How it works
+
+Declarative Automation is an automation method that kicks off runs when criteria are met and contains two main components:
+
+- **An automation condition (<PyObject object="AutomationCondition" />**), which represents when an individual asset should be executed.
+- **A sensor** which evaluates each <PyObject object="AutomationCondition" /> and launches runs in response to their status.
+
+### Automation conditions
+
+Dagster provides two pre-built conditions:
+
+<table
+  className="table"
+  style={{
+    width: "100%",
+  }}
+>
+  <thead>
+    <tr>
+      <th
+        style={{
+          width: "25%",
+        }}
+      >
+        Name
+      </th>
+      <th
+        style={{
+          width: "40%",
+        }}
+      >
+        Description
+      </th>
+      <th>Useful for</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <strong>AutomationCondition.eager()</strong>
+      </td>
+      <td>
+        This condition will materialize an asset:
+        <ul>
+          <li>If the asset has never been materialized before, or</li>
+          <li>
+            When the asset's parents update, as long as none of the parents are
+            currently missing or have an update in progress
+          </li>
+        </ul>
+      </td>
+      <td>
+        <ul
+          style={{
+            marginTop: "0px",
+          }}
+        >
+          <li
+            style={{
+              marginTop: "0px",
+            }}
+          >
+            Automatically propagating changes through the asset graph
+          </li>
+          <li>Ensuring assets remain up-to-date</li>
+        </ul>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <strong>AutomationCondition.cron(cron_schedule)</strong>
+      </td>
+      <td>
+        This condition will materialize an asset once per cron schedule tick,
+        after all of its parents have been updated since the tick
+      </td>
+      <td>
+        Regularly updating an asset without worrying about the specifics of how
+        its parents update
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Automation conditions can be set on the <PyObject object="asset" decorator /> decorator or on an <PyObject object="AssetSpec" />:
+
+```python
+from dagster import AssetSpec, AutomationCondition, asset
+
+@asset(automation_condition=AutomationCondition.eager())
+def my_eager_asset(): ...
+
+AssetSpec("my_cron_asset", automation_condition=AutomationCondition.cron("@daily"))
+```
+
+The core <PyObject object="AutomationCondition" /> framework is extremely flexible, allowing you to build custom conditions from the ground up. Refer to the [Customizing automation conditions guide](TODO) for more information.
+
+### Sensors
+
+By default, a single sensor with the name `default_automation_condition_sensor` will be available for each code location, and will monitor all assets within that location. To use multiple sensors or change the properties of the default sensor, refer to the <PyObject object="AutomationConditionSensorDefinition" /> documentation.
+
+For an automation condition sensor to run, it must be turned on and an active [`dagster-daemon` process](/deployment/dagster-daemon) must be running. If you used [`dagster dev` to start the Dagster UI/webserver](/guides/running-dagster-locally), the daemon process will be automatically launched alongside the webserver.
+
+After these criteria are met, the sensor's evaluation history will be visible in the UI:
+
+<TODO>SCREENSHOT</TODO>
+
+You'll also be able to view a detailed history of each asset's evaluations on the asset's [**Asset Details** page](/concepts/webserver/ui#asset-details). This allows you to see why an asset was or wasn't materialized at different points in time:
+
+<TODO>SCREENSHOT</TODO>
+
+---
+
+## Getting started
+
+To use Declarative Automation, you'll need to enable the automation condition sensor in the Dagster UI:
+
+1. Navigate to **Deployment > Sensors**
+2. Locate the desired code location.
+3. Toggle the `default_automation_condition_sensor` sensor on to enable it.
+
+From here, you can:
+
+- Define custom automation conditions
+- See a history of each evaluation for this sensor
+- Navigate to individual assets to see a history of their evaluations
+
+---
+
+## Related
+
+<ArticleList>
+  <ArticleListItem
+    title="Asset definitions"
+    href="/concepts/assets/software-defined-assets"
+  ></ArticleListItem>
+  <ArticleListItem
+    title="Automation"
+    href="/concepts/automation"
+  ></ArticleListItem>
+  <ArticleListItem
+    title="Schedules"
+    href="/concepts/automation/schedules"
+  ></ArticleListItem>
+</ArticleList>