GAEA Synthetic Scout Ticket Digitization Example
=================================================

Purpose
-------
This package demonstrates one possible relational delivery for digitized scout
ticket information. Every identifier, operator, location, date, depth, interval
and result is synthetic. The package is provided only to illustrate data
organization, source traceability and exception handling.

It must not be used for regulatory filing, title review, drilling, completion,
production, reserve estimation, engineering design or geological interpretation.

Package contents
----------------
source_scout_ticket.svg  Synthetic source record with one intentionally unclear value.
wells.csv                One wellbore-level record.
completions.csv          Completion-level record linked by well_id.
formation_tops.csv       Repeating formation-top records.
casing.csv               Repeating casing-string records.
tests.csv                Initial test records.
production.csv           Example monthly production records.
source_documents.csv     Source-document and page linkage.
exceptions.csv           Uncertain, illegible or unresolved fields.
data_dictionary.csv      Field definitions, units and relationship notes.

Transcription policy represented
--------------------------------
1. Values are captured only when present and legible.
2. Missing values remain blank rather than being invented.
3. Ambiguous values are placed in the exception register.
4. Normalized values retain their source text where applicable.
5. Each structured record remains linked to its source document and page.
6. A wellbore can have multiple completions, tops, casing strings and tests.

