This folder keeps the checked-in JSON examples that back Shopflow’s builder-facing read-only surfaces.
In plain language:
this is the sample-card rack. it tells you which example to open first instead of making you guess from file names alone.
The checked-in rack currently covers these current-scope apps:
ext-albertsonsext-amazonext-krogerext-temuIt also now includes common agent/distribution example artifacts:
| App | Builder app snapshot | Operator decision brief | Workflow copilot brief | Builder outcome bundle |
|---|---|---|---|---|
ext-albertsons |
snapshot | decision brief | workflow brief | outcome bundle |
ext-amazon |
snapshot | decision brief | workflow brief | outcome bundle |
ext-kroger |
snapshot | decision brief | workflow brief | outcome bundle |
ext-temu |
snapshot | decision brief | workflow brief | outcome bundle |
If you need repo-local generated runtime payload files instead of checked-in
samples, use pnpm builder:write-runtime-payloads -- --app <appId> for those
same current-scope apps.
If the checked-in rack needs to catch up with repo-owned generated truth, run:
pnpm builder:refresh-example-rack
That refresh command rewrites the checked-in examples from generated runtime payload files and matching outcome bundles instead of relying on hand-maintained JSON.
It also rewrites the common agent/distribution example artifacts listed above.
builder-app-snapshot if you want the raw app-state picture first.operator-decision-brief if you want the shortest “why now / what next” answer.workflow-copilot-brief if you want the AI-facing summary layer.builder-outcome-bundle if you want one joined current-scope bundle.These files are not: