# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-08-29T11:36:24Z", "synthesisSha256": "956dbc3ff4c0dd2ba1b3e99e4a4dcdf1a8f7932fd8c4b76b52d26d0cd3c8cea2", "providerMode": "single-provider-waiver", "providers": [ "Claude" ], "waivedProviders": [ "Grok" ] }, "metaModel": { "id": "WM-ACT-025", "registryId": "vr.wm-act-025", "name": "Meeting / Session", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "event", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.MTG" ], "tags": [ "meeting", "session", "act.mtg" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-025-meeting-session/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-025", "model": { "registry_id": "vr.wm-act-025", "model_id": "WM-ACT-025", "name": "Meeting / Session", "entry_kind": "event", "purpose": "Provide the context an agent needs to convene, run, observe and hand off a single meeting or session occurrence — identity, convening basis, timing, setting, participation, agenda, conduct, outcomes and record obligations — without owning the durable records, the convening body or the parties it references.", "scope_statement": "WM-ACT-025 models one bounded occurrence in which two or more parties are convened, synchronously or in mixed mode, to transact business under a shared agenda. It covers the occurrence from convocation to close: how it is identified and classified, on whose authority it was called, when and where it takes place, who was invited and who was actually present, what was on the agenda, what procedural acts and votes occurred, what outcomes were reached, what was captured during the session, how open the session was, and which durable records it owes. It deliberately stops at the boundary of the artefacts it produces and the actors it references: minutes and transcripts (WM-REC-012), decision records (WM-REC-010), the convening body (WM-ORG-018), parties, places, tasks and documents are referenced with subject-specific binding parameters only. The model is storage- and interface-neutral; iCalendar, JSCalendar, schema.org, XCON and vendor conferencing objects are alignments and projections, not the semantics.", "in_scope": [ "Identity, classification and revision of a single meeting or session occurrence, including its position in a recurring series.", "Binding to the convening authority and the convocation notice, with the sufficiency tests attached to that notice.", "Planned and observed timing, suspension and resumption, rescheduling, postponement and cancellation of the occurrence.", "Physical setting, virtual conferencing endpoints, mixed-mode equivalence, reserved resources and accessibility provision.", "Invited and actual participation: roles, invitation response state, delegation and proxy, presence observation and recusal.", "Quorum determination at this occurrence, measured against a threshold rule owned by the convening body.", "Agenda composition, adoption, amendment, deferral and carry-over, with references to tabled papers.", "Conduct of proceedings: procedural acts, speaking-turn management, motions, voting method, tally and declared result.", "Outcomes reached and follow-up assignments, expressed as references to the records and tasks that carry them.", "In-session capture (recording, live transcription) with notification and consent basis, and the obligation to produce durable records.", "Openness and closure of the session or its portions, observer admission, and the inventory of session-held personal data.", "Declarative alignment to calendar, event and conferencing vocabularies." ], "out_of_scope": [ "Drafting, approval, authenticity, publication and disposition of the minutes or transcript — owned by WM-REC-012; 'approval of the minutes' appears here only as an agenda item of a later session.", "Content, status, rationale, supersession and implementation tracking of decision records — owned by WM-REC-010.", "Composition, mandate, terms of reference, standing membership, chair designation rules and delegated powers of the convening body — owned by WM-ORG-018.", "Master identity, contact data and affiliation of persons and organisations — owned by the adopting Dimension's party models.", "Master data for places, buildings and rooms — only the reference and a local room designation are held here.", "Generic occurrence semantics shared by all activities — owned by the parent model WM-ACT-018.", "Execution and completion lifecycle of assigned actions — owned by the task model.", "Version and custody management of tabled papers — owned by the document model.", "Runtime evaluation and enforcement of access decisions, and storage of audit trails; this model carries classifications and references to audit events only.", "Operation of calendaring transport (iTIP, CalDAV) and conferencing media transport, floor-control protocol mechanics and codec negotiation.", "Decisions taken without a meeting (written resolutions, silence or written procedure) where no session occurrence exists.", "Meeting-effectiveness analytics, sentiment scoring and engagement metrics." ], "boundary_notes": [ { "neighbor": "WM-REC-012 — minutes or transcript record", "distinction": "This model records that a record is owed, which content the applicable regime requires, who must produce and certify it, and which agenda item each passage anchors to. The record's own draft, approval, correction, authenticity and disposition lifecycle belongs to WM-REC-012.", "source_refs": [ "SRC-010", "SRC-012", "SRC-013" ] }, { "neighbor": "WM-REC-010 — decision record", "distinction": "Putting a question, the voting method, the tally and the declaration of the result are session conduct and are modelled here. The durable decision with its rationale, status, supersession and implementation is carried by WM-REC-010 and referenced by identifier.", "source_refs": [ "SRC-010", "SRC-012" ] }, { "neighbor": "WM-ORG-018 — governance body", "distinction": "Quorum thresholds, membership, voting entitlement and delegated powers are properties of the body's constitution. This model records only the determination made at this occurrence and the officer who presided over it.", "source_refs": [ "SRC-011", "SRC-012" ] }, { "neighbor": "WM-ACT-018 — parent activity model", "distinction": "Generic occurrence identity, scheduling status and cancellation semantics common to all activities are inherited from the parent. This model specialises only the deliberative surface: agenda, quorum, motions, capture and record obligation.", "source_refs": [ "SRC-001", "SRC-009" ] }, { "neighbor": "Party models for persons and organisations", "distinction": "Participants are references. Role, invitation response, presence intervals and recusal are occurrence-scoped facts held here; names, addresses and affiliations are not mastered here.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "Access-policy evaluation and audit services", "distinction": "The model classifies openness, marks closed portions and stores references to audit events raised elsewhere. It does not evaluate authorisation, enforce it, or hold the audit trail.", "source_refs": [ "SRC-012" ] }, { "neighbor": "Conferencing platform (XCON model or vendor service)", "distinction": "Conference object state, admission policy enforcement, floor control and media handling are the platform's runtime concern. This model binds the conference object identifier, the published endpoints and the exported attendance observations.", "source_refs": [ "SRC-006", "SRC-015", "SRC-005" ] }, { "neighbor": "Calendar interchange formats", "distinction": "iCalendar, JSCalendar and schema.org Event are alignments. Mappings are recorded with their lossy points; no conformance is claimed and no format is required by the semantics.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ] }, "sources": [ { "id": "SRC-001", "title": "RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)", "organization": "Internet Engineering Task Force (IETF)", "url": "https://datatracker.ietf.org/doc/html/rfc5545", "version_or_date": "September 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:05:00Z", "relevance": "Normative source for VEVENT identity (UID, RECURRENCE-ID, SEQUENCE), ORGANIZER/ATTENDEE with ROLE, PARTSTAT, CUTYPE, RSVP, DELEGATED-TO/FROM and MEMBER, DTSTART/DTEND/DURATION, RRULE, STATUS, CLASS, LOCATION and TRANSP." }, { "id": "SRC-002", "title": "RFC 8984: JSCalendar: A JSON Representation of Calendar Data", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc8984.html", "version_or_date": "July 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:06:00Z", "relevance": "Participant object semantics (roles, participationStatus, expectReply, kind, delegatedTo/From, memberOf), VirtualLocation, recurrenceOverrides, privacy levels, and the rule that participant-only changes do not increment sequence." }, { "id": "SRC-003", "title": "RFC 9073: Event Publishing Extensions to iCalendar", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc9073.html", "version_or_date": "August 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:07:00Z", "relevance": "PARTICIPANT component and PARTICIPANT-TYPE, VLOCATION and LOCATION-TYPE, VRESOURCE and RESOURCE-TYPE, CALENDAR-ADDRESS and STRUCTURED-DATA — support for structured participant, location and resource context." }, { "id": "SRC-004", "title": "RFC 5546: iCalendar Transport-Independent Interoperability Protocol (iTIP)", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc5546.html", "version_or_date": "December 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:08:00Z", "relevance": "Scheduling methods (PUBLISH, REQUEST, REPLY, ADD, CANCEL, REFRESH, COUNTER, DECLINECOUNTER), organizer/attendee authority split, SEQUENCE increment rules and DTSTAMP as tiebreaker, and the delegation workflow." }, { "id": "SRC-005", "title": "RFC 7986: New Properties for iCalendar", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc7986.html", "version_or_date": "October 2016", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:09:00Z", "relevance": "CONFERENCE property for conferencing access information, with FEATURE values AUDIO, CHAT, FEED, MODERATOR, PHONE, SCREEN, VIDEO and the LABEL parameter." }, { "id": "SRC-006", "title": "RFC 6501: Conference Information Data Model for Centralized Conferencing (XCON)", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc6501.html", "version_or_date": "March 2012", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:10:00Z", "relevance": "Conference object identifier (XCON-URI), conference-description and conference-state, admission policies (closedAuthenticated, openAuthenticated, anonymous), user roles (administrator, moderator, participant), endpoints, floor control and sidebars." }, { "id": "SRC-007", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:11:00Z", "relevance": "Timestamp profile requiring seconds and an explicit time offset or Z, and the documented distinction between '-00:00' (offset unknown) and 'Z'/'+00:00' (UTC reference)." }, { "id": "SRC-008", "title": "iCalendar Element Registries", "organization": "Internet Assigned Numbers Authority (IANA)", "url": "https://www.iana.org/assignments/icalendar/icalendar.xhtml", "version_or_date": "Last updated 2026-03-26", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:12:00Z", "relevance": "Normative registries for participation statuses, participation roles, calendar user types, methods, classifications, relationship types, participant types, resource types and feature types — the governed code lists this model binds to." }, { "id": "SRC-009", "title": "Event — Schema.org Type", "organization": "Schema.org Community Group (W3C)", "url": "https://schema.org/Event", "version_or_date": "Schema.org version 30.0, 2026-03-19", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-29T09:13:00Z", "relevance": "eventStatus (EventScheduled, EventCancelled, EventPostponed, EventRescheduled, EventMovedOnline), eventAttendanceMode, organizer/attendee/performer, subEvent/superEvent, recordedIn and maximumAttendeeCapacity." }, { "id": "SRC-010", "title": "Akoma Ntoso Version 1.0 Part 1: XML Vocabulary, OASIS Standard", "organization": "OASIS LegalDocML Technical Committee", "url": "https://docs.oasis-open.org/legaldocml/akn-core/v1.0/os/part1-vocabulary/akn-core-v1.0-os-part1-vocabulary.html", "version_or_date": "OASIS Standard, 29 August 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:14:00Z", "relevance": "Debate and debateReport vocabulary: rollCall, quorum, voting and declarationOfVote, proceduralMotions, pointOfOrder, adjournment, administrationOfOath, speech/speechGroup with by/as/to attribution, and TLCPerson/TLCRole/TLCOrganization references." }, { "id": "SRC-011", "title": "Companies Act 2006, Part 13, Chapter 6: Records of resolutions etc.", "organization": "UK Government (legislation.gov.uk, The National Archives)", "url": "https://www.legislation.gov.uk/ukpga/2006/46/part/13/chapter/6", "version_or_date": "c.46, as revised on legislation.gov.uk", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-29T09:15:00Z", "relevance": "Section 355 requires records of resolutions and general meeting minutes to be kept for at least ten years; section 356 makes signed minutes evidence that the meeting was duly held; section 358 governs inspection." }, { "id": "SRC-012", "title": "5 U.S.C. § 552b — Open meetings (Government in the Sunshine Act)", "organization": "Legal Information Institute, Cornell Law School (reproducing the United States Code)", "url": "https://www.law.cornell.edu/uscode/text/5/552b", "version_or_date": "Current U.S. Code text as published by LII", "source_type": "legislation", "primary_source": false, "authority_tier": 2, "accessed_at": "2026-08-29T09:16:00Z", "relevance": "Statutory definition of a 'meeting' as deliberation by the number of members required to take action, the open-meeting default, the ten closure exemptions, the recorded majority vote required to close, and retention of a transcript, recording or minutes of closed portions." }, { "id": "SRC-013", "title": "5 U.S.C. § 1009 — Advisory committee procedures (Federal Advisory Committee Act)", "organization": "Legal Information Institute, Cornell Law School (reproducing the United States Code)", "url": "https://www.law.cornell.edu/uscode/text/5/1009", "version_or_date": "Current U.S. Code text as published by LII", "source_type": "legislation", "primary_source": false, "authority_tier": 2, "accessed_at": "2026-08-29T09:17:00Z", "relevance": "Federal Register notice of each meeting, the open-meeting requirement, and detailed minutes containing persons present, a complete and accurate description of matters discussed and conclusions reached, and copies of reports, with accuracy certified by the chairman." }, { "id": "SRC-014", "title": "Accessibility of Remote Meetings (W3C Group Note)", "organization": "World Wide Web Consortium (W3C), Accessible Platform Architectures Working Group", "url": "https://www.w3.org/TR/remote-meetings/", "version_or_date": "W3C Group Note, 22 July 2022", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-29T09:18:00Z", "relevance": "Requirements for real-time captions, sign language interpretation, advance circulation of agenda and materials in accessible native formats, early collection of accommodation needs, and equivalent access for remote and in-room participants in hybrid meetings." }, { "id": "SRC-015", "title": "meetingAttendanceReport resource type — Microsoft Graph v1.0", "organization": "Microsoft", "url": "https://learn.microsoft.com/en-us/graph/api/resources/meetingattendancereport", "version_or_date": "Microsoft Graph v1.0 reference, page updated 2025-05-13", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 3, "accessed_at": "2026-08-29T09:19:00Z", "relevance": "Concrete platform attendance observation: meetingStartDateTime, meetingEndDateTime, totalParticipantCount, attendanceRecords with join/leave intervals, and a documented one-year retention policy from the meeting date for attendance reports." } ], "structure": { "bundles": [ { "id": "session-constitution", "name": "Session constitution and convening basis", "description": "What this occurrence is, how it is identified and classified, and the authority and notice under which it exists.", "rationale": "Nothing else about a meeting is interpretable until the occurrence is uniquely identifiable, correctly classified for the procedural regime that applies to it, and traceable to a party entitled to convene it. Statutory open-meeting and company-law regimes attach their obligations to exactly these facts.", "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-012", "SRC-013" ], "layers": [ { "id": "identity-and-classification", "name": "Identity and classification", "description": "Stable identification of the occurrence across systems and revisions, and the classification axes that select the applicable obligations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008", "SRC-009" ], "findings": [ { "id": "session-instance-identity", "name": "Occurrence identity and revision resolution", "description": "How one meeting occurrence is distinguished from its series, from its own earlier revisions, and from copies of it held in other systems.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "master-identifier-of-occurrence", "text": "Which authoritative master-system identifier designates this occurrence, and which governed global identifier is published for it?", "kind": "identity", "answer_data": [ "Master-system meeting identifier and the name of the issuing system of record", "Governed global identifier or IRI published for the occurrence", "Flag stating which identifier is authoritative where both exist" ] }, { "id": "series-instance-discriminator", "text": "How is a single occurrence distinguished from its recurring series when both carry the same identifier?", "kind": "identity", "answer_data": [ "Series identifier", "Recurrence instance discriminator with its own time zone reference", "Detached-instance flag" ] }, { "id": "prevailing-revision-rule", "text": "Which revision counter and timestamp determine which copy of the meeting definition prevails when two differ?", "kind": "provenance", "answer_data": [ "Revision sequence number", "Definition last-updated instant", "Originating product or system identifier", "Tie-break rule applied" ] }, { "id": "external-identifier-binding", "text": "Which external system identifiers are bound to this occurrence, and which of them may be treated as authoritative?", "kind": "interoperability", "answer_data": [ "Conferencing platform meeting identifier", "Calendar object identifier", "Register or docket reference", "Authority flag per bound identifier" ] } ], "data_elements": [ { "id": "session-identifier", "name": "Session identifier", "description": "Authoritative identifier of the occurrence, assigned by the identity priority of the adopting Dimension.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "series-identifier", "name": "Series identifier", "description": "Identifier of the recurring series that generated this occurrence, where one exists.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "recurrence-instance-key", "name": "Recurrence instance key", "description": "Discriminator that selects this occurrence within its series, expressed as the original scheduled start with its time zone.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "revision-sequence", "name": "Revision sequence", "description": "Monotonic counter incremented when the convener changes the definition of the occurrence.", "value_kind": "number", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-002" ] }, { "id": "definition-updated-at", "name": "Definition updated at", "description": "Instant at which the current revision of the definition was created.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "external-identifier-map", "name": "External identifier binding", "description": "Bound identifiers held by other systems for the same occurrence, each with its authority flag.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-015" ] } ], "artifacts": [], "inline_only_rationale": "Identity is reference data carried on the occurrence entry itself: identifiers, a revision counter, a revision instant and a binding map. No document, media object or issued instrument is produced by resolving identity, and materialising one would create a second competing identifier space." }, { "id": "session-classification", "name": "Session classification", "description": "The classification axes — meeting type, formality, attendance mode and openness class — that select which procedural, disclosure and record obligations bind this occurrence.", "source_refs": [ "SRC-009", "SRC-012", "SRC-013", "SRC-008" ], "questions": [ { "id": "meeting-type-and-formality", "text": "What meeting type and formality class does this session belong to under the convening body's rules?", "kind": "classification", "answer_data": [ "Meeting type code (for example board, committee, general meeting, working session)", "Formality class (constituted or informal)", "Code list reference and its governing register" ] }, { "id": "attendance-mode-assignment", "text": "Is the session conducted in person, online or in a mixed mode, and which mode applies to each participant?", "kind": "classification", "answer_data": [ "Session-level attendance mode", "Per-participant mode where mixed", "Equivalence statement for mixed mode" ] }, { "id": "openness-class-scope", "text": "Which openness class applies to the session as a whole, and may individual portions carry a different class?", "kind": "access", "answer_data": [ "Session openness class", "Portion-level openness override flag", "Instrument that fixes the default class" ] }, { "id": "post-notice-reclassification", "text": "Which classification changes are permitted after the notice has been issued, and what re-notification does each trigger?", "kind": "constraint", "answer_data": [ "Permitted classification transitions", "Re-notification obligation per transition", "Minimum lead time for the re-issued notice" ] } ], "data_elements": [ { "id": "meeting-type-code", "name": "Meeting type code", "description": "Governed code identifying the procedural class of the occurrence.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-012", "SRC-013" ] }, { "id": "attendance-mode-code", "name": "Attendance mode", "description": "Whether the occurrence is offline, online or mixed.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "openness-class-code", "name": "Openness class", "description": "Whether the occurrence defaults to open, closed or restricted observation.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-012" ] }, { "id": "classification-basis-reference", "name": "Classification basis reference", "description": "Reference to the rule, statute or terms of reference that fixes the classification.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] } ], "artifacts": [], "inline_only_rationale": "Classification is a small set of coded values plus a pointer to the instrument that fixes them. The instrument itself is a document owned by another model, so declaring an artifact here would duplicate the governing body's rule set rather than describe the occurrence." } ] }, { "id": "convening-basis", "name": "Convening authority and notice", "description": "The binding to the party entitled to call the session, and the convocation act that makes it effective.", "source_refs": [ "SRC-011", "SRC-012", "SRC-013", "SRC-004" ], "findings": [ { "id": "convening-authority-binding", "name": "Convening authority binding", "description": "Reference to the body, office or instrument under whose authority the session is called, and the presiding arrangement for this occurrence only.", "source_refs": [ "SRC-011", "SRC-012", "SRC-010" ], "questions": [ { "id": "convening-body-and-entitlement", "text": "Which governance body or office convened this session, and under which rule or instrument was it entitled to do so?", "kind": "authority", "answer_data": [ "Convening body reference", "Convening instrument reference (statute, articles, terms of reference)", "Office or role that exercised the power" ] }, { "id": "requisition-threshold-met", "text": "Who requested the session, and was a minimum requisition threshold required and satisfied?", "kind": "requirement", "answer_data": [ "Requisitioner references", "Required threshold expression", "Threshold satisfied flag and evidence pointer" ] }, { "id": "presiding-officer-for-occurrence", "text": "Which chair or acting officer presided over this occurrence, and how was that determined?", "kind": "ownership", "answer_data": [ "Presiding officer reference", "Designation basis (standing role, election at the sitting, deputising rule)", "Interval of the session over which each officer presided" ] }, { "id": "terms-of-reference-resolution", "text": "Which standing terms of reference constrain this session, and from where are they resolved at read time?", "kind": "relationship", "answer_data": [ "Terms of reference pointer", "Resolution endpoint or register", "Version or effective-date marker of the referenced terms" ] } ], "data_elements": [ { "id": "convening-body-reference", "name": "Convening body reference", "description": "Reference to the governance body or office that convened the occurrence.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] }, { "id": "convening-instrument-reference", "name": "Convening instrument reference", "description": "Reference to the rule, statute or terms of reference conferring the power to convene.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "presiding-officer-reference", "name": "Presiding officer reference", "description": "Party reference for the officer presiding, with the interval presided over.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "requisition-basis", "name": "Requisition basis", "description": "Statement of who requested the session and against which threshold.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [], "inline_only_rationale": "The mandate, membership and delegated powers that make the convening act valid are owned by WM-ORG-018. This finding therefore holds only pointers and occurrence-scoped parameters; issuing an artifact here would reproduce the body's constitutional documents inside a session record." }, { "id": "notice-and-convocation", "name": "Notice and convocation", "description": "The act of announcing the session to those entitled to attend or observe, and the sufficiency tests that attach to that announcement.", "source_refs": [ "SRC-012", "SRC-013", "SRC-004", "SRC-011" ], "questions": [ { "id": "notice-issuance-parameters", "text": "What notice was issued, to whom, through which channel, and how long before the session?", "kind": "process", "answer_data": [ "Notice issued instant", "Addressee set or public channel", "Lead duration between issue and planned start" ] }, { "id": "mandatory-notice-content", "text": "Does the applicable regime require public announcement, and which content must that announcement carry?", "kind": "requirement", "answer_data": [ "Public announcement required flag and its legal basis", "Mandatory content elements (time, place, subject matter, open or closed status, contact person)", "Publication venue" ] }, { "id": "notice-defect-consequence", "text": "What is the consequence for the validity of business transacted if the notice period or content requirement was not met?", "kind": "exception", "answer_data": [ "Defect description", "Curative step taken (waiver, re-notice, ratification)", "Validity impact statement" ] }, { "id": "amended-notice-trigger", "text": "Which post-issuance changes require an amended or re-issued notice?", "kind": "constraint", "answer_data": [ "Change types that trigger re-notice", "Minimum re-notice lead time", "Reference from amended notice to the superseded one" ] } ], "data_elements": [ { "id": "notice-issued-at", "name": "Notice issued at", "description": "Instant at which the convocation notice was issued or published.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013", "SRC-007" ] }, { "id": "notice-channel", "name": "Notice channel", "description": "Channel through which the notice was communicated or published.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "notice-lead-duration", "name": "Notice lead duration", "description": "Interval between notice issuance and the planned start.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "notice-defect-note", "name": "Notice defect note", "description": "Recorded defect in notice and the curative step taken.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "meeting-notice", "name": "Meeting notice or convocation", "description": "The issued announcement of the session carrying time, place or access channel, subject matter, openness status and contact point.", "media_or_form": [ "written convocation", "calendar invitation message", "public register or gazette announcement" ], "serial": true, "identity_strategy": "Notice identifier assigned by the issuing secretariat or, where a public register is used, the register's published notice identifier, which is authoritative; the notice always carries the session identifier and the revision sequence current at issue.", "source_refs": [ "SRC-013", "SRC-012", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "time-and-setting", "name": "Time, series position and setting", "description": "When the occurrence is scheduled and observed, where it sits in a series, and the physical, virtual and accessibility conditions under which it takes place.", "rationale": "A session is bounded in time and place, and both the planned and the observed values carry procedural weight. Calendaring standards fix the time and recurrence semantics, conferencing standards fix the access channel, and accessibility guidance fixes the conditions for equivalent participation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-014" ], "layers": [ { "id": "time-and-series", "name": "Timing, series position and schedule change", "description": "Planned and observed temporal extent, recurrence position, and the transitions that move or end the occurrence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009" ], "findings": [ { "id": "planned-and-observed-timing", "name": "Planned and observed timing", "description": "The scheduled temporal extent of the occurrence and the times actually observed for opening, suspension, resumption and close.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-015" ], "questions": [ { "id": "planned-extent-and-zone", "text": "What are the planned start and end of the session, and in which named time zone were they expressed?", "kind": "temporal", "answer_data": [ "Planned start instant", "Planned end instant or planned duration", "Named scheduling time zone identifier" ] }, { "id": "observed-session-times", "text": "What actual opening, suspension, resumption and closing times were observed, and by which observer?", "kind": "measurement", "answer_data": [ "Observed instants per procedural boundary", "Observer or capturing system reference", "Observation or ingestion instant where it differs from the event instant" ] }, { "id": "governing-time-for-deadlines", "text": "Which time value governs a procedural deadline when the planned and observed times diverge?", "kind": "constraint", "answer_data": [ "Governing time selection rule", "Deadline expressions anchored to it", "Divergence tolerance" ] }, { "id": "unbounded-session-handling", "text": "How are all-day, open-ended and multi-day sessions bounded in this model?", "kind": "definition", "answer_data": [ "Boundary convention for each case", "Treatment of overnight adjournment as one occurrence or several", "Rule for sessions with no scheduled end" ] } ], "data_elements": [ { "id": "planned-start", "name": "Planned start", "description": "Scheduled start of the occurrence.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "planned-end", "name": "Planned end", "description": "Scheduled end of the occurrence, where a planned duration is not used instead.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "scheduling-time-zone", "name": "Scheduling time zone", "description": "Named time zone in which the planned times were expressed, retained alongside the offset.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "observed-open-at", "name": "Observed open at", "description": "Instant at which the session was actually opened.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015", "SRC-007" ] }, { "id": "observed-close-at", "name": "Observed close at", "description": "Instant at which the session was actually closed or adjourned sine die.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "suspension-interval", "name": "Suspension interval", "description": "Intervals during which proceedings were suspended and later resumed.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "Timing is a set of instants, a named zone and observation metadata held directly on the occurrence. Any document that carries these values is either the notice or the durable record, both of which are modelled elsewhere, so no separate artifact belongs to this finding." }, { "id": "series-and-recurrence-position", "name": "Series membership and recurrence position", "description": "Whether the occurrence was generated by a recurrence rule, what it inherits from the series, and how it relates to the sessions before and after it.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "questions": [ { "id": "generating-recurrence-rule", "text": "Was this occurrence generated by a recurrence rule, and what rule expression produced it?", "kind": "composition", "answer_data": [ "Recurrence rule expression", "Series definition reference", "Generated or manually created flag" ] }, { "id": "instance-override-scope", "text": "Which properties of this occurrence override the series definition and which remain inherited?", "kind": "relationship", "answer_data": [ "Overridden property set", "Inherited property set", "Override patch reference" ] }, { "id": "series-detachment-effect", "text": "How is an occurrence detached from its series, and what identity does it carry afterwards?", "kind": "lifecycle", "answer_data": [ "Detachment trigger", "Identifier retained or newly minted", "Residual link to the former series" ] }, { "id": "adjacent-session-linkage", "text": "Which sessions immediately precede and follow this one for the purpose of carrying business over?", "kind": "relationship", "answer_data": [ "Preceding occurrence reference", "Following occurrence reference", "Carried-over item references" ] } ], "data_elements": [ { "id": "recurrence-rule-expression", "name": "Recurrence rule expression", "description": "Rule that generated the occurrence within its series.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "series-reference", "name": "Series reference", "description": "Reference to the series or superordinate event of which this is an instance.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "instance-override-flag", "name": "Instance override flag", "description": "Whether this occurrence differs from the series-generated default.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "adjacent-session-reference", "name": "Adjacent session reference", "description": "References to the preceding and following occurrences in the series.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "Series position is expressed entirely as rule text, references and an override flag. Materialising a series as an artifact would either duplicate the parent activity model's series entity or freeze a computed expansion that must stay derivable." }, { "id": "schedule-change-and-cancellation", "name": "Schedule change, postponement and cancellation", "description": "The scheduling status of the occurrence and the authorised transitions that move, postpone, replace or cancel it.", "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ], "questions": [ { "id": "scheduling-status-state-set", "text": "What is the current scheduling status of the occurrence, and which statuses are terminal?", "kind": "state", "answer_data": [ "Current status code", "Permitted transitions", "Terminal status set" ] }, { "id": "schedule-change-authority", "text": "Who may postpone, reschedule or cancel this occurrence, and what confirmation does each action require?", "kind": "authority", "answer_data": [ "Authorised actor reference per action", "Confirmation or countersignature requirement", "Notification obligation triggered" ] }, { "id": "counter-proposal-resolution", "text": "How is a counter-proposal of a different time recorded, and how is it resolved?", "kind": "process", "answer_data": [ "Counter-proposal content and proposer", "Resolution outcome (accepted, declined)", "Resulting revision sequence" ] }, { "id": "obligations-surviving-cancellation", "text": "Which obligations survive a cancellation and which are extinguished by it?", "kind": "requirement", "answer_data": [ "Surviving record and notification obligations", "Extinguished obligations", "Reference to the replacement occurrence where one exists" ] } ], "data_elements": [ { "id": "scheduling-status", "name": "Scheduling status", "description": "Coded status of the occurrence, aligned to calendaring and event vocabularies.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] }, { "id": "status-changed-at", "name": "Status changed at", "description": "Instant at which the scheduling status last changed.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "schedule-change-reason", "name": "Schedule change reason", "description": "Stated reason for postponement, rescheduling or cancellation.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "superseding-session-reference", "name": "Superseding session reference", "description": "Reference to the occurrence that replaces a postponed or rescheduled session.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "scheduling-message", "name": "Scheduling message", "description": "An exchanged scheduling communication that creates, updates, answers, counter-proposes or cancels the occurrence between the convener and the invited parties.", "media_or_form": [ "invitation request", "participation reply", "cancellation notice", "counter-proposal" ], "serial": false, "identity_strategy": "Message identifier assigned by the sending scheduling agent, always carrying the session identifier, the recurrence instance key where applicable, the revision sequence and the message timestamp used as the tiebreaker when sequences match.", "source_refs": [ "SRC-004", "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "setting-and-access-channel", "name": "Setting, access channel and accessibility", "description": "The physical venue and resources, the virtual conferencing endpoints, and the accessibility conditions for equivalent participation.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-014" ], "findings": [ { "id": "physical-setting-and-resources", "name": "Physical setting and reserved resources", "description": "Where the occurrence physically takes place, what capacity the setting has, and which rooms, equipment and support services are reserved for it.", "source_refs": [ "SRC-003", "SRC-009", "SRC-001" ], "questions": [ { "id": "authoritative-place-reference", "text": "Where does the session physically take place, and which place record is authoritative for that location?", "kind": "spatial", "answer_data": [ "Venue reference to the place model", "Local room or floor designation", "Coordinates or address as published on the notice" ] }, { "id": "reserved-resource-set", "text": "Which rooms, equipment and support resources are reserved for the session, and by whom were they reserved?", "kind": "composition", "answer_data": [ "Resource references with resource type codes", "Reserving party reference", "Reservation interval" ] }, { "id": "capacity-and-oversubscription", "text": "What is the capacity of the setting, and how is over-subscription handled?", "kind": "constraint", "answer_data": [ "Maximum attendee capacity", "Prioritisation or waiting rule", "Overflow arrangement" ] }, { "id": "no-physical-venue-case", "text": "How is the physical setting recorded when the session has no physical venue at all?", "kind": "exception", "answer_data": [ "Null-venue convention", "Substituted virtual location reference", "Effect on notice content requirements" ] } ], "data_elements": [ { "id": "venue-reference", "name": "Venue reference", "description": "Reference to the authoritative place record for the physical setting.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "room-designation", "name": "Room designation", "description": "Local designation of the room or space within the venue.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "venue-coordinates", "name": "Venue coordinates", "description": "Point geometry for the setting where published.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "reserved-resource", "name": "Reserved resource", "description": "Rooms, equipment and services reserved for the occurrence with their resource type codes.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "attendee-capacity", "name": "Attendee capacity", "description": "Maximum number of attendees the setting or session admits.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "Venue and resource master records are owned by place and asset models; this finding carries references, a local designation and capacity numbers. A booking confirmation belongs to the reservation system, not to the semantics of the session." }, { "id": "virtual-and-hybrid-access-channel", "name": "Virtual access channel and mixed-mode equivalence", "description": "The conferencing endpoints published for the session, the admission control applied to them, and what guarantees equivalent participation across modes.", "source_refs": [ "SRC-005", "SRC-006", "SRC-002", "SRC-014" ], "questions": [ { "id": "published-endpoint-features", "text": "Which conferencing endpoints are published for this session, and what features does each provide?", "kind": "interoperability", "answer_data": [ "Endpoint URI per channel", "Feature codes (audio, video, chat, screen, phone, moderator)", "Human-readable label per endpoint" ] }, { "id": "moderator-credential-separation", "text": "Which credential or access code distinguishes moderator entry from ordinary participant entry?", "kind": "security", "answer_data": [ "Reference to the secret store holding the moderator code", "Distribution rule for participant access codes", "Rotation trigger" ] }, { "id": "virtual-admission-control", "text": "How is admission to the virtual room controlled before and during the session?", "kind": "access", "answer_data": [ "Admission policy code (anonymous, authenticated, closed list)", "Lobby or waiting-room behaviour", "Admitting role reference" ] }, { "id": "mixed-mode-equivalence", "text": "In a mixed-mode session, what guarantees that remote and in-room participants have equivalent standing?", "kind": "quality", "answer_data": [ "Equivalence measures adopted", "Known asymmetries", "Escalation route when equivalence fails" ] } ], "data_elements": [ { "id": "conference-endpoint", "name": "Conference endpoint", "description": "Published access point for the conferencing system serving the occurrence.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "endpoint-feature-code", "name": "Endpoint feature code", "description": "Governed feature codes describing what an endpoint supports.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "admission-control-mode", "name": "Admission control mode", "description": "Policy governing who may join the virtual room.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "moderator-secret-reference", "name": "Moderator secret reference", "description": "Pointer to the externally held moderator access code; the value itself is never stored here.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [], "inline_only_rationale": "Endpoints and admission modes are reference data, and access codes must remain in an external secret store rather than being materialised as an artifact of the session. Conference state and floor mechanics are the platform's runtime concern, not a document this model issues." }, { "id": "accessibility-and-accommodation", "name": "Accessibility provision and accommodation", "description": "The accessibility services provided for the occurrence, how participant accommodation needs are captured, and how provision quality is assessed.", "source_refs": [ "SRC-014", "SRC-009" ], "questions": [ { "id": "accessibility-services-provided", "text": "Which accessibility services are provided for this session, and who requested each one?", "kind": "requirement", "answer_data": [ "Service codes (live captioning, sign language interpretation, language interpretation, assistive listening)", "Requesting party reference", "Provider reference" ] }, { "id": "material-circulation-deadline", "text": "By when must agenda and materials be circulated so that participants using assistive technology can prepare?", "kind": "temporal", "answer_data": [ "Circulation deadline instant", "Required accessible formats", "Actual circulation instant" ] }, { "id": "unmet-accommodation-fallback", "text": "How are accommodation requests captured, and what fallback applies when a request cannot be met?", "kind": "exception", "answer_data": [ "Capture channel and deadline", "Unmet request record with reason", "Fallback measure and who authorised it" ] }, { "id": "caption-interpretation-quality", "text": "How is the quality of live captioning or interpretation assessed for this occurrence?", "kind": "quality", "answer_data": [ "Quality assessment method", "Automatic versus human-corrected indication", "Defect notes raised during the session" ] } ], "data_elements": [ { "id": "accommodation-request", "name": "Accommodation request", "description": "Recorded accessibility need raised for this occurrence, with its status.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "accessibility-service-code", "name": "Accessibility service code", "description": "Coded accessibility service actually provided.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "material-circulation-at", "name": "Material circulation instant", "description": "Instant at which accessible materials were circulated.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014", "SRC-007" ] }, { "id": "caption-quality-note", "name": "Caption quality note", "description": "Assessment note on live caption or interpretation quality for this occurrence.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] } ], "artifacts": [ { "id": "accommodation-request-record", "name": "Accessibility accommodation request", "description": "The captured request for an accessibility accommodation for this occurrence, together with the disposition given to it.", "media_or_form": [ "request form submission", "service desk ticket", "correspondence entry" ], "serial": false, "identity_strategy": "Request identifier issued by the capturing service desk or registration system, bound to the session identifier and the requesting party reference; where no such system exists a Dimension-assigned ULID is used.", "source_refs": [ "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "participation-and-quorum", "name": "Participation, presence and quorum", "description": "Who was invited, in what capacity, who actually took part, and whether the occurrence was competent to transact business.", "rationale": "Calendaring standards define invitation roles and response states normatively; conferencing platforms produce observed presence data; company law and open-meeting law attach validity to quorum and to the recorded list of persons present. These are distinct facts and must not be conflated.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-011", "SRC-013", "SRC-015" ], "layers": [ { "id": "roles-and-invitation", "name": "Roles, invitation state and substitution", "description": "The invited population, the capacity each party holds, and the mechanisms by which participation can be transferred or withdrawn.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "participant-roles-and-invitation-state", "name": "Participant roles and invitation state", "description": "The capacity in which each invited party is expected to take part, and the current state of their response to the invitation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-008" ], "questions": [ { "id": "role-per-invited-party", "text": "Which role does each invited party hold in this occurrence, and which roles must be filled for it to proceed?", "kind": "classification", "answer_data": [ "Role code per invitee (chair, required participant, optional participant, non-participant, secretary)", "Mandatory role set for this meeting type", "Vacancy indication where a mandatory role is unfilled" ] }, { "id": "invitation-response-state", "text": "What invitation response has each invited party given, and when was that response last updated?", "kind": "state", "answer_data": [ "Participation status code per invitee", "Response updated instant", "Free-text participation comment where given" ] }, { "id": "invitee-kind-distinction", "text": "Which invited entries denote individuals, which denote groups, and which denote rooms or other resources?", "kind": "definition", "answer_data": [ "Calendar user type per entry", "Group membership reference where the entry stands for a group", "Resource entries excluded from headcount" ] }, { "id": "response-expectation-default", "text": "Is a response expected from each invitee, and what is assumed when none is given by the session start?", "kind": "constraint", "answer_data": [ "Response-expected flag per invitee", "Default assumed status", "Effect of a non-response on quorum counting" ] } ], "data_elements": [ { "id": "invitee-reference", "name": "Invitee reference", "description": "Reference to the party model entry for an invited person, group or resource.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "participant-role-code", "name": "Participant role code", "description": "Governed role code describing the capacity of the invitee at this occurrence.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "participation-status-code", "name": "Participation status code", "description": "Governed response state of the invitee to the invitation.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "participant-kind-code", "name": "Participant kind code", "description": "Whether the invited entry is an individual, group, room or other resource.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "response-updated-at", "name": "Response updated at", "description": "Instant at which the participation status was last changed by the invitee.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] } ], "artifacts": [], "inline_only_rationale": "Invitation state is a per-party tuple of role, status and instant held on the occurrence, and the parties themselves are mastered elsewhere. The document that carries these values outward is the scheduling message already declared under schedule change, so no additional artifact is warranted." }, { "id": "delegation-proxy-and-recusal", "name": "Delegation, proxy and recusal", "description": "Transfer of participation to another party, the rights that transfer with it, and the withdrawal of a participant from part of the proceedings.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011" ], "questions": [ { "id": "delegation-target-record", "text": "May an invitee delegate participation, and to whom was participation delegated for this occurrence?", "kind": "relationship", "answer_data": [ "Delegating party reference", "Delegate party reference", "Delegation acceptance state" ] }, { "id": "delegated-rights-scope", "text": "Does a delegate or alternate inherit the delegator's speaking and voting rights in full?", "kind": "authority", "answer_data": [ "Rights transferred", "Rights withheld", "Instrument that fixes the transfer rule" ] }, { "id": "proxy-instruction-lifetime", "text": "How is a proxy or voting instruction recorded, and when does it lapse?", "kind": "lifecycle", "answer_data": [ "Proxy instruction reference", "Validity interval", "Revocation event and instant" ] }, { "id": "recusal-trigger-and-scope", "text": "Which declared interests require a participant to withdraw from part of the proceedings, and over which items?", "kind": "exception", "answer_data": [ "Declared interest statement", "Affected agenda item references", "Withdrawal interval and whether the participant was counted for quorum" ] } ], "data_elements": [ { "id": "delegation-link", "name": "Delegation link", "description": "Directed link recording that participation was delegated from one party to another for this occurrence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "proxy-instruction-reference", "name": "Proxy instruction reference", "description": "Reference to the externally held proxy or voting instruction.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "substitution-scope-code", "name": "Substitution scope", "description": "Extent of rights transferred to a delegate or alternate.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "recusal-declaration", "name": "Recusal declaration", "description": "Declared interest and consequent withdrawal from named agenda items.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011", "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "Delegation and recusal are relationship facts and interval statements scoped to this occurrence. The proxy instrument itself is a governed document owned by the document or company-secretarial model and is referenced rather than reproduced." } ] }, { "id": "presence-and-quorum", "name": "Presence observation and quorum determination", "description": "What was actually observed about presence, and the competence determination derived from it against an externally owned threshold.", "source_refs": [ "SRC-013", "SRC-011", "SRC-012", "SRC-015", "SRC-010" ], "findings": [ { "id": "presence-observation", "name": "Presence observation", "description": "Observed presence of parties during the occurrence, the source and reliability of each observation, and reconciliation between competing sources.", "source_refs": [ "SRC-015", "SRC-013", "SRC-010" ], "questions": [ { "id": "presence-interval-per-party", "text": "Who was actually present, and for which intervals of the occurrence was each party present?", "kind": "measurement", "answer_data": [ "Party reference per presence record", "Join and leave instants per interval", "Total attendance duration" ] }, { "id": "presence-observation-provenance", "text": "Which observation source produced each presence record, and how reliable is that source?", "kind": "provenance", "answer_data": [ "Observation source code (roll call, signed sheet, platform telemetry)", "Observing actor or system reference", "Observation or ingestion instant distinct from the event instant" ] }, { "id": "presence-source-reconciliation", "text": "How is presence reconciled when in-room and platform-derived observations disagree?", "kind": "validation", "answer_data": [ "Precedence rule between sources", "Recorded discrepancy", "Corrected value and who authorised the correction" ] }, { "id": "platform-presence-availability", "text": "For how long does platform-derived presence data remain retrievable before it expires at source?", "kind": "retention", "answer_data": [ "Source retention window", "Export deadline", "Reference to the exported copy once taken" ] } ], "data_elements": [ { "id": "presence-record", "name": "Presence record", "description": "Per-party observed presence at the occurrence with role as observed.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015", "SRC-013" ] }, { "id": "presence-interval", "name": "Presence interval", "description": "Join and leave instants forming one continuous interval of presence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "observed-participant-count", "name": "Observed participant count", "description": "Total number of parties observed present.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "presence-observed-at", "name": "Presence observed at", "description": "Instant at which the presence observation was captured or ingested.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-015" ] } ], "artifacts": [ { "id": "attendance-register", "name": "Attendance register", "description": "The list of persons recorded as present at the occurrence, in the form required by the applicable regime.", "media_or_form": [ "signed attendance sheet", "roll-call list", "attendance list annexed to the record" ], "serial": false, "identity_strategy": "Identified by the session identifier plus a register sequence within the occurrence; where a secretariat register system exists, its register entry identifier is authoritative.", "source_refs": [ "SRC-013", "SRC-010", "SRC-011" ] }, { "id": "platform-attendance-report", "name": "Platform attendance report", "description": "Exported attendance observation produced by the conferencing platform, containing per-participant join and leave intervals and totals.", "media_or_form": [ "conferencing platform attendance report", "join and leave interval export" ], "serial": false, "identity_strategy": "The platform's report identifier is authoritative for the exported copy; it is bound to the session identifier and to the platform conference object identifier, and the export instant is recorded separately from the meeting instants.", "source_refs": [ "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "quorum-determination", "name": "Quorum determination", "description": "The determination, at this occurrence, of whether the number and composition of those present met the threshold required to transact business.", "source_refs": [ "SRC-011", "SRC-012", "SRC-010" ], "questions": [ { "id": "applicable-quorum-rule", "text": "Which quorum rule applies to this occurrence, and which instrument defines the threshold?", "kind": "requirement", "answer_data": [ "Reference to the quorum rule owned by the convening body", "Threshold expression as resolved at the occurrence", "Composition conditions beyond a bare count" ] }, { "id": "quorum-satisfaction-points", "text": "Was the quorum satisfied at the opening and at each point where business was decided?", "kind": "validation", "answer_data": [ "Check instant per determination", "Counted parties and exclusions", "Satisfied or not-satisfied outcome per check" ] }, { "id": "quorum-loss-consequence", "text": "What is the effect on business transacted if the quorum is lost part-way through the occurrence?", "kind": "exception", "answer_data": [ "Loss instant", "Items affected", "Consequence applied (suspension, adjournment, invalidation of the item)" ] }, { "id": "quorum-verification-trigger", "text": "Who verifies the quorum, and on whose request must a verification be carried out?", "kind": "authority", "answer_data": [ "Verifying officer reference", "Minimum requesting number where a request is required", "Verification method used" ] } ], "data_elements": [ { "id": "quorum-rule-reference", "name": "Quorum rule reference", "description": "Pointer to the externally owned rule that fixes the threshold for this occurrence.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "quorum-threshold-value", "name": "Quorum threshold value", "description": "Threshold as resolved for this occurrence, expressed as a count or proportion.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] }, { "id": "quorum-check", "name": "Quorum check", "description": "One determination of quorum with its instant, counted population and outcome.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010", "SRC-012" ] }, { "id": "quorum-satisfied-flag", "name": "Quorum satisfied flag", "description": "Outcome of the most recent quorum determination.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [], "inline_only_rationale": "The threshold rule is owned by the convening body model and is only referenced here; what is local is a small series of determinations with instants, counts and outcomes. Publishing these as an artifact would pre-empt the minutes, which is the record that carries them outward." } ] } ] }, { "id": "agenda-and-conduct", "name": "Agenda and conduct of proceedings", "description": "The business set down for the occurrence, the procedural acts by which it was handled, and the deliberative outcomes reached.", "rationale": "Agenda structure, procedural acts, speech attribution and voting are the substance of a session and have an explicit, standardised vocabulary in parliamentary and legal document standards. They are conduct facts of the occurrence, distinct from the durable records that later report them.", "source_refs": [ "SRC-010", "SRC-012", "SRC-013", "SRC-006" ], "layers": [ { "id": "agenda-composition", "name": "Agenda composition and control", "description": "How the business is structured before the session and how it is altered once the session has opened.", "source_refs": [ "SRC-010", "SRC-013", "SRC-014" ], "findings": [ { "id": "agenda-item-structure", "name": "Agenda item structure", "description": "The items of business set down for the occurrence, their ordering, purpose, sponsorship, supporting papers and time allocation.", "source_refs": [ "SRC-010", "SRC-013", "SRC-014" ], "questions": [ { "id": "agenda-item-set-and-order", "text": "Which items make up the agenda, in what order, and what purpose does each item serve?", "kind": "composition", "answer_data": [ "Item identifiers and titles", "Sequence positions", "Purpose class per item (information, discussion, decision)" ] }, { "id": "item-sponsorship-and-expected-outcome", "text": "Who sponsors each item, and what outcome is expected from it?", "kind": "ownership", "answer_data": [ "Sponsoring party or unit reference", "Expected outcome statement", "Presenting party reference where different from the sponsor" ] }, { "id": "tabled-paper-linkage", "text": "Which supporting papers are tabled for each item, and from where do they resolve?", "kind": "relationship", "answer_data": [ "Document references per item", "Resolution endpoint", "Version or effective-date marker of the tabled version" ] }, { "id": "item-time-allocation-overrun", "text": "How much time is allocated to each item, and what happens when the allocation is exceeded?", "kind": "constraint", "answer_data": [ "Allocated duration per item", "Overrun handling rule", "Actual time consumed where observed" ] } ], "data_elements": [ { "id": "agenda-item", "name": "Agenda item", "description": "One item of business set down for the occurrence.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-010", "SRC-013" ] }, { "id": "item-sequence-position", "name": "Item sequence position", "description": "Ordinal position of the item in the agenda as set down.", "value_kind": "number", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "item-purpose-class", "name": "Item purpose class", "description": "Whether the item is for information, discussion or decision.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "tabled-paper-reference", "name": "Tabled paper reference", "description": "Reference to a supporting document tabled for the item.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "item-time-allocation", "name": "Item time allocation", "description": "Time allotted to the item.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [ { "id": "provisional-agenda", "name": "Provisional agenda", "description": "The agenda as circulated before the occurrence, listing items, order, sponsors and tabled papers.", "media_or_form": [ "circulated agenda document", "published agenda entry", "accessible agenda in native format" ], "serial": true, "identity_strategy": "Agenda identifier assigned by the issuing secretariat within the convening body's numbering series, bound to the session identifier and carrying its own circulation instant and version marker.", "source_refs": [ "SRC-013", "SRC-014", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "agenda-adoption-and-amendment", "name": "Agenda adoption and amendment", "description": "The procedural act of adopting the agenda and the in-session changes that add, withdraw, reorder, defer or carry over business.", "source_refs": [ "SRC-010", "SRC-013" ], "questions": [ { "id": "agenda-adoption-act", "text": "Was the agenda formally adopted, and what distinguishes the provisional version from the adopted one?", "kind": "decision", "answer_data": [ "Adoption act and instant", "Differences between provisional and adopted versions", "Objections recorded at adoption" ] }, { "id": "in-session-agenda-change", "text": "How are items added, withdrawn or taken out of order once the session has opened?", "kind": "process", "answer_data": [ "Change type and proposer", "Approval required and given", "Instant of the change" ] }, { "id": "deferred-item-destination", "text": "Which items were deferred, and to which future occurrence were they carried?", "kind": "temporal", "answer_data": [ "Deferred item references", "Target occurrence reference or 'unscheduled'", "Reason for deferral" ] }, { "id": "items-without-debate", "text": "Which items may be disposed of without debate, and under what condition?", "kind": "constraint", "answer_data": [ "Consent or nem-con item set", "Condition that removes an item from that treatment", "Objection threshold" ] } ], "data_elements": [ { "id": "agenda-adopted-flag", "name": "Agenda adopted flag", "description": "Whether the agenda was formally adopted at the occurrence.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "agenda-adopted-at", "name": "Agenda adopted at", "description": "Instant at which the agenda was adopted.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-007" ] }, { "id": "agenda-amendment", "name": "Agenda amendment", "description": "An in-session change to the agenda with proposer, type and instant.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "carry-over-target-reference", "name": "Carry-over target reference", "description": "Occurrence to which a deferred item is carried.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [ { "id": "adopted-agenda", "name": "Adopted agenda", "description": "The agenda as adopted at the occurrence, including in-session amendments and the order actually followed.", "media_or_form": [ "adopted agenda document", "order of business as followed", "annex to the circulated agenda" ], "serial": true, "identity_strategy": "Derived identifier composed of the provisional agenda identifier and the adoption revision, bound to the session identifier; the adoption instant distinguishes it from the circulated version.", "source_refs": [ "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "proceedings-conduct", "name": "Procedural acts and floor management", "description": "The sequence of procedural acts during the occurrence and the allocation of the right to speak.", "source_refs": [ "SRC-010", "SRC-006", "SRC-014" ], "findings": [ { "id": "procedural-events", "name": "Procedural acts", "description": "The ordered procedural acts of the occurrence — call to order, suspension, resumption, points of order, closure of portions and adjournment — with their declaring officer and rule basis.", "source_refs": [ "SRC-010", "SRC-012" ], "questions": [ { "id": "procedural-act-sequence", "text": "Which procedural acts occurred during the occurrence, and in what order?", "kind": "event", "answer_data": [ "Act kind code per act", "Ordinal position and occurrence instant", "Agenda item under which each act took place" ] }, { "id": "declaring-officer-and-rule", "text": "Who declared each procedural act, and under which rule was the declaration made?", "kind": "authority", "answer_data": [ "Declaring officer reference", "Rule or standing order cited", "Challenge to the declaration where raised" ] }, { "id": "procedural-objection-disposal", "text": "Which procedural objections were raised, and how was each disposed of?", "kind": "exception", "answer_data": [ "Objection text and raiser reference", "Ruling given and by whom", "Appeal outcome where the ruling was challenged" ] }, { "id": "interrupted-proceedings-reconstruction", "text": "How is the sequence of proceedings reconstructed if the occurrence is interrupted or the capture fails?", "kind": "process", "answer_data": [ "Fallback observation source", "Gap markers in the act sequence", "Reconstruction note with its author reference" ] } ], "data_elements": [ { "id": "procedural-act", "name": "Procedural act", "description": "One procedural act of the occurrence with kind, instant, declaring officer and rule basis.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "act-kind-code", "name": "Act kind code", "description": "Governed code for the type of procedural act.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "act-occurred-at", "name": "Act occurred at", "description": "Instant at which the procedural act occurred.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010", "SRC-007" ] }, { "id": "act-rule-basis", "name": "Act rule basis", "description": "Rule or standing order cited for the act.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "Procedural acts are an ordered set of typed events on the occurrence, and the outward-facing document that reports them is the minutes, owned by WM-REC-012. Declaring an artifact here would create a parallel narrative record competing with the durable one." }, { "id": "floor-and-speaking-management", "name": "Floor and speaking management", "description": "How the right to speak is allocated, how contributions are attributed, and who may restrict a participant's channel during the occurrence.", "source_refs": [ "SRC-010", "SRC-006", "SRC-014" ], "questions": [ { "id": "speaking-right-allocation", "text": "How is the right to speak allocated, and in which order are speakers taken?", "kind": "process", "answer_data": [ "Allocation method (list, catch-the-eye, floor request queue)", "Ordered speaker queue", "Party maintaining the queue" ] }, { "id": "contribution-attribution", "text": "Which contributions are attributed to which speaker, and in what capacity did that speaker contribute?", "kind": "provenance", "answer_data": [ "Speaker party reference per turn", "Capacity or role in which they spoke", "Addressee where the contribution is directed" ] }, { "id": "speaking-time-limit", "text": "What speaking-time limits apply, and how is an overrun handled?", "kind": "constraint", "answer_data": [ "Limit per speaker or per group", "Observed turn duration", "Overrun handling applied" ] }, { "id": "channel-restriction-authority", "text": "Who may mute, remove or otherwise restrict a participant's channel, and on what ground?", "kind": "authority", "answer_data": [ "Restricting role reference", "Permitted grounds", "Restriction instant and its duration" ] } ], "data_elements": [ { "id": "speaking-turn", "name": "Speaking turn", "description": "One allocated contribution with speaker reference, capacity, start instant and duration.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "speaking-capacity-code", "name": "Speaking capacity", "description": "Capacity in which the speaker contributed.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "floor-control-policy-code", "name": "Floor control policy", "description": "Policy governing how the floor is granted at this occurrence.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "channel-restriction-event", "name": "Channel restriction event", "description": "An applied restriction on a participant's channel with ground and instant.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "speakers-list", "name": "Speakers list", "description": "The ordered list of parties recognised or queued to speak at the occurrence, with allocated time where limits apply.", "media_or_form": [ "speakers list maintained by the chair or clerk", "platform floor request queue export" ], "serial": false, "identity_strategy": "Identified by the session identifier plus the agenda item reference under which the list was maintained; where a floor-control system produces the queue, its queue identifier is recorded as a bound external identifier.", "source_refs": [ "SRC-010", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "deliberative-outcomes", "name": "Motions, voting and outcomes", "description": "Questions put to the occurrence, the method by which they were decided, and the follow-up that flows from them.", "source_refs": [ "SRC-010", "SRC-012", "SRC-011", "SRC-013" ], "findings": [ { "id": "motion-and-vote-conduct", "name": "Motion and vote conduct", "description": "How a question is put, by which method it is decided, what tally results and who declares the outcome — the conduct of deciding, not the durable decision itself.", "source_refs": [ "SRC-010", "SRC-012", "SRC-011" ], "questions": [ { "id": "question-put-and-mover", "text": "What question was put to the meeting, who moved it, and was a seconder required?", "kind": "process", "answer_data": [ "Motion or question text as put", "Mover and seconder references", "Amendments taken before the substantive question" ] }, { "id": "voting-method-and-threshold", "text": "By which voting method was the question decided, and what threshold applied?", "kind": "decision", "answer_data": [ "Voting method code (voice, show of hands, roll call, secret, electronic)", "Threshold expression (simple majority, qualified majority, unanimity)", "Basis on which the threshold is calculated" ] }, { "id": "tally-and-declaration", "text": "What was the tally, including abstentions, and who declared the result?", "kind": "measurement", "answer_data": [ "Votes in favour, against and abstaining", "Individual votes where the method is recorded", "Declaring officer reference and declaration instant" ] }, { "id": "vote-exclusion-basis", "text": "Which participants were excluded from the vote, and on what basis?", "kind": "exception", "answer_data": [ "Excluded party references", "Exclusion ground (recusal, entitlement, absence)", "Effect on the calculation base" ] }, { "id": "tied-or-failed-vote", "text": "How is a tied or failed vote resolved at this occurrence?", "kind": "constraint", "answer_data": [ "Casting vote entitlement", "Re-put or deferral rule", "Recorded outcome where the question falls" ] } ], "data_elements": [ { "id": "motion-text", "name": "Motion text", "description": "The question as put to the meeting.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "voting-method-code", "name": "Voting method code", "description": "Method by which the question was decided.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-012" ] }, { "id": "decision-threshold", "name": "Decision threshold", "description": "Threshold that had to be met for the question to carry.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "vote-tally", "name": "Vote tally", "description": "Aggregate counts in favour, against and abstaining.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012", "SRC-010" ] }, { "id": "individual-vote", "name": "Individual vote", "description": "Per-party vote where the method records individual positions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012", "SRC-010" ] }, { "id": "result-declared-at", "name": "Result declared at", "description": "Instant at which the result was declared.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "vote-tally-record", "name": "Vote tally record", "description": "The recorded result of a single division at the occurrence, including individual positions where the method requires them.", "media_or_form": [ "roll-call tally sheet", "electronic voting system export", "division list" ], "serial": true, "identity_strategy": "Division number assigned sequentially within the occurrence and bound to the session identifier and the agenda item; where an electronic voting system is used, its division identifier is authoritative for the exported copy.", "source_refs": [ "SRC-012", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "outcome-and-follow-up-assignment", "name": "Outcomes and follow-up assignment", "description": "What the occurrence concluded, which conclusions require a separate durable decision record, and what follow-up work was assigned or referred.", "source_refs": [ "SRC-013", "SRC-010", "SRC-012" ], "questions": [ { "id": "conclusion-to-record-routing", "text": "Which conclusions did the occurrence reach, and which of them require a separate durable decision record?", "kind": "decision", "answer_data": [ "Conclusion statement per agenda item", "Routing flag indicating a decision record is owed", "Reference to the decision record once created" ] }, { "id": "follow-up-assignment", "text": "Which follow-up actions were assigned, to whom, and by when?", "kind": "ownership", "answer_data": [ "Action statement", "Assignee party reference", "Due date and the task record reference where one is opened" ] }, { "id": "referral-destination", "text": "Which matters were referred to another body or to a later occurrence?", "kind": "relationship", "answer_data": [ "Referral target reference", "Referred item reference", "Instruction accompanying the referral" ] }, { "id": "outcome-evidence-basis", "text": "What evidence shows that an outcome was actually reached rather than merely discussed?", "kind": "evidence", "answer_data": [ "Supporting division or consensus indication", "Procedural act reference that concluded the item", "Confidence or contestation note" ] } ], "data_elements": [ { "id": "outcome-statement", "name": "Outcome statement", "description": "Conclusion reached on an agenda item as recorded at the occurrence.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "decision-record-reference", "name": "Decision record reference", "description": "Reference to the durable decision record that carries the outcome forward.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "action-assignment", "name": "Action assignment", "description": "Assigned follow-up with assignee reference and due date.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "referral-target-reference", "name": "Referral target reference", "description": "Body or occurrence to which a matter was referred.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [ { "id": "action-item-list", "name": "Action item list", "description": "The list of follow-up actions as assigned at the occurrence, each with assignee and due date, handed off to the task model for execution.", "media_or_form": [ "action list annexed to the agenda or record", "task hand-off export" ], "serial": false, "identity_strategy": "Identified by the session identifier plus an action ordinal within the occurrence; once a task record is opened, the task model's identifier becomes authoritative for that action and is recorded as a bound reference.", "source_refs": [ "SRC-013", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "capture-and-record-obligation", "name": "In-session capture and record obligation", "description": "What was captured while the occurrence ran, on what basis, and which durable records the occurrence owes to whom.", "rationale": "Capture during a session and the durable record produced from it are different things with different owners. Open-meeting and company-law regimes impose specific obligations to produce and certify records, while capture itself raises notification and consent duties at the moment it happens.", "source_refs": [ "SRC-012", "SRC-013", "SRC-011", "SRC-014" ], "layers": [ { "id": "session-capture", "name": "Capture and record hand-off", "description": "Recording and live transcription performed during the occurrence, and the obligation to produce durable records from it.", "source_refs": [ "SRC-012", "SRC-013", "SRC-011", "SRC-014" ], "findings": [ { "id": "recording-and-transcription-capture", "name": "Recording and transcription capture", "description": "Whether and how the occurrence was recorded or live-transcribed, the notification and consent basis for doing so, and where the captured media are held pending disposition.", "source_refs": [ "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "capture-scope-and-modality", "text": "Was the occurrence recorded or live-transcribed, and which portions were captured in which modality?", "kind": "event", "answer_data": [ "Capture start and stop instants", "Modality per capture (audio, video, live caption, automatic transcript)", "Portions deliberately excluded from capture" ] }, { "id": "capture-notification-and-consent", "text": "How were participants notified before capture began, and where consent was required, how was it obtained and recorded?", "kind": "privacy", "answer_data": [ "Notification method and instant", "Consent basis relied on", "Per-participant consent state where individual consent is required" ] }, { "id": "capture-media-custody", "text": "Which capture media were produced, and where are they held pending disposition?", "kind": "provenance", "answer_data": [ "Media object references", "Holding location or custodian reference", "Duration and integrity evidence per object" ] }, { "id": "consent-withdrawal-effect", "text": "What happens to captured media if a participant withdraws consent after the occurrence?", "kind": "exception", "answer_data": [ "Withdrawal instant and scope", "Remediation applied (redaction request, restriction, disposal request)", "Reference to the policy owner that executes the remediation" ] } ], "data_elements": [ { "id": "capture-started-at", "name": "Capture started at", "description": "Instant at which a capture began.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-012" ] }, { "id": "capture-stopped-at", "name": "Capture stopped at", "description": "Instant at which a capture ended.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "capture-modality-code", "name": "Capture modality", "description": "Modality of the capture performed.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014", "SRC-012" ] }, { "id": "capture-consent-basis", "name": "Capture consent basis", "description": "Stated basis on which capture was lawful at this occurrence.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "capture-notification-flag", "name": "Capture notification given", "description": "Whether participants were notified before capture began.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] } ], "artifacts": [ { "id": "session-capture-media", "name": "Session capture media", "description": "The raw audio, video or live-caption stream captured during the occurrence, before any editorial process turns it into a durable transcript.", "media_or_form": [ "audio recording", "video recording", "live caption stream export" ], "serial": false, "identity_strategy": "Media object identifier assigned by the capturing platform is authoritative for the object; it is bound to the session identifier and the capture start instant, and any checksum or signature is recorded with its algorithm name.", "source_refs": [ "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "record-production-obligation", "name": "Record production obligation and linkage", "description": "Which durable records the occurrence owes, under which rule, who must produce and certify them, and how they anchor back to items and acts of this occurrence.", "source_refs": [ "SRC-013", "SRC-012", "SRC-011", "SRC-010" ], "questions": [ { "id": "records-owed-and-basis", "text": "Which durable records must this occurrence produce, and under which rule is each one required?", "kind": "requirement", "answer_data": [ "Record type owed (minutes, transcript, decision record, summary)", "Legal or policy basis per record type", "Deadline for production" ] }, { "id": "minimum-record-content", "text": "Which minimum content must the required record carry for this meeting type?", "kind": "constraint", "answer_data": [ "Mandatory content elements (persons present, matters discussed, conclusions reached, reports received, recorded votes)", "Content elements that may be withheld", "Source of the content requirement" ] }, { "id": "producer-and-certifier", "text": "Who is responsible for producing the record, and who must certify its accuracy?", "kind": "ownership", "answer_data": [ "Producing party reference", "Certifying officer reference", "Certification form required" ] }, { "id": "record-anchor-linkage", "text": "How is the produced record linked back to this occurrence and to individual agenda items and procedural acts?", "kind": "relationship", "answer_data": [ "Produced record reference", "Anchor map from record passages to item and act identifiers", "Resolution state of the reference" ] } ], "data_elements": [ { "id": "required-record-type", "name": "Required record type", "description": "Type of durable record the occurrence is obliged to produce.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013", "SRC-011" ] }, { "id": "record-obligation-basis", "name": "Record obligation basis", "description": "Reference to the rule imposing the record obligation.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012", "SRC-011" ] }, { "id": "certifying-officer-reference", "name": "Certifying officer reference", "description": "Party who must certify the accuracy of the produced record.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "produced-record-reference", "name": "Produced record reference", "description": "Reference to the durable record produced from this occurrence.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011", "SRC-010" ] }, { "id": "item-to-record-anchor", "name": "Item to record anchor", "description": "Mapping from agenda items and procedural acts to passages of the produced record.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "The minutes, transcript and decision records are owned by WM-REC-012 and WM-REC-010; declaring them as artifacts here would duplicate their identity, approval and disposition lifecycle. What is local is the obligation statement, the producer and certifier references, and the anchor map, all of which are reference data on the occurrence." } ] } ] }, { "id": "confidentiality-and-interchange", "name": "Confidentiality, admission and interchange", "description": "How open the occurrence is, what personal data it holds, and how it is projected into external vocabularies and platforms.", "rationale": "Openness classification and closure procedure are governed by statute in public-body settings, and session context concentrates personal data about attendance and contributions. Interchange is a separate, purely declarative concern that keeps the model independent of any storage format or platform.", "source_refs": [ "SRC-012", "SRC-013", "SRC-001", "SRC-002", "SRC-009", "SRC-006", "SRC-015" ], "layers": [ { "id": "confidentiality-and-admission", "name": "Openness, admission and personal data", "description": "The openness determination and its procedure, who may be admitted to observe, and the personal data the occurrence holds about participants.", "source_refs": [ "SRC-012", "SRC-013", "SRC-002", "SRC-015" ], "findings": [ { "id": "openness-closure-and-admission", "name": "Openness, closure and admission", "description": "Whether the occurrence or parts of it are closed, on what ground and by what procedure, and who may be admitted to observe what remains open.", "source_refs": [ "SRC-012", "SRC-013", "SRC-006" ], "questions": [ { "id": "closed-portion-identification", "text": "Is the occurrence open to observers, and which portions of it are closed?", "kind": "access", "answer_data": [ "Openness state per portion", "Portion boundaries expressed as item or interval references", "Default applied where no explicit determination was made" ] }, { "id": "closure-ground-and-certification", "text": "On which stated ground is each closed portion justified, and who certified that the ground applies?", "kind": "authority", "answer_data": [ "Exemption ground code and its statutory or policy source", "Certifying officer reference", "Written statement of reasons reference" ] }, { "id": "closure-procedure-step", "text": "What procedural step is required before a portion may be closed?", "kind": "process", "answer_data": [ "Required vote or determination and its threshold", "Recorded positions of those voting", "Instant at which closure took effect" ] }, { "id": "observer-admission-conditions", "text": "Who is entitled to observe without participating, and which registration or accreditation conditions apply?", "kind": "constraint", "answer_data": [ "Entitlement rule", "Registration or accreditation requirement", "Admission limit and how it is allocated" ] }, { "id": "exclusion-and-embargo", "text": "On what ground may an attendee be excluded during the occurrence, and what embargo applies to what they learned?", "kind": "security", "answer_data": [ "Exclusion ground and authorising role", "Exclusion instant and scope", "Embargo expression and its end instant" ] } ], "data_elements": [ { "id": "openness-state", "name": "Openness state", "description": "Whether the occurrence, or a named portion of it, is open, closed or restricted.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-012" ] }, { "id": "closed-portion", "name": "Closed portion", "description": "A portion of the occurrence closed to observation, with its boundaries and ground.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "closure-ground-code", "name": "Closure ground code", "description": "Coded exemption ground relied on to close a portion.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "observer-count", "name": "Observer count", "description": "Number of observers admitted.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "embargo-until", "name": "Embargo until", "description": "Instant until which information from the occurrence is embargoed.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012", "SRC-007" ] } ], "artifacts": [ { "id": "closure-certification", "name": "Closure certification and statement of reasons", "description": "The certification that closing a portion of the occurrence is permitted on a stated ground, together with the written statement of reasons where the regime requires one.", "media_or_form": [ "signed certification", "statement of reasons published with the notice", "register entry recording the closure vote" ], "serial": true, "identity_strategy": "Certification identifier assigned by the issuing legal office, bound to the session identifier and to the closed-portion boundaries; where a public register publishes the certification, the register identifier is authoritative.", "source_refs": [ "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "personal-data-in-session", "name": "Personal data held by the occurrence", "description": "The inventory of personal data the session context holds about participants, why each element is necessary, and when it becomes due for disposition.", "source_refs": [ "SRC-015", "SRC-012", "SRC-014", "SRC-002" ], "questions": [ { "id": "personal-data-inventory", "text": "Which personal data about participants does the session context hold, and why is each element necessary?", "kind": "privacy", "answer_data": [ "Element inventory (identifiers, contact addresses, presence intervals, contributions, accommodation needs)", "Necessity statement per element", "Element-level minimisation decision" ] }, { "id": "processing-basis-per-element", "text": "What is the stated basis for processing attendance, contribution and capture data at this occurrence?", "kind": "authority", "answer_data": [ "Processing basis per element group", "Instrument or policy relied on", "Party accountable for the basis" ] }, { "id": "sensitive-disclosure-containment", "text": "Which sensitive or special-category disclosures may arise during the occurrence, and how are they contained?", "kind": "security", "answer_data": [ "Sensitivity flags on portions or elements", "Containment measure applied", "Restriction on onward reference" ] }, { "id": "session-data-disposition-due", "text": "When does session-held personal data become due for disposition, and which policy owner executes that disposition?", "kind": "retention", "answer_data": [ "Disposition due instant per element group", "Retention rule reference", "Executing policy owner reference and the outcome reference once executed" ] } ], "data_elements": [ { "id": "personal-data-inventory-entry", "name": "Personal data inventory entry", "description": "One category of personal data held by the occurrence, with necessity and sensitivity markers.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015", "SRC-014" ] }, { "id": "processing-basis", "name": "Processing basis", "description": "Stated basis for processing a category of session-held personal data.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "sensitivity-flag", "name": "Sensitivity flag", "description": "Marker indicating that a portion or element carries heightened sensitivity.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "disposition-due-at", "name": "Disposition due at", "description": "Instant at which a category of session-held data becomes due for disposition.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015", "SRC-011" ] }, { "id": "retention-rule-reference", "name": "Retention rule reference", "description": "Pointer to the externally owned retention schedule governing disposition.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] } ], "artifacts": [], "inline_only_rationale": "This finding is a register of data categories, bases and due dates held on the occurrence. The retention schedule and any erasure evidence are owned by the adopting Dimension's records and data-protection policies, so producing an artifact here would assert ownership of a disposition process this model does not execute." } ] }, { "id": "interchange-bindings", "name": "Interchange and platform binding", "description": "Declarative mapping of the occurrence into external calendar, event and conferencing vocabularies, with the lossy points and reconciliation rules recorded.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-006", "SRC-015", "SRC-008" ], "findings": [ { "id": "interchange-and-platform-binding", "name": "Interchange and platform binding", "description": "Which external vocabularies and platforms the occurrence is projected into or bound to, which mappings are lossy, and which system holds authority for which field.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-006", "SRC-015", "SRC-008" ], "questions": [ { "id": "target-vocabulary-mapping", "text": "Which external calendar or event vocabularies is this occurrence projected into, and which fields map without loss?", "kind": "interoperability", "answer_data": [ "Target vocabulary and version per projection", "Field-level mapping table", "Lossless field set" ] }, { "id": "unmappable-local-concept", "text": "Which local concepts have no equivalent in a target vocabulary, and how are they carried across?", "kind": "constraint", "answer_data": [ "Unmappable concept list per target", "Extension or structured-data carrier used", "Loss note recorded on the projection" ] }, { "id": "cross-copy-reconciliation", "text": "How are conflicting copies of the same occurrence reconciled across systems?", "kind": "validation", "answer_data": [ "Precedence rule between systems", "Revision and timestamp comparison procedure", "Recorded reconciliation outcome" ] }, { "id": "platform-object-authority", "text": "Which conferencing platform hosts the occurrence, which object identifier does it assign, and which of its data is authoritative here?", "kind": "provenance", "answer_data": [ "Platform reference and conference object identifier", "Field-level authority flags", "Platform role to procedural role mapping" ] }, { "id": "platform-exit-obligation", "text": "What must be exported and retained if the hosting platform is decommissioned or the tenancy ends?", "kind": "retention", "answer_data": [ "Export obligation per data class", "Source-side expiry window", "Reference to the exported copy and its custodian" ] } ], "data_elements": [ { "id": "interchange-profile", "name": "Interchange profile", "description": "Named external vocabulary and version into which the occurrence is projected.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] }, { "id": "field-mapping-entry", "name": "Field mapping entry", "description": "One mapping between a local data element and a target vocabulary term, with a loss marker.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-009" ] }, { "id": "platform-conference-object-id", "name": "Platform conference object identifier", "description": "Identifier assigned by the hosting conferencing system to the conference object.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-015" ] }, { "id": "field-authority-flag", "name": "Field authority flag", "description": "Marker stating whether the platform copy or the local copy is authoritative for a field.", "value_kind": "boolean", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "reconciliation-rule", "name": "Reconciliation rule", "description": "Rule applied when copies of the occurrence disagree across systems.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "Projections into iCalendar, JSCalendar, schema.org or a conferencing object are format bindings, not artifacts of the occurrence; treating them as artifacts would contradict the requirement that the model stay independent of storage format and interface. The one genuine exchanged document, the scheduling message, is declared under schedule change and is not duplicated here." } ] } ] } ] }, "functions": [ { "id": "convene-session", "name": "Convene session", "description": "Create an occurrence entry bound to a convening authority, assign its identifier and fix its classification before any notice is issued.", "inputs": [ "Convening body or office reference", "Convening instrument reference", "Meeting type, attendance mode and openness class", "Planned start with a named time zone" ], "outputs": [ "Occurrence entry with an assigned identifier at revision sequence zero", "Classification set", "Convening authority binding" ], "preconditions": [ "The convening reference resolves, or an explicit unattached flag is recorded", "A planned start and named time zone are supplied" ], "effects": [ "An occurrence exists in a pre-notice state", "The applicable procedural and record obligations become determinable from the classification" ], "source_refs": [ "SRC-001", "SRC-011", "SRC-012" ] }, { "id": "compile-agenda", "name": "Compile and circulate agenda", "description": "Assemble items with order, purpose, sponsor, tabled-paper references and time allocation, and circulate them in accessible formats within the required lead time.", "inputs": [ "Item submissions with sponsor references", "Tabled document references", "Carried-over items from the preceding occurrence", "Accessibility circulation deadline" ], "outputs": [ "Provisional agenda artifact", "Item-to-document reference map" ], "preconditions": [ "The occurrence exists and is not cancelled", "Each tabled document reference resolves to a version marker" ], "effects": [ "Participants can prepare in advance in accessible formats", "Deferred business from the preceding occurrence is carried forward" ], "source_refs": [ "SRC-010", "SRC-013", "SRC-014" ] }, { "id": "dispatch-invitations", "name": "Dispatch invitations and collect responses", "description": "Issue the invitation to each invited party with its role, and record returned participation statuses, delegations and counter-proposals without altering the occurrence's revision for response-only changes.", "inputs": [ "Invitee references with role codes", "Response-expected flags", "Conferencing endpoints and access instructions" ], "outputs": [ "Scheduling messages sent", "Participation status per invitee with response instants", "Recorded delegations and counter-proposals" ], "preconditions": [ "The occurrence has a planned start and a resolved access channel or venue", "Roles required for the meeting type are assigned" ], "effects": [ "Invitation state becomes readable per party", "Response-only updates leave the revision sequence unchanged" ], "source_refs": [ "SRC-004", "SRC-001", "SRC-002" ] }, { "id": "determine-quorum", "name": "Determine quorum", "description": "Compare the observed present population against the threshold rule resolved from the convening body and record the determination with its instant and counted base.", "inputs": [ "Presence observations", "Resolved quorum threshold reference", "Exclusions such as recusals and resource entries" ], "outputs": [ "Quorum check record with counted base and outcome", "Quorum satisfied flag at the determination instant" ], "preconditions": [ "A quorum rule reference resolves, or the absence of a rule is explicitly recorded", "At least one presence observation exists" ], "effects": [ "The competence of the occurrence to transact business at that instant is recorded", "Loss of quorum can be linked to the items it affects" ], "source_refs": [ "SRC-011", "SRC-012", "SRC-010" ] }, { "id": "sequence-proceedings", "name": "Sequence proceedings", "description": "Record the ordered procedural acts of the occurrence and the speaking turns allocated under them, each with a declaring or presiding officer reference and an event instant.", "inputs": [ "Procedural act declarations", "Speaking turn allocations", "Adopted agenda order" ], "outputs": [ "Ordered procedural act sequence", "Speakers list with attributed turns" ], "preconditions": [ "The occurrence has been opened", "The agenda has been adopted or an explicit no-adoption note is recorded" ], "effects": [ "The course of the occurrence is reconstructible from typed events", "Contributions are attributable to parties and capacities" ], "source_refs": [ "SRC-010", "SRC-006" ] }, { "id": "conduct-vote", "name": "Conduct vote and declare result", "description": "Put a question, apply the chosen voting method and threshold, record the tally and any exclusions, and record the declaration of the result as conduct of the occurrence.", "inputs": [ "Question as put with mover reference", "Voting method and threshold", "Entitled voter set with exclusions" ], "outputs": [ "Vote tally record", "Declared result with declaring officer and instant" ], "preconditions": [ "Quorum was satisfied at the point the question was put, or the deficiency is recorded", "Exclusions on grounds of interest or entitlement have been applied" ], "effects": [ "The division is recorded with its counted base", "A routing flag indicates whether a durable decision record is owed" ], "source_refs": [ "SRC-012", "SRC-010", "SRC-011" ] }, { "id": "revise-schedule", "name": "Revise or cancel schedule", "description": "Change the time, setting or status of the occurrence, increment the revision sequence, and issue the corresponding scheduling messages and re-notice where required.", "inputs": [ "Requested change with actor reference", "Reason statement", "Replacement occurrence reference where applicable" ], "outputs": [ "Updated scheduling status with change instant", "Incremented revision sequence", "Issued scheduling messages and amended notice where required" ], "preconditions": [ "The requesting actor holds the authority to make the change", "The occurrence is not in a terminal status" ], "effects": [ "Copies held elsewhere can be reconciled by sequence and timestamp", "Surviving obligations after cancellation remain explicit" ], "source_refs": [ "SRC-004", "SRC-001", "SRC-009" ] }, { "id": "set-openness", "name": "Determine openness and close a portion", "description": "Record the openness determination for the occurrence or a named portion, the ground relied on, the procedural step taken and the certification obtained.", "inputs": [ "Portion boundaries", "Proposed exemption ground", "Determination vote or decision with positions" ], "outputs": [ "Openness state per portion", "Closure certification artifact with statement of reasons" ], "preconditions": [ "The exemption ground is one recognised by the applicable regime", "The required determination step has been completed and recorded" ], "effects": [ "Downstream disclosure of the portion is constrained by the recorded classification", "The ground and certifier remain attributable" ], "source_refs": [ "SRC-012", "SRC-013" ] }, { "id": "commission-records", "name": "Commission durable records", "description": "Emit the record obligations owed by the occurrence to the owning record models, with content requirements, producer and certifier references and anchor points, and record the returned identifiers.", "inputs": [ "Record obligation basis per record type", "Producer and certifier references", "Item and act anchor map" ], "outputs": [ "Record obligation entries with deadlines", "Bound references to produced records once returned" ], "preconditions": [ "The occurrence has closed or the portion generating the obligation has concluded", "The applicable content requirement has been resolved" ], "effects": [ "The obligation and its linkage are visible from the occurrence", "No draft, approval or disposition state is created here; those remain with the owning record models" ], "source_refs": [ "SRC-013", "SRC-011", "SRC-012" ] }, { "id": "emit-interchange-projection", "name": "Emit interchange projection", "description": "Produce a projection of the occurrence into a named external vocabulary, recording the field mapping actually applied and every lossy point rather than silently dropping data.", "inputs": [ "Target vocabulary and version", "Field mapping table", "Access scope of the requester" ], "outputs": [ "Projection in the target vocabulary", "Loss notes for unmappable concepts" ], "preconditions": [ "The mapping for the target vocabulary has been tested and recorded", "Closed-portion and personal-data restrictions have been applied to the projected field set" ], "effects": [ "External systems can consume the occurrence without the model claiming conformance", "Recorded loss notes make the projection falsifiable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-008" ] } ], "composition": [ { "target": "WM-ACT-018 — parent activity or occurrence model", "relation": "EXTEND", "purpose": "Specialise the generic occurrence with the deliberative surface only: agenda, quorum determination, procedural acts, motions, capture and record obligation. Generic occurrence identity, scheduling status and cancellation semantics remain defined by the parent and are not redefined here.", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] }, { "target": "WM-REC-012 — minutes or transcript record", "relation": "CHILD", "purpose": "Carry the obligation to produce a durable record, its required content, producer and certifier references, and the anchor map from items and acts to record passages. The record's draft, approval, correction, authenticity, publication and disposition lifecycle stays with the target. Mandatory where an open-meeting or company-law regime applies; absent otherwise.", "required": false, "source_refs": [ "SRC-013", "SRC-011", "SRC-012" ] }, { "target": "WM-REC-010 — decision record", "relation": "CHILD", "purpose": "Route a declared outcome to a durable decision record and hold the returned reference. Decision rationale, status, supersession and implementation tracking belong to the target; only the conduct of putting and deciding the question is modelled here.", "required": false, "source_refs": [ "SRC-010", "SRC-012" ] }, { "target": "WM-ORG-018 — governance body", "relation": "REFERENCE", "purpose": "Bind the occurrence to the body that convened it and resolve the quorum threshold, voting entitlement and presiding rules from it at read time. Membership, mandate and delegated powers are not copied into the occurrence.", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] }, { "target": "Party model for persons and organisations (identifier assigned by the adopting Dimension)", "relation": "REFERENCE", "purpose": "Resolve every invitee, presiding officer, speaker, voter and assignee to a mastered party. Role, invitation status, presence intervals and recusal are occurrence-scoped and held locally; identity attributes are not.", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "Place and facility model (identifier assigned by the adopting Dimension)", "relation": "REFERENCE", "purpose": "Resolve the venue and reserved rooms. The occurrence holds the reference, a local room designation and capacity only.", "required": false, "source_refs": [ "SRC-003", "SRC-009" ] }, { "target": "Document model for tabled papers (identifier assigned by the adopting Dimension)", "relation": "REFERENCE", "purpose": "Bind agenda items to the versions of the papers tabled for them. Document versioning and custody remain with the target.", "required": false, "source_refs": [ "SRC-013", "SRC-010" ] }, { "target": "Task or action model (identifier assigned by the adopting Dimension)", "relation": "REFERENCE", "purpose": "Hand off assigned follow-up actions with assignee and due date. Execution, progress and completion lifecycle belong to the target.", "required": false, "source_refs": [ "SRC-013" ] }, { "target": "Access-policy evaluation and audit-event services of the adopting Dimension", "relation": "REFERENCE", "purpose": "Carry openness classifications, closed-portion markers and references to audit event identifiers. Authorisation evaluation, enforcement and audit-trail storage are performed and owned by the target services.", "required": false, "source_refs": [ "SRC-012" ] }, { "target": "Records retention schedule and data-protection policy of the adopting Dimension", "relation": "REFERENCE", "purpose": "Resolve retention floors and disposition rules for occurrence-held data. The model records due dates and outcome references; the target owns and executes disposition.", "required": true, "source_refs": [ "SRC-011", "SRC-012", "SRC-015" ] }, { "target": "IETF RFC 5545 iCalendar and RFC 5546 iTIP", "relation": "ALIGN", "purpose": "Align occurrence identity, recurrence, participant roles and statuses, status values and revision semantics to the normative calendaring vocabulary; mapping is declarative and recorded conflicts are not silently resolved.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "IETF RFC 8984 JSCalendar and RFC 9073 event publishing extensions", "relation": "ALIGN", "purpose": "Align participant, virtual location, structured participant type and resource semantics; note that JSCalendar excludes participant-only changes from the sequence counter, which the local revision rule mirrors.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "schema.org Event", "relation": "ALIGN", "purpose": "Align attendance mode, event status, organiser and attendee roles, superordinate and subordinate event links, and the recordedIn relation used for the durable record link. The postponed and rescheduled statuses have no lossless calendaring equivalent and are recorded as a conflict.", "required": false, "source_refs": [ "SRC-009", "SRC-001" ] }, { "target": "OASIS Akoma Ntoso Version 1.0 debate vocabulary", "relation": "ALIGN", "purpose": "Align procedural act kinds, roll call, quorum, voting and speech attribution vocabulary. Akoma Ntoso models the debate document rather than the occurrence, so its document-level structures belong to WM-REC-012.", "required": false, "source_refs": [ "SRC-010" ] }, { "target": "IETF RFC 6501 XCON conference information data model", "relation": "ALIGN", "purpose": "Align the conference object identifier, admission policy and platform role vocabulary. Conference state, floor control mechanics and media handling remain the platform's runtime concern.", "required": false, "source_refs": [ "SRC-006", "SRC-005" ] }, { "target": "IANA iCalendar Element Registries", "relation": "ALIGN", "purpose": "Source governed code lists for participation statuses, participation roles, calendar user types, methods, classifications, participant types, resource types and feature types instead of minting local equivalents.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name one accountable owner for the Meeting / Session package who can decide classification code lists, approve alignment mappings and sign off breaking changes; the registry entry currently carries only a placeholder owner and must be resolved before the model leaves candidate status.", "Declare the authoritative master system for meeting identifiers (typically the secretariat or governance register) and publish the fallback order used when that system has not yet issued an identifier.", "Publish the resolved references for the four external dependencies this model cannot function without: the convening body model, the party model, the durable record models and the retention schedule.", "Register the local code lists that have no IANA or schema.org equivalent — meeting type, formality class, procedural act kind, voting method, closure ground — with their governing instrument and review cycle." ], "namespace_guidance": "Mint occurrence identifiers in a namespace controlled by the adopting Dimension and never inside a vendor calendar's identifier space. Where a globally scoped identifier is published, use a domain-qualified form whose right-hand side is a domain the Dimension controls, so that the identifier stays resolvable when the calendaring or conferencing platform changes. Keep platform-assigned conference object identifiers and attendance report identifiers in a separate bound-identifier map rather than promoting one of them to the primary identifier.", "registry_links": [ "IANA iCalendar Element Registries for participation statuses, roles, calendar user types, methods, classifications, participant types, resource types and feature types (https://www.iana.org/assignments/icalendar/icalendar.xhtml)", "schema.org type and enumeration registry for event status and attendance mode terms (https://schema.org/Event)", "The adopting Dimension's own model registry entry vr.wm-act-025, which records the relations to WM-ORG-018, WM-REC-012 and WM-REC-010 and their review state" ] }, "canon_and_patch": { "canonicalization_rules": [ "Express every instant as an RFC 3339 date-time with seconds and an explicit offset or Z, and retain the named scheduling time zone as a separate value, because a local wall-clock recurrence rule cannot be reconstructed from a fixed offset.", "Order agenda items by their sequence position as set down, and record the order actually followed as a separate observed sequence rather than by mutating the original ordering.", "Normalise governed code values to the registered token in its registered case; unregistered local extensions carry an explicit local prefix so they are never mistaken for registered values.", "Canonicalise party references to the master identifier before comparison; display names and calendar addresses are never used as join keys.", "Represent presence as half-open intervals with explicit join and leave instants; a missing leave instant is recorded as open rather than defaulted to the session close." ], "patch_rules": [ "Patches address stable local identifiers, never array positions, so that inserting an agenda item or a procedural act does not invalidate outstanding patches.", "Any change by the convener to the definition of the occurrence — start, end, setting, agenda, status — increments the revision sequence and records the change instant and the acting party reference.", "Participation status changes, presence observations and attendance corrections do not increment the revision sequence, mirroring the normative calendaring rule that attendee responses are not organiser revisions.", "Differences between a series definition and one occurrence are expressed as an instance patch against the series, not by copying the whole definition.", "A patch never modifies a referenced target model's record; changes to minutes, decision records, tasks or party data are requested through the owning model and only the returned reference is updated here." ], "compatibility_rules": [ "Adding a value to a local code list, or adding an optional data element, is a minor change; removing a required element, narrowing a cardinality or changing the identity strategy is breaking.", "Changing which system is authoritative for a field is breaking for consumers that rely on the field authority flags, and must be announced with the mapping table it affects.", "An alignment mapping may be corrected, but a correction that changes previously emitted projections is recorded as a conflict entry with the affected profile and version, not applied silently.", "Deprecated elements remain readable for at least one full retention cycle of the occurrences that use them before removal is proposed." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier issued by the system of record for meetings in the adopting Dimension — for example the governance secretariat's meeting register identifier or the docket number of the convening body — which always takes precedence when it exists.", "Governed global identifier or IRI published for the occurrence, such as a domain-qualified calendaring UID or a Dimension-controlled URI, used when no master-system identifier has been issued.", "UUID or ULID assigned by the adopting Dimension as a last resort, retained as an alias once a master-system identifier is later issued so that existing references continue to resolve.", "A meeting date, a room booking reference, a position in a series, a conferencing join code or an agenda title is never an identifier; each may be an attribute or a bound external identifier, but none may be promoted to primary identity." ], "timestamp_rule": "Every instant is recorded as an RFC 3339 date-time with seconds and an explicit UTC offset or Z, and the named scheduling time zone is retained beside it because an offset alone cannot reproduce local wall-clock or daylight-saving behaviour. Event time — when the session actually opened, suspended, resumed, voted or closed — is recorded separately from observation or ingestion time — when a clerk, conferencing platform or importer captured or loaded the value — whenever the two differ, and neither is inferred from the other. Where the offset is genuinely unknown but the instant is known in UTC, the '-00:00' form is used rather than 'Z', preserving the documented distinction.", "serial_naming_rule": "Serial artifacts — notices, agendas, divisions and closure certifications — are numbered within the issuing register or within the occurrence, never across this model as a whole: notices and agendas take the convening body's register series, divisions take a sequential ordinal within the occurrence, and closure certifications take the issuing legal office's series. The serial is a human-facing label; the artifact's identity remains the issuing register's identifier bound to the session identifier.", "integrity_rule": "Every artifact is bound to the occurrence by the session identifier plus the revision sequence current at issue, and to the agenda item or portion it concerns where one applies. Where a checksum or signature exists it is recorded with its algorithm name, and captured media additionally record duration and byte length. The model records integrity evidence and its provenance; it does not verify signatures, enforce integrity or hold the audit trail of verification, which belong to the services referenced by the adopting Dimension." }, "policies": [ "Session context is captured only for the declared purpose of conducting and recording the occurrence; introducing a capture modality beyond those notified to participants requires a fresh notification before capture resumes and, where the applicable regime requires it, a recorded consent basis.", "Openness classification is determined before the occurrence opens; moving a portion to a closed classification requires a recorded procedural act, a stated ground drawn from the applicable regime and an identified certifier, and the fact that a closure occurred remains disclosable even when its content does not.", "Alignment with external vocabularies is declarative. Conformance is asserted only where a field mapping has been tested and recorded, and every unmappable concept is carried as an explicit loss note rather than dropped.", "Personal data held by the occurrence is limited to what the procedural or record obligation requires; presence intervals, contribution attributions and accommodation needs are minimised at capture and carry an explicit necessity statement.", "This model records references to decisions, records, tasks and audit events; it never mirrors their state. A stale reference is reported as unresolved rather than resolved from a local copy." ], "crud": { "read": [ "A read returns identity, classification, planned timing, openness state and the convening binding by default; participant response detail, presence intervals, contribution attributions and closed-portion content are withheld unless the requester holds the corresponding scope.", "A closed occurrence is read in the state it held at close; linked record and decision references are returned as references with their resolution state, never resolved into local copies at read time.", "Projections into external vocabularies are read-only derivations that apply the requester's access scope before mapping, so that a projection can never disclose more than a direct read would." ], "create": [ "An occurrence may be created only with a planned start and a named time zone, an openness class, and either a resolved convening reference or an explicit unattached flag stating that no governance body convened it.", "Creation assigns the identifier by the declared identity priority; where a provisional Dimension-assigned identifier is used, it is retained as an alias once the master-system identifier is issued.", "Creating an occurrence never creates a minutes, transcript, decision or task record; it may only record that such a record is owed, with its basis and deadline." ], "update": [ "Convener changes to the definition increment the revision sequence and record the change instant and acting party reference; response, presence and attendance-correction updates do not increment it.", "After close, updates are limited to attendance corrections, linkage of produced records and decisions, disposition markers and reconciliation outcomes, each carrying a reason and an actor reference.", "An update never rewrites a recorded procedural act, division tally or declared result in place; a correction is recorded as a new entry that supersedes the earlier one and retains it." ], "delete": [ "Occurrence entries are not hard-deleted while any retention obligation over them is live. The entry is closed, marked non-current and scheduled for disposition against the retention schedule referenced by the adopting Dimension; statutory floors differ by regime (for example a ten-year floor for company meeting records and resolutions, and a two-year floor for closed-meeting transcripts under the United States open-meeting statute), and the strictest applicable floor governs.", "Where an occurrence entry must be withdrawn because it was created in error or duplicates another, a tombstone is retained carrying the identifier, its aliases, the withdrawal reason, the withdrawing actor and the withdrawal instant, so that references held by notices, minutes, decision records and calendar copies do not dangle.", "Disposal of the minutes or transcript is executed under WM-REC-012, and disposal of decision records under WM-REC-010. This model neither performs nor authorises those disposals; it records the reference, its resolution state and the disposal outcome reported back to it.", "Erasure or restriction of participant personal data held by the occurrence — presence intervals, calendar addresses, accommodation requests and capture media — is executed by the adopting Dimension's data-protection policy owner and its designated processor. This model records the disposition due instant, the request and the returned outcome reference, not the erasure operation itself.", "Capture media held by a conferencing platform expire under that platform's own retention policy; where the occurrence owes a longer-lived record, the export obligation and its deadline are recorded here and the exported copy's custodian reference is bound before the source window closes." ] }, "roles": [ { "name": "Model owner", "responsibilities": [ "Decide and publish the local code lists, the identity priority and the authoritative master system for meeting identifiers", "Approve alignment mappings and record conflicts rather than resolving them silently", "Sign off breaking changes and their migration path" ] }, { "name": "Session secretariat or clerk", "responsibilities": [ "Create the occurrence, issue notice within the required lead time and circulate accessible agenda materials", "Maintain the attendance register, quorum determinations, procedural act sequence and division records during the occurrence", "Commission the durable records owed and bind the returned references and anchor maps" ] }, { "name": "Presiding officer", "responsibilities": [ "Declare procedural acts, rule on objections and declare voting results", "Determine and certify the closure of portions on a stated ground where the regime permits it", "Confirm the accuracy of the attendance and division records for which the applicable regime requires certification" ] }, { "name": "Interoperability steward", "responsibilities": [ "Maintain and test the field mappings to calendaring, event and conferencing vocabularies and record every lossy point", "Maintain the bound external identifier map and the field authority flags between platform and local copies", "Trigger export obligations before a platform's source retention window closes" ] }, { "name": "Data protection and records liaison", "responsibilities": [ "Maintain the personal data inventory, necessity statements and processing bases for occurrence-held data", "Resolve the applicable retention floors and record disposition due instants and returned outcome references", "Route erasure, restriction and disposal requests to the owning policy and record models rather than executing them here" ] } ], "access": { "default_rule": "Deny by default. A caller reaches an occurrence only through an explicitly granted scope, and the openness class together with any closed-portion markers further restricts the field set returned; where no explicit determination exists, the more restrictive of the meeting type's default and the requester's scope applies.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Where a statutory open-meeting regime applies, the notice fields, agenda, openness status and the fact that a portion was closed are readable without authentication, even though the closed portion's content is not.", "A participant may always read their own participation record: their role, invitation status, delegation state, presence intervals and any accommodation request they submitted.", "Closed-portion content is restricted to parties recorded as present for that portion, plus the certifying officer and the record producer named for it.", "Accessibility accommodation data is restricted to the accommodation coordinator and the requesting participant, and is excluded from every general attendance projection.", "A legal hold or live proceeding suspends disposition and re-opens read access for the designated custodian even where a disposition due instant has passed.", "Capture media are readable only under an explicit media scope that is separate from the scope granting access to the occurrence itself." ], "audit_requirements": [ "Every read of closed-portion content and every export of capture media, presence data or attendance reports must be recorded by the adopting Dimension's audit service; this model stores only the returned audit event reference and never the trail itself.", "Changes to the openness class, to a closure ground, to the certified attendance register and to a recorded division must be attributable to an acting party reference and an event instant recorded separately from the ingestion instant.", "Access decisions are evaluated and enforced by the referenced access-policy service; this model records the classification inputs and the decision reference, and asserts no enforcement of its own." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Model ID", "Registry ID", "Owner", "Retention policy URL", "Alignment conflicts URL" ], "read_order": [ "Read AGENTS.md first and resolve Name, Type, Model ID and Registry ID before touching any occurrence data.", "Follow the Specification URL to obtain the bundle, layer and finding structure, the identity priority and the timestamp rule.", "Follow the Storage type URL to learn the projection in use — file tree, document store, graph or version-controlled text — remembering that the projection is not the semantics.", "Follow the Interface URL to learn the read, create, update and delete surface and the scope names required for each.", "Follow the Processes URL to learn the convening, agenda, invitation, quorum, voting, closure and record hand-off procedures and their preconditions.", "Resolve the referenced convening body, party, record and retention models before writing; if any is unresolved, create only the unattached-flagged form and report the gap.", "Consult the Alignment conflicts URL before emitting any external projection, so that recorded conflicts are carried as loss notes rather than resolved locally." ] } }, "coverage": { "claim": "Claude-only coverage of one convened meeting or session occurrence — identity and classification, convening authority and notice, planned and observed timing, series position, physical and virtual setting, accessibility, participation, presence and quorum, agenda composition and conduct, motions and voting, in-session capture, record obligation, openness and interchange — across 6 bundles, 12 layers, 25 findings, 103 questions, 12 artifacts and 10 functions, grounded in 15 sources (IETF calendaring/conferencing, IANA registries, OASIS Akoma Ntoso, schema.org Event, one W3C Group Note, UK company law and two LII reproductions of US federal open-meeting statute). Coverage is partial by construction and by audit: durable records (WM-REC-012, WM-REC-010), the convening body (WM-ORG-018), party/place/document/task masters and access-evaluation and audit services are referenced rather than owned; meeting-level security controls are an admitted gap; and the retention, access, temporal and identity checklist dimensions are over-claimed relative to the questions the structure actually carries and are downgraded by this audit. Sources were not verified live during this audit and no independent second-provider review exists. No universal completeness is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Occurrence identity, series and recurrence discrimination, revision sequence and bound external identifiers are grounded in RFC 5545, RFC 8984 and RFC 6501; the identity priority puts the master-system identifier first and explicitly excludes dates, join codes and series positions." }, { "dimension": "lifecycle", "status": "covered", "notes": "Convocation, adoption of agenda, opening, suspension, resumption, closure of portions, adjournment, cancellation and post-close correction are modelled as occurrence states and typed acts. The lifecycles of the minutes and decision records are deliberately excluded and referenced." }, { "dimension": "relationships", "status": "covered", "notes": "Links to the convening body, parent activity model, record models, party, place, document and task models are declared as composition entries with an explicit ownership boundary in each purpose statement." }, { "dimension": "temporal", "status": "covered", "notes": "Planned versus observed times, named scheduling time zone retained beside the offset, suspension intervals, presence intervals, recurrence position and deadline anchoring are all modelled; RFC 3339 with seconds and explicit offset is required and event time is separated from observation time." }, { "dimension": "provenance", "status": "covered", "notes": "Observation source and observing actor for presence, contribution attribution with speaking capacity, declaring officer for every procedural act, originating product for revisions, and platform-versus-local field authority flags." }, { "dimension": "ownership", "status": "covered", "notes": "Convening authority binding, presiding officer for the occurrence, item sponsorship, action assignee, record producer and certifier are each held as references with an occurrence-scoped meaning; standing mandates remain with the governance body model." }, { "dimension": "validation", "status": "covered", "notes": "Quorum determination against an externally owned threshold, notice sufficiency and defect handling, presence source reconciliation, cross-copy reconciliation by revision and timestamp, and outcome evidence questions." }, { "dimension": "access", "status": "covered", "notes": "Openness classification, closed-portion grounds and certification, observer admission and exclusion, embargo, plus a deny-by-default service rule with named exceptions. Evaluation and enforcement are explicitly delegated." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Disposition due instants, the strictest-applicable-floor rule with two divergent statutory examples, tombstones for withdrawn entries, platform export obligations before source expiry, and explicit statements that the record models and the Dimension's data-protection policy execute disposal." }, { "dimension": "interoperability", "status": "covered", "notes": "Declarative alignment to iCalendar, iTIP, JSCalendar, RFC 9073, schema.org, Akoma Ntoso and XCON, with a field mapping table, loss notes for unmappable concepts and recorded conflicts instead of asserted conformance." }, { "dimension": "accessibility", "status": "covered", "notes": "Accommodation capture, provided services, advance circulation deadlines in accessible native formats and caption or interpretation quality assessment, grounded in the W3C remote-meetings note; the note is a Group Note, not a Recommendation, so it is treated as guidance rather than a normative requirement." }, { "dimension": "privacy", "status": "covered", "notes": "Capture notification and consent basis, personal data inventory with necessity statements, sensitivity flags and consent-withdrawal handling. No jurisdiction-specific lawfulness determination is made by the model." }, { "dimension": "decision conduct", "status": "covered", "notes": "Motion, voting method, threshold, tally, exclusions and result declaration are modelled as session conduct, with routing to WM-REC-010 for the durable decision." }, { "dimension": "measurement", "status": "covered", "notes": "Presence counts and intervals, participant totals, observed item durations, division tallies and observed procedural timings, each carrying its observation source." }, { "dimension": "audit trail", "status": "not-applicable", "notes": "Deliberately not owned. The model records classification inputs and audit event references; the trail itself and its retention belong to the adopting Dimension's audit service, in line with the reference-not-ownership rule." }, { "dimension": "security", "status": "gap", "notes": "Moderator credentials are held as a pointer to an external secret store and channel restriction is modelled, but no primary source was found for a governed vocabulary of meeting-level security controls such as lobby policy, watermarking or exfiltration limits. Marked as a gap rather than presented as canonical." } ], "known_omissions": [ "Multilingual regimes beyond the fact that interpretation was provided: language coverage per speaker, booth assignment and relay chains are not modelled.", "Floor control protocol mechanics, media negotiation and codec selection; only the floor control policy code and the resulting speaking turns are held.", "Cost, travel, catering and logistics of convening a meeting.", "Hearing and tribunal specifics — oath administration, witness examination sequence, exhibits and evidentiary rulings — are only partially reachable through the generic procedural act vocabulary.", "Machine-evaluable encoding of standing orders, so that a rule such as a casting-vote entitlement can be checked automatically rather than recorded as text.", "Decisions taken without a meeting (written resolutions, silence procedure) are excluded by definition and need a sibling model if the adopting Dimension transacts business that way.", "Anonymous or unregistered public attendance at large open meetings, where a per-party presence record cannot be produced.", "Meeting-effectiveness analytics and engagement scoring." ], "conflicts": [ "Status vocabularies diverge: iCalendar STATUS offers only TENTATIVE, CONFIRMED and CANCELLED, while schema.org adds EventPostponed, EventRescheduled and EventMovedOnline. Postponement and rescheduling therefore have no lossless calendaring equivalent and must be carried as a loss note plus a superseding-occurrence reference.", "Three incompatible role vocabularies exist: iCalendar ROLE (CHAIR, REQ-PARTICIPANT, OPT-PARTICIPANT, NON-PARTICIPANT), JSCalendar roles (owner, attendee, optional, informational, chair, multi-valued) and XCON roles (administrator, moderator, participant). No normative crosswalk between them was found; the mapping is recorded as a conflict rather than asserted.", "Identifier spaces do not compose: an iCalendar UID, an XCON conference object URI and a vendor meeting identifier are independent namespaces with no normative binding, which is why the model keeps a bound-identifier map with authority flags instead of promoting one to primary identity.", "Statutory retention floors conflict across jurisdictions: UK company law requires records of resolutions and meetings to be kept for at least ten years, while the United States open-meeting statute requires closed-meeting transcripts, recordings or minutes for at least two years, or one year after the related proceeding ends, whichever is later. A platform default such as a one-year attendance report retention may be shorter than both.", "The statutory definition of a meeting is narrower than the calendaring one: an open-meeting statute defines a meeting as deliberation by the number of members required to take action that determines official business, whereas any calendaring event with attendees qualifies structurally. Classification therefore cannot be derived from structure alone.", "Revision semantics are not a plain version counter: the organiser controls the sequence, participant responses must not increment it, and where sequences tie the message timestamp decides. Systems that treat the counter as a generic optimistic-lock version will diverge.", "Akoma Ntoso models the debate document rather than the session entity, so its vocabulary supports procedural act and speech classification here but its document structures belong to the minutes model. Treating it as a session schema would duplicate WM-REC-012." ], "regional_assumptions": [ "Recording legality varies by jurisdiction, including between all-party and one-party consent regimes. The model records a consent basis and notification facts but makes no legality determination.", "The open-meeting obligations, closure exemptions and minute-content requirements cited are United States federal; equivalent regimes in other jurisdictions differ in the closure grounds, the certification role and the retention floor.", "The ten-year retention floor for meeting records is drawn from UK company law and applies to companies constituted under it, not to public bodies or to other jurisdictions.", "Quorum, proxy, casting-vote and written-resolution rules are entity-type and jurisdiction specific and are always resolved from the convening body's instrument rather than defaulted here.", "Time handling assumes proleptic Gregorian dates and IANA time zone identifiers; non-Gregorian recurrence and jurisdictions with irregular daylight-saving changes need the named zone retained, which is why an offset alone is not accepted.", "Platform retention windows and export behaviour are vendor and tenancy specific; the one-year attendance report window cited is one vendor's documented policy, not a general rule." ], "adversarial_checks": [ "Searched for a normative crosswalk between iCalendar ROLE, JSCalendar roles and XCON roles and found none; recorded it as a conflict rather than inventing a mapping and presenting it as canonical.", "Tested whether approval of the minutes belongs to this model. It does not: approval appears here only as an agenda item of a later occurrence, while the approval state of the record is owned by WM-REC-012. The record-production finding was rewritten to hold obligation and linkage only.", "Tested whether quorum rules should be local. Rejected: the threshold is a property of the convening body's constitution, so only the determination event, its counted base and its outcome are held here.", "Tested whether an audit trail of who viewed a closed session belongs here. Rejected under the reference-not-ownership rule; the model stores audit event references and classification inputs, and the checklist marks audit trail as not-applicable rather than covered.", "Checked counterexamples that stress the definition: asynchronous written procedures (excluded, no occurrence exists), always-on standing conference bridges (excluded until a convened occurrence is declared on them) and one-to-one calls (in scope structurally but usually carrying no agenda, quorum or record obligation).", "Verified that no declared artifact duplicates the minutes, transcript or decision record; the twelve artifacts are notices, agendas, registers, platform exports, speaker lists, division records, action lists, capture media, scheduling messages, accommodation requests and closure certifications.", "Checked whether the interchange finding should declare a projection artifact. Rejected, because treating a format projection as an artifact would contradict the requirement that the model remain independent of storage format and interface; the only exchanged document declared is the scheduling message.", "Re-read every bundle, layer, finding and function against the three known-relation rationales and moved decision rationale, record approval, body membership and task execution out to composition links, out_of_scope entries or boundary notes." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "claude" ], "waivedProviders": [ "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-08-29T09:06:27Z", "scope": "Queued subject-model research from WM-XCT-013 onward", "active_providers": [ "claude" ], "waived_providers": [ { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-08-29T09:06:27Z", "reason": "The repository owner explicitly instructed the research queue to continue without Grok after repeated structured-output failures." } ], "review_rule": "Claude-only results require a separate no-tools adversarial audit and remain reviewable drafts with a visible single-provider hold." }, "boundaryDecision": { "entry_kind": "event", "status": "accepted", "rationale": "The aggregate root is a single bounded occurrence from convocation to close, with planned versus observed instants, a scheduling status set, generation by a recurrence rule, occurrence-scoped participation and determination facts, and outward references to the durable records it owes. Every finding is instance-scoped; none masters a durable entity. That is an event/occurrence, not an entity, document or agent, and it correctly specialises the parent activity model WM-ACT-018 rather than restating it. The frozen registry record's entry_kind of 'standalone-mm' is a record-plane classification in a different vocabulary from the subject-model entry kind 'event', so the two are not contradictory, but the registry field and the subject entry kind must be reconciled explicitly at publication rather than silently coexisting." }, "decisions": [ { "concept": "Aggregate root is the single convened occurrence, not the recurring series", "disposition": "accepted", "rationale": "Root scope is coherent: identity, timing, participation, quorum, conduct and record obligation are all instance-scoped, and the series appears only as a generating rule, an inheritance/override flag and adjacent-session links. Nothing in the structure mints series-level state, so the root holds under adversarial stress." }, { "concept": "Ownership of the recurring series definition", "disposition": "deferred", "rationale": "The series-and-recurrence-position rationale asserts that materialising a series would duplicate the parent activity model's series entity, but WM-ACT-018 appears in the frozen contract only as parent_ids, with no relation stating that it owns a series definition. The assertion is plausible but uncontracted; resolve before the CONTAINS graph is treated as closed." }, { "concept": "CONTAINS WM-REC-012 and WM-REC-010 versus the model's disclaimer of record ownership", "disposition": "accepted as produces-and-references", "rationale": "The frozen instance_semantics read 'Meeting produces minutes or transcript' and 'may produce decision records', which supports composition-by-production rather than lifecycle ownership. The model's split — obligation, producer, certifier and anchor map held locally, draft/approval/disposition owned by the record models — is consistent with that reading and does not contradict the contract." }, { "concept": "Coverage checklist asserts normative rules that no finding or question carries", "disposition": "rejected as stated; downgrade affected dimensions", "rationale": "Retention claims a strictest-applicable-floor rule and tombstones, access claims a deny-by-default service rule with named exceptions, temporal claims RFC 3339 with seconds and explicit offset is required, and identity claims the priority explicitly excludes dates and join codes. None of these appears in any of the 103 questions or in a finding description. These notes pre-empt answers the model does not carry and must be restated as questions or the dimensions downgraded from covered to partial." }, { "concept": "Artifact collision between meeting-notice and scheduling-message", "disposition": "accepted with a required disjointness rule", "rationale": "'Calendar invitation message' is a declared form of the serialized meeting-notice while 'invitation request' is a form of the non-serial scheduling-message, so one object can materialise two artifacts with different identity semantics. Require: the governed convocation instrument is the notice; the iTIP/JSCalendar message is its transport projection; when one message performs both roles it is recorded as the notice with the scheduling message as a projection, never as a second identifier." }, { "concept": "session-capture-media versus the statutory transcript or recording owned by WM-REC-012", "disposition": "accepted with an explicit hand-off point required", "rationale": "The cited open-meeting statute makes a transcript or electronic recording of a closed meeting the retained statutory record, so capture media are session-side only while in custody pending disposition. The transition instant at which captured media become the durable record must be named in capture-media-custody and records-owed-and-basis, and serial:false should be re-tested for media that become statutorily retained records." }, { "concept": "provisional-agenda and adopted-agenda both declared serial", "disposition": "accepted with a required derivation link", "rationale": "Two serialized artifacts for one document lineage risk competing identity for what the adoption act arguably makes two states of the same paper. Keep both, since the adoption act is a genuine procedural event, but require an explicit derived-from link from the adopted agenda to the provisional version so the lineage is single-rooted." }, { "concept": "accommodation-request-record as an artifact owned by the occurrence", "disposition": "reclassified to reference plus occurrence-scoped provision record", "rationale": "Declared forms include service desk tickets and correspondence that originate outside the occurrence and are mastered by an accessibility or HR service. The occurrence legitimately owns the provision made and the unmet-request fallback; the request instrument itself should be referenced rather than declared as a session artifact." }, { "concept": "Questions phrased as if the session owned rules held elsewhere", "disposition": "rejected as phrased; narrow to occurrence-scoped facts", "rationale": "recusal-trigger-and-scope asks which declared interests require withdrawal, and proxy-instruction-lifetime asks when a proxy lapses; both are properties of the interests register and the proxy instrument, not of this occurrence. Narrow to which recusals occurred over which items against a referenced declaration, and whether a valid proxy was presented and accepted at this occurrence." }, { "concept": "Missing functions for capture control with consent and for presence reconciliation", "disposition": "recorded as a gap; cannot be added in single-provider mode", "rationale": "recording-and-transcription-capture carries an artifact, a consent basis and a withdrawal exception with no function that starts, notifies or stops capture; presence-observation carries two artifacts and a reconciliation question with no function that closes the register, imports the platform report and reconciles them. The waiver forbids adding functions here, so these are carried forward as named structural gaps." }, { "concept": "Vendor tier-3 retention window stated as a platform default in the conflicts list", "disposition": "rejected as a general statement", "rationale": "The one-year attendance report retention is sourced only to a tier-3 vendor page dated 2025-05-13, over a year stale as of this audit, and the regional assumptions already concede it is one vendor's policy. Restate it in the conflict entry as a dated, named-vendor illustration rather than as a platform default that undercuts statutory floors." }, { "concept": "No procedural-rules authority behind motions, points of order, seconders and tied votes", "disposition": "deferred to research", "rationale": "motion-and-vote-conduct and procedural-events rest on Akoma Ntoso, which the conflicts list itself concedes models the debate document rather than the session entity, plus two statutes that do not supply a procedural vocabulary. The conduct surface is under-sourced relative to the rest of the model and needs a parliamentary-procedure or standing-orders authority." }, { "concept": "Identifier and name drift against the model's own prose vocabulary", "disposition": "accepted rename while the record is candidate", "rationale": "Finding id procedural-events carries the name 'Procedural acts', and session-instance-identity uses 'instance' where every prose statement uses 'occurrence'. The record is status candidate with no external references in the frozen contract, so normalising the slugs now is cheaper than carrying the drift into published identifiers." }, { "concept": "Model name rendered as the slash form 'Meeting / Session' with alternate_names empty", "disposition": "reclassified", "rationale": "The slash is doing the work of an alternate name, which produces an unstable display and sort key. Publish a single canonical name and move the second term into the registry alternate_names field, which is currently empty." }, { "concept": "Registry purpose is a fragment duplicated from priority_rationale, and source fields are empty or stale", "disposition": "rejected; reconcile at publication", "rationale": "purpose and priority_rationale are both 'Participants, agenda, decisions and record', source_url, namespace_uri and the source group/category/format fields are empty despite 15 researched sources, and source_version_or_year of 2026-08-22 predates the research run. The registry record does not currently represent the researched result." }, { "concept": "Security marked as a gap and audit trail marked not-applicable", "disposition": "accepted", "rationale": "Both are honest refusals to fabricate: no governed vocabulary for meeting-level security controls was found and none was invented, and the audit trail is delegated under the reference-not-ownership rule with only classification inputs and event references retained. These are the correct dispositions and should survive synthesis unchanged." } ], "publicationHolds": [ "Live source and version verification is outstanding for all 15 sources; this audit had no tools and verified nothing live. Before publication, confirm each URL resolves and pin versions, specifically: a point-in-time version for Companies Act 2006 Part 13 Chapter 6 on legislation.gov.uk (the ten-year retention floor depends on it), the post-recodification citation of the Federal Advisory Committee Act at 5 U.S.C. 1009, the current text of 5 U.S.C. 552b, a dated snapshot of the IANA iCalendar Element Registries, the schema.org 30.0 pin, and the Microsoft Graph attendance-report page whose stated update of 2025-05-13 is over a year stale.", "Independent second-provider review is absent by explicit repository-owner authorization: Grok was waived at 2026-08-29T09:06:27Z after repeated structured-output failures. Every publication artifact must carry a visible single-provider hold naming the waived provider, the authorizing party and the timestamp; the artifact stays a reviewable draft and must not be promoted to a reviewed or accepted state on the strength of one provider plus this audit. The registry provenance string, which currently reads 'Claude independent review + systematic gap audit + Claude adversarial audit', must be amended to state the waiver explicitly.", "Substitute tier-1 primary statutory text for the tier-2 Cornell LII reproductions wherever the model relies on them for binding content — closure grounds, minimum record content and the two-year retention floor — or mark those specific claims as reproduction-sourced in the published draft.", "Reconcile the frozen registry record with the researched result before publication: the record-plane entry_kind 'standalone-mm' against the subject entry kind 'event', the fragment purpose duplicated from priority_rationale, the empty source_url/namespace_uri/source_* fields, the stale source_version_or_year of 2026-08-22, and the review_state of boundary-review-required.", "Downgrade the over-claimed coverage checklist dimensions (retention, access, temporal, identity) from covered to partial, or add the missing questions, before the coverage claim is published; as written the checklist asserts a strictest-applicable-floor rule, a deny-by-default access rule, an RFC 3339 seconds-and-offset requirement and identity-priority exclusions that no finding or question in the structure carries.", "Resolve the notice-versus-scheduling-message artifact overlap and name the capture-media to statutory-record hand-off point before any artifact identifiers are minted, so that no two artifacts can be materialised by the same object under different identity semantics.", "Independent second-provider review was explicitly waived by the repository owner; this Claude-only result remains a reviewable draft." ], "deferredResearch": [ "Locate a primary procedural-rules authority (standing orders, parliamentary procedure or a legislative rules-of-order source) to support motions, seconders, points of order, casting votes and tied-vote resolution; Akoma Ntoso is a debate-document vocabulary by the model's own concession and cannot carry the conduct surface alone.", "Establish which model owns the recurring series definition. The structure asserts it belongs to WM-ACT-018, but the frozen relationship contract records WM-ACT-018 only as a parent and contains no series relation, leaving the inheritance and override rules uncontracted.", "Search for a governed vocabulary of meeting-level security controls — lobby and admission policy, watermarking, exfiltration limits, moderator credential handling — to close the dimension currently and correctly marked as a gap rather than fabricated.", "Re-check IANA registries, RFC 9073 and any newer conferencing work for a normative crosswalk between iCalendar ROLE, JSCalendar roles and XCON roles; the absence of one is currently recorded as a conflict and should be re-tested rather than left permanently open.", "Test the retention and closure claims against at least one non-Anglo-American regime (EU or other civil-law open-meeting and corporate record rules) so that the two-jurisdiction basis of the strictest-floor reasoning is not mistaken for a general rule.", "Add an accessibility authority with normative force (EN 301 549, WCAG or an equivalent statutory baseline) alongside the W3C Group Note, which the model itself treats as guidance rather than a requirement.", "Scope the declared sibling model for decisions taken without a meeting (written resolutions and silence procedure), which is excluded by definition here and currently has no home in the registry.", "Re-verify the vendor attendance-report retention window and export behaviour against current vendor documentation, and confirm whether the platform-exit-obligation question is satisfiable within that window." ] }, "statistics": { "sources": 15, "bundles": 6, "layers": 12, "findings": 25, "questions": 103, "artifacts": 12, "functions": 10 } }