# Vercy AI instruction - YAML 1.2 (JSON-compatible)
{
  "vercy": "1.0-draft",
  "publication": {
    "status": "published",
    "adjudicationStatus": "reviewable-draft",
    "publishableCanonical": false,
    "generatedAt": "2026-09-06T08:34:35Z",
    "synthesisSha256": "c7a6a823c6570d03874d6f92ea2b05a6b3b2090b979d57864871b520d095c620",
    "providerMode": "single-provider-waiver",
    "providers": [
      "Codex"
    ],
    "waivedProviders": [
      "Claude",
      "Grok"
    ]
  },
  "metaModel": {
    "id": "WM-ACT-044",
    "registryId": "vr.wm-act-044",
    "name": "Content Publication",
    "version": "0.3.0-research.1",
    "previousVersions": [],
    "entryKind": "aggregate",
    "family": "World Models",
    "category": "Activities and processes",
    "industry": [
      "Cross-industry"
    ],
    "domain": [
      "ACT.PUB"
    ],
    "tags": [
      "content",
      "publication",
      "act.pub"
    ],
    "status": "published"
  },
  "canonicalUrl": "https://ver.cy/models/wm-act-044-content-publication/",
  "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-044",
  "model": {
    "registry_id": "vr.wm-act-044",
    "model_id": "WM-ACT-044",
    "name": "Content Publication",
    "entry_kind": "aggregate",
    "purpose": "Represent one governed content-publication operation that binds an external content revision, records review and authority, issues a release instruction, observes origin and downstream delivery, and preserves corrections or removal without absorbing the systems it coordinates.",
    "scope_statement": "Owns publication-case identity and lineage, target bindings and release metadata snapshots, editorial workflow, review and clearance assertions, decisions, immutable release instructions, packages, channel bindings, delivery attempts, discovery and syndication projections, availability observations, correction, update, retraction, withdrawal and takedown events, provenance, access, retention and interoperability. Content, Publication or Edition, actor, channel, rights, rendition, communication, analytics and record masters remain external.",
    "in_scope": [
      "Publication-case identity, authority, target revision bindings, metadata snapshot, workflow, review, clearances and decision evidence",
      "Release instructions, packages, representations, channels, delivery, canonical locations, discovery, feeds, subscriptions and verified availability",
      "Post-publication observation, correction, retraction, withdrawal, takedown, lifecycle, provenance, retention, interoperability and safe agents"
    ],
    "out_of_scope": [
      "Independent content, edition, actor, organization, role, platform, channel, rights, licence, translation, rendition, communication, analytics or record master lifecycles",
      "Treating approval as availability, delivery acknowledgement as audience reach, syndication as origin authority, unpublishing as erasure or a representation as an edition",
      "Operating publishing platforms, determining legal rights, guaranteeing indexing or reach, moderating all audience interaction or deleting referenced masters"
    ],
    "boundary_notes": [
      {
        "neighbor": "WM-MED-003 Publication / Edition candidate parent",
        "distinction": "The external edition master owns bibliographic identity and edition lineage; this aggregate owns a governed operation that may publish a referenced edition. The registry parent is not an approved relation row.",
        "source_refs": [
          "SRC-003",
          "SRC-007",
          "SRC-008"
        ]
      },
      {
        "neighbor": "Content, Creative Work and Document",
        "distinction": "Those masters own authored meaning and revision history. This model binds the exact revision and records whether, where and under whose authority it was released.",
        "source_refs": [
          "SRC-002",
          "SRC-007",
          "SRC-009"
        ]
      },
      {
        "neighbor": "Channel, Platform, Representation and Rendition",
        "distinction": "External masters own endpoint, platform and media identities. This case stores release-specific bindings, attempts and observations without copying their inventories.",
        "source_refs": [
          "SRC-002",
          "SRC-004",
          "SRC-008"
        ]
      },
      {
        "neighbor": "Rights, Licence, Policy and Accessibility",
        "distinction": "Their masters own normative rules. This model records scoped clearance assertions and evidence for one release decision.",
        "source_refs": [
          "SRC-010",
          "SRC-013"
        ]
      },
      {
        "neighbor": "Communication, Notification, Analytics, Audit and Record",
        "distinction": "Those systems own messages, measurements and records; this case binds qualified references needed to explain publication outcomes.",
        "source_refs": [
          "SRC-001",
          "SRC-006",
          "SRC-009"
        ]
      }
    ]
  },
  "sources": [
    {
      "id": "SRC-001",
      "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-06T08:25:00Z",
      "relevance": "Vocabulary-independent syntax for activities including Create, Update, Delete, Add, Remove and Announce, with collection and paging semantics."
    },
    {
      "id": "SRC-002",
      "title": "The Atom Publishing Protocol",
      "organization": "Internet Engineering Task Force",
      "url": "https://www.rfc-editor.org/info/rfc5023/",
      "version_or_date": "RFC 5023, October 2007",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "HTTP-based creation, editing and deletion of web resources in collections, including media resources and service discovery."
    },
    {
      "id": "SRC-003",
      "title": "The Atom Syndication Format",
      "organization": "Internet Engineering Task Force",
      "url": "https://www.rfc-editor.org/info/rfc4287/",
      "version_or_date": "RFC 4287, December 2005",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Feed and entry metadata, identifiers, updated and published dates, authors, content, links and ordering for syndication."
    },
    {
      "id": "SRC-004",
      "title": "HTTP Semantics",
      "organization": "Internet Engineering Task Force",
      "url": "https://www.rfc-editor.org/info/rfc9110/",
      "version_or_date": "RFC 9110, June 2022",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Resource identifiers, representations, content negotiation, conditional requests, validators, safe and idempotent methods, and response semantics."
    },
    {
      "id": "SRC-005",
      "title": "HTTP Caching",
      "organization": "Internet Engineering Task Force",
      "url": "https://www.rfc-editor.org/info/rfc9111/",
      "version_or_date": "RFC 9111, June 2022",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Cache freshness, validation, invalidation and stored-response behavior needed to distinguish origin change from downstream propagation."
    },
    {
      "id": "SRC-006",
      "title": "WebSub",
      "organization": "World Wide Web Consortium",
      "url": "https://www.w3.org/TR/websub/",
      "version_or_date": "W3C Recommendation, 2 June 2026",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Publisher, hub and subscriber protocol for verified subscriptions and distribution of notifications about updated topic resources."
    },
    {
      "id": "SRC-007",
      "title": "DCMI Metadata Terms",
      "organization": "Dublin Core Metadata Initiative",
      "url": "https://www.dublincore.org/specifications/dublin-core/dcmi-terms/",
      "version_or_date": "DCMI Metadata Terms, continuously maintained; accessed 6 September 2026",
      "source_type": "ontology",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Terms for title, creator, publisher, issued, modified, language, rights, licence, access rights, versions, replacement and bibliographic citation."
    },
    {
      "id": "SRC-008",
      "title": "Data Catalog Vocabulary DCAT Version 3",
      "organization": "World Wide Web Consortium",
      "url": "https://www.w3.org/TR/vocab-dcat-3/",
      "version_or_date": "W3C Recommendation, 22 August 2024",
      "source_type": "ontology",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Separates cataloged resources from distributions and catalog records while covering versions, access URLs, media types, rights and publishers."
    },
    {
      "id": "SRC-009",
      "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-06T08:25:00Z",
      "relevance": "Attributable generation, use, derivation, revision, invalidation and agent responsibility for publication evidence."
    },
    {
      "id": "SRC-010",
      "title": "Web Content Accessibility Guidelines WCAG 2.2",
      "organization": "World Wide Web Consortium",
      "url": "https://www.w3.org/TR/WCAG22/",
      "version_or_date": "W3C Recommendation, 5 October 2023",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Testable accessibility requirements and conformance claims for published web content."
    },
    {
      "id": "SRC-011",
      "title": "Tags for Identifying Languages",
      "organization": "Internet Engineering Task Force",
      "url": "https://www.rfc-editor.org/info/rfc5646/",
      "version_or_date": "RFC 5646, September 2009",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "BCP 47 language-tag syntax and matching context for language-qualified publications and alternates."
    },
    {
      "id": "SRC-012",
      "title": "Date and Time on the Internet: Timestamps",
      "organization": "Internet Engineering Task Force",
      "url": "https://www.rfc-editor.org/info/rfc3339/",
      "version_or_date": "RFC 3339, July 2002",
      "source_type": "standard",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Unambiguous timestamps with seconds and an explicit UTC relationship for publication events and knowledge times."
    },
    {
      "id": "SRC-013",
      "title": "ODRL Information Model 2.2",
      "organization": "World Wide Web Consortium",
      "url": "https://www.w3.org/TR/odrl-model/",
      "version_or_date": "W3C Recommendation, 15 February 2018",
      "source_type": "ontology",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Machine-readable offers, agreements, permissions, prohibitions, duties, constraints and parties for rights-policy references."
    },
    {
      "id": "SRC-014",
      "title": "Web Annotation Data Model",
      "organization": "World Wide Web Consortium",
      "url": "https://www.w3.org/TR/annotation-model/",
      "version_or_date": "W3C Recommendation, 23 February 2017",
      "source_type": "ontology",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Annotation bodies, targets, selectors, motivations, agents and lifecycle metadata for reviews and corrections."
    },
    {
      "id": "SRC-015",
      "title": "Sitemaps XML format",
      "organization": "Google, Microsoft and Yahoo",
      "url": "https://www.sitemaps.org/protocol.html",
      "version_or_date": "Protocol specification, accessed 6 September 2026",
      "source_type": "first-party-doc",
      "primary_source": true,
      "authority_tier": 1,
      "accessed_at": "2026-09-06T08:25:00Z",
      "relevance": "Discovery projection for canonical locators, modification times and alternates without treating indexing as publication success."
    }
  ],
  "structure": {
    "bundles": [
      {
        "id": "publication-case-identity-scope-and-authority",
        "name": "Publication case identity, scope and authority",
        "description": "Groups governed context for publication case identity, scope and authority.",
        "rationale": "A stable operation aggregate separates publication governance from the content and edition masters it coordinates.",
        "source_refs": [
          "SRC-001",
          "SRC-002",
          "SRC-007",
          "SRC-008",
          "SRC-009",
          "SRC-010",
          "SRC-013",
          "SRC-014"
        ],
        "layers": [
          {
            "id": "case-profile-identity-lineage-and-boundaries",
            "name": "Case profile, identity, lineage and boundaries",
            "description": "Groups publication context for case profile, identity, lineage and boundaries.",
            "source_refs": [
              "SRC-001",
              "SRC-002",
              "SRC-007",
              "SRC-008",
              "SRC-009"
            ],
            "findings": [
              {
                "id": "publication-operation-type-scope-target-and-neighbor-boundary",
                "name": "Publication operation type, scope, target and neighbor boundary",
                "description": "Records publication operation type, scope, target and neighbor boundary as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-007",
                  "SRC-008",
                  "SRC-009"
                ],
                "questions": [
                  {
                    "id": "publication-operation-type-scope-target-and-neighbor-boundary-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish publication operation type, scope, target and neighbor boundary?",
                    "kind": "classification",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "publication-operation-type-scope-target-and-neighbor-boundary-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support publication operation type, scope, target and neighbor boundary?",
                    "kind": "decision",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "publication-operation-type-scope-target-and-neighbor-boundary-q03",
                    "text": "How may publication operation type, scope, target and neighbor boundary be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "quality",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "publication-operation-type-scope-target-and-neighbor-boundary-data",
                    "name": "Publication operation type, scope, target and neighbor boundary data",
                    "description": "Structured data for publication operation type, scope, target and neighbor boundary with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-007",
                      "SRC-008",
                      "SRC-009"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "publication-operation-type-scope-target-and-neighbor-boundary-record",
                    "name": "Publication operation type, scope, target and neighbor boundary record",
                    "description": "Versioned evidence-bearing publication record for publication operation type, scope, target and neighbor boundary.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus publication-operation-type-scope-target-and-neighbor-boundary assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-007",
                      "SRC-008",
                      "SRC-009"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "case-identifier-source-version-predecessor-successor-and-lineage",
                "name": "Case identifier, source, version, predecessor, successor and lineage",
                "description": "Records case identifier, source, version, predecessor, successor and lineage as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-007",
                  "SRC-008",
                  "SRC-009"
                ],
                "questions": [
                  {
                    "id": "case-identifier-source-version-predecessor-successor-and-lineage-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish case identifier, source, version, predecessor, successor and lineage?",
                    "kind": "identity",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "case-identifier-source-version-predecessor-successor-and-lineage-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support case identifier, source, version, predecessor, successor and lineage?",
                    "kind": "temporal",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "case-identifier-source-version-predecessor-successor-and-lineage-q03",
                    "text": "How may case identifier, source, version, predecessor, successor and lineage be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "state",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "case-identifier-source-version-predecessor-successor-and-lineage-data",
                    "name": "Case identifier, source, version, predecessor, successor and lineage data",
                    "description": "Structured data for case identifier, source, version, predecessor, successor and lineage with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-007",
                      "SRC-008",
                      "SRC-009"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "case-identifier-source-version-predecessor-successor-and-lineage-record",
                    "name": "Case identifier, source, version, predecessor, successor and lineage record",
                    "description": "Versioned evidence-bearing publication record for case identifier, source, version, predecessor, successor and lineage.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus case-identifier-source-version-predecessor-successor-and-lineage assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-007",
                      "SRC-008",
                      "SRC-009"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          },
          {
            "id": "mandate-roles-rights-clearances-and-decisions",
            "name": "Mandate, roles, rights, clearances and decisions",
            "description": "Groups publication context for mandate, roles, rights, clearances and decisions.",
            "source_refs": [
              "SRC-007",
              "SRC-009",
              "SRC-010",
              "SRC-013",
              "SRC-014"
            ],
            "findings": [
              {
                "id": "publisher-editor-owner-authority-role-and-decision-right",
                "name": "Publisher, editor, owner, authority, role and decision right",
                "description": "Records publisher, editor, owner, authority, role and decision right as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-007",
                  "SRC-009",
                  "SRC-010",
                  "SRC-013",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "publisher-editor-owner-authority-role-and-decision-right-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish publisher, editor, owner, authority, role and decision right?",
                    "kind": "authority",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "publisher-editor-owner-authority-role-and-decision-right-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support publisher, editor, owner, authority, role and decision right?",
                    "kind": "composition",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "publisher-editor-owner-authority-role-and-decision-right-q03",
                    "text": "How may publisher, editor, owner, authority, role and decision right be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "measurement",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "publisher-editor-owner-authority-role-and-decision-right-data",
                    "name": "Publisher, editor, owner, authority, role and decision right data",
                    "description": "Structured data for publisher, editor, owner, authority, role and decision right with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-007",
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "publisher-editor-owner-authority-role-and-decision-right-record",
                    "name": "Publisher, editor, owner, authority, role and decision right record",
                    "description": "Versioned evidence-bearing publication record for publisher, editor, owner, authority, role and decision right.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus publisher-editor-owner-authority-role-and-decision-right assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-007",
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance",
                "name": "Rights, licence, embargo, privacy, legal, fact-check and accessibility clearance",
                "description": "Records rights, licence, embargo, privacy, legal, fact-check and accessibility clearance as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-007",
                  "SRC-009",
                  "SRC-010",
                  "SRC-013",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish rights, licence, embargo, privacy, legal, fact-check and accessibility clearance?",
                    "kind": "validation",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support rights, licence, embargo, privacy, legal, fact-check and accessibility clearance?",
                    "kind": "evidence",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-q03",
                    "text": "How may rights, licence, embargo, privacy, legal, fact-check and accessibility clearance be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "lifecycle",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-data",
                    "name": "Rights, licence, embargo, privacy, legal, fact-check and accessibility clearance data",
                    "description": "Structured data for rights, licence, embargo, privacy, legal, fact-check and accessibility clearance with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-007",
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-record",
                    "name": "Rights, licence, embargo, privacy, legal, fact-check and accessibility clearance record",
                    "description": "Versioned evidence-bearing publication record for rights, licence, embargo, privacy, legal, fact-check and accessibility clearance.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-007",
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          }
        ]
      },
      {
        "id": "content-release-definition-and-editorial-workflow",
        "name": "Content release definition and editorial workflow",
        "description": "Groups governed context for content release definition and editorial workflow.",
        "rationale": "Versioned bindings preserve the distinction between an external content revision and the decision to publish it.",
        "source_refs": [
          "SRC-003",
          "SRC-007",
          "SRC-008",
          "SRC-009",
          "SRC-010",
          "SRC-011",
          "SRC-013",
          "SRC-014"
        ],
        "layers": [
          {
            "id": "content-version-metadata-language-and-audience",
            "name": "Content version, metadata, language and audience",
            "description": "Groups publication context for content version, metadata, language and audience.",
            "source_refs": [
              "SRC-003",
              "SRC-007",
              "SRC-008",
              "SRC-011"
            ],
            "findings": [
              {
                "id": "content-edition-revision-rendition-and-translation-reference",
                "name": "Content, edition, revision, rendition and translation reference",
                "description": "Records content, edition, revision, rendition and translation reference as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-003",
                  "SRC-007",
                  "SRC-008",
                  "SRC-011"
                ],
                "questions": [
                  {
                    "id": "content-edition-revision-rendition-and-translation-reference-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish content, edition, revision, rendition and translation reference?",
                    "kind": "relationship",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "content-edition-revision-rendition-and-translation-reference-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support content, edition, revision, rendition and translation reference?",
                    "kind": "interoperability",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "content-edition-revision-rendition-and-translation-reference-q03",
                    "text": "How may content, edition, revision, rendition and translation reference be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "event",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "content-edition-revision-rendition-and-translation-reference-data",
                    "name": "Content, edition, revision, rendition and translation reference data",
                    "description": "Structured data for content, edition, revision, rendition and translation reference with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-003",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "content-edition-revision-rendition-and-translation-reference-record",
                    "name": "Content, edition, revision, rendition and translation reference record",
                    "description": "Versioned evidence-bearing publication record for content, edition, revision, rendition and translation reference.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus content-edition-revision-rendition-and-translation-reference assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-003",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot",
                "name": "Release metadata, identifier, title, subject, language, audience and provenance snapshot",
                "description": "Records release metadata, identifier, title, subject, language, audience and provenance snapshot as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-003",
                  "SRC-007",
                  "SRC-008",
                  "SRC-011"
                ],
                "questions": [
                  {
                    "id": "release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish release metadata, identifier, title, subject, language, audience and provenance snapshot?",
                    "kind": "provenance",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support release metadata, identifier, title, subject, language, audience and provenance snapshot?",
                    "kind": "quality",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-q03",
                    "text": "How may release metadata, identifier, title, subject, language, audience and provenance snapshot be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "retention",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-data",
                    "name": "Release metadata, identifier, title, subject, language, audience and provenance snapshot data",
                    "description": "Structured data for release metadata, identifier, title, subject, language, audience and provenance snapshot with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-003",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-record",
                    "name": "Release metadata, identifier, title, subject, language, audience and provenance snapshot record",
                    "description": "Versioned evidence-bearing publication record for release metadata, identifier, title, subject, language, audience and provenance snapshot.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-003",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          },
          {
            "id": "workflow-review-approval-and-readiness",
            "name": "Workflow, review, approval and readiness",
            "description": "Groups publication context for workflow, review, approval and readiness.",
            "source_refs": [
              "SRC-009",
              "SRC-010",
              "SRC-013",
              "SRC-014"
            ],
            "findings": [
              {
                "id": "editorial-stage-owner-dependency-deadline-status-and-exception",
                "name": "Editorial stage, owner, dependency, deadline, status and exception",
                "description": "Records editorial stage, owner, dependency, deadline, status and exception as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-009",
                  "SRC-010",
                  "SRC-013",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "editorial-stage-owner-dependency-deadline-status-and-exception-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish editorial stage, owner, dependency, deadline, status and exception?",
                    "kind": "process",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "editorial-stage-owner-dependency-deadline-status-and-exception-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support editorial stage, owner, dependency, deadline, status and exception?",
                    "kind": "state",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "editorial-stage-owner-dependency-deadline-status-and-exception-q03",
                    "text": "How may editorial stage, owner, dependency, deadline, status and exception be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "security",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "editorial-stage-owner-dependency-deadline-status-and-exception-data",
                    "name": "Editorial stage, owner, dependency, deadline, status and exception data",
                    "description": "Structured data for editorial stage, owner, dependency, deadline, status and exception with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "editorial-stage-owner-dependency-deadline-status-and-exception-record",
                    "name": "Editorial stage, owner, dependency, deadline, status and exception record",
                    "description": "Versioned evidence-bearing publication record for editorial stage, owner, dependency, deadline, status and exception.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus editorial-stage-owner-dependency-deadline-status-and-exception assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "review-comment-check-approval-rejection-exception-and-evidence",
                "name": "Review comment, check, approval, rejection, exception and evidence",
                "description": "Records review comment, check, approval, rejection, exception and evidence as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-009",
                  "SRC-010",
                  "SRC-013",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "review-comment-check-approval-rejection-exception-and-evidence-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish review comment, check, approval, rejection, exception and evidence?",
                    "kind": "decision",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "review-comment-check-approval-rejection-exception-and-evidence-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support review comment, check, approval, rejection, exception and evidence?",
                    "kind": "measurement",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "review-comment-check-approval-rejection-exception-and-evidence-q03",
                    "text": "How may review comment, check, approval, rejection, exception and evidence be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "validation",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "review-comment-check-approval-rejection-exception-and-evidence-data",
                    "name": "Review comment, check, approval, rejection, exception and evidence data",
                    "description": "Structured data for review comment, check, approval, rejection, exception and evidence with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "review-comment-check-approval-rejection-exception-and-evidence-record",
                    "name": "Review comment, check, approval, rejection, exception and evidence record",
                    "description": "Versioned evidence-bearing publication record for review comment, check, approval, rejection, exception and evidence.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus review-comment-check-approval-rejection-exception-and-evidence assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-009",
                      "SRC-010",
                      "SRC-013",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          }
        ]
      },
      {
        "id": "release-packaging-channels-and-distribution",
        "name": "Release packaging, channels and distribution",
        "description": "Groups governed context for release packaging, channels and distribution.",
        "rationale": "An immutable instruction and integrity-bound package permit delivery attempts and observed availability to be audited separately.",
        "source_refs": [
          "SRC-001",
          "SRC-002",
          "SRC-003",
          "SRC-004",
          "SRC-005",
          "SRC-008",
          "SRC-010"
        ],
        "layers": [
          {
            "id": "release-instruction-package-and-representations",
            "name": "Release instruction, package and representations",
            "description": "Groups publication context for release instruction, package and representations.",
            "source_refs": [
              "SRC-002",
              "SRC-003",
              "SRC-004",
              "SRC-008",
              "SRC-010"
            ],
            "findings": [
              {
                "id": "release-instruction-scheduled-effective-window-embargo-and-authority",
                "name": "Release instruction, scheduled and effective window, embargo and authority",
                "description": "Records release instruction, scheduled and effective window, embargo and authority as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-002",
                  "SRC-003",
                  "SRC-004",
                  "SRC-008",
                  "SRC-010"
                ],
                "questions": [
                  {
                    "id": "release-instruction-scheduled-effective-window-embargo-and-authority-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish release instruction, scheduled and effective window, embargo and authority?",
                    "kind": "temporal",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "release-instruction-scheduled-effective-window-embargo-and-authority-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support release instruction, scheduled and effective window, embargo and authority?",
                    "kind": "lifecycle",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "release-instruction-scheduled-effective-window-embargo-and-authority-q03",
                    "text": "How may release instruction, scheduled and effective window, embargo and authority be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "identity",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "release-instruction-scheduled-effective-window-embargo-and-authority-data",
                    "name": "Release instruction, scheduled and effective window, embargo and authority data",
                    "description": "Structured data for release instruction, scheduled and effective window, embargo and authority with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-002",
                      "SRC-003",
                      "SRC-004",
                      "SRC-008",
                      "SRC-010"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "release-instruction-scheduled-effective-window-embargo-and-authority-record",
                    "name": "Release instruction, scheduled and effective window, embargo and authority record",
                    "description": "Versioned evidence-bearing publication record for release instruction, scheduled and effective window, embargo and authority.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus release-instruction-scheduled-effective-window-embargo-and-authority assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-002",
                      "SRC-003",
                      "SRC-004",
                      "SRC-008",
                      "SRC-010"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "package-format-media-type-digest-rendition-manifest-and-accessibility",
                "name": "Package, format, media type, digest, rendition, manifest and accessibility",
                "description": "Records package, format, media type, digest, rendition, manifest and accessibility as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-002",
                  "SRC-003",
                  "SRC-004",
                  "SRC-008",
                  "SRC-010"
                ],
                "questions": [
                  {
                    "id": "package-format-media-type-digest-rendition-manifest-and-accessibility-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish package, format, media type, digest, rendition, manifest and accessibility?",
                    "kind": "composition",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "package-format-media-type-digest-rendition-manifest-and-accessibility-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support package, format, media type, digest, rendition, manifest and accessibility?",
                    "kind": "event",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "package-format-media-type-digest-rendition-manifest-and-accessibility-q03",
                    "text": "How may package, format, media type, digest, rendition, manifest and accessibility be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "authority",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "package-format-media-type-digest-rendition-manifest-and-accessibility-data",
                    "name": "Package, format, media type, digest, rendition, manifest and accessibility data",
                    "description": "Structured data for package, format, media type, digest, rendition, manifest and accessibility with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-002",
                      "SRC-003",
                      "SRC-004",
                      "SRC-008",
                      "SRC-010"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "package-format-media-type-digest-rendition-manifest-and-accessibility-record",
                    "name": "Package, format, media type, digest, rendition, manifest and accessibility record",
                    "description": "Versioned evidence-bearing publication record for package, format, media type, digest, rendition, manifest and accessibility.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus package-format-media-type-digest-rendition-manifest-and-accessibility assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-002",
                      "SRC-003",
                      "SRC-004",
                      "SRC-008",
                      "SRC-010"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          },
          {
            "id": "channels-endpoints-delivery-and-acknowledgements",
            "name": "Channels, endpoints, delivery and acknowledgements",
            "description": "Groups publication context for channels, endpoints, delivery and acknowledgements.",
            "source_refs": [
              "SRC-001",
              "SRC-002",
              "SRC-004",
              "SRC-005",
              "SRC-008"
            ],
            "findings": [
              {
                "id": "channel-platform-audience-endpoint-campaign-and-placement-reference",
                "name": "Channel, platform, audience, endpoint, campaign and placement reference",
                "description": "Records channel, platform, audience, endpoint, campaign and placement reference as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-004",
                  "SRC-005",
                  "SRC-008"
                ],
                "questions": [
                  {
                    "id": "channel-platform-audience-endpoint-campaign-and-placement-reference-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish channel, platform, audience, endpoint, campaign and placement reference?",
                    "kind": "relationship",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "channel-platform-audience-endpoint-campaign-and-placement-reference-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support channel, platform, audience, endpoint, campaign and placement reference?",
                    "kind": "retention",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "channel-platform-audience-endpoint-campaign-and-placement-reference-q03",
                    "text": "How may channel, platform, audience, endpoint, campaign and placement reference be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "relationship",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "channel-platform-audience-endpoint-campaign-and-placement-reference-data",
                    "name": "Channel, platform, audience, endpoint, campaign and placement reference data",
                    "description": "Structured data for channel, platform, audience, endpoint, campaign and placement reference with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-004",
                      "SRC-005",
                      "SRC-008"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "channel-platform-audience-endpoint-campaign-and-placement-reference-record",
                    "name": "Channel, platform, audience, endpoint, campaign and placement reference record",
                    "description": "Versioned evidence-bearing publication record for channel, platform, audience, endpoint, campaign and placement reference.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus channel-platform-audience-endpoint-campaign-and-placement-reference assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-004",
                      "SRC-005",
                      "SRC-008"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "delivery-attempt-response-acknowledgement-uri-and-availability-verification",
                "name": "Delivery attempt, response, acknowledgement, URI and availability verification",
                "description": "Records delivery attempt, response, acknowledgement, uri and availability verification as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-004",
                  "SRC-005",
                  "SRC-008"
                ],
                "questions": [
                  {
                    "id": "delivery-attempt-response-acknowledgement-uri-and-availability-verification-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish delivery attempt, response, acknowledgement, uri and availability verification?",
                    "kind": "evidence",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "delivery-attempt-response-acknowledgement-uri-and-availability-verification-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support delivery attempt, response, acknowledgement, uri and availability verification?",
                    "kind": "security",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "delivery-attempt-response-acknowledgement-uri-and-availability-verification-q03",
                    "text": "How may delivery attempt, response, acknowledgement, uri and availability verification be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "provenance",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "delivery-attempt-response-acknowledgement-uri-and-availability-verification-data",
                    "name": "Delivery attempt, response, acknowledgement, URI and availability verification data",
                    "description": "Structured data for delivery attempt, response, acknowledgement, uri and availability verification with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-004",
                      "SRC-005",
                      "SRC-008"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "delivery-attempt-response-acknowledgement-uri-and-availability-verification-record",
                    "name": "Delivery attempt, response, acknowledgement, URI and availability verification record",
                    "description": "Versioned evidence-bearing publication record for delivery attempt, response, acknowledgement, uri and availability verification.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus delivery-attempt-response-acknowledgement-uri-and-availability-verification assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-004",
                      "SRC-005",
                      "SRC-008"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          }
        ]
      },
      {
        "id": "discovery-syndication-subscription-and-access",
        "name": "Discovery, syndication, subscription and access",
        "description": "Groups governed context for discovery, syndication, subscription and access.",
        "rationale": "Discovery projections and propagation records expose reach without redefining the authoritative publication.",
        "source_refs": [
          "SRC-001",
          "SRC-003",
          "SRC-004",
          "SRC-006",
          "SRC-007",
          "SRC-008",
          "SRC-011",
          "SRC-015"
        ],
        "layers": [
          {
            "id": "canonical-location-discovery-indexing-and-metadata",
            "name": "Canonical location, discovery, indexing and metadata",
            "description": "Groups publication context for canonical location, discovery, indexing and metadata.",
            "source_refs": [
              "SRC-003",
              "SRC-004",
              "SRC-007",
              "SRC-008",
              "SRC-011",
              "SRC-015"
            ],
            "findings": [
              {
                "id": "canonical-uri-alternate-language-version-structured-metadata-and-catalog-record",
                "name": "Canonical URI, alternate, language, version, structured metadata and catalog record",
                "description": "Records canonical uri, alternate, language, version, structured metadata and catalog record as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-003",
                  "SRC-004",
                  "SRC-007",
                  "SRC-008",
                  "SRC-011",
                  "SRC-015"
                ],
                "questions": [
                  {
                    "id": "canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish canonical uri, alternate, language, version, structured metadata and catalog record?",
                    "kind": "interoperability",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support canonical uri, alternate, language, version, structured metadata and catalog record?",
                    "kind": "validation",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-q03",
                    "text": "How may canonical uri, alternate, language, version, structured metadata and catalog record be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "process",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-data",
                    "name": "Canonical URI, alternate, language, version, structured metadata and catalog record data",
                    "description": "Structured data for canonical uri, alternate, language, version, structured metadata and catalog record with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-003",
                      "SRC-004",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011",
                      "SRC-015"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-record",
                    "name": "Canonical URI, alternate, language, version, structured metadata and catalog record record",
                    "description": "Versioned evidence-bearing publication record for canonical uri, alternate, language, version, structured metadata and catalog record.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus canonical-uri-alternate-language-version-structured-metadata-and-catalog-record assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-003",
                      "SRC-004",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011",
                      "SRC-015"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "crawl-search-feed-sitemap-catalog-projection-and-discovery-check",
                "name": "Crawl, search, feed, sitemap, catalog projection and discovery check",
                "description": "Records crawl, search, feed, sitemap, catalog projection and discovery check as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-003",
                  "SRC-004",
                  "SRC-007",
                  "SRC-008",
                  "SRC-011",
                  "SRC-015"
                ],
                "questions": [
                  {
                    "id": "crawl-search-feed-sitemap-catalog-projection-and-discovery-check-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish crawl, search, feed, sitemap, catalog projection and discovery check?",
                    "kind": "quality",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "crawl-search-feed-sitemap-catalog-projection-and-discovery-check-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support crawl, search, feed, sitemap, catalog projection and discovery check?",
                    "kind": "identity",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "crawl-search-feed-sitemap-catalog-projection-and-discovery-check-q03",
                    "text": "How may crawl, search, feed, sitemap, catalog projection and discovery check be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "decision",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "crawl-search-feed-sitemap-catalog-projection-and-discovery-check-data",
                    "name": "Crawl, search, feed, sitemap, catalog projection and discovery check data",
                    "description": "Structured data for crawl, search, feed, sitemap, catalog projection and discovery check with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-003",
                      "SRC-004",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011",
                      "SRC-015"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "crawl-search-feed-sitemap-catalog-projection-and-discovery-check-record",
                    "name": "Crawl, search, feed, sitemap, catalog projection and discovery check record",
                    "description": "Versioned evidence-bearing publication record for crawl, search, feed, sitemap, catalog projection and discovery check.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus crawl-search-feed-sitemap-catalog-projection-and-discovery-check assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-003",
                      "SRC-004",
                      "SRC-007",
                      "SRC-008",
                      "SRC-011",
                      "SRC-015"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          },
          {
            "id": "feeds-hubs-subscribers-and-propagation",
            "name": "Feeds, hubs, subscribers and propagation",
            "description": "Groups publication context for feeds, hubs, subscribers and propagation.",
            "source_refs": [
              "SRC-001",
              "SRC-003",
              "SRC-006"
            ],
            "findings": [
              {
                "id": "atom-activitystreams-feed-entry-activity-order-and-announcement",
                "name": "Atom and ActivityStreams feed, entry, activity, order and announcement",
                "description": "Records atom and activitystreams feed, entry, activity, order and announcement as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-003",
                  "SRC-006"
                ],
                "questions": [
                  {
                    "id": "atom-activitystreams-feed-entry-activity-order-and-announcement-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish atom and activitystreams feed, entry, activity, order and announcement?",
                    "kind": "interoperability",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "atom-activitystreams-feed-entry-activity-order-and-announcement-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support atom and activitystreams feed, entry, activity, order and announcement?",
                    "kind": "authority",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "atom-activitystreams-feed-entry-activity-order-and-announcement-q03",
                    "text": "How may atom and activitystreams feed, entry, activity, order and announcement be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "temporal",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "atom-activitystreams-feed-entry-activity-order-and-announcement-data",
                    "name": "Atom and ActivityStreams feed, entry, activity, order and announcement data",
                    "description": "Structured data for atom and activitystreams feed, entry, activity, order and announcement with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-001",
                      "SRC-003",
                      "SRC-006"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "atom-activitystreams-feed-entry-activity-order-and-announcement-record",
                    "name": "Atom and ActivityStreams feed, entry, activity, order and announcement record",
                    "description": "Versioned evidence-bearing publication record for atom and activitystreams feed, entry, activity, order and announcement.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus atom-activitystreams-feed-entry-activity-order-and-announcement assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-003",
                      "SRC-006"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "websub-topic-hub-subscription-notification-verification-and-propagation",
                "name": "WebSub topic, hub, subscription, notification, verification and propagation",
                "description": "Records websub topic, hub, subscription, notification, verification and propagation as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-003",
                  "SRC-006"
                ],
                "questions": [
                  {
                    "id": "websub-topic-hub-subscription-notification-verification-and-propagation-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish websub topic, hub, subscription, notification, verification and propagation?",
                    "kind": "state",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "websub-topic-hub-subscription-notification-verification-and-propagation-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support websub topic, hub, subscription, notification, verification and propagation?",
                    "kind": "relationship",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "websub-topic-hub-subscription-notification-verification-and-propagation-q03",
                    "text": "How may websub topic, hub, subscription, notification, verification and propagation be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "composition",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "websub-topic-hub-subscription-notification-verification-and-propagation-data",
                    "name": "WebSub topic, hub, subscription, notification, verification and propagation data",
                    "description": "Structured data for websub topic, hub, subscription, notification, verification and propagation with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-001",
                      "SRC-003",
                      "SRC-006"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "websub-topic-hub-subscription-notification-verification-and-propagation-record",
                    "name": "WebSub topic, hub, subscription, notification, verification and propagation record",
                    "description": "Versioned evidence-bearing publication record for websub topic, hub, subscription, notification, verification and propagation.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus websub-topic-hub-subscription-notification-verification-and-propagation assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-003",
                      "SRC-006"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          }
        ]
      },
      {
        "id": "post-publication-observation-correction-and-governed-change",
        "name": "Post-publication observation, correction and governed change",
        "description": "Groups governed context for post-publication observation, correction and governed change.",
        "rationale": "Observed quality and governed change preserve what audiences could see and why each successor state exists.",
        "source_refs": [
          "SRC-001",
          "SRC-002",
          "SRC-003",
          "SRC-004",
          "SRC-005",
          "SRC-007",
          "SRC-009",
          "SRC-010",
          "SRC-014"
        ],
        "layers": [
          {
            "id": "availability-reach-feedback-and-quality-observation",
            "name": "Availability, reach, feedback and quality observation",
            "description": "Groups publication context for availability, reach, feedback and quality observation.",
            "source_refs": [
              "SRC-004",
              "SRC-005",
              "SRC-009",
              "SRC-010",
              "SRC-014"
            ],
            "findings": [
              {
                "id": "availability-readability-accessibility-integrity-freshness-and-rendering-observation",
                "name": "Availability, readability, accessibility, integrity, freshness and rendering observation",
                "description": "Records availability, readability, accessibility, integrity, freshness and rendering observation as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-004",
                  "SRC-005",
                  "SRC-009",
                  "SRC-010",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "availability-readability-accessibility-integrity-freshness-and-rendering-observation-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish availability, readability, accessibility, integrity, freshness and rendering observation?",
                    "kind": "measurement",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "availability-readability-accessibility-integrity-freshness-and-rendering-observation-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support availability, readability, accessibility, integrity, freshness and rendering observation?",
                    "kind": "provenance",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "availability-readability-accessibility-integrity-freshness-and-rendering-observation-q03",
                    "text": "How may availability, readability, accessibility, integrity, freshness and rendering observation be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "evidence",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "availability-readability-accessibility-integrity-freshness-and-rendering-observation-data",
                    "name": "Availability, readability, accessibility, integrity, freshness and rendering observation data",
                    "description": "Structured data for availability, readability, accessibility, integrity, freshness and rendering observation with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-009",
                      "SRC-010",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "availability-readability-accessibility-integrity-freshness-and-rendering-observation-record",
                    "name": "Availability, readability, accessibility, integrity, freshness and rendering observation record",
                    "description": "Versioned evidence-bearing publication record for availability, readability, accessibility, integrity, freshness and rendering observation.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus availability-readability-accessibility-integrity-freshness-and-rendering-observation assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-009",
                      "SRC-010",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "analytics-engagement-feedback-moderation-method-limit-and-caveat-reference",
                "name": "Analytics, engagement, feedback, moderation, method, limit and caveat reference",
                "description": "Records analytics, engagement, feedback, moderation, method, limit and caveat reference as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-004",
                  "SRC-005",
                  "SRC-009",
                  "SRC-010",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish analytics, engagement, feedback, moderation, method, limit and caveat reference?",
                    "kind": "quality",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support analytics, engagement, feedback, moderation, method, limit and caveat reference?",
                    "kind": "process",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-q03",
                    "text": "How may analytics, engagement, feedback, moderation, method, limit and caveat reference be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "interoperability",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-data",
                    "name": "Analytics, engagement, feedback, moderation, method, limit and caveat reference data",
                    "description": "Structured data for analytics, engagement, feedback, moderation, method, limit and caveat reference with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-009",
                      "SRC-010",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-record",
                    "name": "Analytics, engagement, feedback, moderation, method, limit and caveat reference record",
                    "description": "Versioned evidence-bearing publication record for analytics, engagement, feedback, moderation, method, limit and caveat reference.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus analytics-engagement-feedback-moderation-method-limit-and-caveat-reference assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-009",
                      "SRC-010",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          },
          {
            "id": "update-correction-retraction-withdrawal-and-takedown",
            "name": "Update, correction, retraction, withdrawal and takedown",
            "description": "Groups publication context for update, correction, retraction, withdrawal and takedown.",
            "source_refs": [
              "SRC-001",
              "SRC-002",
              "SRC-003",
              "SRC-005",
              "SRC-007",
              "SRC-009",
              "SRC-014"
            ],
            "findings": [
              {
                "id": "change-class-reason-authority-affected-version-distribution-and-effective-time",
                "name": "Change class, reason, authority, affected version, distribution and effective time",
                "description": "Records change class, reason, authority, affected version, distribution and effective time as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-003",
                  "SRC-005",
                  "SRC-007",
                  "SRC-009",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "change-class-reason-authority-affected-version-distribution-and-effective-time-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish change class, reason, authority, affected version, distribution and effective time?",
                    "kind": "lifecycle",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "change-class-reason-authority-affected-version-distribution-and-effective-time-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support change class, reason, authority, affected version, distribution and effective time?",
                    "kind": "decision",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "change-class-reason-authority-affected-version-distribution-and-effective-time-q03",
                    "text": "How may change class, reason, authority, affected version, distribution and effective time be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "quality",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "change-class-reason-authority-affected-version-distribution-and-effective-time-data",
                    "name": "Change class, reason, authority, affected version, distribution and effective time data",
                    "description": "Structured data for change class, reason, authority, affected version, distribution and effective time with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-003",
                      "SRC-005",
                      "SRC-007",
                      "SRC-009",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "change-class-reason-authority-affected-version-distribution-and-effective-time-record",
                    "name": "Change class, reason, authority, affected version, distribution and effective time record",
                    "description": "Versioned evidence-bearing publication record for change class, reason, authority, affected version, distribution and effective time.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus change-class-reason-authority-affected-version-distribution-and-effective-time assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-003",
                      "SRC-005",
                      "SRC-007",
                      "SRC-009",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check",
                "name": "Correction, retraction, withdrawal, takedown notice, replacement and propagation check",
                "description": "Records correction, retraction, withdrawal, takedown notice, replacement and propagation check as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-003",
                  "SRC-005",
                  "SRC-007",
                  "SRC-009",
                  "SRC-014"
                ],
                "questions": [
                  {
                    "id": "correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish correction, retraction, withdrawal, takedown notice, replacement and propagation check?",
                    "kind": "event",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support correction, retraction, withdrawal, takedown notice, replacement and propagation check?",
                    "kind": "temporal",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-q03",
                    "text": "How may correction, retraction, withdrawal, takedown notice, replacement and propagation check be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "state",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-data",
                    "name": "Correction, retraction, withdrawal, takedown notice, replacement and propagation check data",
                    "description": "Structured data for correction, retraction, withdrawal, takedown notice, replacement and propagation check with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-003",
                      "SRC-005",
                      "SRC-007",
                      "SRC-009",
                      "SRC-014"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-record",
                    "name": "Correction, retraction, withdrawal, takedown notice, replacement and propagation check record",
                    "description": "Versioned evidence-bearing publication record for correction, retraction, withdrawal, takedown notice, replacement and propagation check.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-003",
                      "SRC-005",
                      "SRC-007",
                      "SRC-009",
                      "SRC-014"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          }
        ]
      },
      {
        "id": "lifecycle-provenance-retention-interoperability-and-agents",
        "name": "Lifecycle, provenance, retention, interoperability and agents",
        "description": "Groups governed context for lifecycle, provenance, retention, interoperability and agents.",
        "rationale": "Event history, policy-controlled retention and safe projections keep publication memory accountable across systems.",
        "source_refs": [
          "SRC-001",
          "SRC-002",
          "SRC-004",
          "SRC-005",
          "SRC-008",
          "SRC-009",
          "SRC-012",
          "SRC-013"
        ],
        "layers": [
          {
            "id": "lifecycle-events-provenance-and-audit",
            "name": "Lifecycle events, provenance and audit",
            "description": "Groups publication context for lifecycle events, provenance and audit.",
            "source_refs": [
              "SRC-001",
              "SRC-002",
              "SRC-009",
              "SRC-012"
            ],
            "findings": [
              {
                "id": "planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event",
                "name": "Planned, submitted, reviewed, approved, scheduled, released, changed and archived event",
                "description": "Records planned, submitted, reviewed, approved, scheduled, released, changed and archived event as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-009",
                  "SRC-012"
                ],
                "questions": [
                  {
                    "id": "planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish planned, submitted, reviewed, approved, scheduled, released, changed and archived event?",
                    "kind": "event",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support planned, submitted, reviewed, approved, scheduled, released, changed and archived event?",
                    "kind": "composition",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-q03",
                    "text": "How may planned, submitted, reviewed, approved, scheduled, released, changed and archived event be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "measurement",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-data",
                    "name": "Planned, submitted, reviewed, approved, scheduled, released, changed and archived event data",
                    "description": "Structured data for planned, submitted, reviewed, approved, scheduled, released, changed and archived event with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-009",
                      "SRC-012"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-record",
                    "name": "Planned, submitted, reviewed, approved, scheduled, released, changed and archived event record",
                    "description": "Versioned evidence-bearing publication record for planned, submitted, reviewed, approved, scheduled, released, changed and archived event.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-009",
                      "SRC-012"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference",
                "name": "Actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference",
                "description": "Records actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-001",
                  "SRC-002",
                  "SRC-009",
                  "SRC-012"
                ],
                "questions": [
                  {
                    "id": "actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference?",
                    "kind": "provenance",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference?",
                    "kind": "evidence",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-q03",
                    "text": "How may actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "lifecycle",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-data",
                    "name": "Actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference data",
                    "description": "Structured data for actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "1",
                    "required": true,
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-009",
                      "SRC-012"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-record",
                    "name": "Actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference record",
                    "description": "Versioned evidence-bearing publication record for actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-001",
                      "SRC-002",
                      "SRC-009",
                      "SRC-012"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          },
          {
            "id": "retention-projection-and-safe-agent-operations",
            "name": "Retention, projection and safe agent operations",
            "description": "Groups publication context for retention, projection and safe agent operations.",
            "source_refs": [
              "SRC-004",
              "SRC-005",
              "SRC-008",
              "SRC-009",
              "SRC-012",
              "SRC-013"
            ],
            "findings": [
              {
                "id": "retention-hold-archive-disposition-tombstone-and-non-cascade-rule",
                "name": "Retention, hold, archive, disposition, tombstone and non-cascade rule",
                "description": "Records retention, hold, archive, disposition, tombstone and non-cascade rule as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-004",
                  "SRC-005",
                  "SRC-008",
                  "SRC-009",
                  "SRC-012",
                  "SRC-013"
                ],
                "questions": [
                  {
                    "id": "retention-hold-archive-disposition-tombstone-and-non-cascade-rule-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish retention, hold, archive, disposition, tombstone and non-cascade rule?",
                    "kind": "retention",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "retention-hold-archive-disposition-tombstone-and-non-cascade-rule-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support retention, hold, archive, disposition, tombstone and non-cascade rule?",
                    "kind": "interoperability",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "retention-hold-archive-disposition-tombstone-and-non-cascade-rule-q03",
                    "text": "How may retention, hold, archive, disposition, tombstone and non-cascade rule be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "event",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "retention-hold-archive-disposition-tombstone-and-non-cascade-rule-data",
                    "name": "Retention, hold, archive, disposition, tombstone and non-cascade rule data",
                    "description": "Structured data for retention, hold, archive, disposition, tombstone and non-cascade rule with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-008",
                      "SRC-009",
                      "SRC-012",
                      "SRC-013"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "retention-hold-archive-disposition-tombstone-and-non-cascade-rule-record",
                    "name": "Retention, hold, archive, disposition, tombstone and non-cascade rule record",
                    "description": "Versioned evidence-bearing publication record for retention, hold, archive, disposition, tombstone and non-cascade rule.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus retention-hold-archive-disposition-tombstone-and-non-cascade-rule assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-008",
                      "SRC-009",
                      "SRC-012",
                      "SRC-013"
                    ]
                  }
                ],
                "inline_only_rationale": null
              },
              {
                "id": "mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability",
                "name": "Mapping loss, agent authority, idempotency, dry-run, post-check and contestability",
                "description": "Records mapping loss, agent authority, idempotency, dry-run, post-check and contestability as source-qualified publication context while preserving external master ownership and separating instruction, delivery and observation.",
                "source_refs": [
                  "SRC-004",
                  "SRC-005",
                  "SRC-008",
                  "SRC-009",
                  "SRC-012",
                  "SRC-013"
                ],
                "questions": [
                  {
                    "id": "mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-q01",
                    "text": "What stable identities, classes, values and explicit unknowns establish mapping loss, agent authority, idempotency, dry-run, post-check and contestability?",
                    "kind": "security",
                    "answer_data": [
                      "identities and classifications",
                      "declared values and states",
                      "explicit unknowns"
                    ]
                  },
                  {
                    "id": "mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-q02",
                    "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support mapping loss, agent authority, idempotency, dry-run, post-check and contestability?",
                    "kind": "quality",
                    "answer_data": [
                      "authority and source",
                      "method and evidence",
                      "times, confidence and limits"
                    ]
                  },
                  {
                    "id": "mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-q03",
                    "text": "How may mapping loss, agent authority, idempotency, dry-run, post-check and contestability be validated, challenged, corrected, related, retained or disposed without losing history?",
                    "kind": "retention",
                    "answer_data": [
                      "validation and challenge",
                      "correction and relationships",
                      "retention and disposition"
                    ]
                  }
                ],
                "data_elements": [
                  {
                    "id": "mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-data",
                    "name": "Mapping loss, agent authority, idempotency, dry-run, post-check and contestability data",
                    "description": "Structured data for mapping loss, agent authority, idempotency, dry-run, post-check and contestability with authority, time, state, evidence and access marking.",
                    "value_kind": "collection",
                    "cardinality": "0..n",
                    "required": false,
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-008",
                      "SRC-009",
                      "SRC-012",
                      "SRC-013"
                    ]
                  }
                ],
                "artifacts": [
                  {
                    "id": "mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-record",
                    "name": "Mapping loss, agent authority, idempotency, dry-run, post-check and contestability record",
                    "description": "Versioned evidence-bearing publication record for mapping loss, agent authority, idempotency, dry-run, post-check and contestability.",
                    "media_or_form": [
                      "logical publication assertion",
                      "instruction, decision, event, representation or evidence record"
                    ],
                    "serial": true,
                    "identity_strategy": "Publication case ID plus mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability assertion or event ID; title, date, URL and digest never identify the publication case alone.",
                    "source_refs": [
                      "SRC-004",
                      "SRC-005",
                      "SRC-008",
                      "SRC-009",
                      "SRC-012",
                      "SRC-013"
                    ]
                  }
                ],
                "inline_only_rationale": null
              }
            ]
          }
        ]
      }
    ]
  },
  "functions": [
    {
      "id": "register-publication-case",
      "name": "Register publication case",
      "description": "Governed operation to register publication case with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "mandate",
        "target content reference",
        "scope",
        "owner"
      ],
      "outputs": [
        "publication case root"
      ],
      "preconditions": [
        "identity, boundary and authority pass"
      ],
      "effects": [
        "a bounded publication operation exists"
      ],
      "source_refs": [
        "SRC-002",
        "SRC-007",
        "SRC-009"
      ]
    },
    {
      "id": "bind-content-release",
      "name": "Bind content release and metadata snapshot",
      "description": "Governed operation to bind content release and metadata snapshot with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "publication case",
        "content and edition references",
        "metadata"
      ],
      "outputs": [
        "immutable release binding"
      ],
      "preconditions": [
        "master references, language and version pass"
      ],
      "effects": [
        "the exact intended revision and metadata are attributable"
      ],
      "source_refs": [
        "SRC-003",
        "SRC-007",
        "SRC-008",
        "SRC-011"
      ]
    },
    {
      "id": "collect-clearances",
      "name": "Collect publication clearances",
      "description": "Governed operation to collect publication clearances with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "release binding",
        "rights policy",
        "review requirements"
      ],
      "outputs": [
        "clearance assertions"
      ],
      "preconditions": [
        "independent authorities and evidence pass"
      ],
      "effects": [
        "editorial, rights, privacy and accessibility states remain separate"
      ],
      "source_refs": [
        "SRC-010",
        "SRC-013",
        "SRC-014"
      ]
    },
    {
      "id": "review-and-decide",
      "name": "Review and decide",
      "description": "Governed operation to review and decide with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "release binding",
        "reviews",
        "clearances"
      ],
      "outputs": [
        "publication decision"
      ],
      "preconditions": [
        "decision authority, exceptions and evidence pass"
      ],
      "effects": [
        "approval or rejection is versioned and contestable"
      ],
      "source_refs": [
        "SRC-009",
        "SRC-014"
      ]
    },
    {
      "id": "issue-release-instruction",
      "name": "Issue release instruction and package",
      "description": "Governed operation to issue release instruction and package with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "approved binding",
        "schedule",
        "package manifest"
      ],
      "outputs": [
        "immutable release instruction"
      ],
      "preconditions": [
        "embargo, integrity, representation and authority pass"
      ],
      "effects": [
        "an executable instruction exists without claiming availability"
      ],
      "source_refs": [
        "SRC-002",
        "SRC-004",
        "SRC-008",
        "SRC-010"
      ]
    },
    {
      "id": "publish-distribute-and-verify",
      "name": "Publish, distribute and verify",
      "description": "Governed operation to publish, distribute and verify with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "release instruction",
        "channels",
        "endpoints"
      ],
      "outputs": [
        "delivery and availability evidence"
      ],
      "preconditions": [
        "idempotency, response and independent observation pass"
      ],
      "effects": [
        "origin and downstream states are recorded separately"
      ],
      "source_refs": [
        "SRC-001",
        "SRC-002",
        "SRC-004",
        "SRC-005"
      ]
    },
    {
      "id": "announce-and-syndicate",
      "name": "Announce and syndicate",
      "description": "Governed operation to announce and syndicate with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "released resource",
        "feed",
        "hub policy"
      ],
      "outputs": [
        "feed entries, activities and notifications"
      ],
      "preconditions": [
        "canonical identity, ordering and subscription verification pass"
      ],
      "effects": [
        "propagation is observable without redefining origin authority"
      ],
      "source_refs": [
        "SRC-001",
        "SRC-003",
        "SRC-006"
      ]
    },
    {
      "id": "observe-publication-quality",
      "name": "Observe publication quality and reach",
      "description": "Governed operation to observe publication quality and reach with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "publication case",
        "observation plan",
        "accessible endpoints"
      ],
      "outputs": [
        "qualified observations"
      ],
      "preconditions": [
        "method, time, evidence and caveats pass"
      ],
      "effects": [
        "availability, accessibility, integrity and reach remain measured claims"
      ],
      "source_refs": [
        "SRC-004",
        "SRC-005",
        "SRC-010"
      ]
    },
    {
      "id": "change-or-remove-publication",
      "name": "Correct, retract, withdraw or take down",
      "description": "Governed operation to correct, retract, withdraw or take down with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "released state",
        "change authority",
        "reason",
        "affected scope"
      ],
      "outputs": [
        "successor instruction and notice"
      ],
      "preconditions": [
        "change class, preservation, propagation and post-check pass"
      ],
      "effects": [
        "history survives and downstream change is verified separately"
      ],
      "source_refs": [
        "SRC-001",
        "SRC-002",
        "SRC-005",
        "SRC-007",
        "SRC-009"
      ]
    },
    {
      "id": "project-retain-and-audit",
      "name": "Project, retain and audit",
      "description": "Governed operation to project, retain and audit with attributable evidence and no hidden master-system mutation.",
      "inputs": [
        "publication revision",
        "target profile",
        "purpose",
        "policy"
      ],
      "outputs": [
        "projection or disposition event"
      ],
      "preconditions": [
        "mapping loss, hold, access and idempotency pass"
      ],
      "effects": [
        "publication context remains interoperable and accountable"
      ],
      "source_refs": [
        "SRC-004",
        "SRC-008",
        "SRC-009",
        "SRC-012",
        "SRC-013"
      ]
    }
  ],
  "composition": [
    {
      "target": "WM-MED-003 Publication / Edition",
      "relation": "CHILD",
      "purpose": "Candidate inheritance of edition and publication identity scaffolding; no approved relation edge exists.",
      "required": false,
      "source_refs": [
        "SRC-003",
        "SRC-007",
        "SRC-008"
      ]
    },
    {
      "target": "Content, Creative Work, Document, Dataset, Edition, Revision, Translation and Rendition models",
      "relation": "REFERENCE",
      "purpose": "Bind the exact release target and representations while authoritative masters retain identity and lifecycle.",
      "required": true,
      "source_refs": [
        "SRC-002",
        "SRC-003",
        "SRC-007",
        "SRC-008",
        "SRC-009"
      ]
    },
    {
      "target": "Person, Organization, Role, Channel, Platform, Rights, Licence and Policy models",
      "relation": "REFERENCE",
      "purpose": "Bind actors, authority, delivery routes and normative constraints without absorbing their masters.",
      "required": true,
      "source_refs": [
        "SRC-004",
        "SRC-007",
        "SRC-010",
        "SRC-013"
      ]
    },
    {
      "target": "Communication, Notification, Analytics, Metric, Audit and Record models",
      "relation": "REFERENCE",
      "purpose": "Bind announcements, observations and accountable evidence with no lifecycle cascade.",
      "required": false,
      "source_refs": [
        "SRC-001",
        "SRC-006",
        "SRC-009"
      ]
    },
    {
      "target": "ActivityStreams, Atom, HTTP, WebSub, DCMI, DCAT, PROV-O, WCAG, BCP 47, ODRL and Web Annotation",
      "relation": "ALIGN",
      "purpose": "Project version-pinned protocol, metadata, provenance, accessibility, language, rights and annotation views with declared loss.",
      "required": false,
      "source_refs": [
        "SRC-001",
        "SRC-002",
        "SRC-003",
        "SRC-004",
        "SRC-005",
        "SRC-006",
        "SRC-007",
        "SRC-008",
        "SRC-009",
        "SRC-010",
        "SRC-011",
        "SRC-013",
        "SRC-014"
      ]
    }
  ],
  "serviceLayers": {
    "dimension": {
      "owner_package_requirements": [
        "Dimension owner and publication mandate",
        "Content, edition, organization, person, role, channel, platform, rights, licence, communication, analytics, record and policy registries",
        "Master mappings for content, editions, revisions, renditions, translations, actors, channels, endpoints and rights",
        "Editorial, release, correction, access, privacy, retention and agent policies"
      ],
      "namespace_guidance": "Mint publication-case, release-instruction, delivery, observation, change-notice and lifecycle-event IDs; preserve every external master identifier.",
      "registry_links": [
        "https://ver.cy/models/",
        "https://ver.cy/model-agent-protocol.md"
      ]
    },
    "canon_and_patch": {
      "canonicalization_rules": [
        "Canonicalize by authoritative master-system publication-case identifier, scope profile and lineage head, never title, URL, date or digest.",
        "Keep content revision, edition, representation, instruction, delivery, observed availability and correction state distinct."
      ],
      "patch_rules": [
        "Extensions declare scope, authority, rights, lifecycle, access and interoperability effects.",
        "Released instructions, decisions, delivery evidence and change notices are immutable; corrections create successors.",
        "Never silently change target revision, authority, embargo, canonical location, rights, observed result or retention."
      ],
      "compatibility_rules": [
        "Ignore additive fields only when identity, boundary, authority, content binding, lifecycle, evidence and provenance survive.",
        "Protocol projections pin versions and declare information loss."
      ]
    },
    "artifact_rules": {
      "identity_priority": [
        "Authoritative master-system publication-case identifier qualified by source and profile.",
        "Governed globally resolvable publication-case IRI.",
        "Dimension UUID when neither preceding identifier exists."
      ],
      "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; separate scheduled, effective, decision, release, delivery, observation, change, ingestion and knowledge times.",
      "serial_naming_rule": "Use {publication-case-id}--{release-or-change-id}--{artifact-kind}--{assertion-or-event-id}.",
      "integrity_rule": "Store digest, media type, case and release binding, source versions, actor, event and knowledge times, access marking and provenance."
    },
    "policies": [
      "The publication case is not a Content, Creative Work, Document, Publication, Edition, Person, Organization, Role, Channel, Platform, Rights, Licence, Translation, Rendition, Dataset, Communication, Analytics, Audit or Record master.",
      "Draft, approval, release instruction, origin delivery, downstream propagation, availability observation and change notice remain separate.",
      "Publication ownership never transfers or cascades ownership of referenced masters.",
      "Agents cannot publish, disclose protected content, waive rights, retract, take down or dispose records without delegated authority."
    ],
    "crud": {
      "read": [
        "Resolve access purpose, case profile, policies, target bindings, decisions, instructions, deliveries, observations, changes, exceptions and holds."
      ],
      "create": [
        "Bind stable case identity, boundary, owner, mandate, profile and authoritative master mappings before review or release."
      ],
      "update": [
        "Append successor decisions, instructions, delivery attempts, observations, notices and lifecycle events with authority, reason, event time, knowledge time and expected revision."
      ],
      "delete": [
        "Apply publication, privacy, legal-hold and records retention policy; retire or tombstone the case separately and never cascade deletion to external masters."
      ]
    },
    "roles": [
      {
        "name": "Publication owner",
        "responsibilities": [
          "Own purpose, scope, mandate and lifecycle."
        ]
      },
      {
        "name": "Editor and workflow steward",
        "responsibilities": [
          "Own intake, review stages, metadata and decision evidence."
        ]
      },
      {
        "name": "Rights and policy steward",
        "responsibilities": [
          "Own licence, privacy, embargo and legal clearance assertions."
        ]
      },
      {
        "name": "Accessibility and quality reviewer",
        "responsibilities": [
          "Own test methods, findings, exceptions and conformance evidence."
        ]
      },
      {
        "name": "Release manager",
        "responsibilities": [
          "Own immutable instructions, packages, schedules and rollback controls."
        ]
      },
      {
        "name": "Channel and distribution steward",
        "responsibilities": [
          "Own endpoint bindings, delivery attempts and propagation checks."
        ]
      },
      {
        "name": "Correction and takedown authority",
        "responsibilities": [
          "Authorize successor notices and preservation behavior."
        ]
      },
      {
        "name": "Records and security steward",
        "responsibilities": [
          "Own protected views, holds, retention, disclosure and auditability."
        ]
      }
    ],
    "access": {
      "default_rule": "Deny embargoed content, personal data, confidential drafts, credentials, unpublished endpoints, legal review and restricted analytics unless a purpose-bound policy permits the minimum necessary view.",
      "scopes": [
        "bundle",
        "layer",
        "finding",
        "artifact"
      ],
      "exceptions": [
        "Declared publisher, regulator, auditor, emergency, court or rights-holder access must cite authority, be time-limited, scoped and logged."
      ],
      "audit_requirements": [
        "Log actor, agent, role, purpose, publication case, operation, authority, policy, RFC 3339 time, affected fields, source revision and outcome without unnecessary protected content."
      ]
    },
    "agents_bootstrap": {
      "filename": "AGENTS.md",
      "required_fields": [
        "Name",
        "Type",
        "Specification URL",
        "Storage type URL",
        "Interface URL",
        "Processes URL"
      ],
      "read_order": [
        "Read Dimension publication, content, rights, privacy, security, records and agent policies.",
        "Read this model and linked content, edition, actor, channel, policy, communication, analytics and audit models before mutation."
      ]
    }
  },
  "coverage": {
    "claim": "WM-ACT-044 covers one governed content-publication case from target binding, editorial review and clearances through immutable release instruction, packaging, origin and downstream delivery, discovery, syndication, availability observation, correction, retraction, withdrawal, takedown, retention and audit. It excludes independent content, edition, actor, platform, channel, rights, communication, analytics and record master lifecycles. Known gaps are platform- and sector-specific profiles, jurisdictional publication duties, an approved WM-MED-003 relation and independent external review after one 120-second timeout each from Claude Sonnet and Grok 4.6.",
    "confidence": "medium",
    "checklist": [
      {
        "dimension": "identity",
        "status": "covered",
        "notes": "Identity is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "classification and definition",
        "status": "covered",
        "notes": "Classification and definition is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "direct properties",
        "status": "gap",
        "notes": "Direct properties is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "recognition and observation",
        "status": "covered",
        "notes": "Recognition and observation is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "capabilities and possible actions",
        "status": "covered",
        "notes": "Capabilities and possible actions is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "composition",
        "status": "covered",
        "notes": "Composition is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "lifecycle",
        "status": "covered",
        "notes": "Lifecycle is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "relationships",
        "status": "covered",
        "notes": "Relationships is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "temporal",
        "status": "covered",
        "notes": "Temporal is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "spatial",
        "status": "gap",
        "notes": "Spatial is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "provenance",
        "status": "covered",
        "notes": "Provenance is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "ownership and stewardship",
        "status": "covered",
        "notes": "Ownership and stewardship is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "validation and quality",
        "status": "covered",
        "notes": "Validation and quality is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "access and privacy",
        "status": "covered",
        "notes": "Access and privacy is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "retention and deletion",
        "status": "covered",
        "notes": "Retention and deletion is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      },
      {
        "dimension": "interoperability",
        "status": "covered",
        "notes": "Interoperability is explicit; external masters, platform profiles and unresolved candidate relations remain held where applicable."
      }
    ],
    "known_omissions": [
      "Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.",
      "The Publication / Edition parent is candidate registry metadata, not an approved relation edge.",
      "Platform-specific APIs, newsroom standards, scholarly publishing rules, app-store workflows and jurisdictional notice duties require separate profiles.",
      "Sitemaps describe discovery hints and do not prove crawling, indexing, ranking or public reach."
    ],
    "conflicts": [
      "Editorial approval, rights clearance, release instruction, successful delivery and public availability are not interchangeable.",
      "A content resource, edition, revision, representation, rendition, canonical URI and delivery URL can overlap but retain different identity and lifecycle rules.",
      "Correction, update, retraction, withdrawal, takedown, unpublish, tombstone and erasure have different authority and preservation effects."
    ],
    "regional_assumptions": [
      "Copyright, privacy, accessibility, retention and takedown duties depend on jurisdiction, audience and channel.",
      "Platform acceptance and HTTP success do not establish legal publication or audience receipt.",
      "Required notices, preservation periods and correction practices vary by sector."
    ],
    "adversarial_checks": [
      "Reject a case without stable identity, target revision, owner, mandate, profile and lineage head.",
      "Reject approval represented as public availability, an HTTP acknowledgement represented as audience reach, or syndication represented as authoritative origin publication.",
      "Reject silent overwrite of decisions, instructions, evidence, corrections or retractions.",
      "Reject autonomous publication, protected disclosure, rights waiver, takedown or disposal outside delegated authority.",
      "Reject timestamps without seconds and an explicit RFC 3339 offset."
    ]
  },
  "researchAdjudication": {
    "providerMode": "single-provider-waiver",
    "activeProviders": [
      "codex"
    ],
    "waivedProviders": [
      "claude",
      "grok"
    ],
    "providerPolicy": {
      "contract_version": "1.0.0",
      "mode": "single-provider-waiver",
      "effective_at": "2026-09-06T00:00:00Z",
      "scope": "Canonical single-stream subject-model research after the six-workstream consolidation",
      "active_providers": [
        "codex"
      ],
      "waived_providers": [
        {
          "provider": "claude",
          "authorized_by": "repository owner",
          "authorized_at": "2026-09-06T00:00:00Z",
          "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability."
        },
        {
          "provider": "grok",
          "authorized_by": "repository owner",
          "authorized_at": "2026-09-06T00:00:00Z",
          "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result."
        }
      ],
      "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.",
      "supplemental_provider_attempts": [
        {
          "provider": "claude",
          "required": false,
          "maximum_attempts": 1,
          "failure_policy": "record-and-continue",
          "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication."
        },
        {
          "provider": "grok",
          "required": false,
          "maximum_attempts": 1,
          "failure_policy": "record-and-continue",
          "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication."
        }
      ]
    },
    "boundaryDecision": {
      "entry_kind": "aggregate",
      "status": "accepted",
      "rationale": "The publication case is a defensible aggregate root for one governed publication operation. It owns the operation identifier, target binding, decisions, instructions, attempts, observations and change history while external masters retain content, edition, actor, channel, rights and evidence identity. The frozen record-plane classifier remains standalone-mm."
    },
    "decisions": [
      {
        "concept": "Publication-case aggregate root and boundary",
        "disposition": "accepted",
        "rationale": "The scope and five boundary notes consistently separate the governed operation from content, edition, actor, platform, rights, communication, analytics and record masters. Stable case lineage and non-cascade rules permit accountable coordination without absorbing those lifecycles."
      },
      {
        "concept": "Approval, instruction, delivery and availability separation",
        "disposition": "accepted",
        "rationale": "Separate findings, artifacts and functions distinguish editorial decisions, immutable release instructions, origin and downstream delivery attempts, acknowledgements and independently timed availability observations. HTTP success and syndication are explicitly rejected as proof of audience reach or origin authority."
      },
      {
        "concept": "Correction, retraction, withdrawal and takedown succession",
        "disposition": "accepted",
        "rationale": "The governed-change layer, change-or-remove function, patch rules and lifecycle artifacts jointly define the invariant: released decisions, instructions and evidence are immutable; a correction or removal action creates a separately identified successor instruction and notice, preserves the affected release binding and records propagation verification."
      },
      {
        "concept": "Artifact identity strategy",
        "disposition": "accepted",
        "rationale": "The identity priority is an explicit policy hierarchy: use a source-qualified authoritative master-system publication-case identifier, otherwise a governed resolvable case IRI, otherwise a Dimension UUID. Namespace guidance requires minting identifiers for case, instruction, delivery, observation, notice and event records. Concrete algorithms and resolvers belong to the adopting Dimension profile rather than this format-neutral specification."
      },
      {
        "concept": "Candidate WM-MED-003 Publication / Edition parent",
        "disposition": "deferred",
        "rationale": "The candidate parent is metadata, not an approved registry edge. The model remains coherent because it requires an external edition or content binding by reference and does not claim edition ownership. Later registry work may approve inheritance or replace it with an explicit reference contract. This limits relationship-completeness claims but does not block a standalone reviewable draft."
      },
      {
        "concept": "Confidential editorial access",
        "disposition": "accepted-with-profile-hold",
        "rationale": "Default-deny access covers embargoed content, personal data, confidential drafts, credentials, legal review and restricted analytics. Access is enforceable at bundle, layer, finding and artifact scopes, exceptions require authority and audit, and eight roles separate duties. Concrete confidentiality labels and role bindings remain mandatory in the adopting Dimension policy profile."
      },
      {
        "concept": "Official standards grounding",
        "disposition": "accepted",
        "rationale": "Fifteen official primary specifications ground protocol, metadata, provenance, accessibility, language, rights, annotation, discovery and timestamp semantics. Protocol standards are not represented as editorial or legal policy, and Sitemaps is limited to a discovery projection."
      },
      {
        "concept": "Single-provider waiver and external-review absence",
        "disposition": "accepted-with-mandatory-hold",
        "rationale": "One Claude Sonnet attempt and one Grok 4.6 attempt for WM-ACT-044 each timed out after 120 seconds. The owner-approved policy permits source-grounded Codex fallback after this separate no-tools audit. Confidence remains medium and publication remains lifecycle published with assurance reviewable-draft plus a visible absence-of-external-review hold."
      }
    ],
    "publicationHolds": [
      "Absence-of-external-review hold: one Claude Sonnet attempt and one Grok 4.6 attempt for WM-ACT-044 each timed out after 120 seconds. No external result was admitted; this model remains a reviewable draft after the separate no-tools audit.",
      "Registry edge approval hold: WM-MED-003 Publication / Edition is only a candidate parent. This blocks complete relationship claims, not standalone reviewable-draft publication.",
      "Policy-profile hold: rights, privacy, accessibility, embargo, correction, takedown, retention and confidential editorial access must bind applicable jurisdictional, sector and Dimension policies before operational use.",
      "Platform-profile hold: API semantics, package formats, validators, cache behavior, feeds, hubs, indexing and downstream removal vary by channel and require version-pinned mappings with declared loss.",
      "Identity-resolution hold: the adopting Dimension must define its authoritative publication-case identifier minting authority, persistence and resolver before production writes.",
      "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft."
    ],
    "deferredResearch": [
      "Approve or reject the candidate WM-MED-003 relation and define edition-to-publication-case cardinality and lineage semantics.",
      "Add platform profiles for web CMS, social, app stores, package registries, scholarly publishing, datasets, newsrooms and private knowledge systems.",
      "Add jurisdiction and sector profiles for rights, privacy, accessibility, correction, retraction, takedown, deposit and retention duties.",
      "Define Dimension-level confidentiality labels, role bindings, identifier minting and resolution, and redacted public projection rules.",
      "Obtain supplemental Claude or Grok review and resolve any material challenge before canonical promotion."
    ]
  },
  "statistics": {
    "sources": 15,
    "bundles": 6,
    "layers": 12,
    "findings": 24,
    "questions": 72,
    "artifacts": 24,
    "functions": 10
  }
}