{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-ai-016","code":"wm-ai-016-agent-handoff-message","url":"https://ver.cy/models/wm-ai-016-agent-handoff-message/","name":"Agent Handoff Message","alternateNames":[],"kind":"world-model","status":"published","version":"0.1.0","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"entity","plane":"","domain":["INF.AI.HND"],"industry":["Cross-industry"],"navPath":"NAV.INF.AI.HND","tags":["agent","handoff","message","inf.ai.hnd"],"facets":{}},"whatItIs":"One logical handoff message and its governed representations. Sending, receiving and responding are separately evidenced occurrences. The message can exist before delivery or acceptance and may transfer context without a task. This format-neutral research proposal is not an execution engine or a grant of authority.","purpose":"Describe an identified communication that proposes or conveys a bounded task or context transfer between agents, with recipient-specific evidence and explicit authority references.","scope":{"in":["Message identity, intent, participant bindings and correlation references","Selected context, remaining work, constraints, uncertainty and artifact access descriptions","Recipient-specific receipt and acceptance evidence references, expiry, supersession and interoperability losses"],"out":["Agent run execution, scheduling, task state machines, cost accounting and compensation","Issuing, expanding, revoking or enforcing delegation mandates or credentials","Agent configuration, tool definitions, full conversation or memory stores and authoritative audit trails","Transport delivery, external artifact retrieval, operational security enforcement and domain-specific dangerous instructions"],"boundaries":[{"neighbor":"WM-AI-004 AI Inference / Agent Run","distinction":"Registry parent is a candidate contextual alignment, not inheritance: a message is not a run. Carry optional originating and receiving run references; execution and task lifecycle remain externally mastered."},{"neighbor":"WM-AI-015 Agent Delegation Mandate","distinction":"Reference an applicable mandate or record that no delegated action is requested. A handoff request, recipient acceptance or role label never issues or widens authority."},{"neighbor":"WM-AI-005 Prompt / Agent Configuration","distinction":"Instructions and configuration remain external versioned masters. Transferred context is untrusted data and cannot silently replace the receiving agent policy."},{"neighbor":"WM-AI-017 Tool Description","distinction":"Optional tool or capability references express requirements only; this message owns neither tool interface definitions nor invocation permissions."},{"neighbor":"A2A task, message and artifact","distinction":"A2A supplies a candidate communication mapping. Local handoff purpose, offer acceptance and work-transfer meaning require a declared application profile; A2A task artifacts retain their own identities."}]},"distinguishingFeatures":["Unlike WM-AI-004 AI Inference / Agent Run: Registry parent is a candidate contextual alignment, not inheritance: a message is not a run. Carry optional originating and receiving run references; execution and task lifecycle remain externally mastered.","Unlike WM-AI-015 Agent Delegation Mandate: Reference an applicable mandate or record that no delegated action is requested. A handoff request, recipient acceptance or role label never issues or widens authority.","Unlike WM-AI-005 Prompt / Agent Configuration: Instructions and configuration remain external versioned masters. Transferred context is untrusted data and cannot silently replace the receiving agent policy.","Unlike WM-AI-017 Tool Description: Optional tool or capability references express requirements only; this message owns neither tool interface definitions nor invocation permissions.","Unlike A2A task, message and artifact: A2A supplies a candidate communication mapping. Local handoff purpose, offer acceptance and work-transfer meaning require a declared application profile; A2A task artifacts retain their own identities."],"structure":{"bundles":[{"id":"bundle-identity","name":"Message identity","description":"Proposed message concern: message identity.","layers":[{"id":"layer-envelope","name":"Logical identity and representation","description":"Preserve one logical communication across authorized representations and delivery attempts. A changed offer or materially changed payload needs a new message linked to the earlier one; it is not an invisible retry.","findings":[{"id":"finding-message-identity","name":"Scoped message identity","description":"Preserve one logical communication across authorized representations and delivery attempts. A changed offer or materially changed payload needs a new message linked to the earlier one; it is not an invisible retry.","questions":[{"text":"Which master namespace and identifier distinguish this message from its task, run and delivery attempts?","id":"q-message-identity-1","kind":"identity"},{"text":"What declared handoff intent distinguishes a context notice, work offer, continuation, return or cancellation request?","id":"q-message-identity-2","kind":"classification"},{"text":"How is reuse of the same message identifier with different content detected and quarantined?","id":"q-message-identity-3","kind":"validation"},{"text":"Which predecessor does a corrected or superseding message identify without rewriting the original?","id":"q-message-identity-4","kind":"lifecycle"}]}]},{"id":"layer-correlation","name":"Participants and correlation","description":"Bind sender, intended recipient and represented principal to governed identities. Context, task, trace and run references serve different purposes and are never interchangeable evidence of access.","findings":[{"id":"finding-participant-binding","name":"Participants and conversation bindings","description":"Bind sender, intended recipient and represented principal to governed identities. Context, task, trace and run references serve different purposes and are never interchangeable evidence of access.","questions":[{"text":"Which sender, intended recipient and represented principal are bound to this transfer?","id":"q-participant-binding-1","kind":"relationship"},{"text":"Which context, task and run identifiers are related, and which are deliberately absent?","id":"q-participant-binding-2","kind":"composition"},{"text":"Who is accountable for the message record and who owns the referenced work after a reported acceptance?","id":"q-participant-binding-3","kind":"ownership"},{"text":"Which trust-domain and tenant bindings prevent a trace or conversation identifier from granting access?","id":"q-participant-binding-4","kind":"security"}]}]}]},{"id":"bundle-work-context","name":"Transferred work and context","description":"Proposed message concern: transferred work and context.","layers":[{"id":"layer-work","name":"Work intent and limits","description":"Describe the bounded remainder and response expected by the sender. Distinguish completed assertions from verified results and proposed actions from authorized actions. Work planning and execution stay external.","findings":[{"id":"finding-remaining-work","name":"Remaining work and expected response","description":"Describe the bounded remainder and response expected by the sender. Distinguish completed assertions from verified results and proposed actions from authorized actions. Work planning and execution stay external.","questions":[{"text":"What goal, remaining work and explicit exclusions are communicated to the recipient?","id":"q-remaining-work-1","kind":"definition"},{"text":"Which completed-work assertions are supported by result references and which remain unverified?","id":"q-remaining-work-2","kind":"evidence"},{"text":"What deliverable, response format and acceptance criteria does this offer request?","id":"q-remaining-work-3","kind":"requirement"},{"text":"Which stated time, cost or tool constraints are only requested limits pending external authorization?","id":"q-remaining-work-4","kind":"constraint"}]}]},{"id":"layer-snapshot","name":"Selected context and uncertainty","description":"Carry the minimum selected context or stable references needed for the declared purpose. Preserve source, version, uncertainty, truncation and omitted material; a summary does not establish completeness or require disclosure of private internal reasoning.","findings":[{"id":"finding-context-selection","name":"Context snapshot and omissions","description":"Carry the minimum selected context or stable references needed for the declared purpose. Preserve source, version, uncertainty, truncation and omitted material; a summary does not establish completeness or require disclosure of private internal reasoning.","questions":[{"text":"Which source revisions and selection process produced the context snapshot or summary?","id":"q-context-selection-1","kind":"provenance"},{"text":"What uncertainties, contradictions and missing dependencies could change the receiving agent interpretation?","id":"q-context-selection-2","kind":"quality"},{"text":"Which purpose and recipient view justify included context and document deliberate omissions?","id":"q-context-selection-3","kind":"privacy"},{"text":"At what observation time was the context valid and what freshness condition requires rechecking it?","id":"q-context-selection-4","kind":"temporal"}]}]}]},{"id":"bundle-payload","name":"Payload and evidence","description":"Proposed message concern: payload and evidence.","layers":[{"id":"layer-parts","name":"Payload references and integrity","description":"Describe typed inline parts and external artifacts with identity, integrity and permitted resolution requirements. Referenced artifacts remain in their master systems; a URL or digest is neither access permission nor proof of safe content.","findings":[{"id":"finding-payload-manifest","name":"Parts and artifact resolution","description":"Describe typed inline parts and external artifacts with identity, integrity and permitted resolution requirements. Referenced artifacts remain in their master systems; a URL or digest is neither access permission nor proof of safe content.","questions":[{"text":"Which ordered content parts are inline and which reference independently mastered artifacts?","id":"q-payload-manifest-1","kind":"composition"},{"text":"What authorization and expiry conditions govern each recipient attempt to resolve an artifact?","id":"q-payload-manifest-2","kind":"access"},{"text":"What digest, size or schema evidence detects missing, altered or incompatible content?","id":"q-payload-manifest-3","kind":"validation"},{"text":"How should an unavailable, quarantined or expired artifact be represented without silently replacing it?","id":"q-payload-manifest-4","kind":"exception"}]}]},{"id":"layer-lineage","name":"Claim attribution and continuity","description":"Keep message authorship, generation activity, derivation and observations distinct. Evidence may be disputed or incomplete. Referenced audit records and traces retain their own authority and retention rules.","findings":[{"id":"finding-provenance-record","name":"Message lineage and evidence","description":"Keep message authorship, generation activity, derivation and observations distinct. Evidence may be disputed or incomplete. Referenced audit records and traces retain their own authority and retention rules.","questions":[{"text":"Who authored or generated this representation and from which source entities was it derived?","id":"q-provenance-record-1","kind":"provenance"},{"text":"What evidence supports a claimed handoff occurrence and who attested or observed it?","id":"q-provenance-record-2","kind":"evidence"},{"text":"How are creation, dispatch, receipt and ingestion times distinguished when clocks disagree?","id":"q-provenance-record-3","kind":"temporal"},{"text":"Which provenance links are asserted, verified, disputed or missing rather than treated as proof of truth?","id":"q-provenance-record-4","kind":"quality"}]}]}]},{"id":"bundle-authority","name":"Authority and trust","description":"Proposed message concern: authority and trust.","layers":[{"id":"layer-mandate","name":"Mandate and principal binding","description":"Reference an existing mandate, policy or authorization decision for requested action and access. Keep actor and subject distinguishable. Transfer no bearer credentials in context; authorization evaluation, token exchange and revocation execution remain external.","findings":[{"id":"finding-authority-reference","name":"Bounded authority reference","description":"Reference an existing mandate, policy or authorization decision for requested action and access. Keep actor and subject distinguishable. Transfer no bearer credentials in context; authorization evaluation, token exchange and revocation execution remain external.","questions":[{"text":"Which mandate or policy authorizes this sender to request this recipient action on behalf of the stated principal?","id":"q-authority-reference-1","kind":"authority"},{"text":"Which audience, scope, expiry and redelegation limits constrain the requested action?","id":"q-authority-reference-2","kind":"constraint"},{"text":"How are credential material and authorization references kept separate in the transferred context?","id":"q-authority-reference-3","kind":"security"},{"text":"What unresolved or revoked authority evidence requires the recipient to defer or refuse action?","id":"q-authority-reference-4","kind":"exception"}]}]},{"id":"layer-trust","name":"Untrusted context handling","description":"Label content trust and instruction provenance. Receiving policies decide how to use context and when to require qualified human review. Context cannot override policy, elevate permissions or establish that a hazardous action is safe.","findings":[{"id":"finding-trust-policy","name":"Recipient trust and escalation policy","description":"Label content trust and instruction provenance. Receiving policies decide how to use context and when to require qualified human review. Context cannot override policy, elevate permissions or establish that a hazardous action is safe.","questions":[{"text":"Which parts are untrusted data or external instructions and how are they separated from receiving policy?","id":"q-trust-policy-1","kind":"security"},{"text":"Which recipient view hides secrets, sensitive payloads and correlation metadata not needed for the purpose?","id":"q-trust-policy-2","kind":"access"},{"text":"What policy condition requires human review, refusal or escalation before acting on the handoff?","id":"q-trust-policy-3","kind":"decision"},{"text":"How are suspicious or policy-conflicting parts quarantined while retaining safe evidence references?","id":"q-trust-policy-4","kind":"exception"}]}]}]},{"id":"bundle-receipt","name":"Receipt and continuation evidence","description":"Proposed message concern: receipt and continuation evidence.","layers":[{"id":"layer-response","name":"Receipt and acceptance distinction","description":"Record observations and external evidence for receipt, acceptance, refusal, clarification or unknown disposition per recipient. These are application-profile concepts. A transport success, silence or task status alone does not prove ownership transfer.","findings":[{"id":"finding-recipient-disposition","name":"Recipient disposition evidence","description":"Record observations and external evidence for receipt, acceptance, refusal, clarification or unknown disposition per recipient. These are application-profile concepts. A transport success, silence or task status alone does not prove ownership transfer.","questions":[{"text":"What is known about each intended recipient receipt separately from acceptance of the offered work?","id":"q-recipient-disposition-1","kind":"state"},{"text":"Who may attest acceptance and which exact message and offer revision does that attestation cover?","id":"q-recipient-disposition-2","kind":"authority"},{"text":"What clarification, partial acceptance or refusal is reported and what work remains with the sender?","id":"q-recipient-disposition-3","kind":"process"},{"text":"Which external assignment or continuation record establishes the effect of an accepted handoff?","id":"q-recipient-disposition-4","kind":"event"}]}]},{"id":"layer-recovery","name":"Retry, expiry and supersession","description":"Retain attempt references and unknown outcomes without promising exactly-once delivery or effects. A2A permits rather than guarantees send idempotency. Cancellation requests and superseding messages do not retract already observed execution.","findings":[{"id":"finding-delivery-ambiguity","name":"Delivery ambiguity and stale offers","description":"Retain attempt references and unknown outcomes without promising exactly-once delivery or effects. A2A permits rather than guarantees send idempotency. Cancellation requests and superseding messages do not retract already observed execution.","questions":[{"text":"How are retries of one unchanged message distinguished from new offers and superseding communications?","id":"q-delivery-ambiguity-1","kind":"lifecycle"},{"text":"What expiry, deadline and clock-skew policy applies to a delayed acceptance or stale context?","id":"q-delivery-ambiguity-2","kind":"temporal"},{"text":"What recorded state preserves an uncertain delivery or conflicting recipient response for reconciliation?","id":"q-delivery-ambiguity-3","kind":"exception"},{"text":"Which external authority decides cancellation or compensation after work may already have started?","id":"q-delivery-ambiguity-4","kind":"constraint"}]}]}]},{"id":"bundle-governance","name":"Interoperability and record governance","description":"Proposed message concern: interoperability and record governance.","layers":[{"id":"layer-profile","name":"Profile and compatibility","description":"Pin the adopted message profile, protocol version and extension semantics. A2A, CloudEvents, PROV-O and Trace Context map distinct concerns. Unsupported critical extensions or lossy field projections require explicit disposition.","findings":[{"id":"finding-profile-mapping","name":"Profile mapping and validation","description":"Pin the adopted message profile, protocol version and extension semantics. A2A, CloudEvents, PROV-O and Trace Context map distinct concerns. Unsupported critical extensions or lossy field projections require explicit disposition.","questions":[{"text":"Which protocol version, application profile and extension vocabulary define this handoff representation?","id":"q-profile-mapping-1","kind":"interoperability"},{"text":"Which required fields and semantic constraints were checked for this exact representation?","id":"q-profile-mapping-2","kind":"validation"},{"text":"What meaning is lost when mapping message roles, intent, parts or identifiers between bindings?","id":"q-profile-mapping-3","kind":"quality"},{"text":"Which acceptance fixtures must pass before claiming operational interoperability?","id":"q-profile-mapping-4","kind":"requirement"}]}]},{"id":"layer-retention","name":"Custody and disposition","description":"Govern only local message representations, recipient views and evidence references. Custodians define retention and erasure by applicable policy. Revision continuity must not require indefinite retention of sensitive payloads.","findings":[{"id":"finding-record-disposition","name":"Record continuity and disposal","description":"Govern only local message representations, recipient views and evidence references. Custodians define retention and erasure by applicable policy. Revision continuity must not require indefinite retention of sensitive payloads.","questions":[{"text":"Which policy determines retention periods and holds for message payloads, metadata and cached references?","id":"q-record-disposition-1","kind":"retention"},{"text":"How can recipient copies or cached payloads be erased while preserving permitted minimal continuity evidence?","id":"q-record-disposition-2","kind":"privacy"},{"text":"Which custodian may correct metadata or retire a local record without altering external task or mandate masters?","id":"q-record-disposition-3","kind":"ownership"},{"text":"How are superseded, redacted or disposed representations resolved for authorized readers?","id":"q-record-disposition-4","kind":"lifecycle"}]}]}]}]},"agentConduct":{"may":["Compose a local handoff draft: Proposed, unimplemented operation. Create a local draft with selected context, recipient bindings and requested effect.","Validate a local representation: Proposed, unimplemented operation. Check local shape, reference consistency, required profile fields and declared constraints.","Prepare a recipient view: Proposed, unimplemented operation. Produce a minimized local view under an existing disclosure policy.","Link recipient disposition evidence: Proposed, unimplemented operation. Bind a reported receipt or acceptance to the exact message and recipient.","Record message supersession: Proposed, unimplemented operation. Link a newly authored message to a prior offer without changing its historical payload.","Record local disposal disposition: Proposed, unimplemented operation. Record approved retention or erasure instructions and observed execution evidence."],"mustNot":["Receipt or role labels never confer authority.","Deny access unless an authorized recipient, purpose and scope are established; filter sensitive metadata as well as payloads."],"requiresHuman":[]},"ethics":{"considerations":["Policy-level review handles suspicious instructions; this model specifies no harmful operational procedures.","Reused message ID with changed payload must remain a conflict, not a harmless retry."],"affectedParties":[]},"owners":{"steward":"Assign an accountable deployer or record custodian role, not a commercial owner name.","roles":[{"name":"Accountable deployer","responsibilities":["Approves the profile and governing policy; does not receive automatic access to every payload."]},{"name":"Sending agent","responsibilities":["Prepares bounded context and evidence under authority; labels unknowns."]},{"name":"Receiving agent","responsibilities":["Records dispositions and validates its own authority before action."]},{"name":"Record custodian","responsibilities":["Controls revisions, recipient views, retention and disposition."]},{"name":"Qualified reviewer","responsibilities":["Resolves policy exceptions and contested handoff evidence."]}],"masterSystems":[]},"relations":[{"target":"WM-AI-004","type":"references","note":"Optional origin/continuation run binding; candidate registry parent is not adopted as inheritance. Execution stays external."},{"target":"WM-AI-015","type":"references","note":"Conditional mandate binding for delegated action. Does not own issuance, scope evaluation or revocation."},{"target":"WM-AI-005","type":"references","note":"Optional pinned receiving instruction/configuration profile; transferred context cannot overwrite it."},{"target":"WM-AI-017","type":"references","note":"Optional capability or tool-description requirements without owning interfaces or permissions."},{"target":"A2A 1.0.0","type":"aligned","note":"Conceptual message/task/part mapping with application-specific handoff semantics and declared losses."},{"target":"PROV-O","type":"aligned","note":"Attribution, derivation and qualified delegation evidence, without proof of authority."},{"target":"CloudEvents 1.0.2","type":"aligned","note":"Optional occurrence envelope for delivery/receipt observations; event identity is separate from message identity."},{"target":"W3C Trace Context","type":"aligned","note":"Optional telemetry correlation with privacy limits; never an authorization or message identity substitute."},{"target":"WM-AI-004 AI Inference / Agent Run","type":"neighbor","note":"Registry parent is a candidate contextual alignment, not inheritance: a message is not a run. Carry optional originating and receiving run references; execution and task lifecycle remain externally mastered."},{"target":"WM-AI-015 Agent Delegation Mandate","type":"neighbor","note":"Reference an applicable mandate or record that no delegated action is requested. A handoff request, recipient acceptance or role label never issues or widens authority."},{"target":"WM-AI-005 Prompt / Agent Configuration","type":"neighbor","note":"Instructions and configuration remain external versioned masters. Transferred context is untrusted data and cannot silently replace the receiving agent policy."},{"target":"WM-AI-017 Tool Description","type":"neighbor","note":"Optional tool or capability references express requirements only; this message owns neither tool interface definitions nor invocation permissions."},{"target":"A2A task, message and artifact","type":"neighbor","note":"A2A supplies a candidate communication mapping. Local handoff purpose, offer acceptance and work-transfer meaning require a declared application profile; A2A task artifacts retain their own identities."},{"target":"WM-AI-004","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","Dimension-assigned UUID or ULID"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Compose a local handoff draft: Proposed, unimplemented operation. Create a local draft with selected context, recipient bindings and requested effect.","Validate a local representation: Proposed, unimplemented operation. Check local shape, reference consistency, required profile fields and declared constraints.","Prepare a recipient view: Proposed, unimplemented operation. Produce a minimized local view under an existing disclosure policy.","Link recipient disposition evidence: Proposed, unimplemented operation. Bind a reported receipt or acceptance to the exact message and recipient.","Record message supersession: Proposed, unimplemented operation. Link a newly authored message to a prior offer without changing its historical payload.","Record local disposal disposition: Proposed, unimplemented operation. Record approved retention or erasure instructions and observed execution evidence."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology","RFC 8693: OAuth 2.0 Token Exchange","RFC 3339: Date and Time on the Internet: Timestamps"]},"context":{"applicability":"required","items":["Format-neutral technical draft; deployment jurisdiction, data-residency, confidentiality, licensing and retention obligations require qualified local review.","No universal transfer of legal responsibility is inferred from agent acceptance."]}},"sources":[{"title":"A2A Protocol Specification","url":"https://a2a-protocol.org/v1.0.0/specification/","note":"A2A project"},{"title":"MCP Security Best Practices","url":"https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices","note":"MCP project"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"RFC 8693: OAuth 2.0 Token Exchange","url":"https://www.rfc-editor.org/rfc/rfc8693","note":"IETF"},{"title":"Trace Context","url":"https://www.w3.org/TR/trace-context/","note":"W3C"},{"title":"LLM Prompt Injection Prevention Cheat Sheet","url":"https://cheatsheetseries.owasp.org/cheatsheets/LLM_Prompt_Injection_Prevention_Cheat_Sheet.html","note":"OWASP"},{"title":"RFC 3339: Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"IETF"},{"title":"CloudEvents Specification","url":"https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md","note":"CNCF CloudEvents project"}],"openQuestions":["Verify all source responses, redirects, current versions, errata and exact living-guidance revisions; record claim-level evidence rather than treating HTTP success as substantive verification.","Develop an adopting profile and nested schemas with fixtures for changed-content retries, lost replies, partial acceptance, concurrent recipients, stale mandates, expired artifacts, redaction and lawful disposal.","Restore independent external review before canonical or publishable-draft promotion.","Independent external provider review is absent under the owner-authorized waiver.","Direct HTTP responses, body hashes, current errata and exact revisions of living guidance are not verified.","Nested field schemas, concrete vocabulary values, acceptance-state transitions and adversarial fixtures require an adopting profile.","No runtime implementation, distributed ownership transaction, exactly-once guarantee, security certification or universal legal retention rule is supplied.","Alternative emerging handoff specifications and domain profiles have not been exhaustively surveyed."],"resources":{"spec":"/models/wm-ai-016-agent-handoff-message/spec.yaml","agents":"/models/wm-ai-016-agent-handoff-message/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-ai-016"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-ai-016-agent-handoff-message/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-21T17:00:26Z","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}}