EM-LEG-03 · Subject model · W1
Internal policies and exceptions
Internal rules, adoption, applicability, exceptions and acknowledgment. The result of an enforcement check belongs to the control model.
Partially published; research continues
Claude: complete-frozen-study-and-audit; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- Policy
- PolicyVersion
- PolicyAdoption
- PolicyException
- Acknowledgement
Deep research 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?
Verifiable invariants
- A rule has an adopting body and a term
- An exception has a scope and an expiration
- Acknowledgment is not proof of execution
End-to-end acceptance scenario
A global policy, a local tightening and a limited exception yield an unambiguous rule for a given date.
Negative case
A document read by an employee means a completed control.
Approaches to compare
- OASIS UBL/FIBO: agreements, parties and obligations
- ODRL: permission, prohibition, duty and constraint
- Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
Candidates in the live catalogue
- WM-ORG-019 · Organization Policy · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-KNW-012 · Policy / Rule · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.