Define the Meeting Job and Permission Boundary

Why this decision matters

A discovery call, proposal review, interview, renewal, and community meeting require different preparation. The agent's job should describe the decision the human needs to make, not a vague goal such as improve meetings. Inputs may include a manual request, approved business profile, booking statement, selected notes, company URL, or authorized calendar event. Each source and action receives its own permission. Reading a calendar does not authorize changing an invitation; creating a draft does not authorize sending it.

This lesson advances the same capstone used throughout the course: the Meeting Preparation and Follow-Up Agent Pack. The learner is not collecting ideas for later. The workbook record created here becomes an input to the next module and must be specific enough that another operator could review it. Where evidence is incomplete, the artifact should show the gap instead of smoothing it over.

Source evidence and limits

C7-S1 supports one meeting type, one prep, one follow-up, and on-demand operation. C7-S3 requires least access and separate authorization for calendar, documents, delivery, recording, and sending.

The sources support the operating method stated above. They do not prove universal performance, guaranteed savings, complete market coverage, causal impact, or a client result. Any date-sensitive product, platform, competitor, legal, pricing, or policy fact must be checked against a current primary source before publication or operational use.

Continuing fictional example

Example: Northstar Operations, Cedar Workshop, and operations lead Jordan Lee are fictional. The meeting concerns inconsistent enquiry handling.

Fictional Northstar Operations chooses a 25-minute discovery call. The agent may read supplied fixture excerpts and save local files. Public research, calendar access, recording, mailbox access, CRM writes, and sending are disabled.

Example boundary: The fixture contains no live person, address, email, profile, company, meeting, or customer result. Its source excerpts exist only to test the course method.

Workbook application

Use Workbook Section 1: Define the Meeting Job and Permission Boundary. Complete Workbook Section 1. Name the meeting type, objective, human owner, required inputs, permitted reads, permitted writes, prohibited actions, and conditions that require stopping for clarification.

1. Write the current evidence or input before adding interpretation.
2. Apply the lesson's decision rule and state the reason for the classification.
3. Mark uncertainty, missing information, and the human owner for the next decision.
4. Check that the result stays inside the course boundaries and can be tested.

Failure modes to inspect

Supporting every meeting type at once; granting broad inbox access; assuming recording consent; defining success as closing the deal; and leaving the output recipient implicit.

A polished output can still fail if its evidence, permissions, identity, denominator, source date, or action boundary is wrong. Review the underlying record rather than grading tone alone. The correct repair may be to narrow the scope, gather a permitted source, label an unknown, or stop the proposed action.

Decision rules

Use the least access needed. Make no external action part of the first version. Treat no-fit, insufficient evidence, and a process-only next step as valid outcomes.

Record the rule in the workbook in language two reviewers can apply consistently. A rule that depends on intuition alone cannot support a deterministic fixture. If reviewers disagree, preserve both readings, identify the missing evidence, and revise the rule before automation.

Three application checks