Follow up to: #3582494 _**NOTE: Before working on this issue, verify it's still relevant and makes sense.**_ **Description** We need to decide how AI Context should model priority, authority, trust, freshness, and quality signals for context items. These concepts are related, but they should not be overloaded into a single ambiguous field. This issue is for discussion and design only. It should separate near-term selection priority from longer-term provenance, review, freshness, and quality scoring. Questions to resolve: - Do we need an item-level `weight` or `priority` field before schema lock? - Is priority different from trust or authority? - What metadata is needed for provenance and freshness? - Should review-by or expiry dates be first-class fields? - How should these signals influence context selection? - Which parts are schema decisions vs later scoring behavior? - What follow-up issues should be created? Potential follow-ups: - Add item priority/weight field - Add trust level metadata - Add provenance/source metadata - Add review-by or expiry fields - Add context quality dashboard - Add authority/freshness scoring [x] AI Assisted Issue