Design inference context-assembly rules

[ScottMorris]

Summary

Design the context-assembly rules that decide which captures, hints, and scopes become active inference input for the current thread or branch.

Scope

• define the default assembly policy before any manual curation
• define how manual exclusions affect prompt or request construction
• keep the design compatible with VerbatimEngine fallback and optional local models

Questions

• what is the default recency or count window for context assembly?
• how are curated exclusions applied when there are multiple branches or resumed threads?
• do pinned items outrank recency trimming if richer curation states are added later?
• should visible summaries and replies use the same assembled context or a separate policy?

Acceptance

• documented v1 context-assembly policy
• explicit contract for inference consumers
• follow-up implementation work identified for the inference pipeline