SharePoint Shared Doc Maintenance

Synthesis Rules

• Treat maintenance as a distinct workflow, not as generic document summarization.
• For roadmap and milestone maintenance, prefer concrete propagation over broad re-summarization.
• Use modification timestamps as a triage tool, not as proof of substantive change.
• For multi-document synthesis requests, verify the source set before writing. If the user asks for a consolidated strategy or a summary of all related materials, enumerate the source documents explicitly and verify that likely variants were not skipped.
• Even if you expect only one source to have changed, enumerate the source set so you do not miss a second updated input.

Verification

• Verification should confirm both the new fact and its placement in the document.
• Do not stop at proving a changed year, date, or milestone appears somewhere. Confirm it appears in the roadmap, recommendations, timing discussion, or risk framing where readers would expect it.
• If the maintained document is already on a low-fidelity fallback format because of connector limits, favor precise content patches over broad structural rewrites.

Recovery Notes

• Optimize for quick triage:
  • list likely source docs once
  • use modification times to narrow the fetch set
  • fetch only the maintained doc plus changed sources
  • extract the exact delta before editing
  • avoid rewriting unaffected sections
• If a changed source contains a strong explicit marker such as UPDATE, TIMELINE CHANGED, revised year ranges, or renamed milestones, treat that as a high-confidence propagation target.