{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-018","code":"wm-act-018-encounter","url":"https://ver.cy/models/wm-act-018-encounter/","name":"Encounter","alternateNames":["X5"],"kind":"world-model","status":"published","version":"1.0.0","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"event","plane":"","domain":["ACT.ENC"],"industry":["Cross-industry"],"navPath":"NAV.ACT.ENC","tags":["encounter","act.enc"],"facets":{}},"whatItIs":"One encounter occurrence or explicitly planned, attempted or disputed encounter record. An occurred encounter needs evidence of engagement involving at least two distinct parties represented by role entries under an adopted interaction profile; incomplete identity is allowed without inventing parties. The two-party criterion is a local boundary decision, not a universal standard definition. Records persist independently of the event they describe.","purpose":"Describe a bounded interaction among parties while preserving separate participation, exchange, perspective, acknowledgement and outcome evidence.","scope":{"in":["Encounter-specific binding to occurrence identity, interaction kind, engagement criterion and segment bounds","Human, organization, group or automated-agent participation by reference with scoped roles and authority","Physical, remote, hybrid and bounded asynchronous channels, exchange references and timing uncertainty","Separate private accounts, proposed shared records, scoped acknowledgements, disputed outcomes and follow-up references","Policy-qualified access, evidence provenance, record corrections, retention and mapping limits"],"out":["Generic occurrence identity issuance, lifecycle engine and conflict resolution belong to WM-ACT-015 or the adopting master","Scheduling, message transport, contract formation, payment settlement and task execution remain in their masters","Clinical care delivery and clinical observations or diagnoses are external domains, not mandatory content of every encounter","Person, organization, location, authority, consent, audit, retention execution and signature verification engines","Persistent relationships, unrestricted broadcasts and unobserved co-presence without evidence of interaction","Operational guidance for dangerous activities; any such encounter uses policy-level references only"],"boundaries":[{"neighbor":"WM-ACT-015 Occurrence / Event","distinction":"Accept conceptual EXTEND for the encounter-specific engagement and perspective facets; delegate generic event identity and state machinery. Executable inheritance awaits a pinned binding."},{"neighbor":"WM-ACT-014 Health Care Delivery","distinction":"Incoming containment is conditional on a clinical profile. A generic meeting or negotiation is not thereby a healthcare event; this model cannot own care delivery."},{"neighbor":"WM-ACT-046 Clinical Observation / Diagnosis","distinction":"Outgoing candidate containment is narrowed to optional external references in clinical profiles. Observations and diagnoses keep independent masters and need not exist for an encounter."},{"neighbor":"Appointment, message, transaction and persistent relationship masters","distinction":"Invitations and calendar responses are plans; a message is an exchange artifact; a transaction outcome needs its own authoritative record; a recurring relationship is not one encounter."},{"neighbor":"Legacy X5 and unreviewed supplement","distinction":"Retain party perspectives and optional mutual records. Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure. Multiple scoped revisions and disputed or absent outcomes are permitted."}]},"distinguishingFeatures":["Unlike WM-ACT-015 Occurrence / Event: Accept conceptual EXTEND for the encounter-specific engagement and perspective facets; delegate generic event identity and state machinery. Executable inheritance awaits a pinned binding.","Unlike WM-ACT-014 Health Care Delivery: Incoming containment is conditional on a clinical profile. A generic meeting or negotiation is not thereby a healthcare event; this model cannot own care delivery.","Unlike WM-ACT-046 Clinical Observation / Diagnosis: Outgoing candidate containment is narrowed to optional external references in clinical profiles. Observations and diagnoses keep independent masters and need not exist for an encounter.","Unlike Appointment, message, transaction and persistent relationship masters: Invitations and calendar responses are plans; a message is an exchange artifact; a transaction outcome needs its own authoritative record; a recurring relationship is not one encounter.","Unlike Legacy X5 and unreviewed supplement: Retain party perspectives and optional mutual records. Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure. Multiple scoped revisions and disputed or absent outcomes are permitted."],"structure":{"bundles":[{"id":"binding","name":"Encounter boundary","description":"Encounter-specific questions about encounter boundary.","layers":[{"id":"interaction-binding","name":"Interaction criterion","description":"Bind the occurrence master to a declared interaction segment. Similar participants, timing or meeting links alone cannot prove two reports describe the same encounter.","findings":[{"id":"engagement","name":"Encounter identity and engagement","description":"Bind the occurrence master to a declared interaction segment. Similar participants, timing or meeting links alone cannot prove two reports describe the same encounter.","questions":[{"text":"Which occurrence master and party-local identifiers refer to this encounter, and what evidence supports their reconciliation?","id":"engagement-q1","kind":"identity"},{"text":"What engagement criterion distinguishes this interaction from a plan, unanswered attempt, broadcast or mere co-presence?","id":"engagement-q2","kind":"definition"},{"text":"What makes this one segment rather than a recurring series, parent encounter or separate follow-up?","id":"engagement-q3","kind":"composition"}]}]},{"id":"progress-assertions","name":"Encounter progress","description":"Record encounter-specific progress assertions against the occurrence master. An imported planned or cancelled record is not evidence that interaction happened; record correction is not a new occurrence.","findings":[{"id":"progress","name":"Planned and observed progress","description":"Record encounter-specific progress assertions against the occurrence master. An imported planned or cancelled record is not evidence that interaction happened; record correction is not a new occurrence.","questions":[{"text":"Which current progress assertion is planned, attempted, active, ended, cancelled, entered in error or unresolved under the adopted profile?","id":"progress-q1","kind":"state"},{"text":"What observation supports opening or ending actual engagement rather than merely opening or closing its record?","id":"progress-q2","kind":"event"},{"text":"How are no-show, disconnection, resumption and conflicting closure reports represented without forcing agreement?","id":"progress-q3","kind":"exception"}]}]}]},{"id":"parties","name":"Participation and authority","description":"Encounter-specific questions about participation and authority.","layers":[{"id":"participation","name":"Party involvement","description":"Identify participating roles, including representatives, interpreters and automated agents, separately from invitees and observers. Unresolved identity may use protected local placeholders; placeholders are not proof of distinct parties.","findings":[{"id":"party-roles","name":"Actual and intended participants","description":"Identify participating roles, including representatives, interpreters and automated agents, separately from invitees and observers. Unresolved identity may use protected local placeholders; placeholders are not proof of distinct parties.","questions":[{"text":"Which parties actually engaged, were merely invited, observed, or remain unidentified, and what supports each status?","id":"party-roles-q1","kind":"relationship"},{"text":"During which segments did each participant join, leave or participate intermittently?","id":"party-roles-q2","kind":"temporal"},{"text":"Which participant is a person, organization, group or automated agent, and what principal does the role represent?","id":"party-roles-q3","kind":"classification"}]}]},{"id":"representation","name":"Representation limits","description":"Keep authority to speak, attest, disclose and bind a principal distinct. Party perspectives are separately stewarded records; stewardship does not settle property rights or authorize disclosure.","findings":[{"id":"authority","name":"Delegation and perspective stewardship","description":"Keep authority to speak, attest, disclose and bind a principal distinct. Party perspectives are separately stewarded records; stewardship does not settle property rights or authorize disclosure.","questions":[{"text":"What mandate, scope and effective period allow a representative to act for a principal in this interaction?","id":"authority-q1","kind":"authority"},{"text":"Who stewards each party account and shared record, and under what accountable policy?","id":"authority-q2","kind":"ownership"},{"text":"Which proposed commitments or acknowledgements exceed the recorded mandate and require referral?","id":"authority-q3","kind":"constraint"}]}]}]},{"id":"context","name":"Channel and time","description":"Encounter-specific questions about channel and time.","layers":[{"id":"channel-segments","name":"Communication setting","description":"An interaction may move among in-person, remote and written channels. Store protected endpoint and place references per segment, never access credentials or transport machinery.","findings":[{"id":"channels","name":"Channels and locations","description":"An interaction may move among in-person, remote and written channels. Store protected endpoint and place references per segment, never access credentials or transport machinery.","questions":[{"text":"Which physical or virtual locations and channel segments contextualize the encounter?","id":"channels-q1","kind":"spatial"},{"text":"What language, interpretation or accessibility arrangements affected participation and record interpretation?","id":"channels-q2","kind":"requirement"},{"text":"Which channel identifiers or recording references must be withheld from each audience?","id":"channels-q3","kind":"security"}]}]},{"id":"time-claims","name":"Timing semantics","description":"Keep planned bounds, observed engagement periods, participant intervals and record ingestion instants separate. Elapsed or connected time does not automatically measure attention, billable service or clinical care.","findings":[{"id":"timing","name":"Bounds and timing uncertainty","description":"Keep planned bounds, observed engagement periods, participant intervals and record ingestion instants separate. Elapsed or connected time does not automatically measure attention, billable service or clinical care.","questions":[{"text":"What are the planned and observed bounds, their time zones, precision and reporting sources?","id":"timing-q1","kind":"temporal"},{"text":"If a duration is reported, which segments, units and exclusions define it and how uncertain is it?","id":"timing-q2","kind":"measurement"},{"text":"How are late reports, unknown ends, clock disagreements and date-only evidence preserved?","id":"timing-q3","kind":"quality"}]}]}]},{"id":"exchange","name":"Exchanges and accounts","description":"Encounter-specific questions about exchanges and accounts.","layers":[{"id":"exchange-links","name":"Exchange references","description":"Index exchanged messages, documents, object references and statements by source and recipient role. A transport receipt is not understanding, agreement, transfer of title or settlement.","findings":[{"id":"items","name":"Items and statements exchanged","description":"Index exchanged messages, documents, object references and statements by source and recipient role. A transport receipt is not understanding, agreement, transfer of title or settlement.","questions":[{"text":"What item or statement was exchanged, by which role and toward which recipient or audience?","id":"items-q1","kind":"relationship"},{"text":"What distinguishes asserted dispatch, receipt, review and disputed delivery for this exchange?","id":"items-q2","kind":"evidence"},{"text":"Which content can be referenced without copying sensitive payload into the encounter?","id":"items-q3","kind":"privacy"}]}]},{"id":"record-versions","name":"Perspective records","description":"Keep a unilateral account distinct from a shared proposal and an acknowledged revision. Multiple documents and translations may describe one encounter; preserve derivation and limited visibility.","findings":[{"id":"accounts","name":"Private and shared accounts","description":"Keep a unilateral account distinct from a shared proposal and an acknowledged revision. Multiple documents and translations may describe one encounter; preserve derivation and limited visibility.","questions":[{"text":"Which author, source material and transformation produced this account or translation?","id":"accounts-q1","kind":"provenance"},{"text":"Which portions are private notes, shared proposals or content approved for a named audience?","id":"accounts-q2","kind":"access"},{"text":"How does a corrected account relate to earlier versions without silently replacing acknowledged content?","id":"accounts-q3","kind":"lifecycle"}]}]}]},{"id":"outcomes","name":"Acknowledgement and consequences","description":"Encounter-specific questions about acknowledgement and consequences.","layers":[{"id":"acknowledgement","name":"Acknowledgement scope","description":"Acknowledge exact record versions and scope per party. Silence, attendance, a digest or technical signature validity does not establish shared agreement; unsigned or disputed encounters remain representable.","findings":[{"id":"attestations","name":"Scoped acknowledgement evidence","description":"Acknowledge exact record versions and scope per party. Silence, attendance, a digest or technical signature validity does not establish shared agreement; unsigned or disputed encounters remain representable.","questions":[{"text":"What exact revision and content scope did each party acknowledge, reject or leave unanswered?","id":"attestations-q1","kind":"evidence"},{"text":"What signature or acknowledgement validation result is available, and what trust or authority questions remain unresolved?","id":"attestations-q2","kind":"validation"},{"text":"How are partial agreement, withdrawal, coercion concerns and later corrections recorded without rewriting prior assertions?","id":"attestations-q3","kind":"exception"}]}]},{"id":"follow-up","name":"Consequences and continuation","description":"Distinguish observed, proposed, agreed and disputed results, including no agreement. Link subsequent encounters and obligations to their masters without executing actions or determining legal or clinical effects.","findings":[{"id":"results","name":"Outcomes and follow-up references","description":"Distinguish observed, proposed, agreed and disputed results, including no agreement. Link subsequent encounters and obligations to their masters without executing actions or determining legal or clinical effects.","questions":[{"text":"Which result was observed or proposed, who supports it, and which qualifications or disagreements remain?","id":"results-q1","kind":"decision"},{"text":"Which external task, commitment, transaction or clinical record carries any resulting obligation or observation?","id":"results-q2","kind":"relationship"},{"text":"Which later encounter continues this one, and how is continuation distinguished from a child segment or recurring schedule?","id":"results-q3","kind":"composition"}]}]}]},{"id":"governance","name":"Disclosure and record continuity","description":"Encounter-specific questions about disclosure and record continuity.","layers":[{"id":"disclosure","name":"Authorized views","description":"Assess collection, recording, transcription and disclosure separately under an adopting legal and purpose profile. Universal consent of all named parties is not assumed; absent or conflicting authority blocks local release.","findings":[{"id":"views","name":"Recording and disclosure authority","description":"Assess collection, recording, transcription and disclosure separately under an adopting legal and purpose profile. Universal consent of all named parties is not assumed; absent or conflicting authority blocks local release.","questions":[{"text":"Which applicable rule and approved purpose authorize this specific recording, transcription or disclosure?","id":"views-q1","kind":"authority"},{"text":"Whose data and sensitive inferences occur in the proposed view, including nonparticipants mentioned in the record?","id":"views-q2","kind":"privacy"},{"text":"What evidence authorizes the recipient and exact scope, and when must the proposed release be refused or escalated?","id":"views-q3","kind":"access"}]}]},{"id":"disposition","name":"Retention and correction","description":"Different accounts and recordings may have different retention rules. Referenced disposition authorities control execution; local correction history must not justify indefinite retention of personal content.","findings":[{"id":"continuity","name":"Correction and disposition obligations","description":"Different accounts and recordings may have different retention rules. Referenced disposition authorities control execution; local correction history must not justify indefinite retention of personal content.","questions":[{"text":"Which retention rule, trigger, hold and disposition authority apply to each account and retained copy?","id":"continuity-q1","kind":"retention"},{"text":"How can a party dispute or correct its account while preserving other parties assertions and signed-version meaning?","id":"continuity-q2","kind":"lifecycle"},{"text":"What minimal lawful evidence can remain after payload erasure, and which remote copies cannot be claimed deleted?","id":"continuity-q3","kind":"constraint"}]}]}]},{"id":"assurance","name":"Evidence and interoperability","description":"Encounter-specific questions about evidence and interoperability.","layers":[{"id":"evidence-quality","name":"Assertion quality","description":"Record support and limitations for each encounter assertion. Presence logs, transcripts and party recollections can conflict; attribution and integrity do not decide which account is true.","findings":[{"id":"quality","name":"Conflicting evidence and recognition","description":"Record support and limitations for each encounter assertion. Presence logs, transcripts and party recollections can conflict; attribution and integrity do not decide which account is true.","questions":[{"text":"Which evidence supports or contradicts each material encounter assertion and who supplied it?","id":"quality-q1","kind":"provenance"},{"text":"What limits arise from missing segments, transcript errors, interpretation or inferred participation?","id":"quality-q2","kind":"quality"},{"text":"Which discrepancies need an authorized reviewer instead of automatic account merging?","id":"quality-q3","kind":"validation"}]}]},{"id":"mapping","name":"Profile bindings","description":"Map only declared encounter facets to pinned external schemas. The general model is not identical to a clinical Encounter, a calendar event or a generic Activity.","findings":[{"id":"interoperability","name":"Profile mapping and loss","description":"Map only declared encounter facets to pinned external schemas. The general model is not identical to a clinical Encounter, a calendar event or a generic Activity.","questions":[{"text":"Which source and target versions map identity, state, parties, bounds and acknowledgement scope without loss?","id":"interoperability-q1","kind":"interoperability"},{"text":"Which mandatory target fields or unsupported semantics require refusal, a qualified extension or a specialist profile?","id":"interoperability-q2","kind":"constraint"},{"text":"Which fixtures establish that no-show, partial participation, disputed records and clinical references survive the mapping?","id":"interoperability-q3","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Bind encounter evidence: Proposed local operation, not implemented. Prepare an encounter-specific projection linked to the authoritative occurrence master.","Record participation assertion: Proposed local operation, not implemented. Append a role-scoped participation account without upgrading invitation to attendance.","Index an exchange: Proposed local operation, not implemented. Link an already evidenced exchange to its item master and permitted audience.","Record scoped acknowledgement: Proposed local operation, not implemented. Record an existing party assertion against exact content and version, preserving disagreement.","Link result and continuation: Proposed local operation, not implemented. Record a qualified outcome and references to external follow-up masters.","Prepare an authorized local view: Proposed local operation, not implemented. Construct a minimal local review view from externally approved purpose and recipient scopes.","Assess profile mapping: Proposed local operation, not implemented. Compare declared encounter facets with a pinned target contract and record loss."],"mustNot":["Planned and unresolved records must not assert occurrence.","Deny access unless actor, purpose, recipient and exact perspective scope are authorized; participation alone grants no right to all private accounts."],"requiresHuman":["Do not assume all-party consent is either always necessary or always sufficient."]},"ethics":{"considerations":["Do not assume all-party consent is either always necessary or always sufficient.","Privacy and records officer","Clinical and privacy sources are scoped examples, not universal definitions.","EDPB guidance concerns EU/EEA data protection; it does not settle national recording or signature law or worldwide privacy duties.","Reject the universal all-party-consent rule and automatic authority from participation.","Person, organization, location, authority, consent, audit, retention execution and signature verification engines","Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure."],"affectedParties":[]},"owners":{"steward":"Accountable record custodian and participating-party roles with scope-specific authority evidence","roles":[{"name":"Encounter record custodian","responsibilities":["Maintain binding, profile and scoped record continuity"]},{"name":"Party or authorized representative","responsibilities":["Supply and qualify only assertions within the evidenced mandate"]},{"name":"Evidence reviewer","responsibilities":["Examine contradictory reports, identity matches and acknowledgement scope"]},{"name":"Privacy and records officer","responsibilities":["Approve recipient views, retention and disposition policy references"]},{"name":"Profile maintainer","responsibilities":["Pin schema mappings and record conformance limits"]}],"masterSystems":[]},"relations":[{"target":"WM-ACT-015","type":"extends","note":"Conceptual specialization of occurrence through engagement, party perspectives and scoped acknowledgement. Generic identity, event history, authority and conflict machinery stay in the occurrence master; runtime binding must be pinned."},{"target":"WM-ACT-014","type":"references","note":"Optional clinical context for the incoming care-delivery containment candidate; no generic requirement that every encounter belongs to care delivery."},{"target":"WM-ACT-046","type":"references","note":"Optional clinical observation or diagnosis reference. Candidate CONTAINS is qualified as a profile association; no mandatory child and no locally owned diagnosis lifecycle."},{"target":"RFC 5545","type":"aligned","note":"Calendar plan, attendee and recurrence references only; not evidence of actual engagement."},{"target":"PROV-O 2013-04-30","type":"aligned","note":"Attribution and derivation vocabulary alignment; no evidence truth or authority inference."},{"target":"FHIR R5 5.0.0 Encounter","type":"aligned","note":"Selected clinical profile comparison only; no universal FHIR resource equivalence or implemented mapping."},{"target":"Activity Vocabulary 2017-05-23","type":"aligned","note":"Exchange and continuity vocabulary alignment; generic activities do not establish encounter engagement."},{"target":"XML Signature 1.1","type":"aligned","note":"Signed-scope and verification-evidence alignment only; signature execution and legal effect are external."},{"target":"WM-ACT-015 Occurrence / Event","type":"neighbor","note":"Accept conceptual EXTEND for the encounter-specific engagement and perspective facets; delegate generic event identity and state machinery. Executable inheritance awaits a pinned binding."},{"target":"WM-ACT-014 Health Care Delivery","type":"neighbor","note":"Incoming containment is conditional on a clinical profile. A generic meeting or negotiation is not thereby a healthcare event; this model cannot own care delivery."},{"target":"WM-ACT-046 Clinical Observation / Diagnosis","type":"neighbor","note":"Outgoing candidate containment is narrowed to optional external references in clinical profiles. Observations and diagnoses keep independent masters and need not exist for an encounter."},{"target":"Appointment, message, transaction and persistent relationship masters","type":"neighbor","note":"Invitations and calendar responses are plans; a message is an exchange artifact; a transaction outcome needs its own authoritative record; a recurring relationship is not one encounter."},{"target":"Legacy X5 and unreviewed supplement","type":"neighbor","note":"Retain party perspectives and optional mutual records. Reject mandatory countersigning, a single channel, one immutable record forever and universal all-party-consent disclosure. Multiple scoped revisions and disputed or absent outcomes are permitted."},{"target":"WM-ACT-046","type":"contains"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier with namespace and revision","Governed global identifier or stable record URI","Local opaque UUID or ULID with reconciliation state"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Bind encounter evidence: Proposed local operation, not implemented. Prepare an encounter-specific projection linked to the authoritative occurrence master.","Record participation assertion: Proposed local operation, not implemented. Append a role-scoped participation account without upgrading invitation to attendance.","Index an exchange: Proposed local operation, not implemented. Link an already evidenced exchange to its item master and permitted audience.","Record scoped acknowledgement: Proposed local operation, not implemented. Record an existing party assertion against exact content and version, preserving disagreement.","Link result and continuation: Proposed local operation, not implemented. Record a qualified outcome and references to external follow-up masters.","Prepare an authorized local view: Proposed local operation, not implemented. Construct a minimal local review view from externally approved purpose and recipient scopes.","Assess profile mapping: Proposed local operation, not implemented. Compare declared encounter facets with a pinned target contract and record loss."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology","FHIR Encounter"]},"context":{"applicability":"required","items":["EDPB guidance concerns EU/EEA data protection; it does not settle national recording or signature law or worldwide privacy duties.","FHIR R5 is a selected clinical schema example, not a current-release or universal encounter claim."]}},"sources":[{"title":"Internet Calendaring and Scheduling Core Object Specification (iCalendar)","url":"https://www.rfc-editor.org/rfc/rfc5545","note":"IETF"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"FHIR Encounter","url":"https://hl7.org/fhir/R5/encounter.html","note":"HL7 International"},{"title":"Activity Vocabulary","url":"https://www.w3.org/TR/activitystreams-vocabulary/","note":"W3C"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"IETF"},{"title":"XML Signature Syntax and Processing Version 1.1","url":"https://www.w3.org/TR/xmldsig-core1/","note":"W3C"},{"title":"Data protection basics","url":"https://www.edpb.europa.eu/sme/learn-the-basics/data-protection-basics_en","note":"European Data Protection Board"},{"title":"Process personal data lawfully","url":"https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en","note":"European Data Protection Board"}],"openQuestions":["Restore independent external review and complete claim, version, update, licensing and source-response verification before canonical promotion.","Develop jurisdiction and sector profiles for disputed, mediated, automated, asynchronous and clinical encounters while preserving separate authority and evidence ownership.","Build nested schemas and mapping fixtures for duplicate-party roles, no-show, hybrid participation, conflicting closure, partial acknowledgements, corrected signed content, scoped erasure and unmappable target constraints.","Independent second-provider review remains absent.","Direct HTTP and response hashes are unmeasured under the owner-reported sandbox restriction; coordinator verification is pending.","Executable nested schemas, event bindings, mapping fixtures, target versions and conformance testing remain incomplete.","Sector and jurisdiction rules for recording, representation, signatures, sensitive data, retention and compelled disclosure need qualified review.","Nonclinical trade, mediated group interaction, cross-border interpretation and asynchronous segment boundaries need additional profile evidence."],"resources":{"spec":"/models/wm-act-018-encounter/spec.yaml","agents":"/models/wm-act-018-encounter/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-018"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-018-encounter/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T14:24:50Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification.","interaction.properties":"Institutional or informational subject: no invented physical properties."},"score":0.75}}