Communication and collaborative meeting
Meeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 9 questions
Meeting and participation Who met, through which channel, and in what role.
Meeting record
The meeting, its agenda and its participants.
Meeting
A meeting with date, channel, organiser and agenda.
- When and through which channel did the meeting take place?
- Which agenda items were planned and which were actually discussed?
Participation
Each participant with role and presence, not consent.
- Who was invited, who attended and in which role?
- Did a participant state agreement, or only attend?
Discussion and sources Threads and messages as sources with their own access rules.
Threads and quotes
Discussion threads and references to messages.
Message reference
A quote or link that keeps its source and access scope.
- Which original message or recording is this quote taken from?
- Who may see the original communication, and does the quote respect that scope?
Outcomes Tasks and decision proposals created from a discussion as separate records.
Outcome records
Assignments and proposals with provenance back to the discussion.
Assignment
A task created from a discussion with an owner and a source link.
- Which task was created from the discussion, and who owns it?
Decision proposal
A proposal that becomes official only by an authorised action.
- Who has the authority to turn the proposal into a decision?
- Has the official status been changed by that authority, and when?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseKNW
- Industry
- Cross-industry
- Tags
- EM-KNW-03W2subjectMeetingMeetingParticipationCommunicationChannelDiscussionThreadMessageReference
What it is Filled
Meeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Why it exists Filled
Meeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Distinguishing features Filled
- Minutes record what was said; they do not prove that every participant agreed.
- Tasks and decisions arising from a meeting are separate records that point back to it.
- A quote keeps the access scope of the original message wherever it is reused.
- Distinct from the decision contour, which records the authorised decision itself rather than the discussion.
What robots and AI may and may not do Filled
Must not
- Treat a phrase in a chat or meeting as an approved policy or decision.
- Record attendance as consent to a proposal.
- Quote a restricted message to people outside its original access scope.
- Change an official status on the basis of a discussion alone.
- Record or transcribe a meeting without the notice the participants are due.
Only with a human decision
- Turning a decision proposal into an official decision.
- Sharing minutes or recordings beyond the original participants.
May
- Summarise a meeting and list proposed tasks and decisions with their sources.
- Create draft tasks linked to the discussion for owners to accept.
- Flag outcomes that lack an owner or an authority.
Moral aspects Filled
- Recording and transcription touch the privacy of participants.
- Attributing agreement to someone who did not give it is unfair and can harm them.
- Outcomes without a clear authority dilute accountability.
Who is affected
- Meeting participants
- People mentioned in the discussion
- Owners of resulting tasks
Owners Filled
Steward
The knowledge and records owner who answers for documents, terms and decision logs.
Master systems
- Calendar system
- Messaging platform
- Document management system
- Decision log
Links to other meta-models Filled
references
- WM-ACT-025 - conceptual-candidate
- WM-REC-012 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by the calendar event or meeting identifier with its date; messages by channel and message identifier.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- Marked by a date, a channel, a participant list and an agenda or thread.
- Often confused with the decision or task that it gave rise to.
Capabilities and actions required Filled
- Outcomes can be traced back to the exact part of the discussion they came from.
- Summaries can be produced while respecting each source's access scope.
Hazards and failure modes required Filled
- Informal remarks mistaken for commitments.
- Leaks of restricted content through quotes and summaries.
- Lost link between a task and the discussion that justified it.
Standards and interfaces required Filled
- IETF RFC 5545 iCalendar for meeting events.
- W3C Activity Streams 2.0 for messages and activities.
- W3C PROV-O for provenance of outcomes.
Context of use required Filled
- Used for team meetings, steering committees, chat channels and email threads.
- Recording and transcription fall under local privacy and employment rules.
Sources Filled
- W3C PROV: claims, sources and actions
- SKOS: concepts, definitions and mapping
- DMS/wiki/ADR practice: document, version, carrier and decision
- W3C PROV Overview - Checked live (HTTP 200) on 2026-10-07.
- W3C SKOS Simple Knowledge Organization System Reference - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to distinguish presence from consent?
- What is carried over from a discussion into an official fact?
- How to observe access rules for the original communication?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-knw-03/brief.json, ver-cy/world-models/card-supplements/em-knw-03.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.