{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-eco-026","code":"wm-eco-026-sales-lead-opportunity","url":"https://ver.cy/models/wm-eco-026-sales-lead-opportunity/","name":"Sales Lead / Opportunity","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Society, people and institutions","entryKind":"aggregate","plane":"","domain":["SOC.ECO.CRM"],"industry":["Cross-industry"],"navPath":"NAV.SOC.ECO.CRM","tags":["sales","lead","opportunity","soc.eco.crm"],"facets":{}},"whatItIs":"Owns pursuit identity, version, profile and status; signal, source and attribution; need, demand, problem, outcome and use-case assertions; qualification dimensions and decisions; offering-fit, scope, quantity, location, timing and dependency assertions; estimated value, budget, amount type, currency, recurrence, range and basis; score, method, version, explanation, confidence, bias and calibration; stage, gate and exception assertions; probability, forecast category, expected-close and as-of assertions; stakeholder, owner, team, influence and decision-group roles; interaction, activity and next-action references; capture, deduplication, merge, split, qualify, convert, nurture, hold, reopen, win, loss, no-decision and closure evidence; quote, order, contract and outcome references; distinct clocks, provenance, privacy, retention, validation and loss-aware projections. External party, customer, account, campaign, product, offering, activity, communication, calendar, quote, order, contract, fulfilment, forecast, financial and records masters remain authoritative.","purpose":"Represent one governed commercial pursuit from an originating lead signal through an explicitly qualified opportunity so agents can coordinate need, fit, stakeholders, activities, value, stage, probability, forecast and outcome without confusing the pursuit with party, customer, account, campaign, offering, quote, order, contract or revenue masters.","scope":{"in":["Pursuit identity, version, classification, lineage, origin, attribution, need, demand, offering fit, scope, quantity, timing, location, dependencies and estimated value","Qualification, score, stage, gates, probability, forecast, stakeholders, consent and preference bindings, activities, next actions, conversion, closure, outcome, clocks, provenance, privacy, retention and projections"],"out":["Owning Party, Contact, Organization, Customer, Account, Campaign, Product, Offering, Activity, Message, Calendar, Quote, Order, Contract, Fulfilment, Invoice, Payment, Revenue, Forecast Period, Records or Consent masters","Treating a lead signal as a known person, a known party as a qualified lead, a qualified lead as a customer, or qualification, score, stage, probability, forecast and outcome as mutually proving facts","Autonomous contact, consent creation, sensitive-attribute inference, adverse action, pricing, quote issuance, order acceptance, contract execution, forecast commitment, financial recognition, disclosure or record destruction"],"boundaries":[{"neighbor":"WM-ORG-014 Customer / Account Relationship","distinction":"The unified registry supplies only a provisional parent signal and the frozen relation ledger has no settled edge. Customer and account relationships remain external; a pursuit binds them when known."},{"neighbor":"Lead signal, party, contact, customer and account","distinction":"Signals may be anonymous or inferred, parties and contacts have external identities, and customer or account status has its own authority. Conversion preserves lineage instead of collapsing these identities."},{"neighbor":"Campaign, offering, activity, message and calendar","distinction":"Attribution, fit and touchpoints are typed references; their content, execution, delivery, scheduling and master lifecycle stay external."},{"neighbor":"Quote, order, contract, fulfilment, forecast and finance","distinction":"Estimated value and probability support a pursuit but are not price, quotation, commitment, order, contract, delivery, recognized revenue or cash. Those masters retain independent authority."},{"neighbor":"TM Forum, UBL, Schema.org, privacy law, ORG, RFC, PROV, DQV, ODRL and OpenAPI","distinction":"Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring."}]},"distinguishingFeatures":["A commercial pursuit from lead signal to qualified opportunity and outcome.","Keeps lead signal, known party, qualified lead, customer and opportunity distinct.","Qualification, score, stage, probability and forecast are separate axes.","Differs from the customer or account relationship, which persists beyond one pursuit."],"structure":{"bundles":[{"id":"pursuit-identity-origin-parties-and-ownership","name":"Pursuit identity, origin, parties and ownership","description":"Groups sales-pursuit context for pursuit identity, origin, parties and ownership.","layers":[{"id":"case-identity-classification-and-lineage","name":"Case identity, classification and lineage","description":"Groups source-qualified sales-pursuit context for case identity, classification and lineage.","findings":[{"id":"pursuit-id-version-profile-status-and-master-system","name":"Pursuit ID, version, profile, status and master system","description":"Records pursuit id, version, profile, status and master system as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish pursuit id, version, profile, status and master system?","id":"pursuit-id-version-profile-status-and-master-system-q01","kind":"identity"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on pursuit id, version, profile, status and master system, for which purpose and under what delegated authority?","id":"pursuit-id-version-profile-status-and-master-system-q02","kind":"ownership"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify pursuit id, version, profile, status and master system?","id":"pursuit-id-version-profile-status-and-master-system-q03","kind":"validation"}]},{"id":"lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage","name":"Lead signal, known party, qualified lead, opportunity, conversion and lineage","description":"Records lead signal, known party, qualified lead, opportunity, conversion and lineage as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish lead signal, known party, qualified lead, opportunity, conversion and lineage?","id":"lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-q01","kind":"classification"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on lead signal, known party, qualified lead, opportunity, conversion and lineage, for which purpose and under what delegated authority?","id":"lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-q02","kind":"authority"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify lead signal, known party, qualified lead, opportunity, conversion and lineage?","id":"lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-q03","kind":"security"}]}]},{"id":"origin-attribution-parties-and-account-binding","name":"Origin, attribution, parties and account binding","description":"Groups source-qualified sales-pursuit context for origin, attribution, parties and account binding.","findings":[{"id":"source-channel-campaign-event-referral-partner-and-attribution","name":"Source, channel, campaign, event, referral, partner and attribution","description":"Records source, channel, campaign, event, referral, partner and attribution as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish source, channel, campaign, event, referral, partner and attribution?","id":"source-channel-campaign-event-referral-partner-and-attribution-q01","kind":"provenance"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on source, channel, campaign, event, referral, partner and attribution, for which purpose and under what delegated authority?","id":"source-channel-campaign-event-referral-partner-and-attribution-q02","kind":"requirement"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify source, channel, campaign, event, referral, partner and attribution?","id":"source-channel-campaign-event-referral-partner-and-attribution-q03","kind":"privacy"}]},{"id":"prospect-contact-customer-account-stakeholder-owner-team-and-authority-role","name":"Prospect, contact, customer, account, stakeholder, owner, team and authority role","description":"Records prospect, contact, customer, account, stakeholder, owner, team and authority role as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish prospect, contact, customer, account, stakeholder, owner, team and authority role?","id":"prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-q01","kind":"ownership"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on prospect, contact, customer, account, stakeholder, owner, team and authority role, for which purpose and under what delegated authority?","id":"prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-q02","kind":"constraint"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify prospect, contact, customer, account, stakeholder, owner, team and authority role?","id":"prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-q03","kind":"retention"}]}]}]},{"id":"need-demand-fit-scope-and-value","name":"Need, demand, fit, scope and value","description":"Groups sales-pursuit context for need, demand, fit, scope and value.","layers":[{"id":"need-demand-use-case-and-offering-fit","name":"Need, demand, use case and offering fit","description":"Groups source-qualified sales-pursuit context for need, demand, use case and offering fit.","findings":[{"id":"expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence","name":"Expressed or inferred need, problem, outcome, use case, confidence and evidence","description":"Records expressed or inferred need, problem, outcome, use case, confidence and evidence as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish expressed or inferred need, problem, outcome, use case, confidence and evidence?","id":"expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-q01","kind":"evidence"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on expressed or inferred need, problem, outcome, use case, confidence and evidence, for which purpose and under what delegated authority?","id":"expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-q02","kind":"process"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify expressed or inferred need, problem, outcome, use case, confidence and evidence?","id":"expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-q03","kind":"access"}]},{"id":"product-service-offering-solution-catalog-specification-and-qualification-reference","name":"Product, service, offering, solution, catalog, specification and qualification reference","description":"Records product, service, offering, solution, catalog, specification and qualification reference as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish product, service, offering, solution, catalog, specification and qualification reference?","id":"product-service-offering-solution-catalog-specification-and-qualification-reference-q01","kind":"relationship"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on product, service, offering, solution, catalog, specification and qualification reference, for which purpose and under what delegated authority?","id":"product-service-offering-solution-catalog-specification-and-qualification-reference-q02","kind":"event"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify product, service, offering, solution, catalog, specification and qualification reference?","id":"product-service-offering-solution-catalog-specification-and-qualification-reference-q03","kind":"exception"}]}]},{"id":"scope-quantity-timing-location-and-value","name":"Scope, quantity, timing, location and value","description":"Groups source-qualified sales-pursuit context for scope, quantity, timing, location and value.","findings":[{"id":"scope-item-quantity-location-timeline-dependency-constraint-and-assumption","name":"Scope, item, quantity, location, timeline, dependency, constraint and assumption","description":"Records scope, item, quantity, location, timeline, dependency, constraint and assumption as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish scope, item, quantity, location, timeline, dependency, constraint and assumption?","id":"scope-item-quantity-location-timeline-dependency-constraint-and-assumption-q01","kind":"constraint"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on scope, item, quantity, location, timeline, dependency, constraint and assumption, for which purpose and under what delegated authority?","id":"scope-item-quantity-location-timeline-dependency-constraint-and-assumption-q02","kind":"measurement"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify scope, item, quantity, location, timeline, dependency, constraint and assumption?","id":"scope-item-quantity-location-timeline-dependency-constraint-and-assumption-q03","kind":"interoperability"}]},{"id":"estimated-value-budget-amount-currency-recurrence-range-and-basis","name":"Estimated value, budget, amount, currency, recurrence, range and basis","description":"Records estimated value, budget, amount, currency, recurrence, range and basis as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish estimated value, budget, amount, currency, recurrence, range and basis?","id":"estimated-value-budget-amount-currency-recurrence-range-and-basis-q01","kind":"measurement"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on estimated value, budget, amount, currency, recurrence, range and basis, for which purpose and under what delegated authority?","id":"estimated-value-budget-amount-currency-recurrence-range-and-basis-q02","kind":"evidence"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify estimated value, budget, amount, currency, recurrence, range and basis?","id":"estimated-value-budget-amount-currency-recurrence-range-and-basis-q03","kind":"decision"}]}]}]},{"id":"qualification-score-stage-probability-and-forecast","name":"Qualification, score, stage, probability and forecast","description":"Groups sales-pursuit context for qualification, score, stage, probability and forecast.","layers":[{"id":"qualification-dimensions-score-and-decision","name":"Qualification dimensions, score and decision","description":"Groups source-qualified sales-pursuit context for qualification dimensions, score and decision.","findings":[{"id":"fit-intent-authority-budget-timing-need-risk-and-qualification","name":"Fit, intent, authority, budget, timing, need, risk and qualification","description":"Records fit, intent, authority, budget, timing, need, risk and qualification as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish fit, intent, authority, budget, timing, need, risk and qualification?","id":"fit-intent-authority-budget-timing-need-risk-and-qualification-q01","kind":"decision"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on fit, intent, authority, budget, timing, need, risk and qualification, for which purpose and under what delegated authority?","id":"fit-intent-authority-budget-timing-need-risk-and-qualification-q02","kind":"quality"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify fit, intent, authority, budget, timing, need, risk and qualification?","id":"fit-intent-authority-budget-timing-need-risk-and-qualification-q03","kind":"identity"}]},{"id":"score-model-method-version-feature-evidence-explanation-confidence-and-bias","name":"Score, model, method, version, feature, evidence, explanation, confidence and bias","description":"Records score, model, method, version, feature, evidence, explanation, confidence and bias as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish score, model, method, version, feature, evidence, explanation, confidence and bias?","id":"score-model-method-version-feature-evidence-explanation-confidence-and-bias-q01","kind":"quality"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on score, model, method, version, feature, evidence, explanation, confidence and bias, for which purpose and under what delegated authority?","id":"score-model-method-version-feature-evidence-explanation-confidence-and-bias-q02","kind":"validation"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify score, model, method, version, feature, evidence, explanation, confidence and bias?","id":"score-model-method-version-feature-evidence-explanation-confidence-and-bias-q03","kind":"classification"}]}]},{"id":"stage-gates-probability-and-forecast","name":"Stage, gates, probability and forecast","description":"Groups source-qualified sales-pursuit context for stage, gates, probability and forecast.","findings":[{"id":"stage-status-gate-criterion-entry-exit-hold-and-exception","name":"Stage, status, gate criterion, entry, exit, hold and exception","description":"Records stage, status, gate criterion, entry, exit, hold and exception as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish stage, status, gate criterion, entry, exit, hold and exception?","id":"stage-status-gate-criterion-entry-exit-hold-and-exception-q01","kind":"state"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on stage, status, gate criterion, entry, exit, hold and exception, for which purpose and under what delegated authority?","id":"stage-status-gate-criterion-entry-exit-hold-and-exception-q02","kind":"security"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify stage, status, gate criterion, entry, exit, hold and exception?","id":"stage-status-gate-criterion-entry-exit-hold-and-exception-q03","kind":"composition"}]},{"id":"probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of","name":"Probability, confidence, basis, calibration, forecast category, expected close and as-of","description":"Records probability, confidence, basis, calibration, forecast category, expected close and as-of as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish probability, confidence, basis, calibration, forecast category, expected close and as-of?","id":"probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-q01","kind":"temporal"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on probability, confidence, basis, calibration, forecast category, expected close and as-of, for which purpose and under what delegated authority?","id":"probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-q02","kind":"privacy"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify probability, confidence, basis, calibration, forecast category, expected close and as-of?","id":"probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-q03","kind":"relationship"}]}]}]},{"id":"stakeholders-interactions-activities-and-next-actions","name":"Stakeholders, interactions, activities and next actions","description":"Groups sales-pursuit context for stakeholders, interactions, activities and next actions.","layers":[{"id":"decision-group-influence-consent-and-preferences","name":"Decision group, influence, consent and preferences","description":"Groups source-qualified sales-pursuit context for decision group, influence, consent and preferences.","findings":[{"id":"stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest","name":"Stakeholder role, influence, decision group, sponsor, champion, blocker and interest","description":"Records stakeholder role, influence, decision group, sponsor, champion, blocker and interest as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish stakeholder role, influence, decision group, sponsor, champion, blocker and interest?","id":"stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-q01","kind":"relationship"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on stakeholder role, influence, decision group, sponsor, champion, blocker and interest, for which purpose and under what delegated authority?","id":"stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-q02","kind":"retention"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify stakeholder role, influence, decision group, sponsor, champion, blocker and interest?","id":"stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-q03","kind":"state"}]},{"id":"contact-point-consent-lawful-basis-preference-objection-channel-and-constraint","name":"Contact point, consent, lawful basis, preference, objection, channel and constraint","description":"Records contact point, consent, lawful basis, preference, objection, channel and constraint as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish contact point, consent, lawful basis, preference, objection, channel and constraint?","id":"contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-q01","kind":"privacy"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on contact point, consent, lawful basis, preference, objection, channel and constraint, for which purpose and under what delegated authority?","id":"contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-q02","kind":"access"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify contact point, consent, lawful basis, preference, objection, channel and constraint?","id":"contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-q03","kind":"lifecycle"}]}]},{"id":"touchpoints-activities-commitments-and-followup","name":"Touchpoints, activities, commitments and follow-up","description":"Groups source-qualified sales-pursuit context for touchpoints, activities, commitments and follow-up.","findings":[{"id":"interaction-meeting-call-message-content-demo-event-task-and-response-reference","name":"Interaction, meeting, call, message, content, demo, event, task and response reference","description":"Records interaction, meeting, call, message, content, demo, event, task and response reference as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish interaction, meeting, call, message, content, demo, event, task and response reference?","id":"interaction-meeting-call-message-content-demo-event-task-and-response-reference-q01","kind":"event"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on interaction, meeting, call, message, content, demo, event, task and response reference, for which purpose and under what delegated authority?","id":"interaction-meeting-call-message-content-demo-event-task-and-response-reference-q02","kind":"exception"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify interaction, meeting, call, message, content, demo, event, task and response reference?","id":"interaction-meeting-call-message-content-demo-event-task-and-response-reference-q03","kind":"temporal"}]},{"id":"next-action-owner-due-date-dependency-commitment-escalation-and-result","name":"Next action, owner, due date, dependency, commitment, escalation and result","description":"Records next action, owner, due date, dependency, commitment, escalation and result as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish next action, owner, due date, dependency, commitment, escalation and result?","id":"next-action-owner-due-date-dependency-commitment-escalation-and-result-q01","kind":"process"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on next action, owner, due date, dependency, commitment, escalation and result, for which purpose and under what delegated authority?","id":"next-action-owner-due-date-dependency-commitment-escalation-and-result-q02","kind":"interoperability"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify next action, owner, due date, dependency, commitment, escalation and result?","id":"next-action-owner-due-date-dependency-commitment-escalation-and-result-q03","kind":"spatial"}]}]}]},{"id":"lifecycle-commercial-boundaries-outcomes-and-learning","name":"Lifecycle, commercial boundaries, outcomes and learning","description":"Groups sales-pursuit context for lifecycle, commercial boundaries, outcomes and learning.","layers":[{"id":"capture-dedup-conversion-progression-and-closure","name":"Capture, deduplication, conversion, progression and closure","description":"Groups source-qualified sales-pursuit context for capture, deduplication, conversion, progression and closure.","findings":[{"id":"capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify","name":"Capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify","description":"Records capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify?","id":"capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-q01","kind":"lifecycle"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify, for which purpose and under what delegated authority?","id":"capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-q02","kind":"decision"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify?","id":"capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-q03","kind":"provenance"}]},{"id":"open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive","name":"Open, progress, hold, reopen, win, loss, no decision, abandon and archive","description":"Records open, progress, hold, reopen, win, loss, no decision, abandon and archive as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish open, progress, hold, reopen, win, loss, no decision, abandon and archive?","id":"open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-q01","kind":"state"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on open, progress, hold, reopen, win, loss, no decision, abandon and archive, for which purpose and under what delegated authority?","id":"open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-q02","kind":"identity"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify open, progress, hold, reopen, win, loss, no decision, abandon and archive?","id":"open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-q03","kind":"ownership"}]}]},{"id":"quote-order-contract-outcome-and-retrospective","name":"Quote, order, contract, outcome and retrospective","description":"Groups source-qualified sales-pursuit context for quote, order, contract, outcome and retrospective.","findings":[{"id":"quote-proposal-tender-negotiation-order-contract-and-commitment-reference","name":"Quote, proposal, tender, negotiation, order, contract and commitment reference","description":"Records quote, proposal, tender, negotiation, order, contract and commitment reference as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish quote, proposal, tender, negotiation, order, contract and commitment reference?","id":"quote-proposal-tender-negotiation-order-contract-and-commitment-reference-q01","kind":"interoperability"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on quote, proposal, tender, negotiation, order, contract and commitment reference, for which purpose and under what delegated authority?","id":"quote-proposal-tender-negotiation-order-contract-and-commitment-reference-q02","kind":"classification"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify quote, proposal, tender, negotiation, order, contract and commitment reference?","id":"quote-proposal-tender-negotiation-order-contract-and-commitment-reference-q03","kind":"authority"}]},{"id":"outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective","name":"Outcome, reason, competitor, alternative, value, decision evidence and retrospective","description":"Records outcome, reason, competitor, alternative, value, decision evidence and retrospective as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish outcome, reason, competitor, alternative, value, decision evidence and retrospective?","id":"outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-q01","kind":"evidence"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on outcome, reason, competitor, alternative, value, decision evidence and retrospective, for which purpose and under what delegated authority?","id":"outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-q02","kind":"composition"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify outcome, reason, competitor, alternative, value, decision evidence and retrospective?","id":"outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-q03","kind":"requirement"}]}]}]},{"id":"governance-provenance-time-access-and-interoperability","name":"Governance, provenance, time, access and interoperability","description":"Groups sales-pursuit context for governance, provenance, time, access and interoperability.","layers":[{"id":"source-provenance-privacy-access-retention-and-correction","name":"Source, provenance, privacy, access, retention and correction","description":"Groups source-qualified sales-pursuit context for source, provenance, privacy, access, retention and correction.","findings":[{"id":"owner-steward-source-actor-activity-derivation-revision-conflict-and-audit","name":"Owner, steward, source, actor, activity, derivation, revision, conflict and audit","description":"Records owner, steward, source, actor, activity, derivation, revision, conflict and audit as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish owner, steward, source, actor, activity, derivation, revision, conflict and audit?","id":"owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-q01","kind":"provenance"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on owner, steward, source, actor, activity, derivation, revision, conflict and audit, for which purpose and under what delegated authority?","id":"owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-q02","kind":"relationship"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify owner, steward, source, actor, activity, derivation, revision, conflict and audit?","id":"owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-q03","kind":"constraint"}]},{"id":"purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone","name":"Purpose, lawful basis, consent, objection, access, minimization, retention and tombstone","description":"Records purpose, lawful basis, consent, objection, access, minimization, retention and tombstone as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish purpose, lawful basis, consent, objection, access, minimization, retention and tombstone?","id":"purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-q01","kind":"access"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on purpose, lawful basis, consent, objection, access, minimization, retention and tombstone, for which purpose and under what delegated authority?","id":"purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-q02","kind":"state"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify purpose, lawful basis, consent, objection, access, minimization, retention and tombstone?","id":"purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-q03","kind":"process"}]}]},{"id":"event-clocks-validation-and-loss-aware-projections","name":"Event clocks, validation and loss-aware projections","description":"Groups source-qualified sales-pursuit context for event clocks, validation and loss-aware projections.","findings":[{"id":"source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time","name":"Source, capture, consent, qualification, stage, contact, forecast, close, observed and known time","description":"Records source, capture, consent, qualification, stage, contact, forecast, close, observed and known time as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish source, capture, consent, qualification, stage, contact, forecast, close, observed and known time?","id":"source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-q01","kind":"temporal"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on source, capture, consent, qualification, stage, contact, forecast, close, observed and known time, for which purpose and under what delegated authority?","id":"source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-q02","kind":"lifecycle"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify source, capture, consent, qualification, stage, contact, forecast, close, observed and known time?","id":"source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-q03","kind":"event"}]},{"id":"identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation","name":"Identity, state, value, TMF, UBL, Schema.org, privacy, ORG, RFC, PROV, DQV, ODRL and API validation","description":"Records identity, state, value, tmf, ubl, schema.org, privacy, org, rfc, prov, dqv, odrl and api validation as source-qualified sales-pursuit context while party, account, campaign, offering, interaction, quote, order, contract, fulfilment, finance and records masters remain independently identifiable.","questions":[{"text":"Which stable pursuit, version, origin, need, party, account, offering and external-master identities plus explicit unknown state establish identity, state, value, tmf, ubl, schema.org, privacy, org, rfc, prov, dqv, odrl and api validation?","id":"identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-q01","kind":"validation"},{"text":"Who asserted, observed, evaluated, owns, may contact, may change or may rely on identity, state, value, tmf, ubl, schema.org, privacy, org, rfc, prov, dqv, odrl and api validation, for which purpose and under what delegated authority?","id":"identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-q02","kind":"temporal"},{"text":"Which source, method, rule, evidence, event time, observation time, as-of time, confidence, validation and correction history qualify identity, state, value, tmf, ubl, schema.org, privacy, org, rfc, prov, dqv, odrl and api validation?","id":"identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-q03","kind":"measurement"}]}]}]}]},"agentConduct":{"may":["Deduplicate and match leads to known parties.","Score leads with an explanation.","Suggest next actions.","Prepare forecasts for review."],"mustNot":["Contact people without a lawful basis or consent.","Infer sensitive attributes.","Manipulate scores or forecasts.","Issue quotes or commit prices.","Retain lead data beyond policy."],"requiresHuman":["Committing forecasts.","Contacting high-risk or sensitive contacts.","Closing large opportunities."]},"ethics":{"considerations":["Lead data is personal data, often gathered without the person's knowledge.","Automated scoring can discriminate.","Aggressive pursuit harms vulnerable people."],"affectedParties":["Prospects and contacts","Sales staff judged by metrics","Customers"]},"owners":{"steward":"Dimension owner, namespace authority, accountable commercial owner and delegated privacy, sales, finance, legal and records authorities","roles":[{"name":"Sales pursuit owner","responsibilities":["Own purpose, scope, profile, lifecycle, accountable use and closure."]},{"name":"Party and account steward","responsibilities":["Own authoritative party, contact, customer and account bindings and correction paths."]},{"name":"Sales process steward","responsibilities":["Own qualification, stage, gate, conversion, merge, split, hold, reopen and closure profiles."]},{"name":"Revenue operations steward","responsibilities":["Own score, probability, forecast and value methods, versions, calibration and conformance evidence."]},{"name":"Commercial and offering steward","responsibilities":["Own offering fit, quote, order, contract and commercial boundary references."]},{"name":"Privacy and legal authority","responsibilities":["Own lawful basis, consent, objection, communication, profiling, access, jurisdiction and retention limits."]},{"name":"Interoperability and records steward","responsibilities":["Own mappings, projection loss, audit, legal hold and record disposition policy."]}],"masterSystems":[]},"relations":[{"target":"WM-ORG-014","type":"references","note":"Resolve the provisional customer or account relationship parent signal without granting containment or cascade mutation authority."},{"target":"Party, Contact, Organization, Customer, Account, Campaign, Product, Offering, Activity, Message, Calendar, Quote, Order, Contract, Fulfilment, Forecast, Invoice, Payment, Revenue and Records models","type":"references","note":"Resolve external identities, states, operations and evidence without duplicating their masters."},{"target":"TMF699, TMF629, TMF632, TMF648 and TMF620; UBL 2.3; Schema.org Demand and Offer; GDPR; ePrivacy Directive; FTC CAN-SPAM; W3C ORG; RFC 3339; PROV-O; DQV; ODRL; OpenAPI 3.1.1","type":"aligned","note":"Project version-pinned sales, party, customer, offer, privacy, organization, temporal, provenance, quality, policy and API views with declared loss."},{"target":"WM-ORG-014 Customer / Account Relationship","type":"neighbor","note":"The unified registry supplies only a provisional parent signal and the frozen relation ledger has no settled edge. Customer and account relationships remain external; a pursuit binds them when known."},{"target":"Lead signal, party, contact, customer and account","type":"neighbor","note":"Signals may be anonymous or inferred, parties and contacts have external identities, and customer or account status has its own authority. Conversion preserves lineage instead of collapsing these identities."},{"target":"Campaign, offering, activity, message and calendar","type":"neighbor","note":"Attribution, fit and touchpoints are typed references; their content, execution, delivery, scheduling and master lifecycle stay external."},{"target":"Quote, order, contract, fulfilment, forecast and finance","type":"neighbor","note":"Estimated value and probability support a pursuit but are not price, quotation, commitment, order, contract, delivery, recognized revenue or cash. Those masters retain independent authority."},{"target":"TM Forum, UBL, Schema.org, privacy law, ORG, RFC, PROV, DQV, ODRL and OpenAPI","type":"neighbor","note":"Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring."},{"target":"WM-ORG-014","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier for pursuit, version, assertion, qualification, activity, forecast, outcome or artifact, qualified by namespace and kind.","Governed globally resolvable pursuit or artifact IRI.","Dimension UUID or ULID when neither preceding identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A lead or opportunity names a party or contact, a source, a need, a stage and an owner.","Often confused with a customer account, a contact, a quote or a campaign response."]},"capabilities":{"applicability":"required","items":["Register sales pursuit: Governed operation to register sales pursuit without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Match and deduplicate candidates: Governed operation to match and deduplicate candidates without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Qualify lead or opportunity: Governed operation to qualify lead or opportunity without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Score with explanation: Governed operation to score with explanation without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Transition stage: Governed operation to transition stage without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Assign owner and collaborators: Governed operation to assign owner and collaborators without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Record interaction and next action: Governed operation to record interaction and next action without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Estimate value, probability and forecast: Governed operation to estimate value, probability and forecast without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Convert, close and record outcome: Governed operation to convert, close and record outcome without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction.","Correct, project, retain and audit: Governed operation to correct, project, retain and audit without autonomous contact, consent creation, party or account mutation, quotation, ordering, contracting, forecasting commitment, financial recognition, disclosure or record destruction."]},"hazards":{"applicability":"required","items":["Spam or unlawful contact.","Duplicate pursuit of the same customer.","Inflated forecasts."]},"interfaces":{"applicability":"required","items":["TM Forum Open APIs for sales and party management.","Schema.org Organization and Person.","IETF RFC 6350 vCard.","W3C Organization Ontology (ORG).","W3C PROV-O."]},"context":{"applicability":"required","items":["Marketing contact, consent, profiling, direct marketing, record retention, tendering and contracting depend on jurisdiction, channel, sector and party type.","GDPR, the ePrivacy Directive and FTC CAN-SPAM guidance are scoped profiles, not universal law, and local implementations may add obligations."]}},"sources":[{"title":"Sales Management API TMF699","url":"https://www.tmforum.org/open-digital-architecture/open-apis/sales-management-api-TMF699/v5.0.0","note":"TM Forum"},{"title":"Customer Management API TMF629","url":"https://www.tmforum.org/open-digital-architecture/open-apis/customer-management-api-TMF629/v5.0","note":"TM Forum"},{"title":"Party Management API TMF632","url":"https://www.tmforum.org/resources/standard/tmf632-party-management-api-rest-specification-r19-0-0/","note":"TM Forum"},{"title":"Quote API TMF648","url":"https://www.tmforum.org/resources/specification/tmf648-quote-api-rest-specification-r16-0-1/","note":"TM Forum"},{"title":"Product Catalog Management API TMF620","url":"https://www.tmforum.org/open-digital-architecture/open-apis/product-catalog-management-api-TMF620/v5.0","note":"TM Forum"},{"title":"Open API Directory","url":"https://www.tmforum.org/open-digital-architecture/open-apis","note":"TM Forum"},{"title":"Universal Business Language Version 2.3","url":"https://docs.oasis-open.org/ubl/UBL-2.3.html","note":"OASIS Open"},{"title":"Demand","url":"https://schema.org/Demand","note":"Schema.org Community Group"},{"title":"Offer","url":"https://schema.org/Offer","note":"Schema.org Community Group"},{"title":"General Data Protection Regulation","url":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","note":"European Union"},{"title":"Directive on privacy and electronic communications","url":"https://eur-lex.europa.eu/eli/dir/2002/58/oj","note":"European Union"},{"title":"CAN-SPAM Act Compliance Guide for Business","url":"https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business","note":"United States Federal Trade Commission"},{"title":"The Organization Ontology","url":"https://www.w3.org/TR/vocab-org/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"OpenAPI Specification 3.1.1","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"}],"openQuestions":["Canonically adjudicate the WM-ORG-014 parent signal and register pursuit relations to party, account, campaign, offering, activity, quote, order, contract, fulfilment, forecast and finance models.","Create business-to-business, consumer, public-sector, partner, marketplace, tender, subscription, fundraising, recruitment and regulated-sector pursuit profiles.","Benchmark and conformance-test organization-specific qualification, stage, scoring, probability, forecast and value methods including calibration and bias controls.","Validate channel, jurisdiction, consent, objection, profiling, competition, tender, contracting, privacy, retention and records policies.","Pin exact TMF699 and adjacent TM Forum release artefacts and validate mappings against concrete implementations.","Obtain independent external research, sales operations, privacy, legal, finance and data-governance review before promotion beyond reviewable-draft assurance.","Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.","WM-ORG-014 is only a provisional parent signal and the frozen candidate relation ledger contains no settled WM-ECO-026 edge.","Business-to-business, consumer, public-sector, partner, marketplace, tender, subscription, regulated-sector and regional pursuits need separate profiles.","Qualification frameworks, score models, calibration, probability, forecast taxonomies, fiscal periods, quotas and revenue-recognition links require organization-specific validation.","TMF699 official path and visible release labelling are inconsistent, and every TMF, UBL, Schema.org, privacy, ORG, PROV, DQV, ODRL and OpenAPI mapping needs release-pinned conformance tests."],"resources":{"spec":"/models/wm-eco-026-sales-lead-opportunity/spec.yaml","agents":"/models/wm-eco-026-sales-lead-opportunity/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-026"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-eco-026-sales-lead-opportunity/spec.yaml","ver-cy/world-models/card-supplements/wm-eco-026-sales-lead-opportunity.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T16:06:25Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}