# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T05:24:22Z", "synthesisSha256": "820c651e6cbd9645a1d21391ab8188be0f69a54aa089bf2eb619571eacf97424", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-028", "registryId": "vr.wm-act-028", "name": "Campaign", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.CAM" ], "tags": [ "campaign", "act.cam" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-028-campaign/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-028", "model": { "registry_id": "vr.wm-act-028", "model_id": "WM-ACT-028", "name": "Campaign", "entry_kind": "aggregate", "purpose": "Represent a governed, coordinated set of activities directed at defined audiences, subjects or environments to produce intended outcomes over a bounded period without absorbing the masters it coordinates.", "scope_statement": "Owns campaign identity and lineage, mandate and problem context, campaign strategy and logic model, objectives, audience and segment definitions, phases and waves, campaign-scoped assignments and variants, message and channel intent, lifecycle, metric definitions and campaign aggregation views, attribution and evaluation assertions, projections, access and retention. Party, project, program, initiative, activity, content, channel, budget, contract, order, payment, event, incident, observation, dataset, policy and generic audit masters remain external.", "in_scope": [ "Campaign identity, class, mandate, owner, problem baseline, scope, objectives, outcome logic, audiences, segments, safeguards and exclusions", "Phases, waves, activities, experiments, messages, offers, assets, channels, schedules, roles, assignments, budgets and resource references, risks and controls", "Authorization, release, launch, pause, resume, change, termination, observations, metrics, evaluation, attribution, learning, interoperability, access, retention and agent operations" ], "out_of_scope": [ "Party, project, program, initiative, activity, content, channel, account, budget, contract, order, payment, event, incident, observation, dataset, policy or audit-log master lifecycle", "Inferring individual audience membership, delivery, exposure, engagement, conversion, behavior change, impact or causation without a source-qualified assertion and method", "Implementing advertising exchanges, social networks, campaign schedulers, content management, payments, analytics engines or universal legal compliance and claiming lossless cross-platform equivalence" ], "boundary_notes": [ { "neighbor": "Project / Program / Initiative / Operation", "distinction": "A campaign may be governed as a project or participate in a program, but this root owns audience or target-directed strategy, waves, messages and campaign measurement, not generic delivery governance.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "neighbor": "Audience / Party / Segment", "distinction": "The campaign owns versioned target definitions and eligibility rules; external person, organization, group and membership assertions keep their identity, authority and lifecycle.", "source_refs": [ "SRC-002", "SRC-009", "SRC-010" ] }, { "neighbor": "Activity / Message / Content / Channel", "distinction": "Campaign-scoped assignments and release bindings are owned here, while executable activities, messages, assets, channels, placements and accounts remain external masters.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009", "SRC-011", "SRC-012" ] }, { "neighbor": "Observation / Metric / Evaluation / Decision", "distinction": "The campaign defines metric use and aggregation and records campaign-specific evaluation; source observations, datasets and external decisions keep independent provenance.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "neighbor": "Threat Campaign / Advertising Campaign", "distinction": "STIX and Google Ads are sector or platform projections. Neither narrows the vendor-neutral root to malicious activity or paid advertising.", "source_refs": [ "SRC-001", "SRC-012" ] } ] }, "sources": [ { "id": "SRC-001", "title": "STIX Version 2.1", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/cti/stix/v2.1/os/stix-v2.1-os.html", "version_or_date": "OASIS Standard, 10 June 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines a campaign as a time-bounded grouping of activities or waves with objectives, targets, resources, identity, observed times, confidence, markings and typed relationships." }, { "id": "SRC-002", "title": "Activity Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/activitystreams-vocabulary/", "version_or_date": "W3C Recommendation, 23 May 2017", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines activities, actors, objects, targets, results, instruments, audience, context, collections and lifecycle verbs for campaign activity exchange." }, { "id": "SRC-003", "title": "Activity Streams 2.0", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/activitystreams-core/", "version_or_date": "W3C Recommendation, 23 May 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines JSON-LD serialization and collection and activity processing for interoperable campaign projections." }, { "id": "SRC-004", "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-06T05:18:00Z", "relevance": "Defines entity, activity, agent, responsibility, generation, derivation, revision and attribution provenance." }, { "id": "SRC-005", "title": "The RDF Data Cube Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-data-cube/", "version_or_date": "W3C Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines observations, measures, dimensions, attributes, slices, datasets and data-structure definitions for metric observations." }, { "id": "SRC-006", "title": "ISO 21502:2020 Project, programme and portfolio management - Guidance on project management", "organization": "International Organization for Standardization", "url": "https://committee.iso.org/sites/tc258/home/projects/published/iso-21502.html", "version_or_date": "ISO 21502:2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Provides the project-management boundary and practices used to distinguish a campaign coordination aggregate from a project master." }, { "id": "SRC-007", "title": "Evaluate complex campaigns", "organization": "World Health Organization", "url": "https://www.who.int/about/communications/evaluation/campaigns-evaluation", "version_or_date": "WHO communication guidance, accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines campaign logic models across inputs, activities, outputs, outcomes and impacts and warns that impact attribution is difficult." }, { "id": "SRC-008", "title": "Applying communication for health: planning guide", "organization": "World Health Organization", "url": "https://www.who.int/publications/i/item/9789290621041", "version_or_date": "ISBN 978-92-9062-104-1, 6 March 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines a six-step communication-intervention cycle: understand, plan, develop, test, implement, evaluate and learn." }, { "id": "SRC-009", "title": "Module 1: Communication Planning", "organization": "Centers for Disease Control and Prevention", "url": "https://www.cdc.gov/healthy-youth/communication-toolkit/communication-planning.html", "version_or_date": "CDC communication toolkit, reviewed 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Identifies goals, audience, messages, methods or tactics, timeline, responsibility, budget and evaluation as communication-plan elements." }, { "id": "SRC-010", "title": "Audience", "organization": "Schema.org Community Group", "url": "https://schema.org/Audience", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines intended audience, audience type and geographic area for cross-sector discovery projections." }, { "id": "SRC-011", "title": "Action", "organization": "Schema.org Community Group", "url": "https://schema.org/Action", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines action status, agent, object, participant, instrument, target, result, place and start and end times." }, { "id": "SRC-012", "title": "Google Ads API Campaign resource", "organization": "Google", "url": "https://developers.google.com/google-ads/api/reference/rpc/v23/Campaign", "version_or_date": "Google Ads API v23, 2026", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Provides one explicitly platform-scoped campaign projection covering status, channel type, audience settings, budgets, bidding, experiments and serving state." }, { "id": "SRC-013", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T05:18:00Z", "relevance": "Defines seconds and explicit-offset timestamps for campaign events, observations and knowledge time." } ], "structure": { "bundles": [ { "id": "identity-mandate-boundary-and-context", "name": "Identity, mandate, boundary and context", "description": "Defines the campaign root, mandate and problem context.", "rationale": "Campaign identity and authority remain distinct from a project, program, initiative, operation, activity, message or channel account.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007" ], "layers": [ { "id": "campaign-definition-identity-and-classification", "name": "Campaign definition, identity and classification", "description": "Distinguishes the aggregate and pins its source-qualified class and lineage.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "findings": [ { "id": "campaign-definition-type-profile-and-neighbor-boundaries", "name": "Campaign definition, type, profile and neighbor boundaries", "description": "Cross-sector definition, inclusion and exclusion criteria, profile, sector and distinctions from projects, initiatives, operations and events.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "campaign-definition-type-profile-and-neighbor-boundaries-q01", "text": "What identifiers, types, roles, scope, versions and values define campaign definition, type, profile and neighbor boundaries?", "kind": "definition", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "campaign-definition-type-profile-and-neighbor-boundaries-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support campaign definition, type, profile and neighbor boundaries?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "campaign-definition-type-profile-and-neighbor-boundaries-q03", "text": "How is campaign definition, type, profile and neighbor boundaries validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "campaign-definition-type-profile-and-neighbor-boundaries-data", "name": "Campaign definition, type, profile and neighbor boundaries data", "description": "Structured campaign data for campaign definition, type, profile and neighbor boundaries.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "campaign-definition-type-profile-and-neighbor-boundaries-record", "name": "Campaign definition, type, profile and neighbor boundaries record", "description": "Versioned evidence-bearing campaign record for campaign definition, type, profile and neighbor boundaries with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus campaign-definition-type-profile-and-neighbor-boundaries assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "campaign-identifier-name-alias-version-source-and-lineage", "name": "Campaign identifier, name, alias, version, source and lineage", "description": "Authoritative campaign ID, names and aliases, class and profile versions, source system, predecessor, successor and duplicate assertions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ], "questions": [ { "id": "campaign-identifier-name-alias-version-source-and-lineage-q01", "text": "What identifiers, types, roles, scope, versions and values define campaign identifier, name, alias, version, source and lineage?", "kind": "identity", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "campaign-identifier-name-alias-version-source-and-lineage-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support campaign identifier, name, alias, version, source and lineage?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "campaign-identifier-name-alias-version-source-and-lineage-q03", "text": "How is campaign identifier, name, alias, version, source and lineage validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "campaign-identifier-name-alias-version-source-and-lineage-data", "name": "Campaign identifier, name, alias, version, source and lineage data", "description": "Structured campaign data for campaign identifier, name, alias, version, source and lineage.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ] } ], "artifacts": [ { "id": "campaign-identifier-name-alias-version-source-and-lineage-record", "name": "Campaign identifier, name, alias, version, source and lineage record", "description": "Versioned evidence-bearing campaign record for campaign identifier, name, alias, version, source and lineage with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus campaign-identifier-name-alias-version-source-and-lineage assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ] } ], "inline_only_rationale": null } ] }, { "id": "mandate-owner-scope-and-problem-context", "name": "Mandate, owner, scope and problem context", "description": "Records why the campaign exists and who may direct it.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-009" ], "findings": [ { "id": "sponsor-owner-steward-mandate-authority-and-jurisdiction", "name": "Sponsor, owner, steward, mandate, authority and jurisdiction", "description": "External actors and roles, mandate source, authority scope, approval, delegation, jurisdiction and effective interval.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "sponsor-owner-steward-mandate-authority-and-jurisdiction-q01", "text": "What identifiers, types, roles, scope, versions and values define sponsor, owner, steward, mandate, authority and jurisdiction?", "kind": "authority", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "sponsor-owner-steward-mandate-authority-and-jurisdiction-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support sponsor, owner, steward, mandate, authority and jurisdiction?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "sponsor-owner-steward-mandate-authority-and-jurisdiction-q03", "text": "How is sponsor, owner, steward, mandate, authority and jurisdiction validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "sponsor-owner-steward-mandate-authority-and-jurisdiction-data", "name": "Sponsor, owner, steward, mandate, authority and jurisdiction data", "description": "Structured campaign data for sponsor, owner, steward, mandate, authority and jurisdiction.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "sponsor-owner-steward-mandate-authority-and-jurisdiction-record", "name": "Sponsor, owner, steward, mandate, authority and jurisdiction record", "description": "Versioned evidence-bearing campaign record for sponsor, owner, steward, mandate, authority and jurisdiction with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus sponsor-owner-steward-mandate-authority-and-jurisdiction assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "problem-opportunity-baseline-scope-population-place-and-assumptions", "name": "Problem, opportunity, baseline, scope, population, place and assumptions", "description": "Problem statement, evidence baseline, intended and excluded scope, affected population, geography, operating context, assumptions and constraints.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010" ], "questions": [ { "id": "problem-opportunity-baseline-scope-population-place-and-assumptions-q01", "text": "What identifiers, types, roles, scope, versions and values define problem, opportunity, baseline, scope, population, place and assumptions?", "kind": "definition", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "problem-opportunity-baseline-scope-population-place-and-assumptions-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support problem, opportunity, baseline, scope, population, place and assumptions?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "problem-opportunity-baseline-scope-population-place-and-assumptions-q03", "text": "How is problem, opportunity, baseline, scope, population, place and assumptions validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "problem-opportunity-baseline-scope-population-place-and-assumptions-data", "name": "Problem, opportunity, baseline, scope, population, place and assumptions data", "description": "Structured campaign data for problem, opportunity, baseline, scope, population, place and assumptions.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "problem-opportunity-baseline-scope-population-place-and-assumptions-record", "name": "Problem, opportunity, baseline, scope, population, place and assumptions record", "description": "Versioned evidence-bearing campaign record for problem, opportunity, baseline, scope, population, place and assumptions with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus problem-opportunity-baseline-scope-population-place-and-assumptions assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "strategy-objectives-outcomes-and-audiences", "name": "Strategy, objectives, outcomes and audiences", "description": "Connects intended change to defined audiences and testable intervention hypotheses.", "rationale": "Goals, outputs, outcomes, impacts, target groups, eligibility and observed membership are different assertions.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ], "layers": [ { "id": "strategy-objectives-and-logic-model", "name": "Strategy, objectives and logic model", "description": "Defines intended change and the reasoning linking activity to outcome.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "vision-goal-objective-target-indicator-and-success-criterion", "name": "Vision, goal, objective, target, indicator and success criterion", "description": "Purpose hierarchy, objective owner, target value and date, indicator reference, acceptance threshold, priority and trade-off.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ], "questions": [ { "id": "vision-goal-objective-target-indicator-and-success-criterion-q01", "text": "What identifiers, types, roles, scope, versions and values define vision, goal, objective, target, indicator and success criterion?", "kind": "requirement", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "vision-goal-objective-target-indicator-and-success-criterion-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support vision, goal, objective, target, indicator and success criterion?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "vision-goal-objective-target-indicator-and-success-criterion-q03", "text": "How is vision, goal, objective, target, indicator and success criterion validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "vision-goal-objective-target-indicator-and-success-criterion-data", "name": "Vision, goal, objective, target, indicator and success criterion data", "description": "Structured campaign data for vision, goal, objective, target, indicator and success criterion.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "vision-goal-objective-target-indicator-and-success-criterion-record", "name": "Vision, goal, objective, target, indicator and success criterion record", "description": "Versioned evidence-bearing campaign record for vision, goal, objective, target, indicator and success criterion with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus vision-goal-objective-target-indicator-and-success-criterion assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "input-activity-output-outcome-impact-hypothesis-and-causal-path", "name": "Input, activity, output, outcome, impact, hypothesis and causal path", "description": "Logic-model nodes and links, intervention hypothesis, assumptions, dependencies, external influences, evidence and uncertainty.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ], "questions": [ { "id": "input-activity-output-outcome-impact-hypothesis-and-causal-path-q01", "text": "What identifiers, types, roles, scope, versions and values define input, activity, output, outcome, impact, hypothesis and causal path?", "kind": "relationship", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "input-activity-output-outcome-impact-hypothesis-and-causal-path-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support input, activity, output, outcome, impact, hypothesis and causal path?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "input-activity-output-outcome-impact-hypothesis-and-causal-path-q03", "text": "How is input, activity, output, outcome, impact, hypothesis and causal path validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "input-activity-output-outcome-impact-hypothesis-and-causal-path-data", "name": "Input, activity, output, outcome, impact, hypothesis and causal path data", "description": "Structured campaign data for input, activity, output, outcome, impact, hypothesis and causal path.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "input-activity-output-outcome-impact-hypothesis-and-causal-path-record", "name": "Input, activity, output, outcome, impact, hypothesis and causal path record", "description": "Versioned evidence-bearing campaign record for input, activity, output, outcome, impact, hypothesis and causal path with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus input-activity-output-outcome-impact-hypothesis-and-causal-path assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "audience-targeting-eligibility-and-protection", "name": "Audience, targeting, eligibility and protection", "description": "Defines intended, reached and affected populations without copying person masters.", "source_refs": [ "SRC-002", "SRC-007", "SRC-009", "SRC-010" ], "findings": [ { "id": "audience-segment-beneficiary-target-affected-party-and-exclusion", "name": "Audience, segment, beneficiary, target, affected party and exclusion", "description": "Audience definitions, segment criteria and version, intended beneficiary, action target, affected non-target groups, inclusion, exclusion and geography.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010" ], "questions": [ { "id": "audience-segment-beneficiary-target-affected-party-and-exclusion-q01", "text": "What identifiers, types, roles, scope, versions and values define audience, segment, beneficiary, target, affected party and exclusion?", "kind": "classification", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "audience-segment-beneficiary-target-affected-party-and-exclusion-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support audience, segment, beneficiary, target, affected party and exclusion?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "audience-segment-beneficiary-target-affected-party-and-exclusion-q03", "text": "How is audience, segment, beneficiary, target, affected party and exclusion validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "audience-segment-beneficiary-target-affected-party-and-exclusion-data", "name": "Audience, segment, beneficiary, target, affected party and exclusion data", "description": "Structured campaign data for audience, segment, beneficiary, target, affected party and exclusion.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "audience-segment-beneficiary-target-affected-party-and-exclusion-record", "name": "Audience, segment, beneficiary, target, affected party and exclusion record", "description": "Versioned evidence-bearing campaign record for audience, segment, beneficiary, target, affected party and exclusion with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus audience-segment-beneficiary-target-affected-party-and-exclusion assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "eligibility-membership-consent-suppression-frequency-and-safeguard", "name": "Eligibility, membership, consent, suppression, frequency and safeguard", "description": "Source-qualified eligibility or membership assertion, purpose, effective interval, consent or other authority, opt-out, suppression, contact frequency and vulnerable-group safeguard.", "source_refs": [ "SRC-002", "SRC-009", "SRC-010" ], "questions": [ { "id": "eligibility-membership-consent-suppression-frequency-and-safeguard-q01", "text": "What identifiers, types, roles, scope, versions and values define eligibility, membership, consent, suppression, frequency and safeguard?", "kind": "privacy", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "eligibility-membership-consent-suppression-frequency-and-safeguard-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support eligibility, membership, consent, suppression, frequency and safeguard?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "eligibility-membership-consent-suppression-frequency-and-safeguard-q03", "text": "How is eligibility, membership, consent, suppression, frequency and safeguard validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "eligibility-membership-consent-suppression-frequency-and-safeguard-data", "name": "Eligibility, membership, consent, suppression, frequency and safeguard data", "description": "Structured campaign data for eligibility, membership, consent, suppression, frequency and safeguard.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "eligibility-membership-consent-suppression-frequency-and-safeguard-record", "name": "Eligibility, membership, consent, suppression, frequency and safeguard record", "description": "Versioned evidence-bearing campaign record for eligibility, membership, consent, suppression, frequency and safeguard with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus eligibility-membership-consent-suppression-frequency-and-safeguard assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-002", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "waves-activities-messages-assets-and-channels", "name": "Waves, activities, messages, assets and channels", "description": "Coordinates campaign-scoped work and references the masters used to deliver it.", "rationale": "A campaign groups planned or observed activity but does not absorb external content, channel, event, project, product or service identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-008", "SRC-009", "SRC-011", "SRC-012" ], "layers": [ { "id": "phases-waves-work-and-schedule", "name": "Phases, waves, work and schedule", "description": "Decomposes execution into governed units with time and dependency.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-009" ], "findings": [ { "id": "phase-wave-work-package-activity-intervention-experiment-and-variant", "name": "Phase, wave, work package, activity, intervention, experiment and variant", "description": "Campaign-scoped decomposition, sequence, external project or activity references, control and treatment variants, hypothesis and assignment rule.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-008", "SRC-011", "SRC-012" ], "questions": [ { "id": "phase-wave-work-package-activity-intervention-experiment-and-variant-q01", "text": "What identifiers, types, roles, scope, versions and values define phase, wave, work package, activity, intervention, experiment and variant?", "kind": "composition", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "phase-wave-work-package-activity-intervention-experiment-and-variant-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support phase, wave, work package, activity, intervention, experiment and variant?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "phase-wave-work-package-activity-intervention-experiment-and-variant-q03", "text": "How is phase, wave, work package, activity, intervention, experiment and variant validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "phase-wave-work-package-activity-intervention-experiment-and-variant-data", "name": "Phase, wave, work package, activity, intervention, experiment and variant data", "description": "Structured campaign data for phase, wave, work package, activity, intervention, experiment and variant.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-008", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "phase-wave-work-package-activity-intervention-experiment-and-variant-record", "name": "Phase, wave, work package, activity, intervention, experiment and variant record", "description": "Versioned evidence-bearing campaign record for phase, wave, work package, activity, intervention, experiment and variant with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus phase-wave-work-package-activity-intervention-experiment-and-variant assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-008", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "schedule-window-milestone-dependency-coordination-and-blackout", "name": "Schedule, window, milestone, dependency, coordination and blackout", "description": "Planned and actual intervals, milestone, dependency, partner coordination, release window, blackout and local-time rule.", "source_refs": [ "SRC-006", "SRC-008", "SRC-009", "SRC-013" ], "questions": [ { "id": "schedule-window-milestone-dependency-coordination-and-blackout-q01", "text": "What identifiers, types, roles, scope, versions and values define schedule, window, milestone, dependency, coordination and blackout?", "kind": "temporal", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "schedule-window-milestone-dependency-coordination-and-blackout-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support schedule, window, milestone, dependency, coordination and blackout?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "schedule-window-milestone-dependency-coordination-and-blackout-q03", "text": "How is schedule, window, milestone, dependency, coordination and blackout validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "schedule-window-milestone-dependency-coordination-and-blackout-data", "name": "Schedule, window, milestone, dependency, coordination and blackout data", "description": "Structured campaign data for schedule, window, milestone, dependency, coordination and blackout.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-008", "SRC-009", "SRC-013" ] } ], "artifacts": [ { "id": "schedule-window-milestone-dependency-coordination-and-blackout-record", "name": "Schedule, window, milestone, dependency, coordination and blackout record", "description": "Versioned evidence-bearing campaign record for schedule, window, milestone, dependency, coordination and blackout with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus schedule-window-milestone-dependency-coordination-and-blackout assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-006", "SRC-008", "SRC-009", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "message-offer-asset-channel-and-touchpoint", "name": "Message, offer, asset, channel and touchpoint", "description": "Connects intent and audience to externally managed delivery objects.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008", "SRC-009", "SRC-011", "SRC-012" ], "findings": [ { "id": "narrative-message-claim-offer-call-to-action-asset-and-localization", "name": "Narrative, message, claim, offer, call to action, asset and localization", "description": "Campaign-scoped message intent and external content, claim, offer and asset references, version, language, locale, approval, accessibility and expiry.", "source_refs": [ "SRC-002", "SRC-008", "SRC-009", "SRC-011" ], "questions": [ { "id": "narrative-message-claim-offer-call-to-action-asset-and-localization-q01", "text": "What identifiers, types, roles, scope, versions and values define narrative, message, claim, offer, call to action, asset and localization?", "kind": "definition", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "narrative-message-claim-offer-call-to-action-asset-and-localization-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support narrative, message, claim, offer, call to action, asset and localization?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "narrative-message-claim-offer-call-to-action-asset-and-localization-q03", "text": "How is narrative, message, claim, offer, call to action, asset and localization validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "narrative-message-claim-offer-call-to-action-asset-and-localization-data", "name": "Narrative, message, claim, offer, call to action, asset and localization data", "description": "Structured campaign data for narrative, message, claim, offer, call to action, asset and localization.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-008", "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "narrative-message-claim-offer-call-to-action-asset-and-localization-record", "name": "Narrative, message, claim, offer, call to action, asset and localization record", "description": "Versioned evidence-bearing campaign record for narrative, message, claim, offer, call to action, asset and localization with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus narrative-message-claim-offer-call-to-action-asset-and-localization assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-002", "SRC-008", "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "channel-touchpoint-placement-delivery-rule-frequency-and-capability", "name": "Channel, touchpoint, placement, delivery rule, frequency and capability", "description": "External channel and account, touchpoint or placement, supported media, delivery rule, audience constraint, frequency, availability and platform status.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009", "SRC-011", "SRC-012" ], "questions": [ { "id": "channel-touchpoint-placement-delivery-rule-frequency-and-capability-q01", "text": "What identifiers, types, roles, scope, versions and values define channel, touchpoint, placement, delivery rule, frequency and capability?", "kind": "interoperability", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "channel-touchpoint-placement-delivery-rule-frequency-and-capability-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support channel, touchpoint, placement, delivery rule, frequency and capability?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "channel-touchpoint-placement-delivery-rule-frequency-and-capability-q03", "text": "How is channel, touchpoint, placement, delivery rule, frequency and capability validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "channel-touchpoint-placement-delivery-rule-frequency-and-capability-data", "name": "Channel, touchpoint, placement, delivery rule, frequency and capability data", "description": "Structured campaign data for channel, touchpoint, placement, delivery rule, frequency and capability.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-009", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "channel-touchpoint-placement-delivery-rule-frequency-and-capability-record", "name": "Channel, touchpoint, placement, delivery rule, frequency and capability record", "description": "Versioned evidence-bearing campaign record for channel, touchpoint, placement, delivery rule, frequency and capability with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus channel-touchpoint-placement-delivery-rule-frequency-and-capability assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-009", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "roles-decisions-resources-budget-risk-and-controls", "name": "Roles, decisions, resources, budget, risk and controls", "description": "Governs responsibility and references capacity and funding needed for execution.", "rationale": "Budget, contract, resource and policy masters remain external; campaign records bind approved envelopes and assignments to the campaign.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-012" ], "layers": [ { "id": "participants-responsibility-decisions-and-exceptions", "name": "Participants, responsibility, decisions and exceptions", "description": "Makes campaign authority and operational accountability explicit.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008", "SRC-009" ], "findings": [ { "id": "team-partner-role-assignment-responsibility-delegation-and-capability", "name": "Team, partner, role assignment, responsibility, delegation and capability", "description": "External actor, campaign role, accountable, responsible, consulted or informed assignment, delegated authority, capability and validity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "team-partner-role-assignment-responsibility-delegation-and-capability-q01", "text": "What identifiers, types, roles, scope, versions and values define team, partner, role assignment, responsibility, delegation and capability?", "kind": "ownership", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "team-partner-role-assignment-responsibility-delegation-and-capability-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support team, partner, role assignment, responsibility, delegation and capability?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "team-partner-role-assignment-responsibility-delegation-and-capability-q03", "text": "How is team, partner, role assignment, responsibility, delegation and capability validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "team-partner-role-assignment-responsibility-delegation-and-capability-data", "name": "Team, partner, role assignment, responsibility, delegation and capability data", "description": "Structured campaign data for team, partner, role assignment, responsibility, delegation and capability.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "team-partner-role-assignment-responsibility-delegation-and-capability-record", "name": "Team, partner, role assignment, responsibility, delegation and capability record", "description": "Versioned evidence-bearing campaign record for team, partner, role assignment, responsibility, delegation and capability with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus team-partner-role-assignment-responsibility-delegation-and-capability assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "decision-approval-gate-exception-escalation-and-change-authority", "name": "Decision, approval, gate, exception, escalation and change authority", "description": "Decision or approval reference, criteria, alternatives, rationale, gate, exception, escalation path, deciding authority and effective time.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "decision-approval-gate-exception-escalation-and-change-authority-q01", "text": "What identifiers, types, roles, scope, versions and values define decision, approval, gate, exception, escalation and change authority?", "kind": "decision", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "decision-approval-gate-exception-escalation-and-change-authority-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support decision, approval, gate, exception, escalation and change authority?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "decision-approval-gate-exception-escalation-and-change-authority-q03", "text": "How is decision, approval, gate, exception, escalation and change authority validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "decision-approval-gate-exception-escalation-and-change-authority-data", "name": "Decision, approval, gate, exception, escalation and change authority data", "description": "Structured campaign data for decision, approval, gate, exception, escalation and change authority.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "decision-approval-gate-exception-escalation-and-change-authority-record", "name": "Decision, approval, gate, exception, escalation and change authority record", "description": "Versioned evidence-bearing campaign record for decision, approval, gate, exception, escalation and change authority with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus decision-approval-gate-exception-escalation-and-change-authority assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "funding-resources-risks-safety-and-compliance", "name": "Funding, resources, risks, safety and compliance", "description": "Records campaign-scoped commitments and controls without owning source masters.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-012" ], "findings": [ { "id": "budget-funding-contract-resource-capacity-cost-and-commitment-reference", "name": "Budget, funding, contract, resource, capacity, cost and commitment reference", "description": "Approved envelope, source of funds, external budget, contract, resource and commitment IDs, allocation, forecast, actual cost and currency.", "source_refs": [ "SRC-006", "SRC-007", "SRC-009", "SRC-012" ], "questions": [ { "id": "budget-funding-contract-resource-capacity-cost-and-commitment-reference-q01", "text": "What identifiers, types, roles, scope, versions and values define budget, funding, contract, resource, capacity, cost and commitment reference?", "kind": "measurement", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "budget-funding-contract-resource-capacity-cost-and-commitment-reference-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support budget, funding, contract, resource, capacity, cost and commitment reference?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "budget-funding-contract-resource-capacity-cost-and-commitment-reference-q03", "text": "How is budget, funding, contract, resource, capacity, cost and commitment reference validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "budget-funding-contract-resource-capacity-cost-and-commitment-reference-data", "name": "Budget, funding, contract, resource, capacity, cost and commitment reference data", "description": "Structured campaign data for budget, funding, contract, resource, capacity, cost and commitment reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "budget-funding-contract-resource-capacity-cost-and-commitment-reference-record", "name": "Budget, funding, contract, resource, capacity, cost and commitment reference record", "description": "Versioned evidence-bearing campaign record for budget, funding, contract, resource, capacity, cost and commitment reference with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus budget-funding-contract-resource-capacity-cost-and-commitment-reference assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-006", "SRC-007", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "risk-hazard-adverse-effect-constraint-control-compliance-and-incident", "name": "Risk, hazard, adverse effect, constraint, control, compliance and incident", "description": "Risk or hazard, affected group, likelihood and impact, safety or legal constraint, control, owner, residual risk, incident reference and response.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "risk-hazard-adverse-effect-constraint-control-compliance-and-incident-q01", "text": "What identifiers, types, roles, scope, versions and values define risk, hazard, adverse effect, constraint, control, compliance and incident?", "kind": "security", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "risk-hazard-adverse-effect-constraint-control-compliance-and-incident-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support risk, hazard, adverse effect, constraint, control, compliance and incident?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "risk-hazard-adverse-effect-constraint-control-compliance-and-incident-q03", "text": "How is risk, hazard, adverse effect, constraint, control, compliance and incident validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "risk-hazard-adverse-effect-constraint-control-compliance-and-incident-data", "name": "Risk, hazard, adverse effect, constraint, control, compliance and incident data", "description": "Structured campaign data for risk, hazard, adverse effect, constraint, control, compliance and incident.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "risk-hazard-adverse-effect-constraint-control-compliance-and-incident-record", "name": "Risk, hazard, adverse effect, constraint, control, compliance and incident record", "description": "Versioned evidence-bearing campaign record for risk, hazard, adverse effect, constraint, control, compliance and incident with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus risk-hazard-adverse-effect-constraint-control-compliance-and-incident assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-execution-observation-measurement-and-learning", "name": "Lifecycle, execution, observation, measurement and learning", "description": "Preserves intended, released and observed campaign states and results.", "rationale": "Delivery, reach, exposure, engagement, conversion, outcome and impact are separate observations with distinct denominators and evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ], "layers": [ { "id": "lifecycle-release-change-and-operating-state", "name": "Lifecycle, release, change and operating state", "description": "Represents campaign transitions and revisions without destructive history changes.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ], "findings": [ { "id": "draft-review-authorize-launch-pause-resume-terminate-and-close-event", "name": "Draft, review, authorize, launch, pause, resume, terminate and close event", "description": "Typed transition, prior and next state, actor, authority, reason, event and effective time, scope, evidence and reversibility.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ], "questions": [ { "id": "draft-review-authorize-launch-pause-resume-terminate-and-close-event-q01", "text": "What identifiers, types, roles, scope, versions and values define draft, review, authorize, launch, pause, resume, terminate and close event?", "kind": "lifecycle", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "draft-review-authorize-launch-pause-resume-terminate-and-close-event-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support draft, review, authorize, launch, pause, resume, terminate and close event?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "draft-review-authorize-launch-pause-resume-terminate-and-close-event-q03", "text": "How is draft, review, authorize, launch, pause, resume, terminate and close event validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "draft-review-authorize-launch-pause-resume-terminate-and-close-event-data", "name": "Draft, review, authorize, launch, pause, resume, terminate and close event data", "description": "Structured campaign data for draft, review, authorize, launch, pause, resume, terminate and close event.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "draft-review-authorize-launch-pause-resume-terminate-and-close-event-record", "name": "Draft, review, authorize, launch, pause, resume, terminate and close event record", "description": "Versioned evidence-bearing campaign record for draft, review, authorize, launch, pause, resume, terminate and close event with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus draft-review-authorize-launch-pause-resume-terminate-and-close-event assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-008", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "plan-release-change-supersession-drift-incident-and-recovery", "name": "Plan release, change, supersession, drift, incident and recovery", "description": "Immutable release, change request, prior and next values, impact, decision, successor, deviation from plan, incident and recovery reference.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-008", "SRC-012" ], "questions": [ { "id": "plan-release-change-supersession-drift-incident-and-recovery-q01", "text": "What identifiers, types, roles, scope, versions and values define plan release, change, supersession, drift, incident and recovery?", "kind": "lifecycle", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "plan-release-change-supersession-drift-incident-and-recovery-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support plan release, change, supersession, drift, incident and recovery?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "plan-release-change-supersession-drift-incident-and-recovery-q03", "text": "How is plan release, change, supersession, drift, incident and recovery validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "plan-release-change-supersession-drift-incident-and-recovery-data", "name": "Plan release, change, supersession, drift, incident and recovery data", "description": "Structured campaign data for plan release, change, supersession, drift, incident and recovery.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-008", "SRC-012" ] } ], "artifacts": [ { "id": "plan-release-change-supersession-drift-incident-and-recovery-record", "name": "Plan release, change, supersession, drift, incident and recovery record", "description": "Versioned evidence-bearing campaign record for plan release, change, supersession, drift, incident and recovery with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus plan-release-change-supersession-drift-incident-and-recovery assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null } ] }, { "id": "metric-definition-observation-and-result-chain", "name": "Metric definition, observation and result chain", "description": "Separates measurement design from source-qualified observations and aggregates.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ], "findings": [ { "id": "metric-indicator-formula-unit-denominator-baseline-target-window-and-segment", "name": "Metric, indicator, formula, unit, denominator, baseline, target, window and segment", "description": "Metric ID and version, definition, formula, unit, numerator and denominator, baseline, target, time window, segment, exclusions and owner.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-012" ], "questions": [ { "id": "metric-indicator-formula-unit-denominator-baseline-target-window-and-segment-q01", "text": "What identifiers, types, roles, scope, versions and values define metric, indicator, formula, unit, denominator, baseline, target, window and segment?", "kind": "measurement", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "metric-indicator-formula-unit-denominator-baseline-target-window-and-segment-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support metric, indicator, formula, unit, denominator, baseline, target, window and segment?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "metric-indicator-formula-unit-denominator-baseline-target-window-and-segment-q03", "text": "How is metric, indicator, formula, unit, denominator, baseline, target, window and segment validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "metric-indicator-formula-unit-denominator-baseline-target-window-and-segment-data", "name": "Metric, indicator, formula, unit, denominator, baseline, target, window and segment data", "description": "Structured campaign data for metric, indicator, formula, unit, denominator, baseline, target, window and segment.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "metric-indicator-formula-unit-denominator-baseline-target-window-and-segment-record", "name": "Metric, indicator, formula, unit, denominator, baseline, target, window and segment record", "description": "Versioned evidence-bearing campaign record for metric, indicator, formula, unit, denominator, baseline, target, window and segment with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus metric-indicator-formula-unit-denominator-baseline-target-window-and-segment assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation", "name": "Delivery, reach, exposure, engagement, conversion, outcome and impact observation", "description": "Observation level, source dataset, subject or segment, period, value, unit, denominator, method, quality, uncertainty, freshness and revision.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-012" ], "questions": [ { "id": "delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation-q01", "text": "What identifiers, types, roles, scope, versions and values define delivery, reach, exposure, engagement, conversion, outcome and impact observation?", "kind": "evidence", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support delivery, reach, exposure, engagement, conversion, outcome and impact observation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation-q03", "text": "How is delivery, reach, exposure, engagement, conversion, outcome and impact observation validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation-data", "name": "Delivery, reach, exposure, engagement, conversion, outcome and impact observation data", "description": "Structured campaign data for delivery, reach, exposure, engagement, conversion, outcome and impact observation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] } ], "artifacts": [ { "id": "delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation-record", "name": "Delivery, reach, exposure, engagement, conversion, outcome and impact observation record", "description": "Versioned evidence-bearing campaign record for delivery, reach, exposure, engagement, conversion, outcome and impact observation with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus delivery-reach-exposure-engagement-conversion-outcome-and-impact-observation assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evaluation-attribution-interoperability-access-and-retention", "name": "Evaluation, attribution, interoperability, access and retention", "description": "Supports cautious evaluation, loss-aware exchange and safe autonomous operation.", "rationale": "Evaluation conclusions remain method-qualified and do not turn correlation, platform credit or campaign ownership into causal truth.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "layers": [ { "id": "attribution-evaluation-decision-and-learning", "name": "Attribution, evaluation, decision and learning", "description": "Records how observations support bounded conclusions and future action.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-012" ], "findings": [ { "id": "attribution-method-counterfactual-credit-window-model-confidence-and-limit", "name": "Attribution method, counterfactual, credit window, model, confidence and limit", "description": "Method and version, exposure and outcome definitions, comparison or control, attribution window, credit rule, assumptions, confounders, confidence and causal limit.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-012" ], "questions": [ { "id": "attribution-method-counterfactual-credit-window-model-confidence-and-limit-q01", "text": "What identifiers, types, roles, scope, versions and values define attribution method, counterfactual, credit window, model, confidence and limit?", "kind": "evidence", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "attribution-method-counterfactual-credit-window-model-confidence-and-limit-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support attribution method, counterfactual, credit window, model, confidence and limit?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "attribution-method-counterfactual-credit-window-model-confidence-and-limit-q03", "text": "How is attribution method, counterfactual, credit window, model, confidence and limit validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "attribution-method-counterfactual-credit-window-model-confidence-and-limit-data", "name": "Attribution method, counterfactual, credit window, model, confidence and limit data", "description": "Structured campaign data for attribution method, counterfactual, credit window, model, confidence and limit.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] } ], "artifacts": [ { "id": "attribution-method-counterfactual-credit-window-model-confidence-and-limit-record", "name": "Attribution method, counterfactual, credit window, model, confidence and limit record", "description": "Versioned evidence-bearing campaign record for attribution method, counterfactual, credit window, model, confidence and limit with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus attribution-method-counterfactual-credit-window-model-confidence-and-limit assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "evaluation-finding-interpretation-decision-lesson-and-recommendation", "name": "Evaluation finding, interpretation, decision, lesson and recommendation", "description": "Evaluation question and method, result set, analyst, interpretation, supporting and contradicting evidence, decision, lesson, recommendation and applicability.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "questions": [ { "id": "evaluation-finding-interpretation-decision-lesson-and-recommendation-q01", "text": "What identifiers, types, roles, scope, versions and values define evaluation finding, interpretation, decision, lesson and recommendation?", "kind": "decision", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "evaluation-finding-interpretation-decision-lesson-and-recommendation-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support evaluation finding, interpretation, decision, lesson and recommendation?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "evaluation-finding-interpretation-decision-lesson-and-recommendation-q03", "text": "How is evaluation finding, interpretation, decision, lesson and recommendation validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "evaluation-finding-interpretation-decision-lesson-and-recommendation-data", "name": "Evaluation finding, interpretation, decision, lesson and recommendation data", "description": "Structured campaign data for evaluation finding, interpretation, decision, lesson and recommendation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "evaluation-finding-interpretation-decision-lesson-and-recommendation-record", "name": "Evaluation finding, interpretation, decision, lesson and recommendation record", "description": "Versioned evidence-bearing campaign record for evaluation finding, interpretation, decision, lesson and recommendation with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus evaluation-finding-interpretation-decision-lesson-and-recommendation assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "projection-access-provenance-retention-and-safe-operation", "name": "Projection, access, provenance, retention and safe operation", "description": "Controls exchange, audience views and lifecycle operations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "findings": [ { "id": "stix-activitystreams-schema-org-data-cube-and-platform-crosswalk", "name": "STIX, ActivityStreams, Schema.org, Data Cube and platform crosswalk", "description": "Pinned source and target versions, identity, activity, audience, status and metric mappings, omissions, semantic conflicts and round-trip class.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "stix-activitystreams-schema-org-data-cube-and-platform-crosswalk-q01", "text": "What identifiers, types, roles, scope, versions and values define stix, activitystreams, schema.org, data cube and platform crosswalk?", "kind": "interoperability", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "stix-activitystreams-schema-org-data-cube-and-platform-crosswalk-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support stix, activitystreams, schema.org, data cube and platform crosswalk?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "stix-activitystreams-schema-org-data-cube-and-platform-crosswalk-q03", "text": "How is stix, activitystreams, schema.org, data cube and platform crosswalk validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "stix-activitystreams-schema-org-data-cube-and-platform-crosswalk-data", "name": "STIX, ActivityStreams, Schema.org, Data Cube and platform crosswalk data", "description": "Structured campaign data for stix, activitystreams, schema.org, data cube and platform crosswalk.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "stix-activitystreams-schema-org-data-cube-and-platform-crosswalk-record", "name": "STIX, ActivityStreams, Schema.org, Data Cube and platform crosswalk record", "description": "Versioned evidence-bearing campaign record for stix, activitystreams, schema.org, data cube and platform crosswalk with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus stix-activitystreams-schema-org-data-cube-and-platform-crosswalk assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "role-view-access-disclosure-provenance-retention-agent-authority-and-audit", "name": "Role view, access, disclosure, provenance, retention, agent authority and audit", "description": "Audience and purpose, authority, included and redacted data, generation and revision provenance, retention, hold, disposition, expected revision, rollback and audit evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013" ], "questions": [ { "id": "role-view-access-disclosure-provenance-retention-agent-authority-and-audit-q01", "text": "What identifiers, types, roles, scope, versions and values define role view, access, disclosure, provenance, retention, agent authority and audit?", "kind": "access", "answer_data": [ "identifiers", "types and roles", "scope and versions", "values and explicit unknowns" ] }, { "id": "role-view-access-disclosure-provenance-retention-agent-authority-and-audit-q02", "text": "Which authority, source, method, evidence, event time and knowledge time support role view, access, disclosure, provenance, retention, agent authority and audit?", "kind": "provenance", "answer_data": [ "authority", "source and method", "evidence", "event and knowledge time", "confidence and uncertainty" ] }, { "id": "role-view-access-disclosure-provenance-retention-agent-authority-and-audit-q03", "text": "How is role view, access, disclosure, provenance, retention, agent authority and audit validated, accessed, changed, contested, corrected and retained?", "kind": "validation", "answer_data": [ "validation", "access and disclosure", "change and dispute", "lineage", "retention" ] } ], "data_elements": [ { "id": "role-view-access-disclosure-provenance-retention-agent-authority-and-audit-data", "name": "Role view, access, disclosure, provenance, retention, agent authority and audit data", "description": "Structured campaign data for role view, access, disclosure, provenance, retention, agent authority and audit.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013" ] } ], "artifacts": [ { "id": "role-view-access-disclosure-provenance-retention-agent-authority-and-audit-record", "name": "Role view, access, disclosure, provenance, retention, agent authority and audit record", "description": "Versioned evidence-bearing campaign record for role view, access, disclosure, provenance, retention, agent authority and audit with authority, time, provenance and access marking.", "media_or_form": [ "logical campaign assertion", "plan, assignment, event, observation or evidence reference" ], "serial": true, "identity_strategy": "Campaign identifier plus phase or wave discriminator when applicable plus role-view-access-disclosure-provenance-retention-agent-authority-and-audit assertion, artifact or event identifier; name, date, timestamp and digest never identify the campaign alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-and-authorize-campaign", "name": "Register and authorize campaign", "description": "Establish campaign identity, boundary, mandate, owner and governing profile.", "inputs": [ "campaign proposal", "sponsor", "mandate", "profile" ], "outputs": [ "authorized campaign root" ], "preconditions": [ "identity, duplicate, mandate, scope, safety and privacy validate" ], "effects": [ "a governed root exists without launching activity" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "define-strategy-objectives-and-logic-model", "name": "Define strategy, objectives and logic model", "description": "Record intended change, measurable objectives and testable causal assumptions.", "inputs": [ "problem baseline", "evidence", "stakeholders" ], "outputs": [ "strategy and logic-model release" ], "preconditions": [ "scope, baseline, outcome definitions, indicators, assumptions and authority validate" ], "effects": [ "planning claims become versioned and falsifiable" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] }, { "id": "define-audiences-eligibility-and-safeguards", "name": "Define audiences, eligibility and safeguards", "description": "Create versioned segment rules, exclusions, consent or authority and protections.", "inputs": [ "audience evidence", "purpose", "policy" ], "outputs": [ "audience and safeguard specification" ], "preconditions": [ "purpose, criteria, data authority, suppression, risk and bias validate" ], "effects": [ "targeting intent is bounded without copying person masters" ], "source_refs": [ "SRC-002", "SRC-009", "SRC-010" ] }, { "id": "plan-waves-activities-messages-and-channels", "name": "Plan waves, activities, messages and channels", "description": "Coordinate campaign-scoped work and external delivery objects.", "inputs": [ "strategy", "audiences", "constraints", "resources" ], "outputs": [ "execution-plan release" ], "preconditions": [ "dependencies, schedule, roles, approvals, accessibility and capacity validate" ], "effects": [ "an executable plan exists without asserting delivery" ], "source_refs": [ "SRC-002", "SRC-006", "SRC-008", "SRC-009", "SRC-011" ] }, { "id": "approve-and-release-campaign-material", "name": "Approve and release campaign material", "description": "Bind approved message, offer, asset and placement versions to a campaign release.", "inputs": [ "content and channel references", "approvals", "release scope" ], "outputs": [ "release manifest" ], "preconditions": [ "claim, content, rights, audience, channel, expiry and approval validate" ], "effects": [ "specific material becomes eligible for controlled delivery" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-009", "SRC-012" ] }, { "id": "launch-pause-resume-or-terminate", "name": "Launch, pause, resume or terminate", "description": "Append an authorized operating-state event across declared scope.", "inputs": [ "campaign release", "transition", "authority", "reason" ], "outputs": [ "lifecycle event and current state" ], "preconditions": [ "expected revision, gate, authority, risk, time and downstream controls validate" ], "effects": [ "operating state changes without rewriting prior releases" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-012" ] }, { "id": "record-delivery-and-result-observations", "name": "Record delivery and result observations", "description": "Attach source-qualified activity and metric observations at defined levels.", "inputs": [ "campaign", "source dataset", "metric definitions" ], "outputs": [ "observation set" ], "preconditions": [ "source, period, unit, denominator, segment, deduplication, quality and freshness validate" ], "effects": [ "delivery, reach, exposure, engagement, conversion, outcome and impact remain distinguishable" ], "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] }, { "id": "evaluate-and-attribute-results", "name": "Evaluate and attribute results", "description": "Apply a declared evaluation and attribution method and record bounded conclusions.", "inputs": [ "observations", "method", "comparison evidence" ], "outputs": [ "evaluation and attribution result" ], "preconditions": [ "method version, counterfactual, window, assumptions, confounders and uncertainty validate" ], "effects": [ "decisions can cite evidence without claiming unsupported causation" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] }, { "id": "revise-close-and-capture-learning", "name": "Revise, close and capture learning", "description": "Create successor plan releases or close the campaign with lessons and recommendations.", "inputs": [ "campaign lineage", "change or closure decision", "evidence" ], "outputs": [ "successor or closure event and learning record" ], "preconditions": [ "authority, expected head, impact, unresolved risks, disposition and applicability validate" ], "effects": [ "current plan changes while released history and limits remain visible" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "project-validate-retain-and-audit", "name": "Project, validate, retain and audit", "description": "Produce a loss-aware view or execute governed validation and record disposition.", "inputs": [ "campaign revision", "target profile or policy", "purpose" ], "outputs": [ "projection, validation, disposition or audit event" ], "preconditions": [ "identity, version, mapping loss, access, legal hold, minimum tombstone and post-checks validate" ], "effects": [ "campaign data remains interoperable and accountable under policy" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "composition": [ { "target": "Project, Program, Initiative, Operation and Activity models", "relation": "REFERENCE", "purpose": "Coordinate delivery work while preserving each external lifecycle and accountability boundary.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-011" ] }, { "target": "Party, Audience, Segment, Role and Mandate models", "relation": "REFERENCE", "purpose": "Resolve owners, partners, audiences, affected groups, eligibility and delegated authority.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010" ] }, { "target": "Content, Message, Offer, Channel, Budget, Contract, Event, Observation, Policy and Audit models", "relation": "REFERENCE", "purpose": "Bind approved external masters to campaign purpose without duplicating their lifecycle.", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009", "SRC-011", "SRC-012" ] }, { "target": "OASIS STIX 2.1 Campaign", "relation": "ALIGN", "purpose": "Project adversarial campaign identity, objective, observed interval, targets, resources, confidence and markings.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "ActivityStreams, PROV-O, Data Cube, Schema.org and Google Ads API", "relation": "ALIGN", "purpose": "Project activities, provenance, observations, audiences, actions and one platform campaign resource with declared loss.", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-010", "SRC-011", "SRC-012" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, campaign governance authority and strategy, audience, safety, privacy and records stewards", "Campaign-type, objective, indicator, audience, channel, lifecycle, attribution, interoperability and retention registries", "Master mappings for parties, roles, projects, activities, content, channels, budgets, contracts, events, observations, policies and audit logs", "Authorization, targeting, consent, release, lifecycle, measurement, attribution, disclosure, retention and agent-operation policies" ], "namespace_guidance": "Mint stable IDs for campaign roots, releases, waves, assignments, events and campaign-scoped assertions. Preserve authoritative external party, project, activity, content, channel, budget, contract, event and dataset identities; never use campaign name or dates as identity.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local campaign, objective, audience, channel, metric and policy registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize a campaign by authoritative source plus campaign identifier and current lineage head, not by name, objective, audience, period, channel or digest.", "Keep plan, forecast, target, released assignment, observed result and analyst interpretation as different assertion classes with source and time." ], "patch_rules": [ "Extensions declare campaign profile, target finding, semantics, authority, lifecycle, privacy, safety, measurement and interoperability impact.", "Released plans and observations are immutable. Corrections, strategy changes, segment changes and profile upgrades create successors with preserved provenance." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, authority, objectives, audience, activity, lifecycle, measurement and provenance remain intact.", "STIX, ActivityStreams, Schema.org, Data Cube and platform mappings pin versions and declare omissions, semantic conflicts and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system campaign identifier qualified by source and campaign class.", "Governed globally resolvable campaign IRI under a controlled namespace.", "Dimension UUID when no authoritative or governed global identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; separate planned, release, event, effective, observation, ingestion and knowledge times and preserve source precision.", "serial_naming_rule": "Use {campaign-id}--{phase-or-wave-id-or-root}--{artifact-kind}--{assertion-or-event-id}; never use campaign name, date, timestamp or digest alone.", "integrity_rule": "Store digest, media type, campaign and release binding, source and profile versions, authority, event and knowledge times, audience and access marking and provenance." }, "policies": [ "Plan, target, forecast, release, delivery, reach, exposure, engagement, conversion, outcome, impact and causal attribution are separate attributable assertions.", "Campaign ownership does not transfer ownership of people, audiences, projects, content, channels, budgets, contracts, events, observations, policy or audit masters.", "Audience criteria, suppression, consent or authority, vulnerable-group safeguards and adverse-effect monitoring are versioned and purpose-bound.", "Agents may validate and project allowlisted data, but audience expansion, release, launch, spending, political or health targeting, protected disclosure and destructive disposition require delegated authority and policy controls." ], "crud": { "read": [ "Resolve Dimension policy, campaign identity and lineage, mandate, objectives, audiences, current release and state, activity and content refs, metrics, provenance and access purpose." ], "create": [ "Record identity, boundary, mandate, owner, problem baseline, strategy, audiences, safeguards, plan, measurements and provenance before authorization or launch." ], "update": [ "Append authorization, release, lifecycle, observation, evaluation, correction or supersession events with actor, authority, reason, event and knowledge time and expected revision; never overwrite released history." ], "delete": [ "Apply retention, legal-hold and audit policy; stop delivery separately from removing eligible working copies, and preserve required campaign lineage, decisions, observations and minimum tombstone evidence." ] }, "roles": [ { "name": "Campaign sponsor or owner", "responsibilities": [ "Own mandate, strategic outcome, authorization and accountable closure." ] }, { "name": "Campaign strategist or steward", "responsibilities": [ "Own boundary, logic model, audiences, plan and change lineage." ] }, { "name": "Audience, safety and ethics steward", "responsibilities": [ "Own targeting safeguards, exclusions, consent or authority and adverse-effect controls." ] }, { "name": "Content and channel steward", "responsibilities": [ "Own approved messages, assets, placements, rights and delivery constraints." ] }, { "name": "Delivery partner or operator", "responsibilities": [ "Execute assigned activities and emit source-qualified delivery evidence." ] }, { "name": "Measurement and evaluation steward", "responsibilities": [ "Own metric definitions, data quality, evaluation and attribution limits." ] }, { "name": "Privacy and records steward", "responsibilities": [ "Control protected data, disclosure, retention, legal hold, disposition and auditability." ] } ], "access": { "default_rule": "Deny person-level audience data, segment membership, suppression lists, contact endpoints, unpublished strategy, security tactics, political or health targeting and raw cross-channel linkage; disclose purpose-bound minimum aggregates and approved material.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Participant-self, campaign operator, safety response, auditor, regulator or court access cites authority and remains minimum-necessary, time-limited and separately logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, campaign, operation, policy, RFC 3339 time, release or affected fields, source revision and outcome without copying protected audience data unnecessarily." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension campaign, audience, safety, privacy, measurement, access, retention and agent-operation policies.", "Read this model and linked party, project, activity, content, channel, budget, contract, event, observation, policy and audit models before mutation." ] } }, "coverage": { "claim": "Single-provider Codex result covering a cross-sector Campaign coordination aggregate across 6 bundles, 12 layers, 24 findings, 72 questions, 24 artifacts and 10 functions grounded in 13 pinned sources, spanning mandate and problem context, strategy and logic model, audiences and safeguards, waves, messages, channels, roles, resources, risk, lifecycle, source-qualified measurement, bounded attribution, interoperability, access and governed disposition. Coverage here is structural, not verified: the provider's all-sixteen-dimensions-covered checklist is downgraded to partial because q02 and q03 are template-identical across every finding, all 24 artifacts share one media_or_form and identity template, no approved relation rows exist, and neither live source resolution nor independent second-provider review was performed. No claim of universal, cross-sector or cross-jurisdictional completeness is made.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Campaign root, release, wave, assignment, event and assertion identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Cross-sector campaign definition and project, program, initiative, operation and event boundaries are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Mandate, objectives, audiences, strategy, work, content, channel, lifecycle and metrics are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Delivery and result observations retain source, level, period, denominator, quality and uncertainty." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, define, plan, release, transition, observe, evaluate, revise, project and audit are governed." }, { "dimension": "composition", "status": "covered", "notes": "Party, project, activity, content, channel, budget, contract, event, dataset, policy and audit masters remain external." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, review, authorization, release, launch, pause, resume, change, termination and closure preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Objectives, audiences, waves, activities, assets, channels, resources, metrics and external masters use typed links." }, { "dimension": "temporal", "status": "covered", "notes": "Planned, release, event, effective, observation, ingestion and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Audience geography, operating context, origin, target and activity location are source-qualified." }, { "dimension": "provenance", "status": "covered", "notes": "Plans, releases, assignments, events, observations, evaluations and projections preserve responsible-agent provenance." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Sponsor, strategist, audience, safety, content, channel, delivery, evaluation, privacy and records duties are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, mandate, audience, lifecycle, schedule, deduplication, denominator, method and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose-bound views, audience protection, suppression and deny-by-default person-level linkage are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Delivery stop, live-state termination, working-copy deletion, retained lineage, legal hold and tombstones are distinguished." }, { "dimension": "interoperability", "status": "covered", "notes": "STIX, ActivityStreams, Schema.org, Data Cube and platform projections are versioned and loss-aware." } ], "known_omissions": [ "No successful independent Claude or Grok result was available; later cross-sector, political, public-health, marketing, fundraising, advocacy, security and legal review is required before canonical promotion.", "No approved relation rows were supplied; the registry parent link to Project and proposed party, activity, content, channel, budget, event, observation, policy and audit links remain holds.", "Sector profiles need their own legal controls, vocabularies, delivery semantics, safety constraints, measurement conventions and interoperability tests.", "Google Ads v23 is only one commercial platform mapping and must never define vendor-neutral campaign semantics." ], "conflicts": [ "Campaign may denote a coordination plan, a set of observed adversarial behaviors or a platform advertising container; profiles must declare which assertions are planned, controlled or inferred.", "Audience targeting, personalization, measurement, cross-channel identity resolution, privacy, fairness and safety objectives can conflict.", "Platform-attributed conversions, observational outcomes and causal impact estimates can disagree while each remains valid under its source method." ], "regional_assumptions": [ "Political communication, advertising, fundraising, health claims, consent, profiling, suppression, record retention and disclosure depend on jurisdiction and sector.", "WHO and CDC guidance informs communication and public-health profiles but does not define all campaign types.", "STIX defines adversarial campaigns and Google Ads defines one advertising platform; both are explicit profiles rather than universal masters." ], "adversarial_checks": [ "Reject a campaign whose identity, mandate, boundary, current release, objective or owner cannot be resolved.", "Reject delivery, reach, exposure, engagement, conversion, outcome, impact or causation inferred from a neighboring metric without source and method.", "Reject silent audience, objective, message, activity, schedule, budget, status, metric or attribution mutation and any history rewrite.", "Reject person-level targeting, suppression removal or cross-channel linkage without purpose, authority, safeguards, access control and audit.", "Reject an agent operation that expands audience, releases content, launches delivery, commits spend, makes protected political or health targeting changes or destroys held evidence without delegated authority." ] }, "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": "Accepted as `aggregate` on the subject axis. Campaign is a consistency and authorization boundary that mints and owns identities with no life outside it: plan releases, phases, waves, campaign-scoped assignments and variants, message and channel bindings, campaign metric definitions and campaign-specific evaluation assertions, while referencing party, project, activity, content, channel, budget, contract, event, observation, policy and audit masters by external identity. That owned-composition-plus-external-reference shape, together with the launch/pause/terminate authorization gate that must hold across declared scope, is the aggregate discriminator. Plain `entity` would understate the release and wave composition and the transactional authorization boundary; `event` would misread a durable governed root as its own transition log; `pattern` or `mixin` would deny it master identity; `registry` and `classifier` are contradicted by the model's own campaign-type and objective registries being declared Dimension-external. Record-plane axis, kept strictly orthogonal: a frozen registry value such as `standalone-mm` states only how the record sits in the model registry (standalone mega-model rather than profile, extension or sector overlay) and is never a subject-model entry kind, so this record can simultaneously be a standalone registry entry whose subject kind is `aggregate`. Residual challenges are recorded as holds rather than a reclassification: the STIX threat campaign and the Google Ads container are observed-behavior and platform projections that do not carry the mandate, release and authorization obligations of the governed root, and the model already declares that conflict." }, "decisions": [ { "concept": "Campaign as the aggregate root rather than a projection of Project or Program", "disposition": "accepted", "rationale": "The declared discriminator holds: audience- or target-directed strategy, waves, message and channel intent, and campaign-scoped measurement are owned here, while ISO 21502-style delivery governance stays with Project/Program. The scope statement and the Project/Program boundary note keep the masters external, so the root earns its own identity rather than duplicating a delivery governance record." }, { "concept": "Entry kind axis separation between subject-model kind and registry record plane", "disposition": "accepted with explicit note", "rationale": "The synthesizer must carry a visible statement that `aggregate` answers what the modeled subject is, while any registry plane value classifies only the record. Collapsing the two axes is the exact error that would corrupt downstream enum validation, so the distinction is recorded rather than assumed." }, { "concept": "Templated q02 and q03 provenance and validation questions across all 24 findings", "disposition": "rejected as researched interrogative content; publication hold", "rationale": "The kind histogram shows provenance 24 and validation 24, meaning two of three questions per finding are verbatim substitutions of the finding name into one sentence. Only q01 varies by kind, and even its declared kind (privacy, security, measurement) is not reflected in its text. This is a generated scaffold, not an interrogation of the subject, and cannot be promoted as researched material." }, { "concept": "Twenty-four artifacts sharing one media_or_form pair and one identity_strategy template", "disposition": "deferred to differentiation pass", "rationale": "Every finding produces exactly one record artifact with the same two media forms and a name-substituted identity rule. A released plan, a suppression rule, a delivery observation and an attribution result have materially different form, mutability and integrity needs, so the artifact layer currently conveys no discriminating information and must be differentiated or partially collapsed." }, { "concept": "Artifact identity_strategy asserting campaign identity instead of artifact identity", "disposition": "rejected as written", "rationale": "The trailing clause 'name, date, timestamp and digest never identify the campaign alone' is a rule about the root, repeated 24 times inside artifact-level identity strategies. The artifact rule should constrain what identifies the artifact; the campaign-identity rule belongs once at the model level. The category slip must be corrected before the identity rules are treated as normative." }, { "concept": "serial_naming_rule token {artifact-kind} and delimiter safety", "disposition": "deferred pending vocabulary and escaping rule", "rationale": "The pattern {campaign-id}--{phase-or-wave-id-or-root}--{artifact-kind}--{assertion-or-event-id} references an artifact-kind vocabulary that appears nowhere in the model, and the '--' delimiter has no escaping or character-set constraint even though identity priority one admits arbitrary external master identifiers. Both gaps make serials non-deterministic in practice." }, { "concept": "Consent records and suppression lists placed inside campaign ownership", "disposition": "narrowed to reference-and-binding only", "rationale": "The eligibility finding names consent, suppression and membership as campaign-scoped, while the scope statement keeps party and membership masters external and access denies person-level segment membership. The defensible reading is that the campaign owns the versioned rule, the purpose binding and the effective interval, and never the consent or suppression record itself; the text must say so explicitly rather than leaving ownership implied." }, { "concept": "Retention of suppression and opt-out evidence beyond campaign disposition", "disposition": "deferred as an unresolved retention gap", "rationale": "The delete rule preserves lineage, decisions, observations and tombstones but is silent on the inverse case: an opt-out or suppression assertion normally must survive longer than the campaign that captured it, or the deletion of working copies silently re-enables contact. This directly contradicts the safeguard policy in effect and needs an explicit retention class." }, { "concept": "Access scopes expressed as bundle, layer, finding and artifact", "disposition": "rejected for person-level and protected data", "rationale": "Those four scopes describe the research record plane, not the subject graph. Person-level audience data, suppression lists, contact endpoints and cross-channel linkage must be scoped over campaign, release, wave, audience, segment and observation. Using documentation structure as the authorization scope is the same plane confusion the entry-kind rule forbids, and it would produce unenforceable access decisions." }, { "concept": "STIX 2.1 cited as support for mandate, authority, jurisdiction and access findings", "disposition": "narrowed to identity, lineage, object versioning and the adversarial profile", "rationale": "STIX models observed adversary campaigns, where no sponsor mandate, approved release or consented audience is available to the observer. Its use under sponsor/mandate/authority and under role-view/access/retention overstates support. It remains strong for campaign identity, aliases, object lineage and the explicitly declared threat-campaign profile." }, { "concept": "Missing neighbor boundary notes for Experiment or Trial, Consent or Permission, and Budget, Contract or Order", "disposition": "deferred as required boundary additions", "rationale": "The phase and wave finding absorbs experiment, variant, hypothesis and assignment rule without any Experiment or Trial boundary note, risking silent capture of an experiment design master. Consent and Budget or Contract appear only as out-of-scope list items with no distinction paragraph, which is weaker than the treatment given to the five documented neighbors." }, { "concept": "Canonicalization by current lineage head versus the three-tier identity priority", "disposition": "flagged for an explicit resolution rule", "rationale": "Canonicalizing by 'authoritative source plus campaign identifier and current lineage head' can be read as making the head part of identity, while identity priority one makes the authoritative master identifier alone identifying. The head must be stated as a resolution pointer that changes without changing identity, or supersession will appear to re-identify the root." }, { "concept": "Coverage checklist marking all sixteen dimensions covered", "disposition": "rejected; downgraded to partial", "rationale": "With a templated question and artifact layer, no approved relation rows, no live source verification and no independent review, 'covered' across every dimension over-claims. The synthesizer should carry the provider's dimension notes but publish the checklist as partial so downstream consumers do not read it as verified completeness." }, { "concept": "project-validate-retain-and-audit as a single function carrying nine source refs", "disposition": "deferred split", "rationale": "Loss-aware projection, governed validation, retention and disposition, and audit evidence are four distinct operations with different authorities and different failure modes. Bundling them under one function with nearly the full source list makes source support untraceable, but the empty add_functions rule of single-provider mode defers the split rather than performing it here." }, { "concept": "Absent standards support for money and commitment, risk management, records retention and consent vocabulary", "disposition": "deferred source-strengthening pass", "rationale": "Budget, cost, currency and commitment cite only project-management guidance and one advertising platform; risk, hazard and control cite communication guidance and STIX; retention and disposition cite no records standard; consent and privacy rest on a tier-two Schema.org term. Candidate standards must be identified and verified live before these findings can claim source grounding." } ], "publicationHolds": [ "Live source and version verification hold: no source URL, version or date was resolved during this no-tools audit. SRC-006 cites ISO 21502 through a committee page for normative text that is paywalled and not readable at that URL; SRC-007 carries an access date but no version; SRC-008, SRC-010, SRC-011 and SRC-012 pin 2026 publication or API versions; SRC-013 pins RFC 3339 as updated by a later RFC. Every pin must be re-fetched, re-dated and re-pinned before promotion, and any unresolvable URL must drop the findings that depend on it to unsupported.", "Absence-of-independent-review hold, owner-authorized: the repository owner waived Claude on 2026-09-06 after 1800, 900, 600 and 300 second attempts produced no result, and waived Grok as unavailable, slow or schema-invalid. Codex is therefore the sole active provider, and this no-tools adversarial pass audits that same stream from local evidence only. It is not, and must never be described as, independent external second-provider review. The waiver, its authorization, and this limitation must appear in every publication artifact.", "Relationship contract hold: frozen_context is empty and no approved relation rows were supplied, so the registry parent link to Project and the proposed party, activity, content, channel, budget, contract, event, observation, policy and audit links remain unadjudicated. Publish with no asserted relations and with the parent link shown as a pending hold rather than an implied edge.", "Question and artifact template hold: q02 and q03 are template-identical across all 24 findings and every artifact reuses one media_or_form pair and one name-substituted identity strategy that mistakenly constrains campaign identity rather than artifact identity. The interrogative and artifact layers must be rewritten per finding, and the {artifact-kind} token plus delimiter escaping must be defined, before canonical promotion.", "Protected-data and operational-guidance hold: access scopes are drawn from the record plane (bundle, layer, finding, artifact) rather than the subject graph, suppression and opt-out retention beyond campaign disposition is unspecified, and consent ownership is only implicitly external. Do not publish or operationalize targeting, suppression, consent or cross-channel linkage guidance from this draft, and do not treat its access rules as enforceable authorization.", "Coverage and status hold: the provider checklist marks all sixteen dimensions covered while the model itself declares that no independent result was obtained and that sector profiles are missing. Publish as reviewable draft with the checklist downgraded to partial, pending cross-sector, political, public-health, marketing, fundraising, advocacy, security, privacy and legal review.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Cross-sector adversarial review of the Campaign root by political communication, public-health, marketing, fundraising, advocacy, security and legal reviewers, since the current source base leans on two public-health bodies, one project-management standard, four W3C vocabularies and one advertising platform.", "Identify and live-verify standards support for the four weakly grounded areas: money, cost and commitment representation (currency-code standard as a candidate), risk and control management, records retention and disposition, and consent or processing-purpose vocabulary. Each candidate must be resolved and version-pinned before it is cited.", "Author the missing neighbor boundary notes for Experiment or Trial, Consent or Permission, and Budget, Contract or Order, and decide explicitly whether experiment design, randomization unit, assignment rule and variant belong to a separate Experiment aggregate rather than inside the campaign wave finding.", "Resolve the canonicalization tension by stating whether the current lineage head is part of canonical identity or only a resolution pointer, and define what supersession, duplicate merge and campaign-successor do to the root identifier and to already-released artifacts.", "Define a retention class for suppression, opt-out and withdrawal evidence that survives campaign closure and working-copy deletion, and reconcile it with data minimization, legal hold and the deny-by-default person-level access rule.", "Re-scope access control over the subject graph (campaign, release, wave, audience, segment, assertion, observation) and specify how participant-self disclosure answers a membership question without minting a new membership assertion.", "De-duplicate the three findings that each carry incident semantics (risk and compliance, lifecycle transition, plan release and recovery), decide which definition-only findings should be inline_only rather than producing a serial artifact, and split the overloaded project-validate-retain-and-audit function into projection, validation, retention and audit operations.", "Decide whether a distinct honor-withdrawal, suppression-enforcement and adverse-effect-response function is required, since the current function set defines audiences and safeguards at plan time but has no runtime operation that enforces a withdrawal or halts delivery on a safety signal short of a full pause or terminate.", "Attempt bounded supplemental Claude and Grok passes when either becomes available, admitting a result only if it is locally schema-valid and its sources and boundaries survive the same adjudication, so that the absence-of-external-review hold can eventually be lifted rather than permanently waived." ] }, "statistics": { "sources": 13, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }