EM-LEG-04 · Subject model · W2
Permits, licenses and authorized activities
A permit from an authorized body, subject, territory, conditions and term. Commercial entitlement and IP grant are mapped but not merged.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-exact-prompt.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- Permit
- Licence
- PermitCondition
- LicenceScope
Deep research questions
- How to distinguish a regulator's permit from a software license?
- How to describe an activity without a classifier code?
- How to record revocation, suspension and restrictions?
Verifiable invariants
- An activity code is not a permit
- The issuing body and the basis are explicit
- A permit does not automatically extend to subsidiaries
End-to-end acceptance scenario
Verify a license for one site, a temporary suspension and a new activity without a permit.
Negative case
The presence of an industry code in the registration is treated as a license.
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-POL-004 · Permit / Authorization · 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.