# Product verification and editorial boundaries

Checked in the live public browser demo on 16 October 2026:

https://spectacular-jalebi-c45e30.netlify.app/catalogops/

## Directly observed behaviour

1. Initial catalogue: 12 fictional products, including AU-101 Studio headphones at EUR 129.00 and 24 units.
2. “Try a sample import” loads a four-row CSV with columns sku,name,category,price,stock.
3. Initial valid sample preview: 1 new, 2 updated, 1 unchanged, 0 invalid. Status: “Preview ready. The catalogue has not changed.”
4. The AU-101 preview contains EUR 119.00 and 30 units. DS-205 Monitor shelf is a new row.
5. “Apply 4 rows” changes the catalogue to 13 products and creates an Activity entry: 1 new, 2 updated, 1 unchanged.
6. Loading and previewing the same sample after applying it gives 0 new, 0 updated, 4 unchanged, 0 invalid.
7. The deliberately invalid sample includes a duplicate AU-101 row, a missing name, price 45.999, stock -2 and stock “ten”. The preview reports validation errors and disables the Apply control. Observed status: “Validation found errors. No changes were saved.”
8. The interface states UTF-8, up to 256 KB and up to 500 products.

All state changes performed during inspection were in the isolated browser demo, stored locally on that device. No production data or external store was modified.

## Product-page statements reflected in copy

The project notes describe a downloadable PHP/PDO and SQLite implementation, transactions, CSRF checks, integer-cent prices and stale-preview rejection. The campaign only refers to the existence of the downloadable implementation. No fresh PHP/backend test run was performed as part of this content campaign.

The product page explicitly states that Netlify runs the browser demo, does not execute PHP, uses fictional data and has no payment or external ERP connection. Those limits are carried through the copy.

## Visual treatment

The campaign uses original, deterministic vector diagrams rather than screenshots. Slides are labelled “Workflow illustrations” and “Fictional data”. They explain observed behaviour without claiming to reproduce the application UI pixel for pixel.

Counts such as 1 new / 2 updated / 1 unchanged describe the initial sample, not conversion, revenue, customers or audience metrics. The repeated sample assumes it has been applied once and the demo has not been reset in between.

## Campaign status and boundaries

This is an independent portfolio campaign, not a commissioned client engagement. It is presented on the portfolio as a case study. Social posts and emails have not been published, sent or scheduled. No audience, reach, conversion or commercial results are claimed.

The seven-day calendar, SEO queries and analytics events are proposals. No tracking has been installed. URL parameters only label the source of a prospective visit; they do not constitute implemented attribution.

The video deliverable is a script, subtitle draft and storyboard. It is not a recorded or edited video.

## Asset verification

The build exports eight 1080x1350 carousel PNGs, three 1200x627 social PNGs and six 1080x1920 storyboard PNGs, each with an SVG source. The PDF has eight 540x675-point pages and a demo link on the final page. The finalization script checks the file dimensions, PDF page count and link annotation, and ZIP integrity.
