Permits, licenses and authorized activities
Support lawful operation by maintaining traceable permit coverage, conditions, status and renewal obligations for the authorized holder.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 9 questions
Permit and issuer This bundle identifies the permit, its issuer and its holder.
Permit record
This layer establishes the record's identity and regulatory classification.
Permit
This finding records the issuing authority and authorized holder.
- Which body issued this permit, and under which legal basis?
- Who holds this permit, and what relationship to the operator does the record establish?
Kind of licence
This finding separates regulatory permits from referenced commercial entitlements and intellectual property grants.
- Does this record establish a regulatory permit or reference a separately maintained commercial entitlement or intellectual property license?
Scope and conditions This bundle records authorized coverage and attached conditions.
Licence scope
This layer identifies the extent and conditions of authorization.
Scope
This finding records coverage supported by the permit or applicable law.
- Which activities, sites and territories does this permit cover?
- Which permit provision or applicable legal provision, if any, supports coverage of subsidiaries or additional sites under this permit?
Conditions
This finding records permit conditions and evidence of their fulfillment.
- Which conditions attach to this permit, and what evidence does its record contain about their fulfillment?
Status over time This bundle preserves permit status and renewal history.
Status events
This layer records dated status changes and their authoritative support.
Status change
This finding records effective status, expiry and renewal evidence.
- What status does this permit record establish for the specified date?
- When does this permit expire, and what renewal progress does its record document?
- Which issuing authority decision or authoritative permit register entry supports this permit's recorded status and effective date?
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 regulatory permit record identifies the issuing authority, holder, authorized activities, territory, conditions and term, while commercial entitlements and intellectual property grants are classified and referenced separately.
Why it exists Filled
Support lawful operation by maintaining traceable permit coverage, conditions, status and renewal obligations for the authorized holder.
Distinguishing features Filled
- An activity classification code in a registry is not a permit.
- A permit names its issuing body, legal basis, holder, scope and term.
- Coverage of subsidiaries or additional sites requires support from permit provisions or applicable law.
- Commercial entitlements and intellectual property grants are classified and referenced rather than maintained as regulatory permits.
What robots and AI may and may not do Filled
Must not
- Treat an industry code in a registration as a licence.
- Assume coverage of subsidiaries, sites or activities without supporting permit provisions or applicable law.
- Report a suspended or revoked permit as valid.
- Apply for, renew or surrender a permit on its own initiative.
Only with a human decision
- A responsible human must authorize applying for, renewing or surrendering a permit.
- A responsible human must decide whether an activity may continue during a suspension.
May
- Track expiry, renewal and status changes of permits.
- Match activities and sites against permits and report gaps.
- Extract conditions from permit documents for review.
Moral aspects Filled
- Operating without a valid permit can endanger public safety and expose the organisation to sanctions.
- Customers and the public rely on permits as a signal of oversight.
Who is affected
- The public and customers
- The permit holder and its officers
- Issuing authorities
Owners Filled
Steward
The permit compliance steward is accountable for permit records, coverage evidence and status interpretation.
Master systems
- An internal permit register maintains the enterprise's permit records.
- An issuing authority's permit register or decision record provides authoritative permit status evidence.
- A document management system retains permit documents and supporting corporate registry extracts, which establish entity details rather than permit status unless legally designated to do so.
Links to other meta-models Filled
references
- WM-POL-004 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by the issuing body and its permit number, with holder and validity period.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- Marked by an issuing authority, a permit number, a holder and a term.
- Often confused with an activity code, a certificate of conformity or a software licence.
Capabilities and actions required Filled
- Permit coverage can be checked for a site, an activity and a date.
- Expiry and suspension can be monitored with alerts.
Hazards and failure modes required Filled
- Activities started before a permit is granted.
- Expired permits not noticed.
- Assuming group-wide coverage from one entity's permit.
Standards and interfaces required Filled
- ISIC by the United Nations Statistics Division and NACE by Eurostat for activity classification, which is not a permit.
- ISO 3166-2 codes for territorial subdivisions.
- ISO 17442 Legal Entity Identifier, operated through GLEIF, for the holder.
Context of use required Filled
- Used for regulated activities such as finance, health, energy, transport and telecoms.
- Rules differ by jurisdiction and must be checked against primary sources.
Sources Filled
- OASIS UBL: business documents for agreements and orders
- FIBO (EDM Council, OMG): financial agreements, parties and obligations
- ODRL: permission, prohibition, duty and constraint
- Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
- OASIS Universal Business Language (UBL) 2.3 - Checked live (HTTP 200) on 2026-10-07.
- W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
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, ver-cy/world-models/card-supplements/em-leg-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.