# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T16:06:25Z", "synthesisSha256": "d3328d28208b086f34be446b5565622d4253d6dbd7fd0ecef70a3b027c0ce64e", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-026", "registryId": "vr.wm-eco-026", "name": "Sales Lead / Opportunity", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.CRM" ], "tags": [ "sales", "lead", "opportunity", "soc.eco.crm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-026-sales-lead-opportunity/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-026", "model": { "registry_id": "vr.wm-eco-026", "model_id": "WM-ECO-026", "name": "Sales Lead / Opportunity", "entry_kind": "aggregate", "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_statement": "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.", "in_scope": [ "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_of_scope": [ "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" ], "boundary_notes": [ { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-013" ] }, { "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.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-012" ] }, { "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-016" ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Sales Management API TMF699", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/sales-management-api-TMF699/v5.0.0", "version_or_date": "Official page accessed 6 September 2026; path and release label require conformance confirmation", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines interfaces for sales leads, sales opportunities, sales quotes and related sales capabilities." }, { "id": "SRC-002", "title": "Customer Management API TMF629", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/customer-management-api-TMF629/v5.0", "version_or_date": "TMF629 v5.0 directory page updated 8 May 2026", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Separates customer and account management from a sales pursuit." }, { "id": "SRC-003", "title": "Party Management API TMF632", "organization": "TM Forum", "url": "https://www.tmforum.org/resources/standard/tmf632-party-management-api-rest-specification-r19-0-0/", "version_or_date": "Approved 2019 publication", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines party identity and relationship access while party mastery remains external." }, { "id": "SRC-004", "title": "Quote API TMF648", "organization": "TM Forum", "url": "https://www.tmforum.org/resources/specification/tmf648-quote-api-rest-specification-r16-0-1/", "version_or_date": "Approved R16.0.1 publication", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines a separately governed quotation lifecycle and its relationship to sales." }, { "id": "SRC-005", "title": "Product Catalog Management API TMF620", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/product-catalog-management-api-TMF620/v5.0", "version_or_date": "TMF620 v5.0 directory page accessed 6 September 2026", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines product offering and specification catalogue boundaries used for offering fit." }, { "id": "SRC-006", "title": "Open API Directory", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis", "version_or_date": "Directory accessed 6 September 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Registers separate sales, party, customer, product, quote, order and related API families." }, { "id": "SRC-007", "title": "Universal Business Language Version 2.3", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/UBL-2.3.html", "version_or_date": "OASIS Standard 15 June 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines RequestForQuotation, Quotation, parties, items and later ordering documents, preserving pre-contract and commitment boundaries." }, { "id": "SRC-008", "title": "Demand", "organization": "Schema.org Community Group", "url": "https://schema.org/Demand", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines public demand for goods or services without defining a private CRM pursuit." }, { "id": "SRC-009", "title": "Offer", "organization": "Schema.org Community Group", "url": "https://schema.org/Offer", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines public offer, price and availability fields for loss-aware projection." }, { "id": "SRC-010", "title": "General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj", "version_or_date": "Regulation EU 2016/679, current official text accessed 6 September 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines purpose limitation, minimisation, lawful basis, data-subject rights, profiling safeguards and retention duties." }, { "id": "SRC-011", "title": "Directive on privacy and electronic communications", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2002/58/oj", "version_or_date": "Directive 2002/58/EC, official text accessed 6 September 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines jurisdiction-scoped privacy and direct-marketing constraints for electronic communications." }, { "id": "SRC-012", "title": "CAN-SPAM Act Compliance Guide for Business", "organization": "United States Federal Trade Commission", "url": "https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business", "version_or_date": "FTC guidance accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines a separate United States commercial-email compliance profile and opt-out responsibilities." }, { "id": "SRC-013", "title": "The Organization Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "W3C Recommendation 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines organizations, units, sites, posts, memberships and roles for external party and ownership references." }, { "id": "SRC-014", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339 July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC relation." }, { "id": "SRC-015", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines entities, activities, agents, attribution, derivation and revision provenance." }, { "id": "SRC-016", "title": "Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines quality dimensions, measurements, annotations and policies for score, probability and forecast evidence." }, { "id": "SRC-017", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines permissions, prohibitions, duties, constraints, assets and parties for policy projection." }, { "id": "SRC-018", "title": "OpenAPI Specification 3.1.1", "organization": "OpenAPI Initiative", "url": "https://spec.openapis.org/oas/v3.1.1.html", "version_or_date": "Version 3.1.1, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T16:02:00Z", "relevance": "Defines HTTP API operations, schemas, responses, security and reusable components." } ], "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.", "rationale": "Identify one commercial pursuit and its lineage without remastering parties, accounts, campaigns or communications", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-015" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ], "questions": [ { "id": "pursuit-id-version-profile-status-and-master-system-q01", "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?", "kind": "identity", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "pursuit-id-version-profile-status-and-master-system-q02", "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?", "kind": "ownership", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "pursuit-id-version-profile-status-and-master-system-q03", "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?", "kind": "validation", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "pursuit-id-version-profile-status-and-master-system-data", "name": "Pursuit ID, version, profile, status and master system data", "description": "Typed pursuit data for pursuit id, version, profile, status and master system, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ] } ], "artifacts": [ { "id": "pursuit-id-version-profile-status-and-master-system-record", "name": "Pursuit ID, version, profile, status and master system record", "description": "Immutable or successor-versioned pursuit evidence for pursuit id, version, profile, status and master system with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for pursuit-id-version-profile-status-and-master-system; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ], "questions": [ { "id": "lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-q01", "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?", "kind": "classification", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-q02", "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?", "kind": "authority", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-q03", "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?", "kind": "security", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-data", "name": "Lead signal, known party, qualified lead, opportunity, conversion and lineage data", "description": "Typed pursuit data for lead signal, known party, qualified lead, opportunity, conversion and lineage, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ] } ], "artifacts": [ { "id": "lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage-record", "name": "Lead signal, known party, qualified lead, opportunity, conversion and lineage record", "description": "Immutable or successor-versioned pursuit evidence for lead signal, known party, qualified lead, opportunity, conversion and lineage with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for lead-signal-known-party-qualified-lead-opportunity-conversion-and-lineage; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "source-channel-campaign-event-referral-partner-and-attribution-q01", "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?", "kind": "provenance", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "source-channel-campaign-event-referral-partner-and-attribution-q02", "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?", "kind": "requirement", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "source-channel-campaign-event-referral-partner-and-attribution-q03", "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?", "kind": "privacy", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "source-channel-campaign-event-referral-partner-and-attribution-data", "name": "Source, channel, campaign, event, referral, partner and attribution data", "description": "Typed pursuit data for source, channel, campaign, event, referral, partner and attribution, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "source-channel-campaign-event-referral-partner-and-attribution-record", "name": "Source, channel, campaign, event, referral, partner and attribution record", "description": "Immutable or successor-versioned pursuit evidence for source, channel, campaign, event, referral, partner and attribution with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for source-channel-campaign-event-referral-partner-and-attribution; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-q01", "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?", "kind": "ownership", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-q02", "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?", "kind": "constraint", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-q03", "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?", "kind": "retention", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-data", "name": "Prospect, contact, customer, account, stakeholder, owner, team and authority role data", "description": "Typed pursuit data for prospect, contact, customer, account, stakeholder, owner, team and authority role, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "prospect-contact-customer-account-stakeholder-owner-team-and-authority-role-record", "name": "Prospect, contact, customer, account, stakeholder, owner, team and authority role record", "description": "Immutable or successor-versioned pursuit evidence for prospect, contact, customer, account, stakeholder, owner, team and authority role with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for prospect-contact-customer-account-stakeholder-owner-team-and-authority-role; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "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.", "rationale": "Represent the need and tentative commercial shape without converting an estimate into an offer or commitment", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "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.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "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.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-q01", "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?", "kind": "evidence", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-q02", "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?", "kind": "process", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-q03", "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?", "kind": "access", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-data", "name": "Expressed or inferred need, problem, outcome, use case, confidence and evidence data", "description": "Typed pursuit data for expressed or inferred need, problem, outcome, use case, confidence and evidence, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence-record", "name": "Expressed or inferred need, problem, outcome, use case, confidence and evidence record", "description": "Immutable or successor-versioned pursuit evidence for expressed or inferred need, problem, outcome, use case, confidence and evidence with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for expressed-inferred-need-problem-outcome-use-case-confidence-and-evidence; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "product-service-offering-solution-catalog-specification-and-qualification-reference-q01", "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?", "kind": "relationship", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "product-service-offering-solution-catalog-specification-and-qualification-reference-q02", "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?", "kind": "event", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "product-service-offering-solution-catalog-specification-and-qualification-reference-q03", "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?", "kind": "exception", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "product-service-offering-solution-catalog-specification-and-qualification-reference-data", "name": "Product, service, offering, solution, catalog, specification and qualification reference data", "description": "Typed pursuit data for product, service, offering, solution, catalog, specification and qualification reference, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "product-service-offering-solution-catalog-specification-and-qualification-reference-record", "name": "Product, service, offering, solution, catalog, specification and qualification reference record", "description": "Immutable or successor-versioned pursuit evidence for product, service, offering, solution, catalog, specification and qualification reference with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for product-service-offering-solution-catalog-specification-and-qualification-reference; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "scope-item-quantity-location-timeline-dependency-constraint-and-assumption-q01", "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?", "kind": "constraint", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "scope-item-quantity-location-timeline-dependency-constraint-and-assumption-q02", "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?", "kind": "measurement", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "scope-item-quantity-location-timeline-dependency-constraint-and-assumption-q03", "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?", "kind": "interoperability", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "scope-item-quantity-location-timeline-dependency-constraint-and-assumption-data", "name": "Scope, item, quantity, location, timeline, dependency, constraint and assumption data", "description": "Typed pursuit data for scope, item, quantity, location, timeline, dependency, constraint and assumption, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "scope-item-quantity-location-timeline-dependency-constraint-and-assumption-record", "name": "Scope, item, quantity, location, timeline, dependency, constraint and assumption record", "description": "Immutable or successor-versioned pursuit evidence for scope, item, quantity, location, timeline, dependency, constraint and assumption with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for scope-item-quantity-location-timeline-dependency-constraint-and-assumption; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "estimated-value-budget-amount-currency-recurrence-range-and-basis-q01", "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?", "kind": "measurement", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "estimated-value-budget-amount-currency-recurrence-range-and-basis-q02", "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?", "kind": "evidence", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "estimated-value-budget-amount-currency-recurrence-range-and-basis-q03", "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?", "kind": "decision", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "estimated-value-budget-amount-currency-recurrence-range-and-basis-data", "name": "Estimated value, budget, amount, currency, recurrence, range and basis data", "description": "Typed pursuit data for estimated value, budget, amount, currency, recurrence, range and basis, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "estimated-value-budget-amount-currency-recurrence-range-and-basis-record", "name": "Estimated value, budget, amount, currency, recurrence, range and basis record", "description": "Immutable or successor-versioned pursuit evidence for estimated value, budget, amount, currency, recurrence, range and basis with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for estimated-value-budget-amount-currency-recurrence-range-and-basis; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "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.", "rationale": "Keep each evaluative assertion source, method, version and time qualified rather than treating it as fact", "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ], "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.", "source_refs": [ "SRC-001", "SRC-016" ], "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.", "source_refs": [ "SRC-001", "SRC-016" ], "questions": [ { "id": "fit-intent-authority-budget-timing-need-risk-and-qualification-q01", "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?", "kind": "decision", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "fit-intent-authority-budget-timing-need-risk-and-qualification-q02", "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?", "kind": "quality", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "fit-intent-authority-budget-timing-need-risk-and-qualification-q03", "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?", "kind": "identity", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "fit-intent-authority-budget-timing-need-risk-and-qualification-data", "name": "Fit, intent, authority, budget, timing, need, risk and qualification data", "description": "Typed pursuit data for fit, intent, authority, budget, timing, need, risk and qualification, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-016" ] } ], "artifacts": [ { "id": "fit-intent-authority-budget-timing-need-risk-and-qualification-record", "name": "Fit, intent, authority, budget, timing, need, risk and qualification record", "description": "Immutable or successor-versioned pursuit evidence for fit, intent, authority, budget, timing, need, risk and qualification with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for fit-intent-authority-budget-timing-need-risk-and-qualification; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-016" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-016" ], "questions": [ { "id": "score-model-method-version-feature-evidence-explanation-confidence-and-bias-q01", "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?", "kind": "quality", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "score-model-method-version-feature-evidence-explanation-confidence-and-bias-q02", "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?", "kind": "validation", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "score-model-method-version-feature-evidence-explanation-confidence-and-bias-q03", "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?", "kind": "classification", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "score-model-method-version-feature-evidence-explanation-confidence-and-bias-data", "name": "Score, model, method, version, feature, evidence, explanation, confidence and bias data", "description": "Typed pursuit data for score, model, method, version, feature, evidence, explanation, confidence and bias, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-016" ] } ], "artifacts": [ { "id": "score-model-method-version-feature-evidence-explanation-confidence-and-bias-record", "name": "Score, model, method, version, feature, evidence, explanation, confidence and bias record", "description": "Immutable or successor-versioned pursuit evidence for score, model, method, version, feature, evidence, explanation, confidence and bias with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for score-model-method-version-feature-evidence-explanation-confidence-and-bias; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ], "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.", "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ], "questions": [ { "id": "stage-status-gate-criterion-entry-exit-hold-and-exception-q01", "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?", "kind": "state", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "stage-status-gate-criterion-entry-exit-hold-and-exception-q02", "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?", "kind": "security", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "stage-status-gate-criterion-entry-exit-hold-and-exception-q03", "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?", "kind": "composition", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "stage-status-gate-criterion-entry-exit-hold-and-exception-data", "name": "Stage, status, gate criterion, entry, exit, hold and exception data", "description": "Typed pursuit data for stage, status, gate criterion, entry, exit, hold and exception, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ] } ], "artifacts": [ { "id": "stage-status-gate-criterion-entry-exit-hold-and-exception-record", "name": "Stage, status, gate criterion, entry, exit, hold and exception record", "description": "Immutable or successor-versioned pursuit evidence for stage, status, gate criterion, entry, exit, hold and exception with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for stage-status-gate-criterion-entry-exit-hold-and-exception; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ], "questions": [ { "id": "probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-q01", "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?", "kind": "temporal", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-q02", "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?", "kind": "privacy", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-q03", "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?", "kind": "relationship", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-data", "name": "Probability, confidence, basis, calibration, forecast category, expected close and as-of data", "description": "Typed pursuit data for probability, confidence, basis, calibration, forecast category, expected close and as-of, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ] } ], "artifacts": [ { "id": "probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of-record", "name": "Probability, confidence, basis, calibration, forecast category, expected close and as-of record", "description": "Immutable or successor-versioned pursuit evidence for probability, confidence, basis, calibration, forecast category, expected close and as-of with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for probability-confidence-basis-calibration-forecast-category-expected-close-and-as-of; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "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.", "rationale": "Bind decision roles, permissions and touchpoints while keeping party, message, activity and calendar masters external", "source_refs": [ "SRC-001", "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017" ], "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.", "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "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.", "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "questions": [ { "id": "stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-q01", "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?", "kind": "relationship", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-q02", "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?", "kind": "retention", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-q03", "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?", "kind": "state", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-data", "name": "Stakeholder role, influence, decision group, sponsor, champion, blocker and interest data", "description": "Typed pursuit data for stakeholder role, influence, decision group, sponsor, champion, blocker and interest, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "artifacts": [ { "id": "stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest-record", "name": "Stakeholder role, influence, decision group, sponsor, champion, blocker and interest record", "description": "Immutable or successor-versioned pursuit evidence for stakeholder role, influence, decision group, sponsor, champion, blocker and interest with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for stakeholder-role-influence-decision-group-sponsor-champion-blocker-and-interest; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "questions": [ { "id": "contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-q01", "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?", "kind": "privacy", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-q02", "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?", "kind": "access", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-q03", "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?", "kind": "lifecycle", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-data", "name": "Contact point, consent, lawful basis, preference, objection, channel and constraint data", "description": "Typed pursuit data for contact point, consent, lawful basis, preference, objection, channel and constraint, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "artifacts": [ { "id": "contact-point-consent-lawful-basis-preference-objection-channel-and-constraint-record", "name": "Contact point, consent, lawful basis, preference, objection, channel and constraint record", "description": "Immutable or successor-versioned pursuit evidence for contact point, consent, lawful basis, preference, objection, channel and constraint with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for contact-point-consent-lawful-basis-preference-objection-channel-and-constraint; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-003", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "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.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "interaction-meeting-call-message-content-demo-event-task-and-response-reference-q01", "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?", "kind": "event", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "interaction-meeting-call-message-content-demo-event-task-and-response-reference-q02", "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?", "kind": "exception", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "interaction-meeting-call-message-content-demo-event-task-and-response-reference-q03", "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?", "kind": "temporal", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "interaction-meeting-call-message-content-demo-event-task-and-response-reference-data", "name": "Interaction, meeting, call, message, content, demo, event, task and response reference data", "description": "Typed pursuit data for interaction, meeting, call, message, content, demo, event, task and response reference, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "interaction-meeting-call-message-content-demo-event-task-and-response-reference-record", "name": "Interaction, meeting, call, message, content, demo, event, task and response reference record", "description": "Immutable or successor-versioned pursuit evidence for interaction, meeting, call, message, content, demo, event, task and response reference with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for interaction-meeting-call-message-content-demo-event-task-and-response-reference; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "next-action-owner-due-date-dependency-commitment-escalation-and-result-q01", "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?", "kind": "process", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "next-action-owner-due-date-dependency-commitment-escalation-and-result-q02", "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?", "kind": "interoperability", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "next-action-owner-due-date-dependency-commitment-escalation-and-result-q03", "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?", "kind": "spatial", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "next-action-owner-due-date-dependency-commitment-escalation-and-result-data", "name": "Next action, owner, due date, dependency, commitment, escalation and result data", "description": "Typed pursuit data for next action, owner, due date, dependency, commitment, escalation and result, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "next-action-owner-due-date-dependency-commitment-escalation-and-result-record", "name": "Next action, owner, due date, dependency, commitment, escalation and result record", "description": "Immutable or successor-versioned pursuit evidence for next action, owner, due date, dependency, commitment, escalation and result with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for next-action-owner-due-date-dependency-commitment-escalation-and-result; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "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.", "rationale": "Preserve conversion and closure evidence while quote, order and contract masters retain their own authority", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-015", "SRC-016" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ], "questions": [ { "id": "capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-q01", "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?", "kind": "lifecycle", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-q02", "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?", "kind": "decision", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-q03", "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?", "kind": "provenance", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-data", "name": "Capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify data", "description": "Typed pursuit data for capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify-record", "name": "Capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify record", "description": "Immutable or successor-versioned pursuit evidence for capture, deduplicate, link, merge, split, qualify, convert, nurture and disqualify with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for capture-deduplicate-link-merge-split-qualify-convert-nurture-and-disqualify; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ], "questions": [ { "id": "open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-q01", "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?", "kind": "state", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-q02", "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?", "kind": "identity", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-q03", "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?", "kind": "ownership", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-data", "name": "Open, progress, hold, reopen, win, loss, no decision, abandon and archive data", "description": "Typed pursuit data for open, progress, hold, reopen, win, loss, no decision, abandon and archive, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive-record", "name": "Open, progress, hold, reopen, win, loss, no decision, abandon and archive record", "description": "Immutable or successor-versioned pursuit evidence for open, progress, hold, reopen, win, loss, no decision, abandon and archive with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for open-progress-hold-reopen-win-loss-no-decision-abandon-and-archive; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ], "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ], "questions": [ { "id": "quote-proposal-tender-negotiation-order-contract-and-commitment-reference-q01", "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?", "kind": "interoperability", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "quote-proposal-tender-negotiation-order-contract-and-commitment-reference-q02", "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?", "kind": "classification", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "quote-proposal-tender-negotiation-order-contract-and-commitment-reference-q03", "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?", "kind": "authority", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "quote-proposal-tender-negotiation-order-contract-and-commitment-reference-data", "name": "Quote, proposal, tender, negotiation, order, contract and commitment reference data", "description": "Typed pursuit data for quote, proposal, tender, negotiation, order, contract and commitment reference, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "quote-proposal-tender-negotiation-order-contract-and-commitment-reference-record", "name": "Quote, proposal, tender, negotiation, order, contract and commitment reference record", "description": "Immutable or successor-versioned pursuit evidence for quote, proposal, tender, negotiation, order, contract and commitment reference with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for quote-proposal-tender-negotiation-order-contract-and-commitment-reference; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ], "questions": [ { "id": "outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-q01", "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?", "kind": "evidence", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-q02", "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?", "kind": "composition", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-q03", "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?", "kind": "requirement", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-data", "name": "Outcome, reason, competitor, alternative, value, decision evidence and retrospective data", "description": "Typed pursuit data for outcome, reason, competitor, alternative, value, decision evidence and retrospective, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective-record", "name": "Outcome, reason, competitor, alternative, value, decision evidence and retrospective record", "description": "Immutable or successor-versioned pursuit evidence for outcome, reason, competitor, alternative, value, decision evidence and retrospective with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for outcome-reason-competitor-alternative-value-decision-evidence-and-retrospective; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "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.", "rationale": "Qualify authority, clocks, privacy, quality, correction and projection loss", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "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.", "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ], "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.", "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ], "questions": [ { "id": "owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-q01", "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?", "kind": "provenance", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-q02", "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?", "kind": "relationship", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-q03", "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?", "kind": "constraint", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-data", "name": "Owner, steward, source, actor, activity, derivation, revision, conflict and audit data", "description": "Typed pursuit data for owner, steward, source, actor, activity, derivation, revision, conflict and audit, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ] } ], "artifacts": [ { "id": "owner-steward-source-actor-activity-derivation-revision-conflict-and-audit-record", "name": "Owner, steward, source, actor, activity, derivation, revision, conflict and audit record", "description": "Immutable or successor-versioned pursuit evidence for owner, steward, source, actor, activity, derivation, revision, conflict and audit with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for owner-steward-source-actor-activity-derivation-revision-conflict-and-audit; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ], "questions": [ { "id": "purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-q01", "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?", "kind": "access", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-q02", "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?", "kind": "state", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-q03", "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?", "kind": "process", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-data", "name": "Purpose, lawful basis, consent, objection, access, minimization, retention and tombstone data", "description": "Typed pursuit data for purpose, lawful basis, consent, objection, access, minimization, retention and tombstone, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ] } ], "artifacts": [ { "id": "purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone-record", "name": "Purpose, lawful basis, consent, objection, access, minimization, retention and tombstone record", "description": "Immutable or successor-versioned pursuit evidence for purpose, lawful basis, consent, objection, access, minimization, retention and tombstone with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for purpose-lawful-basis-consent-objection-access-minimization-retention-and-tombstone; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-015", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-q01", "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?", "kind": "temporal", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-q02", "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?", "kind": "lifecycle", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-q03", "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?", "kind": "event", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-data", "name": "Source, capture, consent, qualification, stage, contact, forecast, close, observed and known time data", "description": "Typed pursuit data for source, capture, consent, qualification, stage, contact, forecast, close, observed and known time, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time-record", "name": "Source, capture, consent, qualification, stage, contact, forecast, close, observed and known time record", "description": "Immutable or successor-versioned pursuit evidence for source, capture, consent, qualification, stage, contact, forecast, close, observed and known time with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for source-capture-consent-qualification-stage-contact-forecast-close-observed-and-known-time; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-q01", "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?", "kind": "validation", "answer_data": [ "pursuit, version and external master identifiers", "lead-signal, qualified-lead or opportunity profile and schema version", "asserted, inferred, observed, unknown, disputed and superseded states" ] }, { "id": "identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-q02", "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?", "kind": "temporal", "answer_data": [ "actor, owner, team, stakeholder, source system and affected party", "purpose, lawful basis, consent, preference, policy, role and delegation", "confidence, bias, objection, exception, segregation of duties and accountability" ] }, { "id": "identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-q03", "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?", "kind": "measurement", "answer_data": [ "source, method, model or rule version and evidence", "event, observation, ingestion, effective, forecast and knowledge times", "confidence, calibration, uncertainty, predecessor, successor, access, retention and projection loss" ] } ], "data_elements": [ { "id": "identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-data", "name": "Identity, state, value, TMF, UBL, Schema.org, privacy, ORG, RFC, PROV, DQV, ODRL and API validation data", "description": "Typed pursuit data for identity, state, value, tmf, ubl, schema.org, privacy, org, rfc, prov, dqv, odrl and api validation, qualified by source, method, version, scope, authority, time, confidence, access and conflict.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation-record", "name": "Identity, state, value, TMF, UBL, Schema.org, privacy, ORG, RFC, PROV, DQV, ODRL and API validation record", "description": "Immutable or successor-versioned pursuit evidence for identity, state, value, tmf, ubl, schema.org, privacy, org, rfc, prov, dqv, odrl and api validation with declared profile and projection loss.", "media_or_form": [ "logical sales-pursuit specification assertion", "identity, need, qualification, score, stage, stakeholder, activity, forecast, outcome, validation or projection record" ], "serial": true, "identity_strategy": "Pursuit ID plus independent version, assertion, activity, decision or event ID and artifact kind for identity-state-value-tmf-ubl-schemaorg-privacy-org-rfc-prov-dqv-odrl-and-api-validation; party, email, account name, date, amount, filename or digest never identifies the pursuit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-sales-pursuit", "name": "Register sales pursuit", "description": "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.", "inputs": [ "source signal or request", "party or account hints", "purpose and authority" ], "outputs": [ "versioned pursuit assertion" ], "preconditions": [ "identity, duplicate, lawful-purpose, source and authority checks pass" ], "effects": [ "does not create a party, customer, account, consent, quote, order or contract" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010" ] }, { "id": "match-and-deduplicate-candidates", "name": "Match and deduplicate candidates", "description": "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.", "inputs": [ "candidate pursuits", "party, account, need and source evidence" ], "outputs": [ "match assertions and merge or link proposal" ], "preconditions": [ "method, threshold, explanation, confidence and human-review policy pass" ], "effects": [ "preserves candidates until an authorized merge or link decision" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-015", "SRC-016" ] }, { "id": "qualify-lead-or-opportunity", "name": "Qualify lead or opportunity", "description": "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.", "inputs": [ "pursuit revision", "qualification profile", "need, fit and stakeholder evidence" ], "outputs": [ "versioned qualification assertion" ], "preconditions": [ "criterion, evidence, authority, time and unknown handling pass" ], "effects": [ "qualification does not create consent, customer status, quote, order or commitment" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-016" ] }, { "id": "score-with-explanation", "name": "Score with explanation", "description": "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.", "inputs": [ "pursuit features", "score model and version" ], "outputs": [ "source-qualified score assertion and explanation" ], "preconditions": [ "purpose, permitted features, calibration, bias and access controls pass" ], "effects": [ "score remains contestable and never becomes fact or sole adverse-action authority" ], "source_refs": [ "SRC-010", "SRC-016" ] }, { "id": "transition-stage", "name": "Transition stage", "description": "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.", "inputs": [ "pursuit revision", "stage profile", "gate evidence" ], "outputs": [ "successor stage assertion" ], "preconditions": [ "entry, exit, exception, authority, event time and knowledge time pass" ], "effects": [ "does not silently rewrite qualification, score, probability, forecast or outcome" ], "source_refs": [ "SRC-001", "SRC-015", "SRC-016" ] }, { "id": "assign-owner-and-collaborators", "name": "Assign owner and collaborators", "description": "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.", "inputs": [ "pursuit", "role and organization references", "delegation" ], "outputs": [ "versioned ownership and collaboration assertions" ], "preconditions": [ "role, scope, authority, segregation and access pass" ], "effects": [ "does not alter external organization, post or membership masters" ], "source_refs": [ "SRC-003", "SRC-013", "SRC-017" ] }, { "id": "record-interaction-and-next-action", "name": "Record interaction and next action", "description": "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.", "inputs": [ "pursuit", "external activity evidence", "preference and authority" ], "outputs": [ "interaction reference and governed follow-up assertion" ], "preconditions": [ "purpose, channel, consent or lawful basis, objection, due time and owner pass" ], "effects": [ "does not autonomously contact a person, send a message or create consent" ], "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-014" ] }, { "id": "estimate-value-probability-and-forecast", "name": "Estimate value, probability and forecast", "description": "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.", "inputs": [ "pursuit scope and amount basis", "method, model and evidence" ], "outputs": [ "as-of value, probability and forecast assertions" ], "preconditions": [ "currency, range, recurrence, method, calibration, authority and time pass" ], "effects": [ "estimate is not a price, quote, order, contract, revenue recognition or cash" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-016" ] }, { "id": "convert-close-and-record-outcome", "name": "Convert, close and record outcome", "description": "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.", "inputs": [ "pursuit revision", "conversion or closure evidence", "authorized decision" ], "outputs": [ "successor lineage, closure and outcome assertions" ], "preconditions": [ "identity, reason, external references, authority, event time and correction path pass" ], "effects": [ "does not issue a quote, order, contract or financial record or close external disputes" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-015" ] }, { "id": "correct-project-retain-and-audit", "name": "Correct, project, retain and audit", "description": "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.", "inputs": [ "pursuit revision", "purpose-bound access", "target profile", "records policy" ], "outputs": [ "successor correction, filtered view, loss-declaring projection, retention result or audit event" ], "preconditions": [ "purpose, authority, privacy, mapping, digest, legal hold and lifecycle checks pass" ], "effects": [ "projection never replaces the canonical pursuit and deletion never cascades to external masters" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "composition": [ { "target": "WM-ORG-014", "relation": "REFERENCE", "purpose": "Resolve the provisional customer or account relationship parent signal without granting containment or cascade mutation authority.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "target": "Party, Contact, Organization, Customer, Account, Campaign, Product, Offering, Activity, Message, Calendar, Quote, Order, Contract, Fulfilment, Forecast, Invoice, Payment, Revenue and Records models", "relation": "REFERENCE", "purpose": "Resolve external identities, states, operations and evidence without duplicating their masters.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-013", "SRC-015" ] }, { "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", "relation": "ALIGN", "purpose": "Project version-pinned sales, party, customer, offer, privacy, organization, temporal, provenance, quality, policy and API views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, accountable commercial owner and delegated privacy, sales, finance, legal and records authorities", "Authoritative Party, Organization, Customer, Account, Campaign, Offering, Activity, Communication, Quote, Order, Contract, Fulfilment, Finance and Records registries", "Approved lead, opportunity, sales-process, qualification, score, probability, forecast, jurisdiction, privacy, retention and interoperability profiles", "Role, delegation, contact, consent, objection, stage, conversion, closure, disclosure and agent-operation policies" ], "namespace_guidance": "Mint pursuit, version, assertion, qualification, stage, activity-reference, forecast, outcome, validation and projection IDs; preserve external master identifiers.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative pursuit identifier, owner namespace and version head, never by party, email, account name, campaign, date, value, filename or digest alone.", "Keep lead signal, party, customer, account, campaign, offering, activity, message, quote, order, contract, fulfilment, forecast and financial result independently identifiable." ], "patch_rules": [ "Extensions declare profile, identity, origin, need, parties, qualification, score, stage, probability, forecast, privacy, lifecycle and interoperability effects.", "Issued versions are immutable; conversions, merges, splits, corrections, stage changes, holds, reopenings and closures create linked successors with reason and authority.", "Never silently change party binding, consent, need, value, currency, score method, probability basis, stage, expected close, outcome, authority or privacy marking." ], "compatibility_rules": [ "Ignore additive fields only when identity, version, need, parties, assertions, methods, states, times, authority, access and provenance survive.", "Every projection pins specification version and declares loss in lifecycle, qualification, stage, score, probability, value, authority, privacy and evidence semantics." ] }, "artifact_rules": { "identity_priority": [ "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." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish source, capture, consent, qualification, score, stage, contact, forecast, expected-close, actual-close, observed, ingested and known times whenever they differ.", "serial_naming_rule": "Use {pursuit-id}--{version-id}--{assertion-activity-decision-or-event-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, pursuit and version IDs, profile, actor, purpose, source and method versions, event and knowledge times, confidentiality, retention and provenance." }, "policies": [ "The pursuit owns commercial evaluation and coordination context but not party, customer, account, campaign, catalog, activity, message, quote, order, contract, fulfilment, finance or records masters.", "Lead signal, known party, qualified lead, customer or account and opportunity remain distinct classifications; conversion records lineage rather than identity collapse.", "Qualification, score, stage, probability, forecast and actual outcome are separate source-qualified axes and cannot prove one another.", "Agents cannot autonomously contact people, create consent, infer sensitive attributes, manipulate scores, commit forecasts, issue quotes or orders, execute contracts, disclose or destroy records without delegated authority." ], "crud": { "read": [ "Resolve pursuit head, classification, lineage, origin, need, parties, fit, value, qualification, score, stage, probability, forecast, stakeholders, activities, outcome, access and projection loss." ], "create": [ "Bind identity, source, purpose, owner, profile, need, external parties and offerings, lawful processing basis and initial unknown states before assertions are accepted." ], "update": [ "Append successor qualification, score, stage, probability, forecast, activity, value, ownership, conversion, closure and correction assertions with source, method, reason, authority, event time and knowledge time." ], "delete": [ "Apply legal hold, contract, marketing, privacy, tax and Dimension retention policy; tombstone only the catalogue view, preserve required lineage, and never cascade deletion to external party, communication, quote, order, contract or financial masters." ] }, "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." ] } ], "access": { "default_rule": "Deny personal contact data, private communications, needs, budgets, scores, probabilities, stakeholder influence, competitor data, pricing, forecasts and outcomes unless purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared operational, legal, audit, regulatory, subject-rights or incident access must cite authority, scope, purpose and time limit and be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, pursuit and version, operation, authority, policy, RFC 3339 time, affected assertions, source revision and outcome without duplicating restricted party data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension namespace, sales, party, privacy, communication, commercial, forecast, retention and agent policies.", "Read this pursuit and linked party, account, campaign, offering, activity, quote, order, contract, finance and records models before mutation." ] } }, "coverage": { "claim": "WM-ECO-026 covers one governed sales pursuit from lead signal and need through qualification, fit, value, stage, stakeholders, activities, probability, forecast, conversion, closure, outcome, governance and loss-aware projections. Relation, organization-specific methodology, jurisdiction, conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "ownership", "status": "covered", "notes": "Ownership is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "validation", "status": "covered", "notes": "Validation is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "access", "status": "covered", "notes": "Access is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; organization, methodology, jurisdiction, legal-effect, relation and external-review profiles remain held where applicable." } ], "known_omissions": [ "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." ], "conflicts": [ "Lead signal, known party, qualified lead, customer or account and opportunity are related but not interchangeable.", "Qualification, score, stage, probability, forecast category, expected close and actual outcome belong to separate assertion axes.", "Estimated value, budget, list price, quote, order, contract, recognized revenue and cash are related but not equivalent.", "Purpose, lawful basis, consent, preference and channel permission may differ and must coexist with jurisdiction and objection evidence." ], "regional_assumptions": [ "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." ], "adversarial_checks": [ "Reject a pursuit that absorbs party, customer, account, campaign, catalog, activity, message, quote, order, contract, fulfilment or finance masters.", "Reject conversion that collapses a signal, party, lead, account and opportunity into one identity.", "Reject qualification, score, probability or forecast without source, method, version, evidence, as-of time, confidence, calibration and contestability.", "Reject value without amount type, currency, range, recurrence, basis and explicit non-equivalence to price or commitment.", "Reject autonomous contact, consent creation, sensitive-attribute inference, adverse action, forecast commitment, quote, order, contract, disclosure or destruction without authority.", "Reject a projection that hides stage, scoring, probability, value, privacy, authority, provenance or information loss." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "The root is a versioned commercial-pursuit aggregate spanning a lead signal to an explicitly qualified opportunity. Party, customer, account, campaign, product, offering, activity, communication, quote, order, contract, fulfilment, forecast, finance and records masters remain external." }, "decisions": [ { "concept": "Sales-pursuit aggregate root", "disposition": "accepted-with-explicit-boundary", "rationale": "One pursuit can bind signal, need, qualification, fit, stage, stakeholders, value, forecast and outcome evidence without absorbing adjacent identity, communication, commercial or financial masters." }, { "concept": "WM-ORG-014 parent signal", "disposition": "accepted-as-provisional-reference", "rationale": "The unified registry supplies a parent hint but the frozen relation ledger has no settled WM-ECO-026 edge. It grants no containment or cascade authority." }, { "concept": "Signal, party, lead, customer, account and opportunity", "disposition": "accepted-as-separate-identities-and-classifications", "rationale": "A signal may be anonymous, a party is not a qualified lead, and neither a lead nor opportunity proves customer or account status. Conversion records lineage." }, { "concept": "Need and offering fit", "disposition": "accepted-as-source-qualified-assertions", "rationale": "Expressed and inferred needs remain distinguishable and contestable, while offerings and specifications remain external versioned catalogue records." }, { "concept": "Qualification, score, stage, probability and forecast", "disposition": "accepted-as-distinct-assertion-axes", "rationale": "Each axis carries its own method, version, evidence, authority, confidence and as-of time. None is promoted to objective fact or allowed to prove another." }, { "concept": "Estimated value and commercial commitment", "disposition": "accepted-with-commercial-and-financial-boundary", "rationale": "Budget and estimated value are typed estimates and never substitute for price, quote, order, contract, recognized revenue or cash." }, { "concept": "Stakeholders, interactions and next actions", "disposition": "accepted-with-external-master-and-contact-controls", "rationale": "The pursuit binds roles and external activity references. It cannot autonomously contact a person, create consent, send a message or mutate calendar and communication masters." }, { "concept": "Privacy, direct marketing and profiling", "disposition": "accepted-with-jurisdiction-and-purpose-holds", "rationale": "GDPR, ePrivacy and FTC guidance are scoped profiles. Purpose, lawful basis, consent, preference, objection and channel permission remain separate and no sensitive-attribute inference is permitted." }, { "concept": "Conversion, merge, split and closure", "disposition": "accepted-as-successor-lineage", "rationale": "Lifecycle changes preserve prior identities, source evidence, reasons, authority and clocks rather than overwriting history or cascading into adjacent masters." }, { "concept": "Interoperability projections", "disposition": "accepted-with-loss-declaration", "rationale": "TM Forum, UBL, Schema.org, privacy, ORG, RFC, PROV, DQV, ODRL and OpenAPI cover different facets and never replace the canonical pursuit aggregate." }, { "concept": "TMF699 release identification", "disposition": "accepted-with-publication-hold", "rationale": "The official URL path and visible release labelling are inconsistent; the mapping stays provisional until a release-specific artefact and conformance suite are pinned." }, { "concept": "Single-provider waiver and local no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audited the frozen validated result and comparison without new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-ECO-026 each timed out after 120 seconds; no external result was admitted.", "Relation hold: WM-ORG-014 is only a provisional parent signal and the frozen relation ledger contains no settled WM-ECO-026 edge.", "Identity hold: lead signal, known party, qualified lead, customer or account and opportunity remain distinct and conversion preserves lineage.", "Methodology hold: qualification dimensions, stages, scores, probabilities and forecast categories require organization-specific definitions, versioning, calibration and review.", "Bias and profiling hold: score and propensity features require purpose, lawful basis, minimization, fairness, explanation, contestability and prohibited-attribute controls.", "Commercial boundary hold: estimated value, budget, offer, list price, quote, order, contract, forecast, recognized revenue and cash remain distinct.", "Communication hold: purpose, lawful basis, consent, preference, objection and channel permission remain separate; agents cannot autonomously contact or create consent.", "Jurisdiction hold: GDPR, ePrivacy and FTC CAN-SPAM are scoped profiles; national, sector, consumer, employment, competition, tender and records rules need validation.", "TMF699 source hold: the official URL path and visible release labelling are inconsistent, so the mapping requires release-specific confirmation.", "State-axis hold: qualification, score, stage, probability, forecast category, expected close, actual close and outcome states and clocks must not collapse.", "Authority hold: merge, conversion, stage change, contact, quote, order, contract, forecast commitment, disclosure and destruction require delegated authority.", "Interoperability hold: every TMF, UBL, Schema.org, privacy, ORG, RFC, PROV, DQV, ODRL and OpenAPI projection needs release pins, conformance evidence and loss declarations.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 18, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }