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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseLEG
- Industry
- Cross-industry
- Tags
- EM-LEG-04W2subjectPermitLicencePermitConditionLicenceScope
What it is Filled
A permit from an authorized body, subject, territory, conditions and term. Commercial entitlement and IP grant are mapped but not merged.
Why it exists Filled
A permit from an authorized body, subject, territory, conditions and term. Commercial entitlement and IP grant are mapped but not merged.
Distinguishing features Derived, awaiting review
- An activity code is not a permit
- The issuing body and the basis are explicit
- A permit does not automatically extend to subsidiaries
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: The presence of an industry code in the registration is treated as a license.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Юридическая функция / владелец договора
Master systems
- CLM
- подписанные документы
- нормативные источники
Links to other meta-models Filled
references
- WM-POL-004 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- Permit
- Licence
- PermitCondition
- LicenceScope
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- 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
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-leg-04/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.