← Back to catalogue
Published

Internal policies and exceptions

EM-LEG-03 · em-leg-03

Internal rules, adoption, applicability, exceptions and acknowledgment. The result of an enforcement check belongs to the control model.

Enterprise profiles Enterprise subject EnterpriseLEG

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 9 questions

Policy and adoption Internal rules, who adopted them and for how long.

Policy versions

Versions of a policy and their adoption.

Policy version

A version with its text, scope and validity.

  1. Which version of the policy applies on a given date?
  2. What scope does the policy cover?

Adoption

The body that adopted or revoked the policy and when.

  1. Which body adopted the policy, and on what authority?
  2. Who may revoke or change it?
Inheritance and exceptions How group policies combine with local rules and exceptions.

Local rules

Local tightening and limited exceptions.

Group inheritance

How a group policy applies to subsidiaries with local changes.

  1. Does a local entity inherit the group policy, and with which changes?

Exception

An exception with scope, approver and expiry.

  1. What is the scope of the exception, who approved it and when does it expire?
  2. Which rule results for a given unit and date after combining all layers?
Acknowledgement Confirmation that people have read a policy, apart from execution.

Acknowledgement records

Who acknowledged which version and when.

Acknowledgement

A dated acknowledgement of a specific version by a person.

  1. Which version did the person acknowledge, and when?
  2. Is there separate evidence that the policy is actually followed?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseLEG
Industry
Cross-industry
Tags
EM-LEG-03W1subjectPolicyPolicyVersionPolicyAdoptionPolicyExceptionAcknowledgement

What it is Filled

Internal rules, adoption, applicability, exceptions and acknowledgment. The result of an enforcement check belongs to the control model.

Why it exists Filled

Internal rules, adoption, applicability, exceptions and acknowledgment. The result of an enforcement check belongs to the control model.

Distinguishing features Filled

  • A policy is adopted by an identified body for a stated term.
  • Exceptions are scoped and expire; they do not silently become the rule.
  • Acknowledging a policy is not evidence that it is carried out.
  • Distinct from the control contour, which records whether a rule is actually enforced.

What robots and AI may and may not do Filled

Must not

  • Treat a policy read by an employee as a completed control.
  • Extend an exception beyond its scope or expiry.
  • Adopt, revoke or change a policy without the adopting body.
  • Apply a revoked version as current.

Only with a human decision

  • Adopting, changing or revoking a policy.
  • Granting or extending an exception.

May

  • Compute the effective rule for a unit and date from group, local and exception layers.
  • Remind people to acknowledge new versions.
  • Flag expired exceptions that are still in use.

Moral aspects Filled

  • Policies shape employees' duties and can lead to disciplinary consequences.
  • Unfair exceptions undermine equal treatment.
  • Acknowledgement tracking is personal data about employees.

Who is affected

  • Employees bound by the policy
  • Managers granting exceptions
  • Compliance and audit staff

Owners Filled

Steward

The legal function or contract owner who answers for legal records and their interpretation.

Master systems

  • Policy management system
  • Document management system
  • Learning management system

Links to other meta-models Filled

neighbor

  • EM-LEG-02

references

  • WM-ORG-019 - conceptual-candidate
  • WM-KNW-012 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by the policy identifier and version number with its adopting body and effective date.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • Marked by an adopting body, a version, a scope and an effective date.
  • Often confused with an external norm or with a procedure or work instruction.

Capabilities and actions required Filled

  • The effective rule can be computed for any unit and date.
  • Exceptions can be tracked to expiry.

Hazards and failure modes required Filled

  • Stale exceptions that never expire.
  • Conflicting local and group rules without precedence.
  • Acknowledgement figures used as compliance figures.

Standards and interfaces required Filled

  • W3C ODRL Information Model for permissions, prohibitions and duties.
  • ISO 37301 for compliance management systems.
  • ISO/IEC 27001 for information security policies.

Context of use required Filled

  • Used for codes of conduct, security, procurement and data handling policies.
  • Group structures need precedence rules between group and local policy.

Sources Filled

  1. OASIS UBL: business documents for agreements and orders
  2. FIBO (EDM Council, OMG): financial agreements, parties and obligations
  3. ODRL: permission, prohibition, duty and constraint
  4. Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
  5. W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
  6. OASIS Universal Business Language Technical Committee - Checked live (HTTP 200) on 2026-10-07.
  7. W3C ODRL Vocabulary and Expression 2.2 - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • Who can adopt and revoke a rule?
  • How to inherit a rule within a group with a local exception?
  • How to distinguish acknowledgment from execution?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

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

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