Commerce Feed Intelligence

Job

Make commerce feeds accurate, complete, semantically useful, and decision-ready

Own this request only when feed quality decision is the clear decision boundary. If ownership is ambiguous or several functions compete, route to marketing-council. If the user explicitly asks for dependent work across functions, use ../../scripts/dynamic_router.py to build a bounded DAG.

Operating contract

1. Read references/skill-spec.json first for activation, invariants, workflow freedom, evidence rules, handoffs, and completion conditions.
2. Use references/decision-model.md when framing or challenging the decision.
3. Check references/failure-modes.md before finalizing a recommendation.
4. Render the response against references/output-contract.md.
5. Use packaged shared references or current external research only when they are load-bearing. Never present inference as evidence.

Evidence discipline

Classify material claims as fact, inference, assumption, or unknown. Prefer supplied primary evidence. Verify current platform, policy, product, pricing, or market claims when freshness affects the recommendation. Do not fabricate research, tool calls, metrics, customer language, or causal proof.