SOUTH-ASIA · NP
Nepal
Nepali in Devanagari is the federal official-language baseline. The Constitution recognizes all mother tongues as languages of the nation and permits additional provincial official languages; those are not all completed by this edition.
Source status: NATIONAL_BASELINE_DEFINED_LOCAL_REVIEW_PENDING
The linked edition supplies a shared written blueprint. Terminology, permitted official use and transaction requirements are assessed for this country and the actual document.
Business and delivery worksheet
English working reference. Named owners, evidence and transaction decisions remain to be completed.
HSIMC South Asia C0-001 · English worksheet · 20 November 2026
Status: Unfilled worksheet; local professional decisions and task acceptance are pending.
Language baseline
Nepali in Devanagari is the federal official-language baseline. The Constitution recognizes all mother tongues as languages of the nation and permits additional provincial official languages; those are not all completed by this edition.
| Role | Shared written editions |
|---|---|
| Country baseline | Nepali |
| Official-purpose / link role | No additional language assigned by this scope |
| Shared engineering reference | English; this does not imply official status in every country |
Record the actual task
Task ID: ___ · Contract ID: ___ · Object/input version: ___ · Delivery version: ___ · Intended use and destination: ___
For each question, record the answer, accountable owner, current source or evidence, reviewer, decision and date. The JSON companion provides individual fields.
Country and language decisions
- Which province, local authority and recipients are involved? Check whether an additional provincial or local language is needed alongside Nepali and record that extension explicitly.
Parties and authority
- Who are the legal contracting parties, service locations and authorized signatories? Record their verified identities and the source of authority.
- Which party may instruct each human, device or service? Define delegation limits, changes, suspension and escalation contacts.
Task and deliverable
- What human intent, physical or digital object, input version and operating conditions does this task cover?
- What must each node deliver, in which version and format, by what handover, and against which measurable acceptance criteria?
- Which contract language and controlling text will the parties use? Who verifies translated engineering meaning, identifiers and units?
Tax, invoicing and payment questions
- For the actual goods, services, licensing, human work and locations involved, which registrations and tax treatments need checking against current official sources?
- Who issues the invoice and pays whom? Which invoice fields, currency, withholding, indirect-tax, payment and record requirements apply to the specific transaction? Record the reviewer, source date and conclusion; do not assume a regional exemption.
Customs and movement of physical goods
- Will equipment, samples, finished goods or temporary imports cross a border? Identify exporter, importer, route, declared description, classification and origin evidence.
- Which current customs procedures, valuation, permits, documentary evidence and any claimed preference conditions apply to this actual movement? Mark this section not applicable only with a reason.
Product, service and site requirements
- Which product, service, installation, operator, calibration, safety, label and instruction requirements apply to the intended use and destination? Who confirms the applicable current requirements?
- Who controls local execution, equipment readiness, maintenance and incident handling? Identify the evidence required before physical action and after completion.
Data and permissions
- Which data, images, recordings, personal information, designs and confidential materials are needed? Who has permission to collect, share, process and retain them?
- Which recipients, storage locations, cross-border transfers, access controls and retention/deletion decisions apply? Link the applicable sources and task-specific approvals.
Evidence and acceptance
- Link the input and output hashes, methods, responsible nodes, timestamps, observations, deviations, checks and professional-review records to the same task and object versions.
- Who accepts which exact delivery version, against which criteria and evidence? Record accept, accept with conditions, request changes or reject, together with reasons and authority.
- What changes trigger a new review: source content, translation, destination, intended use, law, supplier, process, device, data route or accepted version? Record the next check or event trigger.
Acceptance record
Decision: pending · Exact accepted version: ___ · Acceptance authority: ___ · Criteria: ___ · Evidence: ___ · Conditions/reasons: ___ · Date: ___ · Next review trigger: ___
This worksheet contains questions for an actual task. No business, tax, customs, product or data approval is recorded. The regional grouping does not create a shared legal or tax regime.
Scope sources
- Office of the Attorney General, Nepal — Constitution of Nepal, revised English version as amended, Articles 6 and 7. Retrieved 2026-11-20. Direct open returned no usable PDF text. WIPO's constitutional text corroborates the language provisions.
- World Intellectual Property Organization, WIPO Lex — Constitution of Nepal 2015, Articles 6 and 7. Retrieved 2026-11-20. WIPO record is the 2015 version; the official government indexed amended text was used to cross-check these provisions.
Human Authority · Local Capability · Global Participation.
Bring a capability. Help deliver a real outcome.
QR encodes the address shown here.
URL → QR → COPY → PRINT → NFC
This URL is ready to move.
https://hsimc.tech/whitepaper/global-value/regions/south-asia/countries/np/QR and URL are ready. NFC writing starts only when you choose it.
Write this URL as an NDEF URI record, then tap the tag independently to verify it. Sharing an address does not grant execution authority.