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

# Deployment and feedback loop

> Configure stages 8 and 9 for the project type, and record actionable post-delivery feedback.

Deployment and observability requirements in the nine-stage workflow depend on the project type. Libraries, CLIs, internal scripts, and online services should not be forced onto the same path.

## Stage configuration

```json theme={null}
{
  "deploymentMode": "required",
  "observabilityMode": "feedback-only"
}
```

| Field | Value | Meaning |
| - | - | - |
| `deploymentMode` | `required` | The deployment stage must be completed |
| | `optional` | Run it when the project has a deployment target |
| | `none` | The project has no deployment stage |
| `observabilityMode` | `runtime` | Runtime metrics, logs, or alerts and a feedback loop are required |
| | `feedback-only` | Runtime observability is not required, but the feedback log is still maintained |
| | `none` | Stage 9 does not apply |

## Record feedback

```bash theme={null}
npx @caesarlo/sdlc-harness feedback log \
  --source "support-ticket-182" \
  --severity S2 \
  --observation "Users cannot retry safely after checkout times out" \
  --disposition Actioned \
  --detail "Created M2-CHECKOUT-004"
```

[See the `feedback log` options →](/sdlc-harness-docs/reference/command-feedback#log)

Severity values are `S1`, `S2`, `S3`, and `S4`. Disposition values are `Actioned`, `Deferred`, `Declined`, and `Monitoring`. For `Deferred` and `Declined`, explain the reason in `detail`.

The command writes a new entry at the top of `docs/product/feedback-log.md`. You can also edit the file manually, but the `[feedback-log]` check in `validate` checks the date, source, observation, severity, and disposition.

## Return from feedback to development

```mermaid theme={null}
flowchart LR
  A["Deploy / release"] --> B["Runtime signal or user feedback"]
  B --> C["feedback log"]
  C --> D{"Disposition"}
  D -->|Actioned| E["New requirement / ADR / feature"]
  D -->|Monitoring| B
  D -->|Deferred / Declined| F["Record the reason"]
```

A feedback entry does not create a feature automatically. For an `Actioned` entry, record the corresponding feature or requirement ID in `detail` to preserve traceability.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.