Skip to main content
SELL.SYSTEMSAI CAMPUS
Enter Meeting Intelligence Lab
LanguageEnglish
02 / 09Meeting Intelligence and AI Revenue Operations Lab

Mission 1 · CRM contract

GitHub
Structured CRM contract separating commands, lifecycle state, artifacts, review, errors, and audit references
Mission 1 · CRM contract

Model business state before integration code.

Define a stable monday.com contract that separates operator commands, lifecycle state, artifacts, AI review, errors, and audit references.

Build sequence

  1. Create explicit Zoom Action and Zoom Status fields; never overload one human-editable status for both command and state.
  2. Map Zoom Link, Recording Link, Transcript, AI Score, Score Reasoning, Meeting Summary, Next Actions, Processing Error, and Last Event ID.
  3. Use stable column identifiers and status label IDs or indexes where the API supports them.
  4. Document file-column upload behavior separately from ordinary JSON column updates.
  5. Write the allowed state-transition table and reject unsupported transitions before any provider call.

Required proof

  • Sanitized schema export or screenshot.
  • Field-to-contract mapping and state-transition table.
  • One rejected-transition example with a clear operator error.

Reference files and sources

Official vendor documentation

Assessment gate

Pass

Pass: every field has one purpose, stable identifiers are recorded, and invalid transitions are deterministic.

Revise

Revise: the schema works but mixes commands, states, artifacts, or errors in ways that create ambiguity.

Hard fail

Hard fail: real customer data, access tokens, board secrets, or an unverifiable screenshot is submitted.

Human-reviewed submission