Record weekly evidence
Record one week of evidence for one product, across Product, Sales, and Marketing. Run this once per product per week.
Goal
One weekly snapshot saved against a product, carrying up to three area signals with values, trend, and an explicit status for each area.
Steps
Pick the product and the week
A snapshot belongs to one product and one week. A product can hold only one snapshot per week, so recording again for the same week updates that week rather than adding a second record.
Fill each of the three areas
Every snapshot carries at most one signal per area, and the areas are always product, sales, and marketing. For each area, record what it was working toward and what actually happened.
Set an honest status on every area
Status is what separates an area you measured from one you did not. Use populated when you have a real value, not_applicable when the area genuinely does not apply to this product this week, and missing when it should have a value but you do not have one. None of these is the same as recording a current_value of zero, which asserts you measured the area and it came out at zero.
Write it through your agent
Snapshots are written over MCP with upsert_weekly_snapshot. There is no HTTP write route; the REST surface is read-only. The call requires an idempotencyKey, so a retry after a dropped connection updates the same week rather than creating a duplicate.
Check freshness on the portfolio
Open the portfolio and confirm the product now reads as recorded for this week. A product with no snapshot for the week reads as having nothing recorded, which is the signal you want rather than a silent gap.
Worth knowing
Evidence is copied, not linked
The metric name, target, and unit are stored on the signal itself. Raising a target next month changes the target, not the weeks you already recorded.
One snapshot per product per week
The constraint is on the product and the week together, which is what makes freshness comparable across the portfolio.