§ Intel Cabinet

The market behind the project.

Five files — competitor landscape, market intelligence, persona pricing, whitespace atlas, website-design audit — plus one compiled brief. Produced by the competitor-intel orchestra (Agents 1–6). Each file is the rendered view of one JSON in /data/; the brief is what they compile to.

Internal desk — refreshed research date pending.

Competitors mapped
SEA-weighted, all six buckets.
TAM
Bottom-up derivation, currency in market_size.currency_label.
SOM
Year-3 (or 5) obtainable share after SAM filters.
Attack plans
Blue-ocean niches ranked by SOM, beatability, time-to-win.
§ The Bottom Line

What the intel says — in four findings.

Top four implications from market-intelligence.json → market_size.implications[]. Each carries an agent_targets[] field that says which downstream agents the implication shapes.

Finding 01

Findings will appear once Agent 2 (market-intelligence-analyst) writes implications.

This dashboard reads the top four entries from market_size.implications[] and renders them as headline + body. Make sure Agent 2 produces structured implications, not bullet text.

§ Top-5 Direct Threats

Who to watch most closely.

Pulled from the top_five rationale field of the competitor file. The first two entries often carry the silent NBAs (DIY alternatives, in-house build) — note them as the unmarked baseline the named competitors fight against.

RankCompetitorWhy they matter
Top-5 will appear once Agent 1 writes top_five[].The rationale field is rendered here verbatim. Keep it ≤ 200 chars; explain WHY the competitor matters, not what they sell.
§ Freshness Ritual

Intelligence decays — keep it dated.

This desk is a snapshot, not a feed. Every figure is tied to a research date and a named source so a reader always knows how stale it is. See methodology/07-methodology-curator.md.

Quarterly

Competitor & design rescan

Re-run Agents 1 and 5 every quarter — competitor positioning and websites change fastest.

On policy change

Market & pricing refresh

Re-run Agents 2 and 3 whenever a regulatory dependency in market.policies[] updates. The implications cascade into pricing tiers.

Annually

Full orchestra rerun

Rebuild TAM/SAM/SOM and the strategy canvas from scratch every May. Set meta.research_date on every JSON when it lands.

Page last edited: checking…