Reject bad metric shape.
Every row needs a non-empty SKU, finite non-negative measures, and an explicit ad status. An invalid contract is blocked, not summarized.
RomeoApps
RomeoApps-owned portfolio proof / synthetic only
A bounded n8n analyzer for export-shaped advertising metrics: validate the contract, calculate ACOS, expose no-sales or high-ACOS leakage, and rank the largest rows for human review.
This is not an Amazon API integration, a client result, or an automatic budget action. The inactive fixture stops at a decision-grade human-review output.
The useful seam
Performance workflows become expensive when a plausible number silently turns into a budget decision. This fixture makes the contract and the handoff visible before a connector, credential, or production write exists.
Every row needs a non-empty SKU, finite non-negative measures, and an explicit ad status. An invalid contract is blocked, not summarized.
No-sales and high-ACOS rows become a ranked waste list with a Pareto inclusion flag. The output remains a review queue.
No ad pause, repricing, CRM write, Slack alert, or automatic recommendation is connected. The next move is an acceptance decision.
Synthetic decision register
The runtime receipt binds these deterministic fixtures to the same inactive workflow export. No row below is customer data.
Production boundary
The proof is deliberately narrower than a client build. It shows the analysis seam and its controls, then names the evidence needed for a paid first unit.
Agree the fields, currency, attribution window, and missing-data behavior.
Keep Amazon, catalog, database, and messaging credentials outside the fixture until written scope and protected payment exist.
Define the exact output, failure cases, and human action boundary before any connector is introduced.
Return the export, run receipt, decision register, and rollback or next-step note—not a claim that a client result already exists.
Public evidence
The public receipt exposes the runtime version, workflow hash, case counts, decision counts, and zero-side-effect controls. The exact inactive export is kept in the RomeoApps portfolio packet and can be shared through a written fit route.
Truthful boundary