Skip to content

Contracts

Repository Role Contract

  • SharePoint remains the system of record for documents and permissions
  • this repo is the gateway for agent access to SharePoint-derived context
  • durable Git artifacts should be derived, selective, and useful for retrieval or analysis
  • this repo must not become a full SharePoint mirror or replacement document management system

Auth Contract

  • first run may require interactive Microsoft 365 login
  • token cache is workspace-scoped
  • required permissions are Files.Read.All, Sites.Read.All, and User.Read

Session Contract

  • downloaded files are cached in d:/github/.sharepoint-session/
  • cached files persist until explicit cleanup
  • analysis outputs are saved separately under analyses/

Curation Contract

  • keep raw document authority in SharePoint whenever possible
  • commit inventories, extracted summaries, and analysis artifacts when they materially improve agent context
  • avoid bulk-importing unmanaged document collections into Git
  • treat analyses/ as derived context, not canonical document storage

Support Contract

  • PowerPoint analysis is currently the most mature path
  • other file types should be treated as partial or planned capability unless documented otherwise