{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-044","code":"wm-act-044-content-publication","url":"https://ver.cy/models/wm-act-044-content-publication/","name":"Content Publication","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"aggregate","plane":"","domain":["ACT.PUB"],"industry":["Cross-industry"],"navPath":"NAV.ACT.PUB","tags":["content","publication","act.pub"],"facets":{}},"whatItIs":"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.","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":{"in":["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":["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"],"boundaries":[{"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."},{"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."},{"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."},{"neighbor":"Rights, Licence, Policy and Accessibility","distinction":"Their masters own normative rules. This model records scoped clearance assertions and evidence for one release decision."},{"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."}]},"distinguishingFeatures":["Models the act of releasing content to channels, not the content, work or edition itself.","Keeps approval, release instruction, delivery, propagation and availability as separate states.","Records corrections, retractions and takedowns as new events with notices.","Binds rights, licence and accessibility clearances to each release."],"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.","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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish publication operation type, scope, target and neighbor boundary?","id":"publication-operation-type-scope-target-and-neighbor-boundary-q01","kind":"classification"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support publication operation type, scope, target and neighbor boundary?","id":"publication-operation-type-scope-target-and-neighbor-boundary-q02","kind":"decision"},{"text":"How may publication operation type, scope, target and neighbor boundary be validated, challenged, corrected, related, retained or disposed without losing history?","id":"publication-operation-type-scope-target-and-neighbor-boundary-q03","kind":"quality"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish case identifier, source, version, predecessor, successor and lineage?","id":"case-identifier-source-version-predecessor-successor-and-lineage-q01","kind":"identity"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support case identifier, source, version, predecessor, successor and lineage?","id":"case-identifier-source-version-predecessor-successor-and-lineage-q02","kind":"temporal"},{"text":"How may case identifier, source, version, predecessor, successor and lineage be validated, challenged, corrected, related, retained or disposed without losing history?","id":"case-identifier-source-version-predecessor-successor-and-lineage-q03","kind":"state"}]}]},{"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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish publisher, editor, owner, authority, role and decision right?","id":"publisher-editor-owner-authority-role-and-decision-right-q01","kind":"authority"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support publisher, editor, owner, authority, role and decision right?","id":"publisher-editor-owner-authority-role-and-decision-right-q02","kind":"composition"},{"text":"How may publisher, editor, owner, authority, role and decision right be validated, challenged, corrected, related, retained or disposed without losing history?","id":"publisher-editor-owner-authority-role-and-decision-right-q03","kind":"measurement"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish rights, licence, embargo, privacy, legal, fact-check and accessibility clearance?","id":"rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-q01","kind":"validation"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support rights, licence, embargo, privacy, legal, fact-check and accessibility clearance?","id":"rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-q02","kind":"evidence"},{"text":"How may rights, licence, embargo, privacy, legal, fact-check and accessibility clearance be validated, challenged, corrected, related, retained or disposed without losing history?","id":"rights-licence-embargo-privacy-legal-fact-check-and-accessibility-clearance-q03","kind":"lifecycle"}]}]}]},{"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.","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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish content, edition, revision, rendition and translation reference?","id":"content-edition-revision-rendition-and-translation-reference-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support content, edition, revision, rendition and translation reference?","id":"content-edition-revision-rendition-and-translation-reference-q02","kind":"interoperability"},{"text":"How may content, edition, revision, rendition and translation reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"content-edition-revision-rendition-and-translation-reference-q03","kind":"event"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish release metadata, identifier, title, subject, language, audience and provenance snapshot?","id":"release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-q01","kind":"provenance"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support release metadata, identifier, title, subject, language, audience and provenance snapshot?","id":"release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-q02","kind":"quality"},{"text":"How may release metadata, identifier, title, subject, language, audience and provenance snapshot be validated, challenged, corrected, related, retained or disposed without losing history?","id":"release-metadata-identifier-title-subject-language-audience-and-provenance-snapshot-q03","kind":"retention"}]}]},{"id":"workflow-review-approval-and-readiness","name":"Workflow, review, approval and readiness","description":"Groups publication context for workflow, review, approval and readiness.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish editorial stage, owner, dependency, deadline, status and exception?","id":"editorial-stage-owner-dependency-deadline-status-and-exception-q01","kind":"process"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support editorial stage, owner, dependency, deadline, status and exception?","id":"editorial-stage-owner-dependency-deadline-status-and-exception-q02","kind":"state"},{"text":"How may editorial stage, owner, dependency, deadline, status and exception be validated, challenged, corrected, related, retained or disposed without losing history?","id":"editorial-stage-owner-dependency-deadline-status-and-exception-q03","kind":"security"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish review comment, check, approval, rejection, exception and evidence?","id":"review-comment-check-approval-rejection-exception-and-evidence-q01","kind":"decision"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support review comment, check, approval, rejection, exception and evidence?","id":"review-comment-check-approval-rejection-exception-and-evidence-q02","kind":"measurement"},{"text":"How may review comment, check, approval, rejection, exception and evidence be validated, challenged, corrected, related, retained or disposed without losing history?","id":"review-comment-check-approval-rejection-exception-and-evidence-q03","kind":"validation"}]}]}]},{"id":"release-packaging-channels-and-distribution","name":"Release packaging, channels and distribution","description":"Groups governed context for release packaging, channels and distribution.","layers":[{"id":"release-instruction-package-and-representations","name":"Release instruction, package and representations","description":"Groups publication context for release instruction, package and representations.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish release instruction, scheduled and effective window, embargo and authority?","id":"release-instruction-scheduled-effective-window-embargo-and-authority-q01","kind":"temporal"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support release instruction, scheduled and effective window, embargo and authority?","id":"release-instruction-scheduled-effective-window-embargo-and-authority-q02","kind":"lifecycle"},{"text":"How may release instruction, scheduled and effective window, embargo and authority be validated, challenged, corrected, related, retained or disposed without losing history?","id":"release-instruction-scheduled-effective-window-embargo-and-authority-q03","kind":"identity"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish package, format, media type, digest, rendition, manifest and accessibility?","id":"package-format-media-type-digest-rendition-manifest-and-accessibility-q01","kind":"composition"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support package, format, media type, digest, rendition, manifest and accessibility?","id":"package-format-media-type-digest-rendition-manifest-and-accessibility-q02","kind":"event"},{"text":"How may package, format, media type, digest, rendition, manifest and accessibility be validated, challenged, corrected, related, retained or disposed without losing history?","id":"package-format-media-type-digest-rendition-manifest-and-accessibility-q03","kind":"authority"}]}]},{"id":"channels-endpoints-delivery-and-acknowledgements","name":"Channels, endpoints, delivery and acknowledgements","description":"Groups publication context for channels, endpoints, delivery and acknowledgements.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish channel, platform, audience, endpoint, campaign and placement reference?","id":"channel-platform-audience-endpoint-campaign-and-placement-reference-q01","kind":"relationship"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support channel, platform, audience, endpoint, campaign and placement reference?","id":"channel-platform-audience-endpoint-campaign-and-placement-reference-q02","kind":"retention"},{"text":"How may channel, platform, audience, endpoint, campaign and placement reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"channel-platform-audience-endpoint-campaign-and-placement-reference-q03","kind":"relationship"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish delivery attempt, response, acknowledgement, uri and availability verification?","id":"delivery-attempt-response-acknowledgement-uri-and-availability-verification-q01","kind":"evidence"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support delivery attempt, response, acknowledgement, uri and availability verification?","id":"delivery-attempt-response-acknowledgement-uri-and-availability-verification-q02","kind":"security"},{"text":"How may delivery attempt, response, acknowledgement, uri and availability verification be validated, challenged, corrected, related, retained or disposed without losing history?","id":"delivery-attempt-response-acknowledgement-uri-and-availability-verification-q03","kind":"provenance"}]}]}]},{"id":"discovery-syndication-subscription-and-access","name":"Discovery, syndication, subscription and access","description":"Groups governed context for discovery, syndication, subscription and access.","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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish canonical uri, alternate, language, version, structured metadata and catalog record?","id":"canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-q01","kind":"interoperability"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support canonical uri, alternate, language, version, structured metadata and catalog record?","id":"canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-q02","kind":"validation"},{"text":"How may canonical uri, alternate, language, version, structured metadata and catalog record be validated, challenged, corrected, related, retained or disposed without losing history?","id":"canonical-uri-alternate-language-version-structured-metadata-and-catalog-record-q03","kind":"process"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish crawl, search, feed, sitemap, catalog projection and discovery check?","id":"crawl-search-feed-sitemap-catalog-projection-and-discovery-check-q01","kind":"quality"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support crawl, search, feed, sitemap, catalog projection and discovery check?","id":"crawl-search-feed-sitemap-catalog-projection-and-discovery-check-q02","kind":"identity"},{"text":"How may crawl, search, feed, sitemap, catalog projection and discovery check be validated, challenged, corrected, related, retained or disposed without losing history?","id":"crawl-search-feed-sitemap-catalog-projection-and-discovery-check-q03","kind":"decision"}]}]},{"id":"feeds-hubs-subscribers-and-propagation","name":"Feeds, hubs, subscribers and propagation","description":"Groups publication context for feeds, hubs, subscribers and propagation.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish atom and activitystreams feed, entry, activity, order and announcement?","id":"atom-activitystreams-feed-entry-activity-order-and-announcement-q01","kind":"interoperability"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support atom and activitystreams feed, entry, activity, order and announcement?","id":"atom-activitystreams-feed-entry-activity-order-and-announcement-q02","kind":"authority"},{"text":"How may atom and activitystreams feed, entry, activity, order and announcement be validated, challenged, corrected, related, retained or disposed without losing history?","id":"atom-activitystreams-feed-entry-activity-order-and-announcement-q03","kind":"temporal"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish websub topic, hub, subscription, notification, verification and propagation?","id":"websub-topic-hub-subscription-notification-verification-and-propagation-q01","kind":"state"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support websub topic, hub, subscription, notification, verification and propagation?","id":"websub-topic-hub-subscription-notification-verification-and-propagation-q02","kind":"relationship"},{"text":"How may websub topic, hub, subscription, notification, verification and propagation be validated, challenged, corrected, related, retained or disposed without losing history?","id":"websub-topic-hub-subscription-notification-verification-and-propagation-q03","kind":"composition"}]}]}]},{"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.","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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish availability, readability, accessibility, integrity, freshness and rendering observation?","id":"availability-readability-accessibility-integrity-freshness-and-rendering-observation-q01","kind":"measurement"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support availability, readability, accessibility, integrity, freshness and rendering observation?","id":"availability-readability-accessibility-integrity-freshness-and-rendering-observation-q02","kind":"provenance"},{"text":"How may availability, readability, accessibility, integrity, freshness and rendering observation be validated, challenged, corrected, related, retained or disposed without losing history?","id":"availability-readability-accessibility-integrity-freshness-and-rendering-observation-q03","kind":"evidence"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish analytics, engagement, feedback, moderation, method, limit and caveat reference?","id":"analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-q01","kind":"quality"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support analytics, engagement, feedback, moderation, method, limit and caveat reference?","id":"analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-q02","kind":"process"},{"text":"How may analytics, engagement, feedback, moderation, method, limit and caveat reference be validated, challenged, corrected, related, retained or disposed without losing history?","id":"analytics-engagement-feedback-moderation-method-limit-and-caveat-reference-q03","kind":"interoperability"}]}]},{"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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish change class, reason, authority, affected version, distribution and effective time?","id":"change-class-reason-authority-affected-version-distribution-and-effective-time-q01","kind":"lifecycle"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support change class, reason, authority, affected version, distribution and effective time?","id":"change-class-reason-authority-affected-version-distribution-and-effective-time-q02","kind":"decision"},{"text":"How may change class, reason, authority, affected version, distribution and effective time be validated, challenged, corrected, related, retained or disposed without losing history?","id":"change-class-reason-authority-affected-version-distribution-and-effective-time-q03","kind":"quality"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish correction, retraction, withdrawal, takedown notice, replacement and propagation check?","id":"correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-q01","kind":"event"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support correction, retraction, withdrawal, takedown notice, replacement and propagation check?","id":"correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-q02","kind":"temporal"},{"text":"How may correction, retraction, withdrawal, takedown notice, replacement and propagation check be validated, challenged, corrected, related, retained or disposed without losing history?","id":"correction-retraction-withdrawal-takedown-notice-replacement-and-propagation-check-q03","kind":"state"}]}]}]},{"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.","layers":[{"id":"lifecycle-events-provenance-and-audit","name":"Lifecycle events, provenance and audit","description":"Groups publication context for lifecycle events, provenance and audit.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish planned, submitted, reviewed, approved, scheduled, released, changed and archived event?","id":"planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-q01","kind":"event"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support planned, submitted, reviewed, approved, scheduled, released, changed and archived event?","id":"planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-q02","kind":"composition"},{"text":"How may planned, submitted, reviewed, approved, scheduled, released, changed and archived event be validated, challenged, corrected, related, retained or disposed without losing history?","id":"planned-submitted-reviewed-approved-scheduled-released-changed-and-archived-event-q03","kind":"measurement"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish actor, tool, source, digest, derivation, invalidation, event time, knowledge time and audit reference?","id":"actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-q01","kind":"provenance"},{"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?","id":"actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-q02","kind":"evidence"},{"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?","id":"actor-tool-source-digest-derivation-invalidation-event-time-knowledge-time-and-audit-reference-q03","kind":"lifecycle"}]}]},{"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.","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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish retention, hold, archive, disposition, tombstone and non-cascade rule?","id":"retention-hold-archive-disposition-tombstone-and-non-cascade-rule-q01","kind":"retention"},{"text":"Which authority, source, method, evidence, event time, knowledge time, confidence and limits support retention, hold, archive, disposition, tombstone and non-cascade rule?","id":"retention-hold-archive-disposition-tombstone-and-non-cascade-rule-q02","kind":"interoperability"},{"text":"How may retention, hold, archive, disposition, tombstone and non-cascade rule be validated, challenged, corrected, related, retained or disposed without losing history?","id":"retention-hold-archive-disposition-tombstone-and-non-cascade-rule-q03","kind":"event"}]},{"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.","questions":[{"text":"What stable identities, classes, values and explicit unknowns establish mapping loss, agent authority, idempotency, dry-run, post-check and contestability?","id":"mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-q01","kind":"security"},{"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?","id":"mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-q02","kind":"quality"},{"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?","id":"mapping-loss-agent-authority-idempotency-dry-run-post-check-and-contestability-q03","kind":"retention"}]}]}]}]},"agentConduct":{"may":["Package approved content with metadata for each channel.","Verify that releases arrived and render correctly.","Monitor availability and report broken or stale copies.","Prepare correction notices for editorial review."],"mustNot":["Publish without the required editorial and rights clearance.","Silently change published content without a correction notice.","Publish personal data or embargoed material.","Report syndication or reach as approval or quality.","Remove content on an unverified takedown request."],"requiresHuman":["Publication, retraction and takedown decisions.","Clearance of rights, defamation or privacy risks."]},"ethics":{"considerations":["Published content can harm reputations and privacy; corrections must be visible and timely.","Accessibility determines who can use the content.","Takedown handling must balance rights holders against freedom of expression."],"affectedParties":["Readers and audiences","People named or shown in content","Authors and rights holders"]},"owners":{"steward":"Dimension owner and publication mandate","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."]}],"masterSystems":[]},"relations":[{"target":"WM-MED-003 Publication / Edition","type":"child","note":"Candidate inheritance of edition and publication identity scaffolding; no approved relation edge exists."},{"target":"Content, Creative Work, Document, Dataset, Edition, Revision, Translation and Rendition models","type":"references","note":"Bind the exact release target and representations while authoritative masters retain identity and lifecycle."},{"target":"Person, Organization, Role, Channel, Platform, Rights, Licence and Policy models","type":"references","note":"Bind actors, authority, delivery routes and normative constraints without absorbing their masters."},{"target":"Communication, Notification, Analytics, Metric, Audit and Record models","type":"references","note":"Bind announcements, observations and accountable evidence with no lifecycle cascade."},{"target":"ActivityStreams, Atom, HTTP, WebSub, DCMI, DCAT, PROV-O, WCAG, BCP 47, ODRL and Web Annotation","type":"aligned","note":"Project version-pinned protocol, metadata, provenance, accessibility, language, rights and annotation views with declared loss."},{"target":"WM-MED-003 Publication / Edition candidate parent","type":"neighbor","note":"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."},{"target":"Content, Creative Work and Document","type":"neighbor","note":"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."},{"target":"Channel, Platform, Representation and Rendition","type":"neighbor","note":"External masters own endpoint, platform and media identities. This case stores release-specific bindings, attempts and observations without copying their inventories."},{"target":"Rights, Licence, Policy and Accessibility","type":"neighbor","note":"Their masters own normative rules. This model records scoped clearance assertions and evidence for one release decision."},{"target":"Communication, Notification, Analytics, Audit and Record","type":"neighbor","note":"Those systems own messages, measurements and records; this case binds qualified references needed to explain publication outcomes."},{"target":"WM-MED-003","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system publication-case identifier qualified by source and profile.","Governed globally resolvable publication-case IRI.","Dimension UUID when neither preceding identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A publication case has target content, a release version, channels, clearances and a release time.","It is confused with the content itself, a publication edition or a social media post."]},"capabilities":{"applicability":"required","items":["Register publication case: Governed operation to register publication case with attributable evidence and no hidden master-system mutation.","Bind content release and metadata snapshot: Governed operation to bind content release and metadata snapshot with attributable evidence and no hidden master-system mutation.","Collect publication clearances: Governed operation to collect publication clearances with attributable evidence and no hidden master-system mutation.","Review and decide: Governed operation to review and decide with attributable evidence and no hidden master-system mutation.","Issue release instruction and package: Governed operation to issue release instruction and package with attributable evidence and no hidden master-system mutation.","Publish, distribute and verify: Governed operation to publish, distribute and verify with attributable evidence and no hidden master-system mutation.","Announce and syndicate: Governed operation to announce and syndicate with attributable evidence and no hidden master-system mutation.","Observe publication quality and reach: Governed operation to observe publication quality and reach with attributable evidence and no hidden master-system mutation.","Correct, retract, withdraw or take down: Governed operation to correct, retract, withdraw or take down with attributable evidence and no hidden master-system mutation.","Project, retain and audit: Governed operation to project, retain and audit with attributable evidence and no hidden master-system mutation."]},"hazards":{"applicability":"required","items":["Defamation or privacy harm from unchecked releases.","Stale copies persisting after a correction.","Accidental early release of embargoed content."]},"interfaces":{"applicability":"required","items":["W3C WCAG 2.2.","IETF Atom (RFC 4287) and RSS 2.0 feeds.","Crossref metadata and DOI for scholarly publications.","C2PA content credentials.","Dublin Core metadata terms."]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"Activity Streams 2.0","url":"https://www.w3.org/TR/activitystreams-core/","note":"World Wide Web Consortium"},{"title":"The Atom Publishing Protocol","url":"https://www.rfc-editor.org/info/rfc5023/","note":"Internet Engineering Task Force"},{"title":"The Atom Syndication Format","url":"https://www.rfc-editor.org/info/rfc4287/","note":"Internet Engineering Task Force"},{"title":"HTTP Semantics","url":"https://www.rfc-editor.org/info/rfc9110/","note":"Internet Engineering Task Force"},{"title":"HTTP Caching","url":"https://www.rfc-editor.org/info/rfc9111/","note":"Internet Engineering Task Force"},{"title":"WebSub","url":"https://www.w3.org/TR/websub/","note":"World Wide Web Consortium"},{"title":"DCMI Metadata Terms","url":"https://www.dublincore.org/specifications/dublin-core/dcmi-terms/","note":"Dublin Core Metadata Initiative"},{"title":"Data Catalog Vocabulary DCAT Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Web Content Accessibility Guidelines WCAG 2.2","url":"https://www.w3.org/TR/WCAG22/","note":"World Wide Web Consortium"},{"title":"Tags for Identifying Languages","url":"https://www.rfc-editor.org/info/rfc5646/","note":"Internet Engineering Task Force"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/info/rfc3339/","note":"Internet Engineering Task Force"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"Web Annotation Data Model","url":"https://www.w3.org/TR/annotation-model/","note":"World Wide Web Consortium"},{"title":"Sitemaps XML format","url":"https://www.sitemaps.org/protocol.html","note":"Google, Microsoft and Yahoo"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-act-044-content-publication/spec.yaml","agents":"/models/wm-act-044-content-publication/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-044"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-act-044-content-publication/spec.yaml","ver-cy/world-models/card-supplements/wm-act-044-content-publication.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T08:34:35Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}