# Agent Task: Review Signals And Draft Decision

## Goal
Turn prototype and beta evidence into a clear signal review and draft promotion decision.

## Context
Signals are evidence, not enthusiasm. `MARKET_SIGNAL.md` defines strength levels, and `PROTOTYPE_PIPELINE.md` requires an explicit decision before promotion.

## Inputs
- A prototype card
- Any related beta notes or beta plan
- Signal notes or records
- `MARKET_SIGNAL.md`
- `templates/signal-record.md`
- `templates/promotion-decision.md`

## Allowed Changes
- Create or refine signal records in `signals/`.
- Summarize beta feedback faithfully.
- Draft a promotion decision for later human review.

## Forbidden Changes
- Do not upgrade weak evidence into strong signal.
- Do not hide contradictory evidence.
- Do not mark promotion as final without explicit approval.

## Expected Output
- A signal summary with strength assessment.
- A draft decision: promote, iterate, park, reject, or merge.

## Acceptance Criteria
- Evidence and counter-evidence are both represented.
- The recommendation matches the recorded signal strength.
- The proposed next step is explicit.

## Human Approval Required For
- Final promotion into another initiative.
- Any external-facing launch or commercial claim.