Documents, spreadsheets and decks with revision history

One file: each saved version or a diff between versions, comments and how they were resolved, the file type, folder context and timestamps.

{
  "file_id": "F-90021",
  "type": "spreadsheet",
  "folder_path": "Finance/Pricing",
  "versions": [
    {"at": "2024-09-02", "by": "fin_role", "ref": "v1"},
    {"at": "2024-09-04", "by": "fin_role", "ref": "v2"}
  ],
  "comments": [{"anchor": "Tiers!C14", "body": "Discount should cap at 20%", "resolved": true}]
}

Editing agents

Learn how drafts change in response to comments.

Spreadsheet agents

Formulas and models as they evolved.

Document understanding

Real business file formats and layouts.

Agreed with the supplier before any work begins. Typical requirements include:

• Files scoped by folder or type before any review
• Personal, HR and legal files excluded
• Third-party documents such as vendor contracts and purchased reports excluded unless licensable

Every dataset has a documented owner and confirmed licensing rights. See data governance on sourcex.si.

• Version history kept, not just final files
• Comment threads
• Domain-heavy files such as financial models and engineering specs

Public sets such as RVL-CDIP are useful references, but limited as enterprise training data. The documents and knowledge category page compares them with licensed data.

• Consulting firms
• Finance teams
• Engineering firms
• Agencies

• Internal wikis and knowledge bases

  Team wikis, internal help centers and decision records with links and edit history.

• FP&A models, budgets and forecasts with versions

  Financial models, budget cycles and forecast revisions, with assumptions and comments.

• Contract drafts, redlines and negotiation threads

  Each draft of an agreement, tracked changes, comments and the emails around them.

• Consulting industry page on sourcex.si
• Financial services industry page on sourcex.si
• Construction industry page on sourcex.si