# DDS — Sample delivery record

Public demonstration. Fictional insurance workflow. No customer data, customer results or confidential files. This is an excerpt, not a full commissioned delivery.

## 1. Observation
The illustrated legacy scenario uses Pending, Open and In progress for the same business state. Teams must reinterpret the labels across screens.

## 2. Decision ADR-001
Use the stable identifier `in_review`; localize its human-readable label. Keep status meaning separate from visual treatment. Do not rely on color alone.

Acceptance: the same identifier means received and awaiting review in every flow. A semantic change requires approval from the product/design owner and engineering reviewer.

## 3. Working implementation
The public demo creates a fictional claim in browser memory. Reload clears it. No backend or customer system is connected.

```ts
export function validateClaimReference(value: string): boolean {
  return /^POL-\d{4}$/.test(value.trim());
}
```

- POL-2048: valid.
- POL-ABC, an empty value or POL-12345: invalid.
- Failed validation preserves the entered value and associates the error with the field.
- Successful creation adds a record with status In review.
- Search and the review-state filter operate on demonstration records.

## 4. Agent instructions
Reuse the shared contract. Keep labels, error descriptions and keyboard access. Do not change status semantics without approval. Run validation and interaction tests before requesting review. Never connect this demo to customer data. Agent instructions do not replace executable tests or human review.

## 5. Handoff checklist
- Confirm scope and known limitations.
- Assign product/design and engineering owners.
- Review default, invalid, valid and empty states.
- Run tests for reference validation and form behavior.
- Verify labels, error associations, keyboard operation and responsive layout.
- Document installation, maintenance and the contribution process in the actual client repository.
- Agree how future changes and support are handled.

## 6. Measurement plan for a real engagement
Agree a baseline before implementation: a comparable flow, rework reasons, review cycles and team effort. Repeat the observation after adoption. Report the measurement period and limitations. This demonstration does not establish a time saving or financial return.

## 7. What a client delivery adds
The agreed editable Figma assets, implementation repository, tool-specific rules, executable checks, installation instructions and recorded walkthrough. Existing foundations can be reused after assessment. Scope, ownership and schedule are agreed before work starts.