# V1.4.4 build validation

**Package:** DoView Board V1.4.4  
**Saved JSON schema:** V1.3.9  
**Validation date:** 25 August 2026

## Release scope

V1.4.4 retains the two-step workflow: Step 1 builds the reviewed structure and Step 2 preserves that structure while adding restrained How mapping. Strict validation establishes technical consistency, not factual or organisational correctness.

## Final V1.4.4 delivery checks

- Step 1 names use `1-4-4-step-1-base-doview-board`.
- Step 2 names use `1-4-4-step-2-prototype-doview-board-with-how-links`.
- Known model and exposed effort components are accepted; unavailable components are omitted.
- Timezone components, `effort-not-exposed`, rc4/rc3 names and old Step segments are rejected.
- ZIP names use the exact HTML stem plus `-plus-additional-files-ai-readible-json-and-prompt-info.zip`.
- Each Step ZIP contains root-level HTML, canonical JSON, prompt-used record and the correct audit.
- HTML inside the ZIP is byte-identical to the separately delivered HTML.
- Completion responses contain exactly two deliverable links with the exact final labels.
- Separate JSON, audit and prompt-record links are rejected.
- The exact human-review paragraph is required.
- The entire Step completion paragraph must be bold.
- Citation definitions or platform-generated material may follow the bold paragraph.

## Retained technical checks

- The opening menu is reproduced verbatim when the subject is absent; a one-line replacement fails.
- The fixed opening menu contains all eleven setup choices, including positive-only/default versus opt-in negative This–Then polarity.
- JavaScript syntax is checked for the engine, builder and every tool.
- The obsolete `doviewboardsuse` URL is rejected in input JSON, canonical JSON and generated HTML.
- `evidenceReviewWorkflow` records `no-separate-step-in-v1.4.4`; explicitly requested supported annotations remain inside Step 1 or Step 2.
- Blank This–Then and How-link annotations pass as the default; populated supported fields require truthful field-specific request declarations.
- This–Then `mainText`, Notes 1–3 and link Traffic Lights pass when explicitly requested; How-link Display Text and Notes 1–3 pass when requested.
- Unsupported How-link Traffic Lights, polarity, Measures and Evaluation Questions fail strict validation.
- Negative This–Then polarity fails in positive-only mode and passes only after explicit opt-in. Enabling it does not require any negative link.
- The saved schema remains V1.3.9.
- Completion counts and deterministic graph metrics are recalculated from the final canonical board.
- Step 2 preserves the accepted Step 1 structure digest.
- Canonical JSON and embedded HTML state must match.
- The compact horizontally scrollable control bar remains present and the removed header site line remains absent.

## Regression fixtures

The V1.4.4 release test report records the default/override, annotation, evidence URL, How-link capability, polarity, structure-digest, no-subject, delivery and package-composition results. Strict validation remains technical validation rather than semantic certification.

## Automated commands

From the package root:

```bash
node tools/release-smoke-test.js
sha256sum -c MANIFEST.sha256
```

For a produced Step delivery ZIP:

```bash
node tools/validate-delivery-zip.js --step 1 --html <board.html> --zip <board-plus-additional-files-ai-readible-json-and-prompt-info.zip>
```