Map a device market with claim-level sources

Why use this

1. A product team examining a device category can confuse manufacturer claims, distributor descriptions and regulatory records because they describe similar products in different terms. Unclear geography or model identifiers make an attractive market map unreliable for decisions.

2. A claim ledger could organize those distinctions before anyone draws conclusions about competitive position. It would help a reviewer see which comparisons are supported, which relationships are inferred and where a product's status needs specialist verification.

Why an agent / simpler alternative

Useful judgment

Match product variants cautiously and compare evidence strength across company, partnership and regulatory claims.

Simpler alternative

Use a spreadsheet for a small shortlist with consistent identifiers and already collected references.

Unsuitable when

The task requires a legal determination, certification judgment or clinical recommendation.

Proposed inputs

1. Name

   Market boundary

   Owner

   Research lead

   Minimum scope

   Device category, geography, date window and inclusion criteria

   Quality check

   Separate product family from model-specific scope.

2. Name

   Reference packet

   Owner

   Authorized researcher

   Minimum scope

   Permitted source excerpts with dates, URLs and product identifiers

   Quality check

   Record source type and unresolved identity matches.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only reference packet and a private claim ledger; no company or regulator outreach.

Compatibility unknowns

1. Unknown: current runtime, browser access and source retrieval coverage.

External actions requiring approval

1. Account access, third-party inquiries, uploads and publication of the market map.

Expected deliverable and review checks

Proposed artifact

Company-product map with claim-level references, geography, dates and uncertainty labels.

Critical checks

1. Regulatory wording is preserved as attributed evidence without inferred approval.

2. Partnership edges distinguish announcements from independently supported relationships.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A family-level statement is assigned to every model.

   Why it matters

   The comparison may misstate product-specific capabilities or status.

   Proposed response

   Narrow the claim to the named model or mark coverage unresolved.

2. Signal

   An old partnership announcement is presented as current.

   Why it matters

   The map can imply a relationship that may have changed.

   Proposed response

   Date the edge and request current supporting evidence before relying on it.

Effort and cost — unknown

Setup work

1. Define comparable attributes and a source-quality hierarchy.

Ongoing review

1. Resolve model ambiguity and refresh time-sensitive claims.

Unknowns

1. Unknown: research coverage, paid-source needs and specialist review effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Five invented excerpts describe two device models, a dated partnership and a regulator entry from another jurisdiction.

Acceptance checks

1. Keep model and jurisdiction scopes separate.

2. Mark the partnership's present status unknown.

Stop conditions

1. A real regulatory conclusion, network retrieval or publication is needed.

Limits

1. Editorial research structure only; no current regulatory applicability, market completeness or device suitability is established.