# Feature and schema decision receipt

Copy into your working project. Empty fields are unknown, not accepted.

## Identity and evidence

- Exercise / interview/source version:
- Participant / date / workshop decision owner:
- Live HVE or desk walkthrough:
- Actual selected project and available run/artifact references:
- Business outcome, constraints and unanswered questions:

## Original outputs

Requested labels identify content, not real IDs or filenames.

| Prompt / label | Actual run or navigation-only read-back | Original artifact/version/path | Run / mirror / review states |
|---|---|---|---|
| | | | |

## Feature decisions

| Feature ID | Client need/source | Value and technology implication | First / later / rejected / unverified | Choice and alternative considered |
|---|---|---|---|---|
| | | | | |

## Schema rationale

| Entity / field / relationship | Supporting selected feature IDs | Purpose and logical type / cardinality | Requiredness / ownership / history | Smaller alternative and tradeoff |
|---|---|---|---|---|
| | | | | |

Do not add a field just because a starter template or product has it. Record why an included feature needs it and what would be lost without it.

## Change and model walkthrough

- Changed client requirement:
- Feature/schema consequences:
- Included now versus deferred, with reason:
- Sample records walked and any model gap:
- Supplied fictional review findings versus actual HVE/other observations:

## Disposition and transfer

- Use for next design request / revise / hold, with source-backed reason:
- Human decisions still open:
- Receiver's explanation and help needed:
- Reusable decision pattern and client-specific facts to replace:
- Next prototype/build question and owner:

A workshop disposition is not operator approval, server acceptance, an implemented schema or a passed runtime test. Any actual implementation/evaluation is recorded separately.