Competitive intel

Beat the reactive cycle. Updates per competitor, weekly implications.

## Competitors

Use the **Competitors** surface. Columns: name, focus, last update, threat level (low / medium / high).

## Updates

One section per competitor. Latest at the top. Each entry: date, source, what they shipped / said.

Scout posts here nightly.

### [Competitor name]

Latest:
- **[date]**: what shipped, with link.

## Implications

Weekly synthesis. Use the **Implications** doc.

Argus drafts. The question is "should we?" not "they did X."

Ship-vs-ignore is the move that matters.

## Cadence

- Daily: Scout updates competitor sections from public sources.
- Weekly: Argus drafts implications doc.
- Monthly: re-rank threat levels, revise focus column.

Fork to next cycle

When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.