Return typed product outcomes for batched and linked extraction passes

[jimador]

Goal

Return typed per-product outcomes from bounded extraction plans that support compatible
multi-product calls and linked later passes.

Context

Facts, decisions, sentiment, and normative claims share proposition lifecycle. Tasks and
recommendations are actionable suggestions with downstream ownership. Batching several
products in one pass and running another pass after entity resolution are independent
capabilities.

Acceptance criteria

• ExtractionRequest declares source revisions, profile, context, products, speaker
  scope, relationship coverage, pass index, and parent or superseded run.
• Outcomes are typed per product with stable ids and independent failures.
• Compatible proposition facets may share one bounded model call.
• Heterogeneous requests partition before execution.
• A later pass can consume resolved entities from its parent.
• Successful siblings remain usable when one product or later pass fails.
• Budgets, pass limits, ordering, and cycle prevention are explicit.
• Tests cover meetings, recommendations, partial decode, later-pass replay, and tenants.

Constraints

• Depends on profile and durable run contracts.
• Preserve serial entity resolution and revision where shared identity requires it.
• DICE returns suggestions but does not own task or notification lifecycle.

Out of scope

• Downstream effect execution.
• Connector-specific routing.
• An unbounded autonomous extraction agent.

Original request

Batch compatible meeting and message products where one model call is valuable, preserve
typed failures, and allow a later resolved-entity pass without coupling the two designs.