{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/carry-the-thread-across-recurring-meetings",
  "id": "MHC-D-RESEARCH-0392",
  "version": "0.1.0",
  "title": "Carry the thread across recurring meetings",
  "summary": "A recurring meeting should inherit state, not amnesia.",
  "kind": "protocol",
  "body": "Before the next meeting, connect three time horizons: what changed since the previous meeting, which open decisions or actions remain, and what future event or milestone the next discussion must prepare for. Use AI summaries only as drafts tied to source notes or artifacts. The useful output is continuity of work, not a longer meeting memory.",
  "limits": [
    "Design research supports the temporal-work framing; this specific compact protocol has not been independently validated as an intervention."
  ],
  "topics": [
    "union-meeting-intentionality"
  ],
  "intents": [],
  "source_ids": [
    "RS-1A4480192E388854"
  ],
  "evidence": [
    {
      "claim": "DIS 2025 design research frames recurring knowledge work as temporal work that depends on both retrospection across prior meetings and prospection toward future work.",
      "source_id": "RS-1A4480192E388854",
      "role": "supports",
      "note": "The framework organizes design thinking; it is not a controlled trial establishing a productivity effect.",
      "locator": "Abstract and framework"
    }
  ],
  "use_when": [
    "A recurring project meeting repeatedly spends time reconstructing what happened last time and what must happen next."
  ],
  "avoid_when": [
    "Design research supports the temporal-work framing; this specific compact protocol has not been independently validated as an intervention."
  ],
  "example": "A weekly migration meeting begins from changed error counts, unresolved mappings and the next cutover milestone rather than replaying the previous call.",
  "check": "Participants can enter the meeting from the current project state without reconstructing the full history verbally.",
  "steps": [
    "Participants can enter the meeting from the current project state without reconstructing the full history verbally."
  ],
  "sources": [
    {
      "id": "RS-1A4480192E388854",
      "title": "Designing Interfaces that Support Temporal Work Across Meetings with Generative AI",
      "url": "https://www.microsoft.com/en-us/research/publication/designing-interfaces-that-support-temporal-work-across-meetings-with-generative-ai/"
    }
  ],
  "relations": [],
  "collections": [
    {
      "id": "RC-DC3FB389E54F5C7A",
      "title": "Make meetings answer a goal instead of merely occupying a slot",
      "url": "/collections/make-meetings-answer-a-goal-instead-of-merely-occupying-a-slot"
    }
  ]
}