The model
TATER Ops adds two coupled features for capturing operational knowledge:
- Meeting Records - a first-class entity for any conversation worth documenting. Captures attendees, agenda, raw transcript, decisions, and every artifact that came out of the meeting.
- Business Documentation - a new home for non-security operational docs: SOPs, process maps, role descriptions, vendor briefs, client procedures, onboarding/offboarding workflows.
MCP-first by design - no internal LLM
TATER is the durable data substrate. Extraction (action items, decisions, summaries, drafted SOPs) happens in your own LLM session via the TATER MCP server. Claude / ChatGPT / Copilot pulls the raw transcript via get_meeting_transcript, your subscription pays for the tokens, and the AI writes structured artifacts back to TATER via the standard MCP tools.
Why this matters: TATER never runs server-side LLM calls. There is no token billing inside TATER. Your existing AI subscription does the compute. The only cost in TATER is data storage and MCP tool-call routing - both negligible.
Capturing a meeting
Manual capture (today)
- Open TATER Ops → Workspace → Meetings and click + New Meeting.
- Fill in title, type, scheduled start, attendees, planned agenda, and the consent attestation if appropriate.
- From the meeting detail page, click + Attach transcript and paste in the transcript text (VTT, SRT, plain, or pasted from Teams / Zoom / Webex).
- Click 🚩 Flag for documentation - TATER creates a Tasker task assigned to you (or whoever you specify) due in 5 days so the doc work itself is tracked.
External LLM capture (the power-user flow)
Open your MCP-capable LLM session (Claude Desktop, Claude API, ChatGPT with the TATER MCP server connector, Copilot) and prompt:
"Pull yesterday's architecture-review meeting from TATER, extract the action items into Tasker tasks, draft a Business Doc for the firewall-change decision, and post the access-review decision to the related control thread."
Your LLM uses the MCP tools (list_meetings, get_meeting_transcript, get_meeting_context, create_business_doc, create_tasker_task, append_meeting_decision, append_meeting_link) to read the meeting and write the artifacts. TATER pays nothing for the LLM compute.
Privacy gates
| Sensitivity | Effect |
|---|---|
normal (default) | Full read/write access. MCP can pull transcript. Standard audit trail. |
confidential | Transcripts accessible but flagged. Recommended for client engagements, vendor calls. |
sensitive | Hard lock. Transcript attach blocked; transcript reads (including MCP) refused. Use for HR / legal / attorney-client / IR-classified meetings. |
Consent attestation (consentAttested) confirms the organizer informed attendees about recording / processing. Every transcript read is audit-logged. Sensitive meetings show as 🔒 in lists and reject transcript-read attempts even from MCP.
Closed-loop view
The meeting detail page shows everything that came out of the meeting:
- Decisions captured (free-form decision log)
- Linked artifacts (tasks, business docs, config docs, risks, change requests, controls, wiki pages)
- Discussed-agenda vs planned-agenda delta (populated by the LLM)
- Summary
Business Docs drafted from a meeting via create_business_doc(source_meeting_id=...) auto-link both ways - the doc records its provenance, and the meeting links back to the doc.
Business Documentation - types
| Type | Use for |
|---|---|
SOP | Standard operating procedures, step-by-step "how do we do X" |
process-map | End-to-end process flow descriptions |
role-description | Role definitions, responsibilities, RACI matrices |
vendor-brief | Non-TPRM operational details about a vendor |
client-procedure | Per-client engagement playbooks |
workflow | General internal workflows |
onboarding | Employee onboarding / offboarding checklists |
general | Anything else operational that doesn't fit a security policy / config doc / playbook |
Distinct from: Policies (security policies with approval workflow), ConfigDocs (technical configuration of specific systems), Implementation Guides (compliance-control rollouts), Playbooks (incident response), and TATERpedia (cross-org public wiki).
MCP tool reference
| Tool | Purpose |
|---|---|
list_meetings | Find meetings by status / since / recurring series |
get_meeting_record | Full meeting record incl. attendees, agenda, links, decisions |
get_meeting_transcript | Raw transcript text (subject to sensitivity gate, audited) |
get_meeting_context | Pre-meeting brief context: prior meetings in series, attendee tasks, related docs |
create_meeting_record | Create a new Meeting (e.g. ingesting from Zoom / Webex / external source) |
update_meeting_record | Update extracted fields: discussed-agenda, summary, topic-tags, actual-attendees |
attach_meeting_transcript | Attach raw transcript content to a Meeting |
flag_meeting_for_documentation | Mark for documentation, auto-create Tasker tracking task |
append_meeting_decision | Add a decision to the meeting's decision log |
append_meeting_link | Link an artifact (task / business doc / risk / change / control / wiki) to the meeting |
list_business_docs | Browse Business Documentation, filter by docType / status / owner |
get_business_doc | Read full body + metadata of a business doc |
create_business_doc | Draft a new business doc (provenance fields preserve source meeting + model) |
update_business_doc | Edit body / status / owner / links; version increments on body change |
Phased delivery
- Phase 1 (shipped): Meeting Records + Business Docs containers, full CRUD, 14 MCP tools, manual transcript paste-in.
- Phase 2 (shipped): File upload - .vtt / .srt / .txt drag-drop with client-side speaker-tag normalization and UTF-8-safe truncation.
- Phase 3 (shipped): In-TATER Outlook calendar view via MSAL Graph (
Calendars.Read), one-click Capture pre-fills the New Meeting modal from the Graph event payload. - Phase 4 (shipped): Pre-meeting brief view, MCP-driven via
get_meeting_contextand the 7-step Meeting Session Pattern in the MCPINSTRUCTIONS. - Phase 5: Teams Premium / Graph live transcript pull (covered today by the Meeting Bot's transcript handler when a Premium tenant is in scope).
- Meeting Bot (shipped through Phase 1.5): TATER meeting bot joins Teams meetings as a participant for direct capture, with per-org config in Manage › Meeting Bot (Cosmos-backed, no env-var redeploys). Cross-tenant chat works; cross-tenant calling is currently blocked at the Bot Framework SDK / Microsoft tenancy layer - path forward tracked in ADO #522 (BYOC per-tenant deploy) and #523 (Federated Identity Credentials + custom credential factory). Phase 2 (real-time media capture for non-Premium tenants via Azure Speech + audio streams) is in progress.
Related
- Ops customization - categories, priorities, statuses
- MCP setup - connecting Claude Desktop / API to TATER