Foundations: requirements, gaps, and open questions.

Every integration ends at the same place: material with a source type, an external ID, a source URL, an author, and a timestamp, flowing into update ingestion. Email via Action Mailbox is the closest analog today.

Zapier's "Submit Update Material" action, Notion's markdown page fetch, a Granola note, and a Slack message or file are all the same primitive. Build the input once, then every source is a thin adapter.

Signals across the documents: attendee and participant domains, known founder emails, calendar titles, folder, channel, database, saved view, external CRM ID, exact normalized name, and prior confirmed matches. Ambiguous matches surface for review and never attach silently.

Company reconciliation for unresolved sources already exists as a concept. Matching is the product issue every source shares.

Formal document, written company update, reviewed meeting summary, raw transcript, private notes, and PostMoney interpretation are different kinds of evidence and stay labeled as such.

Provenance must answer: which source, when, who owned it, summary or transcript, was it edited later, did a user review it, is the speaker known. Nothing spoken becomes canonical without review.

A dated conversation that contains evidence about one or more companies, or about the fund's relationship with them. Visibly distinct from a formal update; it may supplement a reporting period without pretending to be one.

Needed by Granola notes, Affinity meetings and transcripts, Slack chatter, and meeting tools arriving via Zapier. The unit of portfolio memory between updates.

Four related objects proposed from a conversation, each citing the meeting as its source, that can become tasks after review.

Tasks and assignment exist (Tasks V1). The proposal and review step in front of them does not. Accountability without treating a call as a reporting event.

Every platform's webhooks are incomplete: Affinity has no interaction events and an undocumented signature scheme; Notion is at-most-once and aggregated; Granola has no delete or revoke events.

Each needs signature verification where offered, idempotency on event IDs, and a periodic reconciliation sweep. Webhooks prompt refreshes; they are not the record.

Slack: one workspace per account. Notion: one token per authorizing user, many per organization, events routed via accessible_by. Granola: personal versus workspace keys. Affinity: a key acts as its owning user. Zapier: OAuth 2 with explicit organization selection.

All need admin visibility and revocation from inside PostMoney. Who connected what, and how to turn it off.

Digest cards, alerts, and canvases for Slack; database rows and pages for Notion; trigger payloads for Zapier.

The batch run receipt and the cadence model already exist to feed them. One event, several renderings.

The Zapier document's Stage 1: a small, stable set of things PostMoney can receive, emit, and find. Source-material ingestion, company matching, update lifecycle events, review tasks and health signals, confirmed structured observations, report availability.

Coherent enough to support Zapier, native integrations, internal automation, and an eventual public API. Define the contract before the connector.

Distinguish read and preview, draft for approval, reversible internal write, external communication, sensitive data export, and destructive or financially consequential action.

Needed before any assistant acts on the fund's behalf in Slack, Notion, or Zapier. Review scales with consequence.