Reject Cleared Property

Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
Inputs: Do they trigger the failure for the reason the summary gives?
Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?

The other tabs beside Comments are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

Goal: prepare subject-level records keyed by the subject identifier (USUBJID).

Input: demographics records, each carrying the subject identifier used to key the output.

Variables:

USUBJID would be the subject identifier copied from the demographics record.

Note: the subject identifier takes its data type from a shared parent file, and this file clears it. Every column must keep a data type, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Omit type to inherit it unchanged, or replace it with a complete valid value. Only optional immediate fields may use null to clear an inherited value.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: invalid_clear
requirement: REQ-0660

expected/error.yaml

phase: validation
condition: invalid_clear
spec_paths:
  - columns.USUBJID.type
requirement: REQ-0660
context:
  field: type

YAML specification

1 spec file

spec.yaml

Edit14 lines

1schema_version: "1.0"2parents: layers/parent.yaml3domain: ADSL4keys: [USUBJID]56output:7  path: adsl.csv8  columns: [USUBJID]910columns:11  # null clears the type inherited from layers/parent.yaml, but a column12  # must have a type, so it cannot be cleared.13  - name: USUBJID14    type: null

Inputs

Under review1 source file

input/dm.csv

Edit1 row

input/dm.csv
USUBJID

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Dataset Name	Variable Name	Variable Label	Type	Codelist/Controlled Terms	Core	Computational Method	Origin
ADSL	USUBJID					No derivation in this specification; inherited from its parent.	Derived

Version	Date	Author	Description
1.3	2026-09-29	yamaa docs build	Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.2	2026-09-29	yamaa docs build	Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.1	2026-09-29	yamaa docs build	Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0		yamaa docs build	Initial generation from spec.yaml

How to fix

input/dm.csv

Comments

Mapping spec