BHG Infra

Staging documents with a digest

How an agent adds a meeting or document to a project so Sync reads it well. Send the text, the transcript when there is one, and a digest of facts with quotes.

An agent that takes meeting notes or reads email can add what it found to a project with edge_add_project_document. The document lands in the project's Knowledge, where people, the project agent and Sync read it. Then edge_sync_project turns it into proposed changes for the lead.

What to send

FieldWhat it is
projectIdThe project.
titleThe document's title, for example "Acme weekly status — Oct 21".
bodyMdThe notes or document, as Markdown or plain text. Convert files to text first; this tool takes text, not uploads.
transcriptMdThe full transcript, when there is one.
docTypemeeting, email, sow, change order, brd, table or other. It tells Sync how to read it.
occurredAtWhen the meeting or email happened.
sourceUrlWhere it came from, if it has a link.
digestYour read of the document as facts. Send one with every document.

The document then shows three layers in Infra: Original (bodyMd), Transcript (transcriptMd) and Summary (your digest). Another agent can read any layer with edge_get_document and layer.

The digest

A digest is your read of the document as a list of facts. Sync reads it alongside the document.

{
  "by": "Claude",
  "source": { "kind": "meeting", "date": "2026-10-21" },
  "people": [
    { "name": "Priya Shah", "side": "BHG", "role": "Project lead" },
    { "name": "Sam Rivera", "side": "CLIENT", "role": "VP Sales Ops" }
  ],
  "facts": [
    {
      "type": "task",
      "statement": "BHG sends Acme the data mapping workbook by Oct 30.",
      "fields": { "title": "Send Acme the data mapping workbook", "owner": "Priya Shah", "dueDate": "2026-10-30" },
      "quote": "Priya will send the mapping workbook over by the 30th.",
      "speaker": "Sam Rivera"
    },
    {
      "type": "answer",
      "statement": "Acme confirmed overlay reps split credit 50/50 on shared deals.",
      "fields": { "question": "How do overlay reps split credit?", "answer": "50/50 on shared deals", "decidedBy": "Sam Rivera" },
      "quote": "Yes, fifty-fifty on anything shared with an overlay rep.",
      "speaker": "Sam Rivera",
      "about": "DEC-015"
    }
  ]
}

The rules

  • One fact per entry. Each statement is one plain, self-contained fact.
  • Quote whenever you can. Copy the exact words from the document or its transcript. Infra highlights a quote it finds word for word as the fact's source. A fact without a quote still counts, as you stated it.
  • Stated only. Leave out any owner, date or number the source does not give.
  • Leave out small talk and meeting chores (recording, scheduling, filing).
  • speaker is a name from people. about is an Infra reference you already know, such as DEC-015.
  • people[].side is BHG, CLIENT or VENDOR.

Fact types and their fields

type is one of: question, answer, task, date, risk, issue, assumption, dependency, constraint, requirement, scope, agreement, commercial, plan, component, interface, build_object, test_case, deliverable, milestone, meeting, project.

TypeFields
tasktitle, owner, dueDate, description ("Done when: …")
questionquestion, deciderName, answerBy
answerquestion, answer, decidedBy
risk, issuetitle, owner, likelihood (1–5), impact (1–5)
date, milestonename, dueDate
scopekind (IN_SCOPE or OUT_OF_SCOPE), text
commercialtext

How Infra checks a digest

When Sync reads the document, it checks each quote against the text as it is now. A quote found word for word cites its passage. A quote not found is shown in the summary as quote not found in the document, and the fact still counts, citing the document without a passage. So exact quotes make better citations, but they are never required.

After staging

  1. Call edge_sync_project for the project. It reads for about 45 seconds per call; when the answer has remaining above 0, call it again.
  2. The proposed changes wait on the project's Events tab for the lead. The agent cannot approve its own changes.

Requirements

  • A key that can write to the project's Knowledge: a key made for An engagement, with Write ticked, and the delivery toolset on.
  • Someone must have opened the project's Knowledge tab at least once. Until then the tool answers conflict.

On this page