# Afghanistan — country business worksheet

**HSIMC South Asia C0-001 · English worksheet · 20 November 2026**

**Status:** Unfilled worksheet; local professional decisions and task acceptance are pending.

## Language baseline

The current ministry describes Pashto and Dari as official. The 2004 Constitution is historical and listed by the ministry among nullified constitutions; no current constitutional-law conclusion is made. Other local languages remain extensions.

| Role | Shared written editions |
| --- | --- |
| Country baseline | [Pashto](https://hsimc.tech/whitepaper/global-value/regions/south-asia/releases/c0-001/ps/); [Dari](https://hsimc.tech/whitepaper/global-value/regions/south-asia/releases/c0-001/prs/) |
| 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 current authority and documentary requirements apply at the task location? Verify them locally; do not rely on the historical 2004 Constitution as current law.
- Which Pashto/Dari edition and regional terminology does each recipient require, and which bilingual reviewer will compare both against the engineering master?

### 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

- [Ministry of Foreign Affairs, Afghanistan — Background](https://mfa.gov.af/en/background/), Population and Languages. Retrieved 2026-11-20. Used as a current ministry descriptive baseline, not as proof that the 2004 Constitution remains in force.
- [Ministry of Justice, Afghanistan — Collection of Nullified Constitutions of Afghanistan](https://moj.gov.af/en/collection-nullified-constitutions-afghanistan), Constitution dated 28 January 2004 in the collection. Retrieved 2026-11-20. Conflicts with a legacy page title saying 'Enforced'; avoid current constitutional-law claims from that legacy text.
- [Ministry of Justice, Afghanistan — Enforced Constitution of Afghanistan (legacy 2004 text)](https://www.moj.gov.af/en/enforced-constitution-afghanistan), Article 16. Retrieved 2026-11-20. Historical reference only; the current nullified-constitutions collection prevents treating this as current law.
