STRIPED DONKEY / FIDELRA AFRICA
DELIVERY NOTE - UNISSUED TEMPLATE

This template is not a completed purchase, receipt or proof of delivery.
Complete it with the actual agreement and private package at handoff.

DELIVERY IDENTITY
Delivery standard: SD-DATA-DELIVERY 1.0
Release ID: [confirm at handoff]
Product ID and title: [agreed product]
Agreement or accepted quote: [reference]
Licensed organization: [agreed customer]
Handoff date: [actual date]

AGREED SCOPE
Cities and domains: [agreed scope]
Record unit and structure: [agreed scope]
Covered period and observation cutoffs: [agreed scope]
Formats: [agreed formats; include Parquet only when expressly agreed]
Applicable licence and permitted use: [incorporated document versions]

PACKAGE ANATOMY
data/ - agreed synthetic extract
documentation/ - agreed schema, fields, relationships and scope
evidence/ - agreed reports, checks, references and limitations
examples/ - agreed loading, joining or analysis examples
LICENSE.txt - applicable rights and incorporated terms
MANIFEST.json - actual release identity, scope and payload inventory
CHECKSUMS.sha256 - actual SHA-256 fingerprints
DELIVERY_NOTE.txt - this completed handoff note

EXCLUSIONS AND LIMITS
[List exclusions, unavailable artifacts, separately controlled methodology,
known limitations and any agreed follow-up. Empty directories do not imply
evidence was supplied.]

HANDOFF
Secure delivery method: [agreed private channel]
Delivery/payment conditions: [confirm against accepted agreement]
Support contact: [agreed support contact]

VERIFY THE RECEIVED PACKAGE
1. Confirm the release, product, scope and applicable licence.
2. Compare received payload paths and sizes with MANIFEST.json.
3. Compute local SHA-256 hashes and compare with CHECKSUMS.sha256.
4. Check the actual signing state separately.
5. Review release-specific evidence, exclusions and limitations.

MANIFEST.json inventories payload files, LICENSE.txt and this note; it does
not inventory itself or CHECKSUMS.sha256. CHECKSUMS.sha256 covers those
inventoried files plus MANIFEST.json and does not hash itself.

Matching hashes establish recorded file identity, not empirical accuracy,
independent certification or fitness for a particular use. Synthetic records
are not observations of real people or official population estimates.