← Back to catalogue
Published

Disclosure, classification and retention

EM-XCT-05 · em-xct-05

A shared contract for sensitivity, purpose, retention and permitted Projection fields. Specific IAM grants belong to the access model.

Enterprise profiles Enterprise contract EnterpriseXCT

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 8 questions

Classification and purpose How sensitive a fact is and for which purposes it may be used.

Classification

A sensitivity class from a referenced scheme.

Classification assignment

A class assigned to an object or field under a named scheme.

  1. Which classification scheme and class apply to this object or field?
  2. For which purposes may the data be used, and by whom?
Projection and aggregate What may be shown in a view of one object, and in combinations.

Projection contract

Permitted fields of a projection of one canonical object.

Permitted projection

A view of one canonical object restricted by purpose and fields.

  1. Which canonical object does this projection represent?
  2. Which fields are permitted for this purpose and audience?

Aggregate exposure

Whether combining permitted views reveals a closed fact.

  1. Does combining these permitted projections reveal a prohibited individual indicator?
  2. Has the composite report been checked as a separate aggregate?

Retention

How long data is kept and how deletion meets evidence needs.

Retention constraint

A retention period and its interaction with legal holds.

  1. Which retention rule applies, and when does it expire?
  2. Does an evidentiary or legal hold override deletion, and for how long?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise contract
Entry kind
contract
Domain
EnterpriseXCT
Industry
Cross-industry
Tags
EM-XCT-05W0contractDisclosurePolicyClassificationAssignmentRetentionConstraintProjectionContract

What it is Filled

A shared contract for sensitivity, purpose, retention and permitted Projection fields. Specific IAM grants belong to the access model.

Why it exists Filled

A shared contract for sensitivity, purpose, retention and permitted Projection fields. Specific IAM grants belong to the access model.

Distinguishing features Filled

  • A projection always represents exactly one canonical object and exposes only fields permitted for its purpose.
  • A combination of permitted projections is a new aggregate and must be checked on its own.
  • Classification always refers to a named scheme rather than a free label.
  • Specific access grants belong to the access model; this contract states what may be disclosed, not who holds a login.

What robots and AI may and may not do Filled

Must not

  • Combine permitted cards in a way that exposes a prohibited individual indicator.
  • Use data for a purpose that its disclosure policy does not allow.
  • Assign a classification that does not refer to a scheme.
  • Delete data under a legal or evidentiary hold.
  • Treat an access grant as permission to disclose every field.

Only with a human decision

  • Approving a new purpose for personal or confidential data.
  • Releasing an aggregate that may allow re-identification.
  • Lifting a legal hold or deleting data with evidentiary value.

May

  • Assemble context packages only from permitted projections.
  • Check composite reports for re-identification or exposure of closed facts.
  • Report the classification, purpose and retention of a given field.
  • Flag data held beyond its retention period.

Moral aspects Filled

  • Personal data can be exposed through aggregation even when each view looks harmless.
  • Over-retention and premature deletion both harm people, through exposure or through lost evidence.

Who is affected

  • Data subjects
  • Data owners and stewards
  • Recipients of reports and context packages

Owners Filled

Steward

The enterprise information governance policy owner is accountable for disclosure, classification and retention policies and the designation of authorized hold owners.

Master systems

  • An information governance policy system maintains authoritative disclosure and permitted use policies.
  • A classification registry maintains authoritative classification schemes and assignments.
  • A records management system maintains authoritative retention schedules and record retention obligations.
  • A hold management system maintains authoritative legal and evidentiary hold records.

Links to other meta-models Filled

references

  • WM-XCT-002 - conceptual-candidate
  • WM-XCT-003 - conceptual-candidate
  • WM-XCT-035 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A disclosure policy is identified by its own identifier and version.
  • A projection contract is identified by canonical object type, purpose and version.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A classification assignment names a scheme, a class and the object or fields it covers.
  • Often confused with an access control list or a role grant.

Capabilities and actions required Filled

  • Context packages can be assembled automatically from permitted projections.
  • Aggregates can be tested for exposure before release.

Hazards and failure modes required Filled

  • Mosaic effect, where permitted pieces combine into a prohibited disclosure.
  • Purpose creep when data is reused beyond its stated purpose.
  • Loss of evidence when deletion ignores holds.

Standards and interfaces required Filled

  • ISO/IEC 27001 from ISO and IEC, including information classification controls.
  • ISO 15489 from ISO for records management and retention.
  • W3C ODRL for machine-readable usage policies.

Context of use required Filled

  • Used whenever data about people or confidential matters is shared with agents or reports.
  • Data protection law and sector retention rules apply.

Sources Filled

  1. Current Vercy protocol/MMAS/whole-object and the published WM-XCT
  2. W3C PROV/SKOS/SHACL/ODRL where applicable
  3. Practice of source connectors, versioned schemas and policy enforcement
  4. W3C ODRL Vocabulary & Expression 2.2 - Checked live (HTTP 200) on 2026-10-07.
  5. W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
  6. NIST Privacy Framework - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • What is permitted in a projection of a single object?
  • When does an aggregate expose closed facts?
  • How to combine deletion with evidentiary needs?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-xct-05/brief.json, ver-cy/world-models/card-supplements/em-xct-05.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.