Shopify-offshoot document history — SUPERSEDED

Every pre-master Shopify-offshoot fragment is superseded by ../SIGNAL_SHOPIFY_MASTER_v4.md (build spec) under ../SIGNAL_OVERVIEW_v5.md (top-level product overview, content v5.3). Do not cite a fragment; cite the master or the overview.

Supersession chain (recorded in the master's header and Part IV)

original "Democratizing Enterprise Decision Intelligence" draft → Product Definition v2.0 / v2.1 → Final Product Document v3.0 / v3.1 → Story Bank v1.1 / v1.2 → Phase Mapping & ReLU companion → SIGNAL_SHOPIFY_MASTER_v4.0 FINAL (2026-08-11) → overview lineage SIGNAL_OVERVIEW v5.0 → v5.1 (cells 33–36 canonical for LII) → v5.2 (Cell 37 = Data Injector) → v5.3 (Cell 37 = Data Injector & External Intelligence Gateway) — v5.3 is the committed overview content.

Why no fragment files are stored here

Measured on 2026-08-11 during F1 of INTEGRATION PROMPT v2.3: the Drive MIZOKICloudRun board contains no copies of the v2.x spec, v3.x final, story bank, or phase-mapping companion (title searches for "Product Definition", "Story Bank", and "Phase Mapping" returned zero files). The fragments were consolidated into the master and their standalone copies were not retained on the board, so there is nothing to move — this README records the chain instead. If a fragment copy resurfaces, commit it here byte-for-byte with a SUPERSEDED by docs/product/SIGNAL_SHOPIFY_MASTER_v4.md header line prepended.

The superseded v5.0/v5.1/v5.2 overview copies still exist on the Drive board; they are board history and are not committed to the repo.

Resurfaced fragments (committed per the rule above)

• Product Definition v2.1 — resurfaced 2026-08-21 as an owner-supplied copy (pasted into the requesting session; no Drive or repo original existed to checksum against, per the 2026-08-11 measurement above) and committed as SIGNAL_SHOPIFY_PRODUCT_DEFINITION_v2.1.md with the prescribed supersession header (plus a dated provenance note naming its pre-master vintage deltas; body verbatim from the supplied copy). v2.0, the v3.x finals, the story bank, and the phase-mapping companion remain unretained.