# Calculate approved as-of Covenant projection

Calculate approved as-of Covenant projection

## When to use it

Calculate the approved state at a selected date. Pending changes stay outside the approved projection. Changing the date or editing the review requires a fresh projection rather than reusing the previously displayed result.

## Add and configure

1. Add **Calculate approved as-of Covenant projection** from the workflow step picker.
2. Give the step a recognisable name and connect its required inputs.
3. Set the options below. Nested names identify fields within an object or a list item.
4. Validate the recipe, inspect the test result, then run it on the intended data.

The step identifier used in the editor’s code view is `covenant_project`.

## Settings

| Setting | Accepted value | Required | Default | What it controls |
| --- | --- | --- | --- | --- |
| As Of (`as_of`) | string; format date | Yes | Not specified | Date for which to project eligible reviewed terms. |

## Inputs and outputs

| Direction | Port | Content | Required | Multiple records |
| --- | --- | --- | --- | --- |
| Inputs | `in` | records | Yes | Yes |
| Outputs | `out` | records | Yes | Yes |

## Effects, testing, and recovery

Writes information inside Strive.

The declared preview behaviour is to skip this step. Configuration can affect preview behaviour; HTTP GET is a notable exception. Read [dry runs](/docs/workflows/dry-runs) before using a preview with live connections.

Duplicate prevention uses content identity. The step declares safe replay for its supported recovery path.

### Execution bounds

| Limit | Declared bound |
| --- | --- |
| max input bytes | 6291456 |
| max output bytes | 6291456 |
| max records | 100 |
| memory mb | 256 |
| timeout seconds | 120 |

Recovery policy: ambiguous outcome: manual_resolution; cancellation: cooperative; errors: invalid_input, invalid_config, quota_exhausted, timeout, recovery_unsafe, upstream_rejected; max attempts: 1.

## Example: Empty branch

Step settings:

```json
{
  "as_of": "2026-01-01"
}
```

Expected output for this example:

```json
[]
```

## Check the result

Inspect the selected run’s status, counts, errors, and output records. An empty collection can be a valid result, and a completed step can contain per-record failures where the step defines that behaviour. Check the next step’s expected record shape before publishing or delivering the result.