has disclosure policy

• CURIE: gmeow:hasDisclosurePolicy
• IRI: https://blackcatinformatics.ca/gmeow/hasDisclosurePolicy
• Category: property
• Defined by: gmeow:slices/kernel
• Box roles: CBox role, RBox role (What is this?)

Relates a value, entity, or claim to its disclosure policy — the explicit what facet of disclosure control. Domain-free (universal, like hasGranularity and hasSensitivity). NOT functional: in a multi-source merge sources may state different policies, and those claims coexist rather than force the reasoner to collapse distinct policies (Principle 9).

Structure

Property shape: object property; ? -> gmeow:DisclosurePolicy

Practical Pattern

Use gmeow:hasDisclosurePolicy from ? to gmeow:DisclosurePolicy when the relationship itself belongs in the native GMEOW graph.

Example Snippets

These snippets are generated from canonical slice examples and trimmed to the Turtle blocks where this term appears.

Sensitivity And Disclosure

• Source: slices/core/kernel/examples/sensitivity-and-disclosure.ttl
• Examples catalog: open in catalog#example-slices-core-kernel-examples-sensitivity-and-disclosure

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example: the kernel disclosure machinery (Principles 10 and 12). Any entity can
# declare HOW SENSITIVE it is (gmeow:hasSensitivity), the POLICY governing its
# release (gmeow:hasDisclosurePolicy), and WHICH CONSUMERS are eligible to receive
# it (gmeow:eligibleForConsumer → a ProjectionContext). This is the projection/
# disclosure boundary: a confidential record is never deleted, only withheld from
# the wrong consumer (P10 suppression, P12 solver/presentation split). Part-whole
# mereology (gmeow:partOf / gmeow:hasPart) and gmeow:hasDeterminacy (how crisp the
# value is) are the other kernel primitives every slice reuses.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/kernel/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .

# --- A confidential record: sensitive, internal-only, eligible only for the
#     internal archive — withheld from public consumers, not deleted.
ex:salaryRecord a gmeow:InformationObject ;
    rdfs:label                "Compensation record"@en ;
    gmeow:partOf              ex:dossier ;
    gmeow:hasSensitivity      gmeow:sensitivityConfidential ;
    gmeow:hasDisclosurePolicy gmeow:policyInternalOnly ;
    gmeow:eligibleForConsumer gmeow:consumerInternalArchive ;
    gmeow:hasDeterminacy      gmeow:determinacyCrisp .

Common Companion Terms

gmeow:DisclosurePolicy, gmeow:StandpointTenure, gmeow:coarsenTo, gmeow:displayable, gmeow:hasGranularity, gmeow:hasSensitivity, gmeow:validUntil

Cross-Cutting Concerns

disclosure and suppression

External Equivalences

Equivalent or closely aligned targets: dpv

Linkages

Generated from the canonical mapping DSL. SSSOM files are the generated public interchange form for term equivalences.

Term Equivalences

Usage Advice

Use when

• Use to record the release posture of a value or claim — the what facet of disclosure control that the projection layer consults before emitting it to any consumer.

Avoid when

• Avoid using it to carry the sensitivity level (gmeow:hasSensitivity) or the eligible audience (gmeow:eligibleForConsumer); the policy is the posture, not the classification or the audience, and competing source postures must coexist.

How to use

• Point the value at a gmeow:DisclosurePolicy individual and let the solver combine it with sensitivity, consumer eligibility, and source independence to make the final release decision.

Examples

• ex:rumouredClaim gmeow:hasDisclosurePolicy gmeow:policyPublicOnlyWithIndependentSource.