Flowgrammer

Resolve the Meeting, People, and Evidence

Build an identity checklist and source ledger with dates, locators, support, limits, and privacy class.

Why this decision matters

A name alone is not an identity. A company domain, role, event record, and source date help distinguish people with similar names. Calendar failures are not proof that no meeting exists. Booking answers establish what the participant wrote, not independent facts about the company. Search snippets may locate a profile but do not guarantee a current role. Sensitive personal details unrelated to the professional purpose do not belong in the brief.

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-S2 demonstrates calendar-first context and research gaps. C7-S3 requires timezone, cancellation, reschedule, same-name handling, role corroboration, and source ledgers.

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.

The fixture identifies Jordan only as a fictional operations lead through supplied context. No public identity is claimed. The briefing remains limited-evidence and avoids biography, personal contact details, and inferred authority.

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 3: Resolve the Meeting, People, and Evidence. Complete Workbook Section 3. Record the event identifier, timezone, status, company context, identity status, source IDs, checked times, supported claims, limits, and any clarification required.

  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

Selecting the first same-name profile; using an old role as current; treating cancelled meetings as active; publishing private locators; and including home addresses or unrelated personal history.

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

Material ambiguity pauses person-specific findings. Private sources use internal locators. Date of access does not become date of publication. Omit irrelevant personal data.

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

1. Two professionals share the attendee's name, and the company domain does not resolve the match. What should the brief do?

2. A booking answer says the attendee controls the budget. How should the source ledger classify that claim?

3. The calendar lookup fails, but an authorized meeting request contains a valid event identifier and time. What can the agent conclude?

Return to Build a Meeting Preparation and Follow-Up Agent