From 3900bf2c9e7ab15ae396365d2a4faaa167cf8e3d Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Fri, 15 Aug 2025 14:35:35 +0200
Subject: [PATCH 01/11] Draft v8.0 TEMPLATE, STICKY, FLEX, ASSET, GROUP, PROOF,
 alongside V7
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This PR models new structures for GEDCOM V8, to try and take that to a higher level.
It is based on TEMPLATEs and STICKYs. They describe the evidence in documents, on gravestones, in a census, and any other evidence "entity" that can hold genealogical information.
It has 3 huge enumtables so it becomes a bit "Data driven".
It is structured alongside GEDCOM 7.x (for now) to help users and developers get used to this new system. But before implementation the group might decide to totally disconnect it from V7.x and start a new direction.
In that case changes have to be applied to make this draft work.

While designing, time and effort have been spend to make it extendable, reliable, easily changeable, logical, solid and easy for users and developers.

It needs polishing, refinements, help from the group to find missing ends.
It has a huge extra file with examples, they are not there for fun (although some have some fun inside) but they are there as a testbed.
I heavily used that to make sure things would fit.

But I now want to show it all, I can hardly wait.😁
---
 .../gedcom-1-hierarchical-container-format.md |   35 +
 specification/gedcom-2-data-types.md          |  180 +
 .../gedcom-3-structures-1-organization.md     | 1619 ++++-
 .../gedcom-3-structures-3-meaning.md          |   73 +
 ...dcom-3-structures-4-enumerations-entity.md |  336 +
 ...dcom-3-structures-4-enumerations-events.md |  442 ++
 ...edcom-3-structures-4-enumerations-roles.md |  451 ++
 .../gedcom-3-structures-4-enumerations.md     |  270 +
 .../gedcom-6-appendix-examples-sticky.md      | 6130 +++++++++++++++++
 9 files changed, 9502 insertions(+), 34 deletions(-)
 create mode 100644 specification/gedcom-3-structures-4-enumerations-entity.md
 create mode 100644 specification/gedcom-3-structures-4-enumerations-events.md
 create mode 100644 specification/gedcom-3-structures-4-enumerations-roles.md
 create mode 100644 specification/gedcom-6-appendix-examples-sticky.md

diff --git a/specification/gedcom-1-hierarchical-container-format.md b/specification/gedcom-1-hierarchical-container-format.md
index ab1ef74b..175eb631 100644
--- a/specification/gedcom-1-hierarchical-container-format.md
+++ b/specification/gedcom-1-hierarchical-container-format.md
@@ -286,6 +286,41 @@ The following are examples of valid but unrelated lines:
     ````
 :::
 
+## Comments – Inline and standalone comments
+
+GEDCOM 8 supports comments using the `/* ... */` syntax, inspired by common programming languages.  
+A comment may appear either:
+
+- **On its own line**, e.g.: `/* This is a comment */`
+- **At the end of a GEDCOM line**, preceded by **at least 1 space**. e.g.: `0 STICKY @ST0140@   /* PERSON, GROOM */`
+
+Rules:
+- Comments must begin with /* and end with */, on the same line.
+- Comments may not be nested.
+- Comments are ignored by parsers and have no effect on validation.
+- Comments are intended for human readers and may be used freely to annotate records.
+- Inline comments (i.e., following a GEDCOM line) must be preceded by **at least one space**.
+
+A lot of the comments in this specification, could be autogenerated by software. As very often they contain:
+- name of a person
+- event type
+- roles of a person  
+
+So it is not always necessary for users to do that themselves.
+
+:::example
+
+````gedcom
+2 STICKY @ST0140@ /* PERSON, GROOM */
+/* Here we have a comment */
+````
+Illegal use:
+````gedcom
+2 STICKY @ST0140@/* PERSON, GROOM */
+/* Here we have a /*comment*/  */
+````
+:::
+
 ##  The Header and Trailer {#the-header}
 
 Every dataset must begin with a header pseudo-structure and end with a trailer pseudo-structure.
diff --git a/specification/gedcom-2-data-types.md b/specification/gedcom-2-data-types.md
index be8641a5..01103fa1 100644
--- a/specification/gedcom-2-data-types.md
+++ b/specification/gedcom-2-data-types.md
@@ -167,6 +167,141 @@ The URI for the `DateExact` data type is `g7:type-Date#exact`.
 
 The URI for the `DatePeriod` data type is `g7:type-Date#period`.
 
+## Boolean
+
+A `Boolean` is a binary truth value that indicates a positive or negative condition, choice, or state.
+
+GEDCOM 8 SHALL use the values `TRUE` and `FALSE`, in all uppercase, consistent with other enumerated values in the specification.  
+These values MUST appear in uppercase and without quotation marks.
+
+```abnf
+Boolean = "TRUE" / "FALSE"
+```
+
+**Examples**:
+- `TRUE` → value or condition applies
+- `FALSE` → value or condition does not apply
+
+This data type may be used in `FLEX.CONTENTS`, or any other structure where an on/off or yes/no condition is required.
+
+**Note**: Values such as `YES`, `NO`, `1`, or `0` are NOT valid Boolean representations in GEDCOM 8.
+
+The URI for the Boolean data type is: `xsd:boolean`
+
+## Decimal
+
+A decimal is a non-empty sequence of ASCII decimal digits that may include an ASCII period (".") to indicate the decimal point. It represents a rational number in base-10 and can have any number of digits after the decimal point. Leading zeros have no semantic meaning and should be omitted unless immediately preceding the decimal point.
+
+```abnf
+Decimal = 1*DIGIT [ "." 1*DIGIT ]
+```
+The number of digits before the decimal point, plus the number of digits after the decimal point are maximal 18 digits in total.
+Negative Decimal numbers are not supported by this specification.
+
+The URI for the `Decimal` data type is `xsd:decimal`.
+
+## HexaDecimal
+
+A `HexaDecimal` is a non-empty sequence of ASCII hexadecimal digits, representing an unsigned integer in base-16.
+
+Characters MUST be chosen from `0–9` and uppercase letters `A–F`.  
+Letters **must be uppercase** in GEDCOM files to ensure consistency and compatibility across systems.
+
+Leading zeros are permitted but have no semantic meaning.  
+Negative values are not supported.
+
+This type may be used for scalable, compact identifiers where decimal values become inefficient or overly long.
+
+```abnf
+Hexadecimal = 1*( %x30-39 / %x41-46 )  ; 0–9 or A–F (uppercase only)
+```
+:::example  
+**Examples**:
+- `1`
+- `7F`
+- `00A3`
+- `00F4240` (decimal 1,000,000)
+- `2DC6C0`  (decimal 3,000,000)
+:::  
+
+The URI for the `HexaDecimal` data type is:  
+`xsd:hexBinary` (loosely aligned; GEDCOM format is numeric-only, without spacing or byte-grouping).
+
+## HexID
+
+A `HexID` is a cross-reference identifier used to uniquely identify a record within a GEDCOM file using a hexadecimal format.
+This format can be used when the quantity of records (such as STICKYs) may exceed the limitations of base-10 padded numbering.
+
+It is composed of:
+- A record-type prefix (e.g., `ST`, `I`, `R`)
+- A required separator digit `0` (zero)
+- A `Hexadecimal` number that can grow in length as needed
+
+The entire identifier is enclosed in `@` symbols, consistent with GEDCOM cross-reference ID syntax.
+
+```abnf
+HexID = "@" Prefix "0" Hexadecimal "@"
+Prefix = %x41-5A / 2(%x41-5A)  ; one or two uppercase letters A–Z
+```
+::: example   
+**Examples**:
+- `@ST00001@`
+- `@ST003E8@`
+- `@ST0F4240@`  (decimal 1,000,000)
+- `@R02DC6C0@`  (REPO example, decimal 3,000,000)  
+:::
+
+- The `Hexadecimal` portion MUST conform to the rules in the `Hexadecimal` data type definition.
+- The record-type prefix MUST consist of exactly one or two uppercase ASCII letters (A–Z).
+This includes standard GEDCOM record types (S, I, F, etc.) and new custom types such as ST for `STICKY` or `SP` for `SPLAC`.
+
+The URI for the `HexID` type is:  `g8:HexID`  
+_This format is GEDCOM-specific and has no standard XML Schema equivalent._
+
+## PercentLiteral
+
+A percent is a rational number expressed in base-10 with an optional decimal point, representing a proportion out of 100. It includes the percent symbol (`%`). Values should be between `0` and `100`, inclusive. Precision may extend to decimal places, but the total number of digits before and after the decimal point **must not exceed 6 digits**.
+
+```abnf
+Percent    = ( "0" / [1-9] 1*DIGIT ) [ "." 1*DIGIT ] "%"
+```
+- Leading zeros have no semantic meaning and should be avoided unless immediately preceding a decimal point (e.g., 0.5% is valid).
+- Values over 100% are not permitted.
+- Negative values are not permitted.
+
+Examples:
+Valid: `25%, 0.5%, 99.99%, 100%`  
+Invalid: `-5%, 105%, 001.00%, 12.0`
+
+### Genealogical use cases:
+
+- Degree of confidence in a transcription: 95%
+- Estimated certainty of match: 87.5%
+- Percentage of form completion: 100%
+
+The URI for the Percent data type is: `g8:type-PercentLiteral`
+
+## PercentRatioLiteral
+
+This data type expresses ratios or comparisons using a percentage beyond 100%. It is suitable for contexts where the value exceeds a full unit, typically for historical, economic, or biological scaling.  
+Negative values are not permitted.
+
+```abnf
+PercentRatioLiteral = 1*DIGIT [ "." 1*DIGIT ] "%"
+```
+:::example  
+Valid: `110%, 150.75%, 220.5%`  
+Invalid: `-10%, 2, 001.0%`   
+:::
+
+### Genealogical use cases:
+
+- Increase in estate value compared to previous decade: 175%
+- Year-on-year increase in property tax: 122.5%
+- Dowry size compared to average: 300%
+
+The URI for the PercentRatio data type is: `g8:type-PercentRatioLiteral`
+
 ## Time
 
 Time is represented on a 24-hour clock (for example, 23:00 rather than 11:00 PM).
@@ -370,3 +505,48 @@ Version 7.0 only supports the following URLs:
 Additional URLs may be supported in future versions of this specification.
 
 The URI for the `FilePath` data type is `g7:type-FilePath`.
+
+### TupleList Data Type
+
+The `TupleList` data type represents a structured, multi-line encoding of simple two-column tabular data.  
+It is designed for storing genetic data such as DNA marker/allele pairs in a readable and consistent format.
+
+The data type `TupleList` represents a list of structured value pairs, each encoded on a **separate GEDCOM CONT line**, in tuple format:
+
+```
+(rs123456, A)
+(rs789101, C)
+(rs999999, GG)
+```
+
+Each line must contain exactly one tuple:  
+- A **label** (typically a marker ID like `rs123456`)  
+- A **value** (typically an allele value like `A`, `T`, `GG`, etc.)  
+
+These are wrapped in parentheses `()` and separated by a **comma** `,`.  
+A single optional space **may appear after the comma**.
+
+```abnf
+TupleList   = Tuple *( Newline Tuple )
+Tuple       = "(" Label "," SP? Value ")"
+Label       = 1*VCHAR   ; Must not contain comma, newline, or parenthesis
+Value       = 1*VCHAR   ; Must not contain comma, newline, or parenthesis
+Newline     = CRLF / LF / CR
+SP          = %x20      ; ASCII space
+```
+
+All tuples must follow this structure.  
+The format does **not** allow blank lines, comments, or nested groups.
+
+The URI for this data type is:  
+`g8:type-TupleList`
+
+> $\color{Coral}\large{\textsf{✨ Forward Compatibility Note:}}$  
+> Future versions of GEDCOM may allow compact representations such as:  
+> - Semicolon-separated tuples on a single line  
+>   `[(rs123456, A); (rs789101, C)]`  
+> - Tab-delimited formats resembling CSV or raw DNA exports  
+> This v8 format ensures maximum compatibility and readability for current software, while keeping open the door for compressed imports/exports.
+
+> 📎 **See Also:** The structure and usage of this data type is demonstrated in the `ARRAY_STRUCTURE` element.
+
diff --git a/specification/gedcom-3-structures-1-organization.md b/specification/gedcom-3-structures-1-organization.md
index a153daae..36fdad46 100644
--- a/specification/gedcom-3-structures-1-organization.md
+++ b/specification/gedcom-3-structures-1-organization.md
@@ -110,22 +110,39 @@ with any `RECORD`s in between.
 
 ```gedstruct
 [
+n <<ASSET_RECORD>>                         {1:1}
+|
 n <<FAMILY_RECORD>>                        {1:1}
 |
+n <<GROUP_RECORD>>                         {1:1}
+|
 n <<INDIVIDUAL_RECORD>>                    {1:1}
 |
 n <<MULTIMEDIA_RECORD>>                    {1:1}
 |
+n <<PROOF_RECORD>>                         {1:1}
+|
 n <<REPOSITORY_RECORD>>                    {1:1}
 |
 n <<SHARED_NOTE_RECORD>>                   {1:1}
 |
 n <<SOURCE_RECORD>>                        {1:1}
 |
+n <<STICKY_RECORD>>                        {1:1}
+|
 n <<SUBMITTER_RECORD>>                     {1:1}
+|
+n <<TEMPLATE_RECORD>>                      {1:1}
 ]
 ```
 
+***
+$\color{Coral}\large{\textbf{Gedcom 8:}}$
+
+>- **This Draft-PR is written to allow the new structures to go *alongside* GEDCOM 7.X, and because of that in this GEDCOM 8 specification, lines are added in GEDCOM 7 parts, to be able to allow that.**
+>- **If the GEDCOM group would decide to add this PR, but make it a new start, without old GEDCOM 7.x constructions inside it, a few parts of this draft have to be changed to remove some of the old structures and records of current GEDCOM 7.x.**
+***
+
 #### `HEADER` :=
 
 ```gedstruct
@@ -134,28 +151,30 @@ n HEAD                                     {1:1}  g7:HEAD
      +2 VERS <Special>                     {1:1}  g7:GEDC-VERS
   +1 SCHMA                                 {0:1}  g7:SCHMA
      +2 TAG <Special>                      {0:M}  g7:TAG
-  +1 SOUR <Special>                        {0:1}  g7:HEAD-SOUR
-     +2 VERS <Special>                     {0:1}  g7:VERS
-     +2 NAME <Text>                        {0:1}  g7:NAME
-     +2 CORP <Text>                        {0:1}  g7:CORP
+  +1 SOUR <Special>                        {1:1}  g7:HEAD-SOUR
+     +2 VERS <Special>                     {1:1}  g7:VERS
+     +2 NAME <Text>                        {1:1}  g7:NAME
+     +2 CORP <Text>                        {1:1}  g7:CORP
         +3 <<ADDRESS_STRUCTURE>>           {0:1}
         +3 PHON <Special>                  {0:M}  g7:PHON
-        +3 EMAIL <Special>                 {0:M}  g7:EMAIL
+        +3 EMAIL <Special>                 {1:M}  g7:EMAIL
         +3 FAX <Special>                   {0:M}  g7:FAX
-        +3 WWW <Special>                   {0:M}  g7:WWW
+        +3 WWW <Special>                   {1:M}  g7:WWW
      +2 DATA <Text>                        {0:1}  g7:HEAD-SOUR-DATA
         +3 DATE <DateExact>                {0:1}  g7:DATE-exact
            +4 TIME <Time>                  {0:1}  g7:TIME
         +3 COPR <Text>                     {0:1}  g7:COPR
   +1 DEST <Special>                        {0:1}  g7:DEST
-  +1 DATE <DateExact>                      {0:1}  g7:HEAD-DATE
-     +2 TIME <Time>                        {0:1}  g7:TIME
-  +1 SUBM @<XREF:SUBM>@                    {0:1}  g7:SUBM
+  +1 DATE <DateExact>                      {1:1}  g7:HEAD-DATE
+     +2 TIME <Time>                        {1:1}  g7:TIME
+  +1 SUBM @<XREF:SUBM>@                    {1:1}  g7:SUBM
   +1 COPR <Text>                           {0:1}  g7:COPR
   +1 LANG <Language>                       {0:1}  g7:HEAD-LANG
   +1 PLAC                                  {0:1}  g7:HEAD-PLAC
      +2 FORM <List:Text>                   {1:1}  g7:HEAD-PLAC-FORM
-  +1 <<NOTE_STRUCTURE>>                    {0:1}
+  +1 <<NOTE_STRUCTURE>>                    {1:M}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 The header pseudo-structure provides metadata about the entire dataset.
@@ -169,9 +188,134 @@ A few substructures of note:
     - `HEAD`.`SOUR`.`DATA` describes a larger database this data is extracted from.
 - `LANG` and `PLAC` give a default value for the rest of the document.
 
+$\color{Coral}\large{\textbf{Gedcom 8 changes:}}$
+
+>**Some cardinality markers are changed:**
+>- `SOUR`, the program used to create this GEDCOM, should at a minimum give certain information, so users and other software can track the origin of a specific GEDCOM.
+>- `VERS`, `NAME`, `CORP`, `EMAIL` and `WWW`, are the minimal info about the software this GEDCOM was created by, that should be present in a header.
+>- `NOTE`: As more programs now allow users to have some kind of "general info notes" for a specific GEDCOM, the cardinality of `NOTE_STRUCTURE` is changed to {1:M}. That way users can add general information about how they're working or what they need to look at later, and much more, into the header. Now if a header is a bit "out of space" with a lot of added notes, we could also say that the header is only allowed to have 1  maybe 2 inline `NOTE`s and the rest should be links to `SNOTES`.  
+By allowing more `NOTE`s, we also give software the ability to describe when a conversion was performed, and from which GEDCOM version to which new version, it can mention the original filename if that was changed by the conversion, and other things.
+>- `DATE` and `TIME`, The datetime this GEDCOM file was created, is now also mandatory.
+>- `SUBM`, Submitter is now also mandatory.
+>- `CREA` and `CHAN`, added these too, as the header was the only record that did not have these. Because a conversion form 1 GEDCOM version to another, also changes info in the header. (replacing the name of the software for instance)  
+
+>**Further for GEDCOM 8:**
+>- All records that have a `<<CHANGE_DATE>>` and a `<<CREATION_DATE>>`, now have the cardinality markers for those set to **{1:1}**.
+>- As now the `TEMPLATE` is the only place a `SOURCE_CITATION` is used (by the `CITA` structure), at all other places the `SOURCE_CITATION` was used, some lines have been added (`GEDC` and `VERS` from the header) to try to make sure it cannot be used in GEDCOM 8.  
+That way evidence exists on **1 (ONE)** place only: **Inside the `TEMPLATE`**
+
 
 ### Records
 
+#### `ASSET_RECORD` :=
+
+An `ASSET` represents a **physical, living, symbolic, financial, or digital entity** that exists independently but interacts with individuals, groups, and events in genealogical records.
+
+Examples include **heirlooms, land parcels, animals, tools, artworks, digital objects, and persistent conditions such as hereditary diseases**. `ASSET`'s serve as reusable entities that acquire meaning through participation in `TEMPLATE` events via linked `STICKY` records.
+
+```gedstruct
+n @XREF:ASSET@ ASSET                       {1:1}  g8:record-ASSET
+  +1 TYPE <Enum>                           {1:1}  g8:ENTITY-TYPE
+    +2 SUBTYPE                             {1:1}  g8:ENTITY-SUBTYPE
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 TITL <Text>                           {0:1}  g8:TITL
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 TORIGIN <Enum>                        {1:1}  g8:TORIGIN
+  +1 QUAY <Enum>                           {0:1}  g7:QUAY
+  +1 SUBM @<XREF:SUBM>@                    {1:M}  g8:SUBM
+    +2 <<NOTE_STRUCTURE>>                  {0:M}
+  +1 NAME <<NAME_STRUCTURE>>               {0:1}  g8:INDI-NAME 
+  +1 DATE <DateValue>                      {1:1}  g8:DATE-value
+  +1 <<ADDRPLUS_STRUCTURE>>                {0:1}  g8:ADDRPLUS
+  +1 <<SHARED_PLACE_STRUCTURE>>            {0:1}  g8:SPLAC
+  +1 SUBM @<XREF:SUBM>@                    {1:M}  g8:SUBM
+    +2 <<NOTE_STRUCTURE>>                  {0:M}
+  +1 HISTORY                               {1:1}
+    +2 STICKY @<XREF:STICKY>@              {1:M}  g8:STICKY
+      +3 RESN <List:Enum>                  {0:1}  g8:RESN
+      +3 SUBM @<XREF:SUBM>@                {1:M}  g7:SUBM
+        +4 PHRASE <Text>                   {0:1}  g7:PHRASE
+      +3 PROOF @<XREF:PROOF>@              {0:M}  g8:PROOF
+        +4 OUTCOME <Enum>                  {1:1}  g8:OUTCOME
+  +1 RESN <List:Enum>                      {0:1}  g8:RESN
+  +1 <<FLEX_STRUCTURE>>                    {0:M}
+  +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
+  +1 <<NOTE_STRUCTURE>>                    {0:M}
+  +1 <<MULTIMEDIA_LINK>>                   {0:M}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
+```
+
+**💬 Field Notes:**
+- The `TYPE` value must be chosen from the enumset `g8:enumset-ENTITY-TYPE`.
+  - ⚠️ Do not use `PERSON` as an ASSET type. People are always represented via `@INDI@` records and linked there using `STICKY`s.
+  -  For `PROOF` and `OUTCOME`, see the explanation with the `PROOF`-record.
+  - All other `ENTITY` types (e.g., `CREATURES`, `PROPERTY`, `JEWELRY`) are valid.
+- `TYPE`, `SUBTYPE`, and `PHRASE`, are defined the same as for `STICKY`. They go together on 1 line.
+
+:::example
+  - For a horse: 
+  ```gedcom
+  1 TYPE CREATURES, HORSE, "Breeder: Meadow Stud, Christopher Chenery"
+  ```
+  So `TYPE`, `SUBTYPE` and `PHRASE` are on 1 line.
+:::
+  
+- `TITLE` and `NAME`: These are used to "name/describe" the `ASSET`. In case of an animal the `NAME` can be used, in case of for instance a painting, the `TITLE` can be used. `NAME` follows the new GEDCOM8 `NAME`format.<br>**At least 1 of the 2 must be present!**  
+:::example
+  - For a horse: Secretariat  (Meadow Stud, Virginia, USA, owned by Penny Chenery).
+  ```gedcom
+  1 NAME
+  2 TYPE BIRTH 
+  2 FORM Secretariat
+  2 PART Secretariat
+  3 TYPE GIVN
+  1 NAME
+  2 FORM Big Red
+  2 PART Big Red
+  3 TYPE NICK
+  ```
+  - For a painting: `TITLE "Oil painting of Castle King Windemere"`
+:::
+
+- `TORIGIN`, Defines how an `ASSET` was originally entered, generated or reconstructed. This helps distinguish freshly structured entries from those generated or inferred from legacy data. It clarifies the **origin and trust context** of each entry — whether manually entered, system-generated, or reverse-engineered — supporting gradual adoption of the new model and better transparency in data lineage.
+
+- `QUAY`, defines the quality of this whole `ASSET`. Together with `TORIGON`.
+
+- `DATE` A date associated with the asset's "founding", or first documentation.
+- `SUBM`and `NOTE_STRUCTURE` same as for STICKY.
+- `ADDRPLUS_STRUCTURE`: Can be used for the address and other addressing information that might be present for this `ASSET`.
+- `<<SHARED_PLACE_STRUCTURE>>`: if the `ASSET` is a real property (so a non-movable object), like land or a building, it can have an `SPLAC` describing that place. 
+- `HISTORY`: in this section a list of `STICKY`'s is mentioned that were present, or have a `ROLE`, in a `TEMPLATE`. The `HISTORY` section can have many `STICKY`s, coming from many `TEMPLATE`s.
+- `STICKY`s should be sorted chronologically by their internal `DATE`.
+- `RESN` This is meant to have a restriction on just this 1 `STICKY` when needed, or on this whole `ASSET`.
+- `FLEX_STRUCTURE`, this is used for information in the `ASSET` that has no GEDCOM tag, and that should be saved, and later represented, to a user. For instance:
+  - Condition of the `ASSET` (“Mint,” “Restored,” “Damaged in 1942”)
+  - Other possibilities: Inscription or mark, or restoration details, cultural symbolic use (“Used in family weddings,” “Sacred object,” “Tribal spear”).
+
+- All other structures are defined the same as for GEDCOM7.
+
+:::example:   
+**Land inherited from a Will Template**
+```gedcom
+0 @A0002@ ASSET
+1 TYPE LAND, FIELD
+1 TITL "Hilltop Pasture"
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 SUBM @B001@
+1 DATE Mar 10 1871            /* First known presence in documents of this Field */
+1 SPLAC @SP0021@              /* Norfolk, England: location of the field */
+1 HISTORY
+2 STICKY @ST1022@             /* Mar 10 1871: Owned by Edward Hamilton */
+2 STICKY @ST1123@             /* Jul 12 1882: Recieved by George Hamilton, as HEIR of Edward */
+1 NOTE "The field includes a riverbank."
+1 OBJ @O003@                  /* Map of the field */
+1 CREA 2025-05-01
+1 CHAN 2025-07-04
+```
+:::
+
 #### `FAMILY_RECORD` :=
 
 ```gedstruct
@@ -191,7 +335,7 @@ n @XREF:FAM@ FAM                           {1:1}  g7:record-FAM
   +1 <<LDS_SPOUSE_SEALING>>                {0:M}
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 <<SOURCE_CITATION>>                   {1:M}
   +1 <<MULTIMEDIA_LINK>>                   {0:M}
   +1 <<CHANGE_DATE>>                       {0:1}
   +1 <<CREATION_DATE>>                     {0:1}
@@ -202,6 +346,12 @@ The `FAM` record may also be used for cultural parallels to this,
 including nuclear families, marriage, cohabitation, fostering, adoption, and so on, regardless of the gender of the partners.
 Sex, gender, titles, and roles of partners should not be inferred based on the partner that the `HUSB` or `WIFE` structure points to.
 
+$\color{Coral}\large{\textbf{Gedcom 8 changes:}}$
+
+>- In GEDCOM 8 the `FAM` record is no longer used. As the `TEMPLATE` now represents a kind of "mini" tree, describing the relations between all persons and objects inside it.  
+>- Software is free to use an internal FAM construction, but in a GEDCOM 8 file itself, it is no longer needed or supported.  
+
+
 The individuals pointed to by the `HUSB` and `WIFE` are collectively referred to as "partners", "parents" or "spouses".
 
 Some displays may be unable to display more than 2 partners.
@@ -229,6 +379,241 @@ An `INDI` record should not have multiple `FAMS` substructures pointing to the s
 A `FAM` record should not have multiple `CHIL` substructures pointing to the same `INDI`; doing so implies a nonsensical birth order.
 An `INDI` record may have multiple `FAMC` substructures pointing to the same `FAM`, but doing so is not recommended.
 
+#### `GROUP_RECORD` :=
+
+This structure allows GEDCOM 8 to model social affiliations that span beyond family ties and record the source of such affiliations with precision.
+
+```gedstruct
+n @XREF:GROUP@ GROUP                       {1:1}  g8:record-GROUP
+  +1 TYPE <Enum>                           {1:1}  g8:GROUP-TYPE
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 RESN <List:Enum>                      {0:1}  g8:RESN
+  +1 TITL <Text>                           {0:1}  g8:TITL
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 TORIGIN <Enum>                        {1:1}  g8:TORIGIN
+  +1 QUAY <Enum>                           {0:1}  g7:QUAY
+  +1 SUBM @<XREF:SUBM>@                    {1:M}  g8:SUBM
+    +2 <<NOTE_STRUCTURE>>                  {0:M}
+  +1 NAME <<PERSONAL_NAME_STRUCTURE>>      {0:M}  g8:INDI-NAME
+  +1 <<ADDRPLUS_STRUCTURE>>                {0:1}  g8:ADDRPLUS
+  +1 <<SHARED_PLACE_STRUCTURE>>            {0:1}  g8:SPLAC
+  +1 DATE <DateValue>                      {1:1}  g8:DATE-value
+  +1 <<FLEX_STRUCTURE>>                    {0:M}
+  +1 MEMBERS                               {1:1}
+    +2 STICKY @<XREF:STICKY>@              {1:M}  g8:STICKY
+      +3 SUBM @<XREF:SUBM>@                {1:1}  g7:SUBM
+        +4 PHRASE <Text>                   {0:1}  g7:PHRASE
+      +3 RESN <List:Enum>                  {0:1}  g8:RESN
+      +3 PROOF @<XREF:PROOF>@              {0:M}  g8:PROOF
+        +4 OUTCOME <Enum>                  {1:1}  g8:OUTCOME
+  +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
+  +1 <<NOTE_STRUCTURE>>                    {0:M}
+  +1 <<MULTIMEDIA_LINK>>                   {0:M}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
+```
+
+- `GROUP` Defines a named social, cultural, or ancestral unit, such as a clan, caste, guild, farm, religious order, a sports team etc.
+- `TYPE` The category of the group being represented. Must be chosen from `g8:enumset-GROUP-TYPE`.
+- `PHRASE` A human-readable description of the group, only required when `TYPE` is `OTHER`, but allowed in all other cases. `PHRASE` must go on the same line as `TYPE`, separated from it by ", ".
+- `RESN` Optional restriction notice for access or visibility (e.g., privacy settings).
+- `TITL` A short title or label for the group, such as "The Blacksmiths' Guild".
+
+- `TORIGIN`, Defines how an `GROUP` was originally entered, generated or reconstructed. This helps distinguish freshly structured entries from those generated or inferred from legacy data. It clarifies the **origin and trust context** of each entry — whether manually entered, system-generated, or reverse-engineered — supporting gradual adoption of the new model and better transparency in data lineage.
+
+- `QUAY`, defines the quality of this whole `GROUP`. Together with `TORIGIN`.
+
+- `NAME` One or more names used to refer to this group; e.g., "Clan MacGregor", including name parts. It follows the new GEDCOM8 `NAME` format. With this its possible to trace lastnames coming from a `GROUP`.
+>**At least 1 of `NAME` and `TITL` must be present**.
+- `ADDRPLUS_STRUCTURE`: Can be used for the address and other addressing information that might be present for this `GROUP`.
+  - In case of a `CLAN`or `TRIBE` etc. it might only be a WWW adress where info about this `GROUP` can be found.
+- `SHARED_PLACE_STRUCTURE` The group's place of origin, base, or primary region of activity. It follows the new GEDCOM8 `SPLAC` format.
+- `DATE` A date associated with the group's founding, first documentation, or formal recognition. (Can also be a Date period)
+- `FLEX_STRUCTURE`, this is used for information in the `GROUP` that has no GEDCOM tag, and that should be saved, and later represented, to a user. For instance:
+  - Motto or slogan: “Semper Fidelis,” “Strength in Unity”
+  - Origin story: Brief legend or founding tale
+  - Symbol or crest: Heraldry, emblems, tribal markings
+  - Legal registration: Chamber of commerce or civil registration info
+
+- `SUBM` At least one submitter who contributed information about this group. The default `SUBM` is the same as the `SUBM` from the `HEAD`.
+- `MEMBERS` A container for listing individual membership events in the group. `STICKY`s are sorted on `NAME` first and on `DATE` second.
+-  For `PROOF` and `OUTCOME`, see the explanation with the `PROOF`-record.
+- `STICKY` References to STICKY records that reflect an individual’s connection to the group. These `STICKY`s should include the `ROLE`/Event of the person within the group, such as `MEMBER` or `LEADER` or `JOINED`. <br>If a `GROUP` has for instance 3 members and each member has 3 `STICKY`s inside the `MEMBERS` tag, the `STICKY`s will be grouped by member name first, and by `DATE` from inside the `STICKY` second. So like this: Ben, 1864, 1870, 1877, John, 1645, 1646, 1675, William, 1860, 1870, 1899, Peter, 1630.
+- `RESN` This is meant to have a restriction on just this 1 `STICKY` when needed.
+- `QUAY` This is to be able to qualify the connection of this `STICKY` on this specific place.
+- `IDENTIFIER_STRUCTURE` External or internal identifiers for this group, such as catalog or archive numbers.
+- `NOTE_STRUCTURE` Additional notes about the group.
+- `MULTIMEDIA_LINK` Links to images or other media associated with the group.
+- `CHANGE_DATE` The date this group record was last modified.
+- `CREATION_DATE` The date this group record was originally created.
+
+#### Example: Clan Membership
+
+This example illustrates the use of a `GROUP` record to represent a clan, and a corresponding `STICKY` record to indicate a person's membership in that clan at a specific point in time.
+
+- The `GROUP` record uses `TYPE CLAN` and includes a structured `NAME`, an `SPLAC` for geographical association, a `DATE` for historical context, and a `TITL` to clarify the group's nature. `TITL` is the official `GROUP`s "name".
+- The `INDI` record defines John Mackay with a properly structured `NAME`.
+- The `STICKY` record links the individual and the group, marking John as a `CLAN MEMBER` in the year 1820.
+- A `TEMPLATE` reference is included to indicate the source document where this membership was recorded (e.g., "1820 court rolls").
+- The `NOTE` in the `STICKY` provides additional human-readable context.
+
+A `STICKY` that connects an `INDI` to a `GROUP` represents a known relationship at a specific point in time, not necessarily the full duration of membership.
+
+
+The following shows:
+- John Mackay is a member of the Mackay clan.
+- The clan itself is linked to as `GROUP` in the `STICKY`.
+- The relationship is time-stamped and contextualized using `STICKY`.
+
+You may also define roles like `CHIEFTAIN`, `ELDER`, `SPOKESPERSON`, or others using `ROLE` or `SUBTYPE` if culturally relevant.
+
+
+```gedcom
+0 @G0007@ GROUP /* Clan Mackay */
+1 TYPE CLAN
+1 TITL Scottish Highland Clan
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 NAME
+2 FORM Clan Mackay
+2 PART Mackay
+3 TYPE GROUP
+2 PART Clan
+3 TYPE OTHER, Clan
+1 SPLAC @SP037@               /* Sutherland, Scotland *
+1 DATE 1600
+1 MEMBERS
+2 STICKY @ST0008@             /* John Mackay, 1820 */
+~ ~ ~
+
+0 @I0003@ INDI                /* John Mackay */
+1 NAME
+2 FORM John Mackay
+2 PART John
+3 TYPE GIVN
+2 PART Mackay
+3 TYPE SURN
+1 ROLES
+2 STICKY @ST0008@             /* John Mackay mentioned as a clan member */
+~ ~ ~
+
+0 @ST0008@ STICKY             /* Clan member John Mackay */
+1 TYPE PERSON
+1 TITL Clan member John Mackay
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 TEMPLATE @T0123@            /* 1820 court rolls define John as member */
+1 GROUP @G0007@               /* Associated group for John */
+1 ROLE MEMBER
+1 NAME
+2 FORM John Mackay
+2 PART John
+3 TYPE GIVN
+2 PART Mackay
+3 TYPE SURN
+1 DATE 1820
+1 SEX M
+1 SPLAC @SP066@               /* Melvich, Scotland */
+1 OCCU Crofter and Piper
+1 NOTE "John Mackay identified as a clan member in 1820 court rolls."
+~ ~ ~
+```
+#### Tip: Best Practice: Defining Group Membership Periods
+- If no date is provided, the STICKY is treated as undated — indicating only that the relationship existed at some unspecified time.
+
+To express **entry** or **exit** dates, or just **membership** more precisely, use one of the following:
+
+- Use a `DATE RANGE` for a known membership:
+```gedcom
+1 STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 TEMPLATE @T0123@            /* 1820 court rolls */
+1 GROUP @G123@                /* Associated group for John */
+1 Name
+1 FORM John Mackay            /* this is meant to be the full GEDCOM 8 NAME structure */
+1 ROLE MEMBER
+1 DATE FROM 1810 TO 1830      /* Membership over some years, no specific entry and exit date */
+~ ~ ~
+```
+- Use separate STICKYs for joining and leaving:
+
+```gedcom
+1 STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 TEMPLATE @T0456@            /* 1810 guild admission register */
+1 GROUP @G0007@               /* Associated group for John */
+1 Name
+1 FORM John Mackay            /* this is meant to be the full GEDCOM 8 NAME structure */
+1 ROLE JOINED                 /* ROLE JOINED means John entered the Clan */
+1 DATE 1810
+~ ~ ~
+
+1 STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 TEMPLATE @T0111@            /* 1830 community council minutes */
+1 GROUP @G0098@               /* Associated group for John */
+1 Name
+2 FORM John Mackay
+2 PART John
+3 TYPE GIVN
+2 PART Mackay
+3 TYPE LOCATION
+1 ROLE LEFT                   /* ROLE LEFT means John exited the Clan */
+1 DATE 1830
+~ ~ ~
+```
+
+If the exact role is known (e.g., `INITIATED`, `EXPELLED`, `HONOREE`), define this in the ROLE field and include a `DATE`.
+
+If no date is provided, the `STICKY` is treated as undated — indicating only that the relationship existed at some unspecified time.
+
+:::
+
+#### Example: Norwegian Farm Name Group
+:::example
+```gedcom
+0 @G0024@ GROUP
+1 TYPE FARM                   /* groups all farm members of this farm over time */
+1 TITL Lien Farm Group
+1 PHRASE Historic residence unit in Valdres, Norway
+1 SUBM @B001@
+1 NAME
+2 FORM Lien
+2 PART Lien
+3 TYPE LOCATION
+1 NOTE Residents of this farm traditionally adopted 'Lien' as a surname.
+1 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 DATE 1700
+1 MEMBERS
+2 STICKY @ST0091@             /* Ola Lien */
+~ ~ ~
+
+0 @ST0091@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0073@
+1 GROUP @G0024@               /* Lien Farm, Valdres, Norway */
+1 DATE 01 JAN 1832
+1 ROLE MAIN, LEADER, RESIDENT
+1 AGE 39
+1 OCCU Farmer
+1 NOTE Head of household residing at Lien Farm.
+1 NOTE Ola Lien appears in farm census of 1832.
+~ ~ ~
+```
+:::
+
 
 #### `INDIVIDUAL_RECORD` :=
 
@@ -249,24 +634,59 @@ n @XREF:INDI@ INDI                         {1:1}  g7:record-INDI
      +2 <<NOTE_STRUCTURE>>                 {0:M}
   +1 FAMS @<XREF:FAM>@                     {0:M}  g7:FAMS
      +2 <<NOTE_STRUCTURE>>                 {0:M}
+  +1 ROLES                                 {0:1}
+    +2 STICKY @<XREF:STICKY>@              {1:M}  g8:STICKY
+      +3 RESN <List:Enum>                  {0:1}  g8:RESN
+      +3 SUBM @<XREF:SUBM>@                {1:M}  g7:SUBM
+        +4 PHRASE <Text>                   {0:1}  g7:PHRASE
+      +3 PROOF @<XREF:PROOF>@              {0:M}  g8:PROOF
+        +4 OUTCOME <Enum>                  {1:1}  g8:OUTCOME
+  +1 ASSETS                                {0:1}
+    +2 STICKY @<XREF:STICKY>@              {1:M}  g8:STICKY
+      +3 RESN <List:Enum>                  {0:1}  g8:RESN
+      +3 SUBM @<XREF:SUBM>@                {1:M}  g7:SUBM
+        +4 PHRASE <Text>                   {0:1}  g7:PHRASE
+      +3 PROOF @<XREF:PROOF>@              {0:M}  g8:PROOF
+        +4 OUTCOME <Enum>                  {1:1}  g8:OUTCOME
   +1 SUBM @<XREF:SUBM>@                    {0:M}  g7:SUBM
-  +1 <<ASSOCIATION_STRUCTURE>>             {0:M}
   +1 ALIA @<XREF:INDI>@                    {0:M}  g7:ALIA
      +2 PHRASE <Text>                      {0:1}  g7:PHRASE
   +1 ANCI @<XREF:SUBM>@                    {0:M}  g7:ANCI
   +1 DESI @<XREF:SUBM>@                    {0:M}  g7:DESI
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 GEDC                                  {0:1}  g8:GEDC
+    +2 VERS <Special>                      {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>               {1:M}
+      +3 <<ASSOCIATION_STRUCTURE>>         {0:M}
   +1 <<MULTIMEDIA_LINK>>                   {0:M}
-  +1 <<CHANGE_DATE>>                       {0:1}
-  +1 <<CREATION_DATE>>                     {0:1}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 The individual record is a compilation of facts or hypothesized facts about an individual.
 These facts may come from multiple sources.
 Source citations and notes allow documentation of the source where each of the facts were discovered.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes (to make it go alongside GEDCOM 7):}}$
+
+>- `SOURCE_CITATION` and `<<ASSOCIATION_STRUCTURE>>` are now *behind* the same GEDCOM version tag as in the Header.  
+> Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` or `<<ASSOCIATION_STRUCTURE>>` are allowed at this place.   
+> This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and all associations of everything that belongs to it. (inside the `STICKY`s)  
+>- `FAMC` and `FAMS` no longer exist in GEDCOM 8 `INDI`s. As their role is taken over by the `TEMPLATE` itself.  
+>- If an `INDI` has no `ROLES` or `ASSETS` section, it is understood as a GEDCOM 7 `INDI`, where `FAMC` and `FAMS` are possible inside the `INDI`.
+
+$\color{Coral}\large{\textbf{NEW GEDCOM 8 part of INDI record}}$
+
+>- `ROLES`, in this section a list of `STICKY`'s is mentioned that were present, or have a `ROLE`, in a `TEMPLATE`, and contain evidenced information belonging to this `INDI`. The `ROLES` section can have many `STICKY`s, coming from many `TEMPLATE`s.
+>- `STICKY`, The `STICKY` record identifies 1 single person from a `TEMPLATE` record. It describes **all information of this 1 single person** as found in that `TEMPLATE`.
+>- `SUBM`, the user who added this `STICKY` in the `ROLES` section.
+>- `PHRASE`, short description explaining the reason this `STICKY` was added by this user.
+>- `PROOF`, **Experimental Link** to the `PROOF` record, from which result this `STICKY` was added. More `PROOF` records are possible for each `STICKY` as those `PROOF` records may deal with different questions for one and the same `STICKY`.
+>- `OUTCOME`, credibility of this information. (See the `PROOF` record itself.)
+>- `ASSETS`, in this section a list of asset `STICKY`'s is mentioned, that are connected to this `INDI`, as described in the `TEMPLATE` this `STICKY` belongs to.
+
+
 A single individual may have facts distributed across multiple individual records, connected by `ALIA` (alias, in the computing sense not the pseudonym sense) pointers.
 See `ALIA` for more details.
 
@@ -287,6 +707,26 @@ where `@I2@` is a godparent of `@I1@`:
 2 ROLE GODP
 ```
 :::
+***
+$\color{Coral}\large{\textbf{GEDCOM 8 "replacement" for `ASSO`}}$
+
+>With GEDCOM 8 that would be:
+
+>:::example
+
+>The following example refers to 2 individuals, `@I004@` and `@I005@`, where `@I004@` is a godparent of `@I005@`:
+
+```gedcom
+0 @I004@ INDI
+1 ROLES 
+2 STICKY @ST0152@             /* GODPARENT role inside the STICKY */
+```
+>- The `ROLE` of  `I004` is **inside** the `STICKY` now, its the `ROLE` this `INDI (I004)` had, for the `MAIN` person `(I005)` mentioned in the `TEMPLATE` this `STICKY (ST0152)` belongs to. So that makes it absolutely clear who is who in this connection.  
+>- Further: **ALL** events this `INDI` has been part of, are now also in the `ROLES` section, sorted on their `DATE`.
+>- And more: Because parents have been "present" (dead or still alive) at the `BIRT` or from a `MARR` or `ADOP` event of their children, their `ROLE` in those events is also mentioned here. That means **all** children are now kind of present under 1 of their parents (Biological, godparent, or adopting parent). And a long outstanding wish of users, to be able to see **each and every child** of someone, can now be realised easily from this list.  
+
+:::
+***
 
 Events stored as facts within an `INDI` record may also have `FAMC` or `ASSO` tags to indicate families and individuals that participated in those events.
 For example,
@@ -312,9 +752,11 @@ n @XREF:OBJE@ OBJE                         {1:1}  g7:record-OBJE
         +3 FORM <MediaType>                {1:1}  g7:FORM
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<SOURCE_CITATION>>                   {0:M}
-  +1 <<CHANGE_DATE>>                       {0:1}
-  +1 <<CREATION_DATE>>                     {0:1}
+  +1 GEDC                                  {0:1}  g8:GEDC
+    +2 VERS <Special>                      {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>               {1:M}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 The multimedia record refers to 1 or more external digital files, and may provide some additional information about the files and the media they encode.
@@ -325,6 +767,171 @@ The change and creation dates should be for the `OBJE` record itself,
 not the underlying files.
 
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` is now *behind* the same GEDCOM version tag as in the Header.  
+Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` is allowed at this place.   
+This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and everything that belongs to it. (inside the `STICKY`s)  
+
+
+***
+$\color{Fuchsia}\large{\textbf{The following PROOF record is experimental:}}$
+
+#### `PROOF_RECORD` :=
+
+**📜 PROOF_RECORD (experimental)**
+
+The `PROOF` record is an **experimental and optional structure** designed to support **reasoning, weighing, and justification** when evaluating competing `STICKY` records for use in an `INDI` , `GROUP` or `ASSET` role.
+
+>- This structure is currently **an unfinished and provisional concept**.  
+>- It is **not in active use** in the provided examples and may change or be removed in a future version.
+>- Enums belonging to this structure are also defined here, so in case this `PROOF` record will/must be removed, everything is on one place.
+
+**Purpose**  
+
+The `PROOF` record is meant to:
+- Pose a specific genealogical **QUESTION** (e.g., “Which marriage event best matches William Smith?”)
+- List **CANDIDATES** (STICKY references) being considered
+- Provide **ARGUMENTS** and **OUTCOME** ratings _per candidate_
+- Optionally identify a `TOPSTICKY` — the `STICKY` the user considers most accurate
+
+```gedcom
+PROOF_RECORD := 
+n @<XREF:PROOF>@ PROOF                     {1:1}  g8:record-PROOF
+  +1 TYPE <Enum>                           {1:1}  g8:PROOF-TYPE
+  +1 QUESTION <Text>                       {1:1}  g8:QUESTION
+  +1 CANDIDATES                            {1:1}  g8:CANDIDATES
+    +2 STICKY @<XREF:STICKY>@              {1:M}  g8:CANDIDATE-STICKY
+      +3 ARGUMENT <Text>                   {0:M}  g8:ARGUMENT
+      +3 OUTCOME <Enum>                    {0:1}  g8:OUTCOME
+  +1 TOPSTICKY @<XREF:STICKY>@             {0:1}  g8:TOPSTICKY
+  +1 OUTCOME <Enum>                        {0:1}  g8:OUTCOME
+  +1 DATE <Date>                           {0:1}  g7:DATE
+  +1 SUBM @<XREF:SUBM>@                    {0:1}  g7:SUBM
+  +1 <<FLEX_STRUCTURE>>                    {0:M}
+  +1 <<NOTE_STRUCTURE>>                    {0:M}
+  +1 <<MULTIMEDIA_LINK>>                   {0:M}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
+```
+
+**Example Use**  
+A researcher is trying to decide which of two marriage `STICKY` records belongs to a particular `INDI`. They compare `STICKY`s, write arguments, and select the most convincing one.
+
+**Tag Descriptions**
+- `TYPE`: `PROOF_TYPE`: Category of the evaluation (e.g., `BIRTH`, `MARRIAGE`, `IDENTITY`) see `g8:PROOF-TYPE`
+- `QUESTION`: The plain-language question being answered, as filled in by a user. (or maybe by software)
+- `CANDIDATES`: Set of `STICKY` records under consideration. The set could either be given by a user, or software could assist a user in proposing candidate `STICKY`s. As each `STICKY` is tied to 1 `TEMPLATE` the `SOUR` belonging to this `STICKY` can always be reached from that `TEMPLATE`.
+- `ARGUMENT`: Explanatory reasoning from the user in favor of this `STICKY` being correct; may be repeated. Can contain `CONT` as with a `NOTE`.
+- `TOPSTICKY`: The chosen `STICKY` (if one is determined). Can only hold the ID of 1 of the `STICKY`s in the `CANDIDATES` list.
+- `OUTCOME`: Confidence level of this `ARGUMENT` for the selected `STICKY`, from the enumtable `g8:OUTCOME`
+- `DATE`: Optional date when reasoning was formalized
+- `SUBM`: Optional submitter reference responsible for the reasoning.
+- `<<MULTIMEDIA_LINK>>`, link to an `OBJE` for this `PROOF`-record. There is **NO** link to a `SOURCE_CITATION` as that only belongs in the `TEMPLATE`.  
+
+> 🧠 *`ARGUMENT` appears before `OUTCOME` so that evaluators first encounter the reasoning before seeing the resulting confidence level — reinforcing transparent thinking over blind scoring.*
+
+#### `g8:enumset-OUTCOME`
+
+| Value       | Description      |
+|-------------|------------------|
+| `DISPUTED`  | Explicitly contested; arguments exist on both sides                |
+| `SELECTED`  | This is the top candidate (same as the STICKY used in `TOPSTICKY`) |
+| `STRONG`    | Strongly supported by argument(s); high confidence                 |
+| `UNDECIDED` | Unclear or insufficient info to make a judgment                    |
+| `WEAK`      | Weak support; included for completeness or contrast                |
+| `OTHER`     | Used with `PHRASE` for special or ambiguous evaluations            |
+
+**Evaluating OUTCOME:**  
+
+The `OUTCOME` tag represents the status or perceived quality of a candidate argument.
+
+While no formal scoring system is imposed, users may consider:
+
+- **Source Type**: Primary evidence (e.g., original documents) is generally more persuasive than derivative summaries.
+- **Consistency**: Are multiple sources or arguments aligned?
+- **Directness**: Does the evidence relate directly to the claim or is it circumstantial?
+- **Clarity and Logic**: Is the reasoning clearly expressed and logically sound?
+- **Bias**: Could the evidence or its interpretation be skewed?
+- **Currency**: How recent is the evidence?
+
+These factors may influence whether an argument is marked `STRONG`, `DISPUTED`, or otherwise.
+
+Note: These are advisory only — there is no enforced ranking system.
+
+#### `g8:enumset-PROOFTYPE`  
+Defines the kind of question this PROOF record is trying to resolve. Each value describes a specific genealogical topic under investigation.  
+
+| ENUM          | Description    |
+|---------------|----------------|
+| `BIRTHDATE`   | Determining the date of a person’s birth                                    |
+| `BIRTHPLACE`  | Determining the place of a person’s birth                                   |
+| `CHILDREN`    | Evaluating whether someone is a child of the person                         |
+| `DEATHDATE`   | Determining the date of death                                               |
+| `DEATHPLACE`  | Determining the place of death                                              |
+| `GENDER`      | Establishing or confirming the person’s sex/gender                          |
+| `IDENTIFIER`  | Determining whether two records refer to the same individual                |
+| `IMMIGRATION` | Determining the date/place of immigration or emigration                     |
+| `MARRIAGE`    | Confirming that a marriage took place (spouse identity, location, timeframe)|
+| `MARRIAGEDATE`| Determining the exact or likely date of a marriage                          |
+| `NAME`        | Resolving questions around full name, alternate spellings, or nicknames     |
+| `OCCUPATION`  | Confirming a person’s job or profession                                     |
+| `PARENTS`     | Confirming who the person's parents are                                     |
+| `RELIGION`    | Confirming religious affiliation or denomination                            |
+| `RESIDENCE`   | Confirming a person’s key location during a time period                     |
+| `OTHER`       | Other question not listed above; use with `PHRASE` to describe the topic    |
+
+The `PROOF`-TYPE enum describes the focus of a specific proof record — the *question* under evaluation. This may involve choosing between competing `STICKY` entries (e.g., two birth records), or validating a single assertion.
+
+Typical examples include `BIRTHDATE`, `NAME`, or `PARENTS` — but users may also define their own focus via the `OTHER` + `PHRASE` combination.
+
+Note: Some record plausibility issues (e.g., implausible lifespans) are not ideal for `PROOF`-type records unless competing candidate data exists.
+
+:::example  
+
+**💍 Example: PROOF Record — Which Marriage Belongs to Margaret Puddlewharf?**
+
+```gedcom
+0 @P0201@ PROOF
+1 TYPE MARRIAGE
+1 QUESTION What is the correct marriage event for Margaret Puddlewharf of Devon?
+1 CANDIDATES
+2 STICKY @ST2011@  /* 1879 marriage to Henry Bibble at Exeter Cathedral */
+3 ARGUMENT The 1879 Exeter record lists Margaret as 24 years old, matches known birthdate.
+3 OUTCOME SELECTED
+2 STICKY @ST2012@  /* 1881 marriage to Charles Flingham in Barnstaple */
+3 ARGUMENT The 1881 Barnstaple entry lists a Margaret Puddlewharf, age 30, but no parents.
+3 OUTCOME WEAK
+2 STICKY @ST2013@  /* Undated mention of marriage in cousin’s letter */
+3 ARGUMENT Letter mentions a 'Margaret marrying a tall man from Barnstaple' but is undated.
+3 OUTCOME DISPUTED
+1 TOPSTICKY @ST2011@
+1 DATE 29 JUL 2025
+1 SUBM @B001@
+1 NOTE Concluded by age match and parental details listed in the 1879 parish register.
+```
+:::
+
+**📍In the INDI block (snippet only):**  
+
+```gedcom
+1 ROLES
+2 STICKY @ST2011@ /* 1879 marriage to Henry Bibble at Exeter Cathedral */
+3 SUBM @B001@
+3 PROOF @P0201@
+4 OUTCOME SELECTED
+2 STICKY @ST2012@  /* 1881 marriage to Charles Flingham in Barnstaple */
+3 SUBM @B001@
+3 PROOF @P0201@
+4 OUTCOME WEAK
+2 STICKY @ST2013@  /* Undated mention of marriage in cousin’s letter */
+3 SUBM @B001@
+3 PROOF @P0201@
+4 OUTCOME DISPUTED
+```
+
+
+
 
 #### `REPOSITORY_RECORD` :=
 
@@ -338,8 +945,8 @@ n @XREF:REPO@ REPO                         {1:1}  g7:record-REPO
   +1 WWW <Special>                         {0:M}  g7:WWW
   +1 <<NOTE_STRUCTURE>>                    {0:M}
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
-  +1 <<CHANGE_DATE>>                       {0:1}
-  +1 <<CREATION_DATE>>                     {0:1}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 The repository record provides information about an institution or person that has a collection of sources.
@@ -360,15 +967,24 @@ n @XREF:SNOTE@ SNOTE <Text>                {1:1}  g7:record-SNOTE
   +1 TRAN <Text>                           {0:M}  g7:NOTE-TRAN
      +2 MIME <MediaType>                   {0:1}  g7:MIME
      +2 LANG <Language>                    {0:1}  g7:LANG
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 GEDC                                  {0:1}  g8:GEDC
+    +2 VERS <Special>                      {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>               {1:M}
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
-  +1 <<CHANGE_DATE>>                       {0:1}
-  +1 <<CREATION_DATE>>                     {0:1}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 A catch-all location for information that does not fully fit within other structures.
 It may include research notes, additional context, alternative interpretations, reasoning, and so forth.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` is now *behind* the same GEDCOM version tag as in the Header.  
+Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` is allowed at this place.   
+This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and everything that belongs to it. (inside the `STICKY`s)  
+
+
 A shared note record may be pointed to by multiple other structures. Shared notes should only be used if editing the note in one place should edit it in all other places
 or if the note itself requires an `IDENTIFIER_STRUCTURE`.
 If each instance of the note may be edited separately and no identifier is needed, a `NOTE` should be used instead.
@@ -418,8 +1034,8 @@ n @XREF:SOUR@ SOUR                         {1:1}  g7:record-SOUR
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
   +1 <<NOTE_STRUCTURE>>                    {0:M}
   +1 <<MULTIMEDIA_LINK>>                   {0:M}
-  +1 <<CHANGE_DATE>>                       {0:1}
-  +1 <<CREATION_DATE>>                     {0:1}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 A source record describes an entire source.
@@ -432,6 +1048,299 @@ This sourcing model is known to be insufficient for some use cases and may be re
 
 A `SOURCE_RECORD` may contain a pointer to a `SHARED_NOTE_RECORD` and vice versa. Applications must not create datasets where these mutual pointers form a cycle. Applications should also ensure they can handle invalid files with such cycles in a safe manner.
 
+#### `STICKY_RECORD` :=
+
+The `STICKY` record identifies 1 single entity from a `TEMPLATE` record. It describes all information of this 1 single entity as found on that `TEMPLATE`. So 1 `TEMPLATE` can own many `STICKY`'s.
+The same `STICKY` might be linked to many different `INDI`'s, or other records.  
+It is possible for a GEDCOM 8 file to have `STICKY`s that are **not yet linked into an `INDI`s `ROLES` section**, That can happen when a user decides not all `STICKY`s from 1 `TEMPLATE` are important enough to have their own `INDI`.  
+For instance non related persons in a Census.
+
+```gedcom
+n @XREF:STICKY@ STICKY                          {1:1}  g8:record-STICKY
+  +1 TYPE <Enum>                                {1:1}  g8:ENTITY-TYPE
+    +2 SUBTYPE <Enum>                           {1:1}  g8:ENTITY-SUBTYPE
+    +2 PHRASE <Text>                            {0:1}  g8:PHRASE
+  +1 TITLE <Text>                               {0:1}  g8:TITLE
+    +2 PHRASE <Text>                            {0:1}  g8:PHRASE
+  +1 SUBM @<XREF:SUBM>@                         {1:M}  g8:SUBM
+    +2 <<NOTE_STRUCTURE>>                       {0:M}
+  +1 TEMPLATE @<XREF:TEMPLATE>@                 {1:1}  g8:TEMPLATE
+  +1 TORIGIN <Enum>                             {1:1}  g8:TORIGIN
+  +1 QUAY <Enum>                                {0:1}  g7:QUAY
+  +1 DATE <DateValue>                           {1:1}  g8:DATE-value
+  +1 <<SHARED_PLACE_STRUCTURE>>                 {0:1}  g8:SPLAC
+  +1 MAINROLE <Enum>                            {0:0}  g8:STICKY-MAINROLE
+    +2 ROLE <Enum>                              {1:M}  g8:STICKY-ROLE
+  +1 GROUP @<XREF:GROUP>@                       {0:M}  g8:GROUP
+  +1 ASSET @<XREF:ASSET>@                       {0:M}  g8:ASSET
+  +1 RESN <List:Enum>                           {0:1}  g8:RESN
+  +1 TDABOVI <Special>                          {0:1}  g8:TDABOVI
+  +1 <<PERSONAL_NAME_STRUCTURE>>                {0:M}  g8:INDI-NAME
+  +1 PEDI <Enum>                                {0:1}  g7:PEDI
+  +1 SEX <Enum>                                 {0:1}  g8:SEX
+  +1 <<FLEX_STRUCTURE>>                         {0:M}
+  +1 <<LDS_INDIVIDUAL_ORDINANCE>>               {0:1}
+  +1 <<LDS_SPOUSE_SEALING>>                     {0:1}
+  +1 <<FAMILY_EVENT_STRUCTURE>>                 {0:1}
+  +1 <<INDIVIDUAL_EVENT_STRUCTURE>>             {0:1}
+  +1 <<INDIVIDUAL_ATTRIBUTE_STRUCTURE>>         {0:M}
+  +1 <<MULTIMEDIA_LINK>>                        {0:M}
+  +1 LANG <Language>                            {0:M}  g8:SUBM-LANG
+  +1 <<IDENTIFIER_STRUCTURE>>                   {0:M}
+  +1 <<NOTE_STRUCTURE>>                         {0:M}
+  +1 <<CHANGE_DATE>>                            {1:1}
+  +1 <<CREATION_DATE>>                          {1:1}
+```
+- The TYPE value must be chosen from the unified enumset `g8:enumset-ENTITY-TYPE`.
+  - This list includes `PERSON`, which is valid only in `STICKY`'s that reference an `INDI`.
+  - All other `ASSET` types (e.g., `ARTWORK`, `ESTATE`, `PROPERTY`) can be used, regardless of the referenced record type.
+- `SUBTYPE` is required and further narrows the kind of `STICKY` object (depends on `TYPE`).
+   - Most `STICKY`s are of `TYPE` `PERSON` and dont need a `SUBTYPE`, as for a `PERSON` most of the time there is a `ROLE` and `SUBROLE` to further define the `PERSON`.<br>Incase of annotated events, `SUBTYPE` for a person is needed to be able to define the secondary "event" of this `STICKY`.<br>Example: a censustype event where for 1 or more persons there are annotated "events" written in the margin, like *"moved to London feb 89"*. 
+   - When `TYPE` and `SUBTYPE` both are present, they are written on 1 and the same line for readability, with ", " separating them.
+- `PHRASE` This is optonal, **except** for `TYPE` `OTHER`, in that case there **must** be a `PHRASE`; `PHRASE`must be written on the same line as `TYPE`, separated from the `TYPE` contents by ", ". As follows:
+  - `1 TYPE OTHER, "spoon with inscription"`
+  - or `1 TYPE ARTWORK, PAINTING, "Oil painting of Castle King Windemere"`
+
+- `TITLE`, only for an `ENTITY` type `STICKY`: this is the **official title** of this `STICKY` in case it is an item that has a Title, like a painting, a testreport, a book, etc. In case the `STICKY` is about an official document, the `TITLE` is the official title of the document, and `PHRASE` can be a further description. See **Example 08: Naturalization and Passport**
+- `TITL.PHRASE` this can be a further description or subtitle.
+
+- `SUBM` lists the contributor(s) of this STICKY entry.  
+  - The first listed submitter is considered primary, and is the same `SUBM` as used in the `HEAD` of the GEDCOM file.
+  - Additional submitters may represent later changes or annotations.
+  - Use `NOTE` for detailed explanation of edits if needed.
+
+- `TORIGIN`, Defines how a `TEMPLATE` or `STICKY` was originally entered, generated or reconstructed. This helps distinguish freshly structured entries from those generated or inferred from legacy data. It clarifies the **origin and trust context** of each entry — whether manually entered, system-generated, or reverse-engineered — supporting gradual adoption of the new model and better transparency in data lineage.
+
+- `QUAY`, defines the quality of this whole `STICKY`. Together with `TORIGIN`.
+
+- `<<INDIVIDUAL_ATTRIBUTE_STRUCTURE>>`, same as in GEDCOM7, but **without the event part**.
+- `<<FAMILY_EVENT_STRUCTURE>>`, `<<INDIVIDUAL_EVENT_STRUCTURE>>`, `<<LDS_SPOUSE_SEALING>>` and `<<LDS_INDIVIDUAL_ORDINANCE>>`, same as in GEDCOM7, but **without the event part**.
+  - This structure describes the event the linked `TEMPLATE` is about, with the GEDCOM7 tags that excist for the event **in this specific context**.
+  - If the `TEMPLATE` describes an event, for which there is no official GEDCOM tag, it will use the general `EVEN`tag, as follows:<br>`1 EVEN TYPE, SUBTYPE`<br>where `TYPE` and `SUBTYPE` are the same as the event type and subtype of this `TEMPLATE`. So for instance:<br>`1 EVEN DEATH, DISAPPEARED`<br>Doing it this way helps software to understand the event as it comes from the same enum table as is used for the main `TYPE` and `SUBTYPE` for the `TEMPLATE` itself.
+
+- `MAINROLE` defines the contextual function of the participants in this `TEMPLATE`. It is defined as {0:0}
+because:
+  - It is only present to give the user a smaller list of subroles to choose from. The main `ROLE` itself is not mentioned.
+  - There is 1 exeption to that: It is required if `TYPE=PERSON` and this `STICKY` describes an annotated event.
+- `ROLE`:  
+  - It refines the participant’s position in that role, such as `MAIN`, `FATHER`, `MEMBER`, `CHILD`, etc.
+  - `ROLE`s are mentioned on the same line as `ROLE`, separated from each other by ", ".
+  - The first `ROLE` is separated from `ROLE` by 1 space.
+  - There can be more subroles, like for instance `ROLE MAIN, BRIDE` or `ROLE FATHER, BRIDE, PRIEST` (Father of the bride, who also is the priest in the ceremony) 
+- `GROUP`, if present, it points to the `GROUP` this `STICKY` has a connection with. The connection is described in the `TEMPLATE` this `STICKY` belongs to.
+- `ASSET`, only for non-`PERSON` `STICKY`'s, if present, points to the `ASSET` describing the "lifecycle" of this `ASSET`.
+  - **Not all `ASSET`s will have, or need to have, their own `ASSET`record. Only those a user finds important enough.**
+
+> The following applies to `GROUP` and `ASSET`: if a `STICKY` is about a person related to a certain `GROUP` or the `STICKY` describes an entity for which an `ASSET` already excists, or needs to be created, this `STICKY` must have a `GROUP` or `ASSET` link on this place inside the `STICKY`. And if necessary the corresponding `GROUP`- or `ASSET`- record must be created.
+
+- `TEMPLATE`, pointer to the `TEMPLATE` instance this `STICKY` was derived from (so the `TEMPLATE` in which `ROLES` section this `STICKY` is mentioned.)
+  - The `TEMPLATE` pointer is technically deducible from the `STICKY`'s internal ID or generation context, but is required in the export for:
+    - human readability
+    - easy tracing of origin
+    - consistent parsing across tools
+
+- `DATE` The same `DATE` as in the `TEMPLATE` this record refers to (e.g. the date of the marriage, baptism, will) – It defines the date of the described entity's role or involvement. This supports chronological sorting of `STICKY`'s in an `INDI`, `GROUP` or `ASSET`.
+
+- `TDABOVI` This is only valid if the `TEMPLATE` this `STICKY` belongs to, contains secondary events that together form a mini-tree. (also see the `TDECUJUS` description with the `TEMPLATE` itself.)  
+  - **Example: a family bible with a handwritten part**, that describes many people of a family in a tree-like way.  
+  In that case, it is **the D'Aboville number of this `STICKY`'s person** in the mini-tree inside this `TEMPLATE`. 
+
+- `PERSONAL_NAME_STRUCTURE`, this is the Name of the person, or asset in this `STICKY`.
+  - It follows the new GEDCOM8 Name structure!
+- `FLEX_STRUCTURE`, this is used for information in the `STICKY` that has no GEDCOM tag, and that should be saved, and later represented, to a user. For instance:
+  - Signature information: "signed with a mark", or "Signature illegible".
+  - Comments written in the margin: "Clerk wrote: 'mother possibly misnamed'".
+  - Witness behaviour: "Witness appeared intoxicated"
+
+- `INDIVIDUAL_ATTRIBUTE_STRUCTURE`, partly the same as for `INDI`
+  -  It only describes facts and attributes known about the STICKY object **in this specific context**.
+  -  It **doesnt have the `EVENT_DETAIL` structure** inside. As the `TEMPLATE` itself describes the **event** or **situation**.
+  - For instance it describes `BURI` with a `TYPE` and an `AGE` and nothing more. As the event itself, is already described in the `TEMPLATE` this `STICKY` comes from / belongs to.
+- `SEX`, `LANG`, `MULTIMEDIA_LINK`, and `IDENTIFIER_STRUCTURE` are standard GEDCOM7 elements.  
+  -  These are used as defined in GEDCOM7 unless otherwise noted.
+---
+
+#### IMPORTANT!
+- The `STICKY` only contains data that is directly or indirectly found in or on the `TEMPLATE`**it is part of!** So if, in older records, hardly any other information is present, the `STICKY` might not contain much more than eventdate, name, and `ROLE`'s. But more modern records might have a lot of information about people for instance, `NAME`, `AGE` and or `BIRT`, `RESI` and or `ADDR`, `OCCU`, `RELI`, marriage status like "widow", and more.<br>Each of those go in their corresponding `TAG` in the `STICKY`.
+- Each `STICKY` is an unseparable part of only 1 `TEMPLATE`.
+- Each new `TEMPLATE` gets its own `STICKY`'s! A `STICKY` can not be reused for another `TEMPLATE` as it only "belongs" to 1 !
+- 1 and the same `STICKY` **can be connected to more records**, as it can be part of for instance an `INDI` but at the same time it can also be part of a `GROUP` (as a `GROUP` member).<br>In case the `STICKY` for instance is a child, it can be linked in its own `INDI`, but also in the `INDI`'s of both its Father and Mother, as they have the parent role on a birth certificate.
+>  - **This means the `FAM` record is no longer used in GEDCOM 8**.
+- `ADOP` and `PEDI`: If the `TEMPLATE` is about an adoption, the `TEMPLATE`, as wel as the `STICKY` of the child, have `ADOP` inside it, followed by `PEDI` with the type of "pedigree". In case of an adoption it will be `1 PEDI ADOPTED`, in case of a sealing it will be `1 PEDI SEALING` etcetera. 
+
+#### SPECIAL CASES:
+
+`ROLE`'s inside a `STICKY` have a very important function. They define the `ROLE` or `ROLE`'s the `STICKY`-entity has in the `TEMPLATE` it belongs to.  
+Now it is also mentioned that `ROLE`'s are separated from eachother by a ", ". When 2 `ROLE`'s are directly after one another, and those `ROLE`'s are family related, we pronounce the "," as: **"of the"**, see below. 
+
+- `ROLE MAIN`: This role denotes the main entity, or entities, of the `TEMPLATE`. It is a necessary role, to be able to define family related connections. For instance:
+  - `ROLE MAIN, BRIDE` This defines that this `STICKY` is the bride (a main person) in a marriage. But as often her father, mother and maybe brothers and sisters and other family members are present, we need `MAIN` as a reference point. So we can say:
+  - `ROLE MOTHER, BRIDE` which is the mother **of the** bride. And we can also have:
+  - `ROLE FATHER, BRIDE, PRIEST`. Here we have a father **of the** bride, who also is the `PRIEST` in the ceremony. For this last one we could also fill in an `OCCU PRIEST` for the father, as that can be concluded from his role.
+  - If a `STICKY` for instance is the birth of a child, and his parents are part of a group, like a `FARM`, the `ROLE`'s for the child become `1 ROLE MAIN, CHILD, MEMBER`, as the child in that case automatically becomes a member too, because of his parents. Further, in that case, the childs `STICKY` gets a pointer to the `GROUP` its parents belong to.
+
+
+- There is no rule/limit on the `ROLE`'s we can combine (although it must be reasonably readable and understandable!), so for instance we can have:
+  - `ROLE MAIN, BRIDE` and in that same `TEMPLATE` we have another `ROLE MAIN, BRIDE`, that gives us a couple with 2 woman.
+  - But as we now might get problems **defining their relatives** we must do it like this:
+    - `ROLE MAIN, BRIDE1` and another `ROLE MAIN, BRIDE2`. So we put a number behind each `BRIDE`, to be able to correctly define their relatives. That way we can say: `ROLE, MOTHER, BRIDE2` and we have the mother **of the** bride number 2. That saves us the trouble of being forced to put names inside a `ROLE` tag otherwise, as we dont want to do that.
+- As we also have the role `PARTNER` which is a person of whom we do not now the sex we can define:
+  - `ROLE MAIN, BRIDE` together with `ROLE MAIN, PARTNER`. Now we have a relationship where one of the 2 does not want to be called man or woman, and in case both dont want to be called that we can also have:
+  - `ROLE MAIN, PARTNER1` and `ROLE MAIN, PARTNER2`. (Again with a number to be able to distinguish between them)
+
+- We can even go one step further and have a relation that has the 3 following roles:
+  - `ROLE MAIN, BRIDE1` and a `ROLE MAIN, BRIDE2` together with this one: `ROLE MAIN, GROOM`. Now we have a polyamorous relationship.
+
+- We must make sure, that in case we have more `ROLE`'s in 1 tag, they follow each other in a logical sequence! So **dont write** `ROLE FATHER, PRIEST, BRIDE` but in stead write `ROLE FATHER, BRIDE, PRIEST` (father of the bride who is also the priest) or `ROLE PRIEST, FATHER, BRIDE` (the priest, who is also father of the bride).
+
+- Another `ROLE` that might need to be numbered is `HEIR`, as there can be more `HEIR`'s in 1 will. So we might see for that `TEMPLATE`: `ROLE HEIR1` , `ROLE HEIR2` etc.
+
+#### Role numbering:
+All `ROLE`'s that appear more than once in 1 `TEMPLATE` and can cause confusion because other persons might have a `ROLE` **that denotes a relationship** to them, are numbered to prevent confusion:
+- Example 1 a will with 3 HEIRS, they will be numbered like this inside the `ROLE` section in the respective `STICKY`s: `HEIR1`, `HEIR2` and `HEIR3`.
+- Example 2 a marriage with 2 brides: the `ROLE` in their `STICKY`s will be: `BRIDE1`and `BRIDE2`, so other family members can be related to the correct Bride. (`ROLE FATHER, BRIDE1` or `ROLE FRIEND, BRIDE2`)
+- Example 3 a Census, where each family member has the `ROLE` `RESIDENT`, here numbering is not necessary as there is no `ROLE` that "relates" to `RESIDENT`.
+
+#### Examples
+
+:::example
+#### STICKY Example 1 – Groom in a Marriage Certificate
+
+This is a full example of a STICKY_RECORD, based on a marriage certificate. It shows the groom as the subject, including personal name, role, and details derived from the certificate's template.
+
+**Explanation:**
+
+- This `STICKY` refers to **Pieter van Dijk**, the groom, age 21, he is a baker.
+- His data is taken only from template @T0123@, (dated 1855-06-14) which corresponds to a marriage certificate from Amsterdam.
+- His occupation, residence, and birth are included in this `STICKY` **because they appear on the document**.
+- `ROLE` is `GROOM`, with `MAIN` to indicate he's a main subject.
+- This `STICKY` is **only filled** with information that is present **on the `TEMPLATE`** it derives from. 
+- This record can now be linked inside an `INDI` record for Pieter, contributing to his `INDI`-timeline, based on this one source.
+
+```gedcom
+0 @ST345@ STICKY              /* Pieter van Dijk */
+1 TYPE PERSON
+1 SUBM @B001@                 /* Original submitter (same as in the HEAD of the GEDCOM) */
+1 TEMPLATE @T0123@            /* The original marriage certificate template this STICKY belongs to */
+1 TORIGIN ORIGDOC             /* Directly derived from an original document */ 
+1 QUAY 3
+1 DATE 1855-06-14             /* The date of that template, so the marriage registration date */
+1 ROLE MAIN, GROOM            /* He is 1 of the 2 MAIN persons, and he is the GROOM */
+1 NAME                        /* In latest NAME format of GEDCOM8 */
+2 TYPE GENERAL
+1 FORM Pieter van Dijk
+2 PART Pieter
+3 TYPE GIVN
+2 PART PIET
+3 TYPE VARIANT
+2 PART van                    /* PART is particle, e.g. Dutch "van", "van de", or "uijt den" — or French "de", Italian "di" */
+3 TYPE PART
+2 PART DIJK
+3 TYPE SURN
+1 SEX M
+1 MARR                        /* Information of the marriage itself */
+2 TYPE CIVIL
+2 DATE 1855-06-14
+2 SPLAC @SP063@               /* Amsterdam, Noord-Holland, Netherlands */
+1 AGE 21
+1 BIRT
+2 DATE ABT 1834               /* Estimated birth date from age */
+2 SPLAC @SP628@               /* Leiden, Zuid-Holland, Netherlands */
+1 OCCU Baker
+1 RESI
+2 DATE ABT 1855
+2 SPLAC @SP063@               /* Amsterdam, Noord-Holland, Netherlands */
+1 NOTE This STICKY only reflects the data for the groom as recorded in this civil marriage record.
+1 CITA
+~ ~ ~
+1 CREA 01 MAY 2025
+1 CHAN 03 MAY 2025
+```
+:::
+
+### STICKY Example 2 – Militaire Willems-Orde Medal ("ASSET" STICKY) 
+
+This `STICKY` describes a medal as an `ASSET`, specifically the Militaire Willems-Orde (4e klasse), awarded in 1831 after the Ten Day Campaign. The 2 `FLEX` entries capture the registry number and a Dutch-language archival description.
+For these 2 values there is no official GEDCOM tag, but this way they can still be entered, and shown to the user.  
+This `STICKY` is an `ASSET` so it has **No `ROLE`'s**  
+The `TEMPLATE` this `STICKY` belongs to, has a `TRANSFER` statement, that describes the "move" for the medal from the organization that cxxx the medal, to the new owner: Willem Johan de Vries, as in the `STICKY` in  example 3.
+
+```gedcom
+0 @ST998@ STICKY
+1 TYPE MILITARY, MEDALS, "Ridder vierde klasse in de Militaire Willems-Orde, uitgereikt na Tiendaagse Veldtocht"
+1 TITL Militaire Willems-Orde – 4e klasse
+1 SUBM @B001@                 /* Submitter of this record (likely from archival source) */
+1 TEMPLATE @T456@             /* This could be a military honors record or award list */
+1 TORIGIN ORIGDOC             /* Directly derived from an original document */ 
+1 QUAY 3
+1 DATE 1831-09-15             /* Actual date of the award ceremony or registration */
+1 SPLAC @SP942@               /* 's-Gravenhage, Zuid-Holland, Netherlands */
+1 FLEX REGNUMBER
+2 CONTENTS MW-1831-00456      /* This is the registration nr of this medal */
+2 PHRASE "Registratie nummer" /* This is the exact text as it is found on the record itself */
+3 LANG nl
+1 FLEX NOTE
+2 CONTENTS "Ridderorde toegekend voor moed en beleid tijdens de Tiendaagse Veldtocht"
+2 PHRASE "Beschrijving van de medaille"
+3 LANG nl
+~ ~ ~
+1 CREA 05 MAY 2025
+1 CHAN 06 MAY 2025
+```
+### STICKY Example 3 – recipient of the medal in `@ST998@` (previous example)
+
+- This `STICKY` describes the recipient of the medal in `@ST998@`, in the previous example.
+- The `FLEX` encodes the rank specifically at the time of the award.
+- `PHRASE` shows the field as seen in the source register.
+- "Militair register van onderscheiding" = "Military Register of Awards"
+- The actual Transfer of the medal to Willem, is done on the `TEMPLATE` itself by means of a `TRANSFER` structure.
+
+```gedcom
+0 @ST999@ STICKY
+1 TYPE PERSON                 /* `PERSON` only has a `SUBTYPE` for secondary events */
+1 TITL "Militair register van onderscheiding, 1831"
+1 SUBM @B001@
+1 TEMPLATE @T456@             /* Same template as the medal itself, STICKY @ST998@ */
+1 TORIGIN ORIGDOC             /* Directly derived from an original document */ 
+1 QUAY 3
+1 DATE 1831-09-15             /* Date on the source document */
+1 ROLE MAIN, RECIPIENT        /* RECIPIENT of the medal */
+1 NAME
+2 TYPE GENERAL
+2 FORM Willem Johan de Vries
+2 PART Willem Johan
+3 TYPE GIVN
+2 PART de
+3 TYPE PART
+2 PART Vries
+3 TYPE SURN
+1 NAME
+2 TYPE INFORMAL
+2 FORM WIM
+2 PART WIM
+3 TYPE ROEPNAAM
+1 SEX M
+1 OCCU Kapitein der Infanterie   /* Captain of Infantry */
+1 BIRT
+2 DATE 1795
+2 SPLAC @SP937@               /* Utrecht, Utrecht, Netherlands */
+1 DEAT
+2 DATE 1847
+2 SPLAC @SP534@               /* Maastricht, Limburg, Netherlands */
+1 FLEX DESCRIPT
+2 CONTENTS "Kapitein der Infanterie"
+2 PHRASE "Rang bij onderscheiding"  /* Rank by distinction */
+3 LANG nl
+1 FLEX NOTE
+2 CONTENTS "Willem Johan de Vries ontving de Militaire Willems-Orde (vierde klasse) voor zijn moed tijdens de Tiendaagse Veldtocht."
+2 PHRASE reden van onderscheiden.
+3 LANG nl
+1 CITA
+~ ~ ~
+1 CREA 05 MAY 2025
+1 CHAN 06 MAY 2025
+```
+
 #### `SUBMITTER_RECORD` :=
 
 ```gedstruct
@@ -446,8 +1355,8 @@ n @XREF:SUBM@ SUBM                         {1:1}  g7:record-SUBM
   +1 LANG <Language>                       {0:M}  g7:SUBM-LANG
   +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<CHANGE_DATE>>                       {0:1}
-  +1 <<CREATION_DATE>>                     {0:1}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
 ```
 
 The submitter record identifies an individual or organization that contributed information contained in the dataset.
@@ -455,6 +1364,253 @@ All records in the document are assumed to be contributed by the
 submitter referenced in the `HEAD`,
 unless a `SUBM` structure inside a specific record points at a different submitter record.
 
+#### `TEMPLATE_RECORD` :=
+
+The `TEMPLATE` record identifies **1 single event**  or situation from a `SOUR`. It describes all information of this 1 single event/situation as found in that `SOUR`. So if a `SOUR` is a churchbook, the `TEMPLATE` defines 1 birth, or 1 marriage etcetera. 
+
+The main information of the `TEMPLATE` is in fact the same as what in GEDCOM V7 was called "SOURCE_CITATION". But the information that in V7 was inside the transcription, so just a "booklike" 1 on 1 transcription of the event/fact data itself, including all the people present at that event or having some relation to the situation, including all information found about those persons / assets, all that is now also put in a `STICKY` of its own.  
+1 `STICKY` for each person or asset involved. And each `STICKY` describing the `ROLE`('s) that person or `ASSET` had in this 1 event.  
+
+---
+> **Linking to a `TEMPLATE`:** The **only place** a link to a `TEMPLATE` is allowed is from **inside a `STICKY`**. Each `STICKY` **always** links back to the `TEMPLATE` it belongs to and is part of.
+---  
+
+#### 📌 Guidelines for Choosing the `MAIN` Person(s) in a TEMPLATE
+
+The `MAIN` person or persons of a `TEMPLATE` represent the primary individual(s) the document is *about*. This may differ from the person who created or signed the record. The goal is to clearly reflect **who is central to the event** described in the `TEMPLATE`.
+
+---
+
+**🔁 NOTE:** `MAIN` is added in the `ROLE` field **inside** each `STICKY`, *not* in the `TEMPLATE` structure itself. This tells software and humans **who the document is about**, without duplicating data in the TEMPLATE header.
+
+---
+
+#### ✅ Common Examples (Straightforward)
+| Event Type           | `MAIN` Person(s)                                   |
+|----------------------|----------------------------------------------------|
+| Birth                | The child being born                               |
+| Marriage             | The couple getting married                         |
+| Tombstone            | All persons named on the stone                     |
+| Family Bible         | The "de cujus" (person the tree starts from) and partner |
+
+#### ⚠️ Tricky Cases (Could be Misunderstood)
+| Document Type              | `MAIN` Person(s) Explanation |
+|----------------------------|------------------------------|
+| **Census household**       | Head of household only — others are included as family but not `MAIN` |
+| **Will / Probate**         | The deceased (decedent, testator). Heirs and executors are not `MAIN` |
+| **Pension Application**    | The applicant (e.g., widow); not the deceased spouse |
+| **Court Case**             | The defendant (person accused or sued); witnesses/judges not `MAIN` |
+| **Affidavit / Declaration**| The person making the sworn statement |
+| **Naturalization**         | The person becoming a citizen |
+| **School Enrollment**      | The student (not the guardian who signs) |
+| **Marriage License Application** | The couple applying; witnesses and officials are not `MAIN` |
+| **Medical Report**         | The patient |
+| **Ship Manifest**          | The immigrant listed (typically head of family or individual traveler) |
+| **DNA Test Report**        | The individual whose DNA is being tested or interpreted |
+
+> 👤 Use `MAIN` only for persons who are central to the event or document's **evidentiary focus**.
+
+So a `TEMPLATE` consists of information from:
+- `EVENT_DETAIL` as a `TEMPLATE` describes the event (or events, see below). **But without** the `ASSOCIATION_STRUCTURE` of the `EVENT_DETAIL`, as that is now described by the `ROLE`'s in each `STICKY`.
+- `SOURCE_CITATION` All information from that is now inside a `CITA_STRUCTURE`. Except the event itself, as that is now taken over by the whole `TEMPLATE`.
+- 1 or more `STICKY`s, each describing 1 person or `ASSET` and its `ROLE` in the event.
+
+```gedstruct
+n @XREF:TEMPLATE@ TEMPLATE                 {1:1}  g8:record-TEMPLATE
+  +1 TYPE  <Enum>                          {1:1}  g8:EVENT-TYPE
+    +2 SUBTYPE  <Enum>                     {1:1}  g8:EVENT-SUBTYPE
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 TITLE <Text>                          {1:1}  g8:TITLE
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 SUBM @<XREF:SUBM>@                    {1:M}  g8:SUBM 
+    +1 <<NOTE_STRUCTURE>>                  {0:M}
+  +1 RESN <List:Enum>                      {0:1}  g8:RESN
+  +1 TORIGIN <Enum>                        {1:1}  g8:TORIGIN
+  +1 QUAY <Enum>                           {0:1}  g7:QUAY
+  +1 DATE <DateValue>                      {1:1}  g8:DATE-value 
+    +2 TIME <Time>                         {0:1}  g8:TIME
+    +2 PHRASE <Text>                       {0:1}  g8:PHRASE
+  +1 <<SHARED_PLACE_STRUCTURE>>            {1:M}  g8:SPLAC
+  +1 <<LDS_INDIVIDUAL_ORDINANCE>>          {0:1}
+  +1 <<LDS_SPOUSE_SEALING>>                {0:1}
+  +1 <<FAMILY_EVENT_STRUCTURE>>            {0:1}
+  +1 <<INDIVIDUAL_EVENT_STRUCTURE>>        {0:1}
+  +1 AGNC <Text>                           {0:1}  g7:AGNC
+  +1 RELI <Text>                           {0:1}  g7:RELI
+  +1 CAUS <Text>                           {0:1}  g7:CAUS
+  +1 PEDI <Enum>                           {0:1}  g7:PEDI
+  +1 SDATE <DateValue>                     {0:1}  g7:SDATE
+    +2 TIME <Time>                         {0:1}  g7:TIME
+    +2 PHRASE <Text>                       {0:1}  g7:PHRASE
+  +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
+  +1 ROLES                                 {1:1}  g8:ROLES
+    +2 STICKY @<XREF:STICKY>@              {1:M}  g8:STICKY
+      +3 RESN <List:Enum>                  {0:1}  g8:RESN
+  +1 TDECUJUS @<XREF:STICKY>@              {0:1}  g8:TDECUJUS
+  +1 <<TRANSFER_STRUCTURE                  {0:M}
+  +1 <<FLEX_STRUCTURE>>                    {0:M}
+  +1 <<ADDRPLUS_STRUCTURE>>                {0:1}  g8:ADDRPLUS
+  +1 <<NOTE_STRUCTURE>>                    {0:M}
+  +1 <<MULTIMEDIA_LINK>>                   {0:M}
+  +1 <<CITA_STRUCTURE>>                    {1:1}
+  +1 <<IDENTIFIER_STRUCTURE>>              {0:M}
+  +1 <<CHANGE_DATE>>                       {1:1}
+  +1 <<CREATION_DATE>>                     {1:1}
+```
+
+:::example  
+##### example of a `TRANSFER`: 
+
+Suppose there is a Will, with a deceased, a witness, an heir, and a piece of land, that Will will have:
+- 1 `STICKY` for the deceased, with roles: `MAIN, DECEASED, GRANTOR` or officially `MAIN, DECEDENT, GRANTOR`. He transfers ownership of the piece of land.
+- 1 person `STICKY` for the witness, with Role: `WITNESS`
+- 1 person `STICKY` for the heir, with role: `HEIR, SON`, if he is also the son of the deceased.
+- 1 `STICKY` for the land, with Sticky type: `ESTATE, PARCEL` or `LAND, FIELD` or `PROPERTY, FARM`, depending on the situation. 
+- a `TRANSFER` structure in the `TEMPLATE` itself, that shows the piece of land goes from the `GRANTOR` (the deceased) to the `GRANTEE` (the heir).  
+:::
+
+So a template can be the origin of many STICKY's. Each of those `STICKY`'s might/can be linked to many different `INDI`'s, or other records.
+
+- `TYPE` and `SUBTYPE`. These 2 belong together. Eacht `TYPE` can have 1 or more `SUBTYPES`. They are written on the same line starting with the choosen `TYPE` value. For instance `TYPE PERSON` for a `STICKY` that describes a person, or `TYPE ESTATE, LAND` for a piece of land in for instance a will. 
+  - `PHRASE` can be used to further specify. It is always part of the `TYPE`-line.
+- `TITLE` this is the **official title** of this certificat, as know by an authority. So not "John Doe Birth Certificate" but:
+  -	"Standard Dutch Birth Certificate (1811-1870)"
+  - "Catholic Church Marriage Record (19th Century)"
+- `TITL.PHRASE` this can be the unofficial "name" of this certificate like: "John Doe Birth Certificate"
+
+- `TORIGIN`, Defines how a `TEMPLATE` or `STICKY` was originally entered, generated or reconstructed. This helps distinguish freshly structured entries from those generated or inferred from legacy data. It clarifies the **origin and trust context** of each entry — whether manually entered, system-generated, or reverse-engineered — supporting gradual adoption of the new model and better transparency in data lineage.
+
+- `QUAY`, defines the quality of this whole `TEMPLATE`. Together with `TORIGON`.
+
+- `DATE` and `<<SHARED_PLACE_STRUCTURE>>`, they describe the date and place of this `TEMPLATE`. This is not necessarely the same as the date and place of the event. For instance a `BIRT` happens a few days earlier, than the actual filing of the birth record itself.
+
+- `<<FAMILY_EVENT_STRUCTURE>>`, `<<INDIVIDUAL_EVENT_STRUCTURE>>`, `<<LDS_SPOUSE_SEALING>>` and `<<LDS_INDIVIDUAL_ORDINANCE>>`, 1 of these must be present in a `TEMPLATE`:
+  - These structures describes the event this `TEMPLATE` is about, with the GEDCOM7 tags that excist for the event **in this specific context**.
+  - Only 1 of these 4 can, and must be present.
+  - If the `TEMPLATE` describes an event, **for which there is no official GEDCOM tag**, it will use the general `EVEN` tag, as follows:<br>`1 EVEN TYPE, SUBTYPE, PHRASE`<br>where `TYPE`, `SUBTYPE`, and `PHRASE` are the same as the event type and subtype of this `TEMPLATE`. So for instance:<br>`1 EVEN DEATH, DISAPPEARED`<br>Doing it this way helps software to understand the event as it comes from the same enum table as is used for the main `TYPE` and `SUBTYPE` for the `TEMPLATE` itself.
+  - The Event of the `TEMPLATE` goes to all person `STICKY`s that have `MAIN`in their `ROLE`. So for `BIRT` its only the child, for a marriage its the `BRIDE` and the `GROOM`, but for a `CENSUS` its all persons who are on the Census. Other persons and assets in the `TEMPLATE` dont get the event, as they were there, but didnot play a `MAIN` `ROLE`. And if they need the event, they can find it through the `TEMPLATE` pointer that is in each `STICKY`.
+  - If a `TEMPLATE` is of type `SECONDARY`, the `TEMPLATE` itself has an event, but the persons in the `TEMPLATE` have not.
+
+- `ROLES`: in this section a list of `STICKY`'s is mentioned that are present, or have a `ROLE`, in the event of this `TEMPLATE`. Each `STICKY` can only be mentioned inside the `ROLES` section of 1 `TEMPLATE`, as it is only part of, and in fact, belongs to, **that** `TEMPLATE`. But that same `STICKY` **can** be mentioned in other records, like the person it belongs to, or the `GROUP` it belongs to.
+
+- `TDECUJUS`, Only used if the `TEMPLATE`, contains secondary events that together form a mini-tree.  
+**Example: a family bible with a handwritten part**, that describes many people of a family in a tree-like way.  
+Normally those people and the events described, would all have their own `TEMPLATE`. As they all would have their own separate official document. But in this case the Bible is the `TEMPLATE` and **the "events" are only annotated inside the Bible's pages**.  
+As in that case the normal `ROLE` system, that defines the connection people have relative to each other in the family, is not possible, as there might be many generations in that annotated part. And `ROLES` are defined for relations of 1, at most, 2 generations apart.  
+  - So in this special case, for the annotated people **inside this `TEMPLATE`**, we use the d'Aboville numbering system.
+  - And **the eldest person in that annotated tree is the De Cujus**.  
+  - Further numbering is done inside the `STICKY`'s belonging to this special `TEMPLATE`, starting from the De Cujus.
+  - The **`TDECUJUS`** points to the `STICKY` that is **the eldest person** in this annotated part of the `TEMPLATE`.  
+
+  The name `TDECUJUS` starts with a **T** to denote it belongs inside a `TEMPLATE` so if there would ever be a DeCujus necessary in GEDCOM, `DECUJUS` can be used. Same for `TDABOVI`.
+
+- `TRANSFER_STRUCTURE`, this is used to be able to denote if an asset `STICKY` is "moving" on or in this `TEMPLATE`. Example:
+  - In case of an asset `STICKY`, for a piece of land on a will `TEMPLATE`, it defines from whom to whom this `ASSET` is transferered
+  - If 1 asset goes to more `HEIR`s, the `SHARE` of the `TRANSFER` is used to define the share of each `HEIR`.
+- `FLEX_STRUCTURE`, this is used for information on the `TEMPLATE` that has no GEDCOM tag, and that should be saved, and later represented, to a user. For instance:
+  - The addres of an agency that is the issuer of the official form, but that can not be saved and/or represented in current GEDCOM.
+  - Other possibilities: Filing location name, Local form number, Reason for record, Document state, Consent or approval line.
+  - Document condition: "Torn, corner missing".
+
+- `ADDRPLUS_STRUCTURE`, If necessary the complete addressing information of the Organization that issued the `TEMPLATE`, in case the `TEMPLATE` describes a document issued by that specific Organisation.<br>For instancce a Will certificate issued by a notary office. Or an adoption certificat issued by a court.
+
+- `SOUR`, this is seen as the origin for this `TEMPLATE`. Now as a `SOUR` in itself can point to more `TEMPLATE`'s (example: church book with many birth records) it is allowed for a `SOUR` to be linked to in other **`TEMPLATE`'s**. But a `SOUR` is only linked to from inside 1 or more `TEMPLATES` never from any other place in the GEDCOM file.
+- `RESN` (below `STICKY`, this is meant to have a restriction on just this 1 `STICKY` when needed.
+- By default the first `SUBM` wil point to the submitter as referenced in the `HEAD`,
+unless there are 1 or more extra `SUBM`'s in this `TEMPLATE` structure. In that case each of these extra `SUBM`'s points to the submitter who changed this `TEMPLATE` record. That way changes can be tracked. The `NOTE_STRUCTURE` of a `SUBM` can be used to describe those changes.
+
+---
+
+#### IMPORTANT!
+- `ADOP` and `PEDI`: If the `TEMPLATE` is about an adoption, the `TEMPLATE`, as wel as the `STICKY` of the child, have `ADOP` inside it, followed by `PEDI` with the type of "pedigree". In case of an adoption it will be `1 PEDI ADOPTED`, in case of a sealing it will be `1 PEDI SEALING` etcetera. 
+
+
+#### TEMPLATE example
+::example
+
+This `TEMPLATE` describes a marriage event (`MARR`) involving several people.
+- `MARR` has a `DATE` and an `SPLAC`, following the GEDCOM 7 convention.
+- **However**, the event description that would normally go *under* the `MARR` tag now appears directly under the `TEMPLATE` itself.  This change is necessary because a `TEMPLATE` can now represent far more events than GEDCOM 7 allowed. And all those events can now be handled the same way.
+
+- If a `TEMPLAYE` describes an event, that has no GEDCOM8 tag, use the general `EVEN` in its place, with `DATE` and `SPLAC` *under* it.
+
+```gedcom
+0 @T0042@ TEMPLATE
+1 TYPE MARRIAGE, CIVIL        /* Eventtype marriage, is MARR tag */
+1 TITL Wedding Certificate Springfield
+2 PHRASE Wedding "Certificate"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 MARR                        /* Family Event */
+2 DATE 18 JUN 1954            /* Marriage date */
+2 SPLAC @SP006@               /* Place of marriage - London */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE, not necessarily the MARR date */
+1 SPLAC @SP006@               /* Place of this event - London */
+1 ROLES
+2 STICKY @ST0142@             /* MAIN, BRIDE */
+2 STICKY @ST0143@             /* MAIN, GROOM */
+2 STICKY @ST0241@             /* FATHER, BRIDE Father of the Bride */
+2 STICKY @ST0242@             /* MOTHER, GROOM, Mother of the Groom */
+2 STICKY @ST0341@             /* UNCLE, BRIDE, Uncle of the Bride */
+2 STICKY @ST0342@             /* FRIEND, GROOM, Friend of the Groom */
+2 STICKY @ST0441@             /* OFFICIANT of the Marriage */
+1 PAGE 5                      /* Pagenumber this certificat is found in the source */
+1 DATA 
+1 CREA 22 JUL 2025
+1 CHAN 22 JUL 2025
+```
+::: 
+
+#### "Missing" information, compared to GEDCOM V7's Source-Citation:
+
+- `EVEN` The Event-tag, is now kind of "substituted" by `TYPE`and `SUBTYPE`of the `TEMPLATE` itself. Together with the tag for the event, mentioned in the `STICKY`s the tag belongs to.
+- `ROLE` now moved inside a `STICKY` as each person or asset present at the event or situation, can have its own `ROLE` or even more roles, like a `FATHER` who is also a `WITNESS` in a marriage. So `ASSO` is no longer needed.
+- Non mentioned tags, have the same meaning as in GEDCOM 7, as they originally came from the `EVENT_DETAIL` or the `SOURCE_CITATION` in GEDCOM7.
+
+#### Handling Annotated (Secondary) Events in Templates
+
+A `TEMPLATE` normally describes a **single event** or action, drawn from one real-world document or genealogical artifact. Its `TYPE` defines the main event it represents (e.g., `CENSUS`, `BAPTISM`, `MARRIAGE`) and determines the structure and roles within.
+
+However, some documents, for instance a Census, also include **additional notes or annotations** about **secondary events**. These are not the primary focus of the Census document but may record occurrences such as:
+
+- The **birth** of a child during the time of residence (`CENSUS`)
+- The **death** of a household member (added later to the census form)
+- A **move or departure** noted in a margin, sometimes with a new address
+
+These secondary facts do **not** alter the `TYPE` of the `TEMPLATE`, which remains bound to the main document’s function. And they are not the **primary event** of the document (which remains a `CENSUS`), but they are real, meaningful notes that deserve structured representation.
+
+So they justify the creation of **additional `STICKY`s**, each of which may describe the side-event involving a person already mentioned in another `STICKY` in this `TEMPLATE`.
+
+Rather than redefining the `TEMPLATE.TYPE`, we handle these as **additional STICKYs** tied to the same template. These `STICKY`s describe **side events**, and have specially designated `STICKY`-subtypes that reflect their **marginal nature** — typically annotations or supplemental facts, described in the `STICKY`-type itself like:
+
+:::examples:
+```
+1 TYPE PERSON, AN_BIRTH
+1 TYPE PERSON, AN_DEATH
+1 TYPE PERSON, AN_LEAVE
+```
+:::
+
+The `TYPE` is still `PERSON`, but the subtype makes it clear this is an *annotation event* — a derived fact extracted from a margin, note, or supplement, not the main event. This method:
+
+- Keeps `TEMPLATE.TYPE` singular and correct
+- Allows side events to be described without muddling the main structure
+- Ensures clarity and integrity for users and software
+
+This approach allows multiple STICKYs per person in the same TEMPLATE:
+
+- One for their **main role** (e.g., household member)
+- One or more for **annotated roles** or **side events**
+
+These additional STICKYs remain linked to the same TEMPLATE.  
+This preserves:
+
+- Structural clarity (one TEMPLATE, multiple participant views)
+- Contextual integrity (the STICKY documents what the template says)
+
+The prefix `AN_` (for “annotation”) distinguishes these subtypes as **secondary**, and signals that their data was derived from **side/marginal notes, comments or supplemental markings**, not from the main event.
+
 ### Substructures
 
 #### `ADDRESS_STRUCTURE` :=
@@ -488,6 +1644,85 @@ Duplicating information bloats files and introduces the potential for self-contr
 `ADR1`, `ADR2`, and `ADR3` should not be added to new files.
 :::
 
+#### `ADDRPLUS_STRUCTURE` :=
+
+An extended address structure containing all relevant information for modern contact records, including physical and digital addresses.  
+It is introduced to be able to describe addresses, especially on `TEMPLATE`'s, that are not addresses belonging to a person, but, for example, to the institution that issued the `TEMPLATE` itself.
+
+```gedstruct
+n ADDRPLUS <Text>                          {1:1}
+  +1 <<ADDRESS_STRUCTURE>>                 {0:1}
+  +1 PHON <Special>                        {0:M}  g7:PHON
+    +2 TITL <Text>                         {1:1}  g7:TITL
+  +1 EMAIL <Special>                       {0:M}  g7:EMAIL
+    +2 TITL <Text>                         {1:1}  g7:TITL
+  +1 FAX <Special>                         {0:M}  g7:FAX
+    +2 TITL <Text>                         {1:1}  g7:TITL
+  +1 WWW <Special>                         {0:M}  g7:WWW
+    +2 TITL <Text>                         {1:1}  g7:TITL
+  +1 AGNC <Text>                           {0:1}  g7:AGNC
+  +1 NOTE_STRUCTURE                        {0:M}  g8:NOTE
+  ```
+
+- The top-level `ADDRPLUS` payload provides a description of what the contact block represents — for example:  
+“Contact information of: Genetic Information Research Institute (GIRI)”.
+- `PHON`, `EMAIL`, `FAX`, and `WWW` follow GEDCOM 7 usage and formatting.
+- `TITL` provides a descriptive label for the contact item, such as a person, role, or institution name.
+- There needs to be at least 1 correct line of contact information present in this structure!
+
+:::example  
+Example: Contact information with titles per entry
+
+```gedcom
+1 ADDRPLUS Contact information of: Genetic Information Research Institute (GIRI)
+2 ADDR 2020 Alameda de las Pulgas
+3 CITY San Mateo
+3 STAE CA
+3 POST 94403
+3 CTRY USA
+2 PHON +1-650-212-2220
+3 TITL Main research line
+2 PHON +1-650-212-2221
+3 TITL Fax line for document intake
+2 EMAIL contact@girinst.org
+3 TITL General correspondence
+2 EMAIL submissions@girinst.org
+3 TITL Sequence data submission desk
+2 WWW https://www.girinst.org
+3 TITL Official research website
+2 AGNC GIRI – Public communications desk
+```
+:::
+
+#### `ARRAY_STRUCTURE` :=
+
+```gedstruct
+n ARRAY                                    {1:1}  g8:ARRAY
+  +1 CONT <ArrayValue>                     {1:M}  g8:type-Array2col
+```
+
+The `ARRAY_STRUCTURE` element is used to encode a structured sequence of related data points — typically pairs like marker and allele values for DNA — in a list format. 
+
+It is designed to support structured genetic data such as DNA segment or marker match tables in a way that is both human-readable and machine-parseable. 
+
+In GEDCOM 8, `ARRAY_STRUCTURE` uses the `TupleList` data type, where each entry is stored as a tuple on its own `CONT` line. It allows the data to be embedded directly in the record while retaining strict formatting requirements.
+
+> ⚠️ The first line with the tag `ARRAY` **may include a GEDCOM comment** to clarify the array content.  
+> However, **no inline comments are permitted inside `CONT` lines** — they must strictly conform to the `TupleList` format.
+
+:::example  
+```gedcom
+1 ARRAY                       /* Example of DNA test output in tuples */
+2 CONT (rs123456, A)
+2 CONT (rs234567, T)
+2 CONT (rs345678, G)
+2 CONT (rs456789, C)
+2 CONT (rs567890, T)
+2 CONT (rs987654, G)
+2 CONT (rs999020, T)
+```  
+:::
+
 
 #### `ASSOCIATION_STRUCTURE` :=
 
@@ -497,7 +1732,7 @@ n ASSO @<XREF:INDI>@                       {1:1}  g7:ASSO
   +1 ROLE <Enum>                           {1:1}  g7:ROLE
      +2 PHRASE <Text>                      {0:1}  g7:PHRASE
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 <<SOURCE_CITATION>>                   {1:M}
 ```
 
 An individual associated with the subject of the superstructure.
@@ -505,6 +1740,11 @@ The nature of the association is indicated in the `ROLE` substructure.
 
 A `voidPtr` and `PHRASE` can be used to describe associations to people not referenced by any `INDI` record.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- The `ASSOCIATION_STRUCTURE` is now no longer needed in GEDCOM 8. All associations are now represented by `ROLE`s in the `STICKY`'s  that belong to a `TEMPLATE`.
+
+
 :::example
 The following indicates that "Mr Stockdale" was the individual's teacher
 and that individual `@I2@` was the clergy officiating at their baptism.
@@ -522,6 +1762,140 @@ and that individual `@I2@` was the clergy officiating at their baptism.
 ```
 :::
 
+#### `CITA_STRUCTURE` :=
+
+```gedstruct
+n CITA                                     {1:1}  g8:CITA
+  +1 SOUR @<XREF:SOUR>@                    {1:1}  g7:SOUR
+  +1 PAGE <Text>                           {0:1}  g7:PAGE
+  +1 DATA                                  {0:1}  g7:SOUR-DATA
+    +2 <<DATE_VALUE>>                      {0:1}
+    +2 TEXT <Text>                         {0:M}  g7:TEXT
+      +3 MIME <MediaType>                  {0:1}  g7:MIME
+      +3 LANG <Language>                   {0:1}  g7:LANG
+  +1 AUTHOR <Text>                         {0:1}
+  +1 TITL <Text>                           {0:1}
+  +1 DATES                                 {0:1}
+    +2 CREATED <DateValue>                 {0:1}
+    +2 PUBLISHED <DateValue>               {0:1}
+    +2 ACCESSED <DateValue>                {0:1}
+    +2 RECORDED <DateValue>                {0:1}
+  +1 REPOSITORY <Text>                     {0:1}
+  +1 TEXTDISPLAY <Text>                    {0:1}
+  +1 TRANSCRIPT <Text>                     {0:1}
+  +1 FORMAT                                {0:1}
+    +2 TYPE <MediaType>                    {1:1}
+  +1 URL <Url>                             {0:1}
+  +1 LANGUAGE <Language>                   {0:1}
+  +1 RECORDID <Text>                       {0:1}
+  +1 VOLUME <Text>                         {0:1}
+  +1 CHAPTER <Text>                        {0:1}
+  +1 SUBCHAPTER <Text>                     {0:1}
+  +1 ITEMTYPE <Enum>                       {0:1}
+  +1 CONTAINER <Text>                      {0:1}
+  +1 SHORTTITLE <Text>                     {0:1}
+  +1 WWWLINK <Special>                     {0:M} g7:WWW
+    +2 VALUE <Url>                         {1:1}
+  +1 QUAY <Enum>                           {0:1}  g7:QUAY
+  +1 <<MULTIMEDIA_LINK>>                   {0:M}
+  +1 <<NOTE_STRUCTURE>>                    {0:M}
+```
+
+This structure is only used *inside* the `TEMPLATE` but is taken out for clarity.  
+It is a replacement for the `SOURCE_CITATION` and contains all tags that went in there, **except the tag `EVEN`** and its underlying tags.  
+As the information in that `EVEN` tag is taken over by the whole `TEMPLATE` itself.  
+
+> The definition and tags might change as the current **GEDCOM Source Citation Committee** is also working on changes for Citation Structures. **But until then, these are the proposed tags**.  
+
+This structure indicates that the pointed-to source record supports the claims made in the superstructure (`TEMPLATE`). Substructures provide additional information about how that source applies to the subject of the citation’s superstructure.  
+Every `CITA_STRUCTURE` **must point to a `SOURCE_RECORD`**. No `voidPtr` is allowed.
+
+Non-mentioned tags have the same meaning as in GEDCOM 7.  
+
+- `SOUR`, a pointer to the formal `@SOUR@` record containing general source metadata. Required. Same as `SOUR` in GEDCOM 7.
+  - Examples:
+  - if `SOUR` itself is a churchbook containing all Marriages over a certain period of time in a certain church in a certain place. In that case the `CITA` record points to and describes only 1 of the marriages as further described in this `TEMPLATE`.
+
+- `PAGE`, `g7:PAGE`, specific location in the source being cited (e.g., page number, folio, volume entry). Equivalent to `PAGES` in Zotero, and `RECORDDETAIL` in EE. `PAGE` can have comma-separated parts like:<br> `PAGE Film: 1234567, Frame: 344, Line: 28`<br>  (See with **Structure Types**)
+
+- `DATA`, a substructure holding extracted or quoted information from the cited source.  
+  This block reflects the *relevant portion* of the source record, often a snippet, sentence, or transcription tied to the citation.  
+  Mirrors `g7:SOUR-DATA`.  
+  Common in platforms that attach literal source content.  
+  Not to be confused with `TRANSCRIPT`, which is often a full verbatim copy.  
+
+  - `TEXT`, the actual content or snippet from the source being cited.  
+  May be a direct quote, a paraphrase, or other extracted content.  
+  Corresponds to `g7:TEXT`.  
+  Multiple `TEXT` lines may be used for multi-part or multi-language citations.  
+
+    - `MIME`, the `<MediaType>` of the specific `TEXT` content.  
+  Indicates the format of the quoted or extracted material, such as `text/plain`, `text/html`, or `application/pdf`.  
+  Corresponds to `g7:MIME`.  
+  Useful in distinguishing machine-readable data from narrative.  
+
+    - `LANG`, the language of the associated `TEXT` block.  
+  Uses standard language codes (e.g., `en`, `de`, `nl`).  
+  Corresponds to `g7:LANG`.  
+  Enables multi-language citations, each with proper attribution.  
+
+- `AUTHOR`, the creator of the content being cited — person, church, agency, or organization. Known as `CREATOR` in Zotero and CSL, and `AUTHOR` in EE/CMOS.
+
+- `TITL`, the full title of the work or document (e.g., book name, registry volume, article). Called `TITLE` in EE, Zotero, CSL, and GEDCOM.
+
+- `DATES`, container for date-related metadata about the source.
+
+  - `CREATED`, date the source was originally written or generated. Matches `DATE` in EE, `CREATION DATE` in citation managers.
+
+  - `PUBLISHED`, when the source was made public or officially distributed. Used by Zotero, CSL, EE.
+
+  - `ACCESSED`, when the researcher accessed or retrieved the source. Matches `ACCESSDATE` in Zotero and `ACCESSED` in CMOS.
+
+  - `RECORDED`, date the entry was logged into the source (e.g., baptism entered into a parish register). Not widely used outside GEDCOM contexts.
+
+- `REPOSITORY`, the archive, website, or institution holding the source. Matches `ARCHIVE` in Zotero, `REPO` in GEDCOM, and `REPOSITORY` in EE.
+
+- `TEXTDISPLAY`, a formatted citation string suitable for output, display, or printing. Equivalent to `CITATIONTEXT` in EE, and `VALUE` in GEDCOM-X citations.
+
+- `TRANSCRIPT`, exact 1:1 copy of the text as it appears in the source. Equivalent to `TEXT` in GEDCOM, `QUOTE` in Zotero, and `TRANSCRIPT` in Gramps.
+
+- `FORMAT`, container for media-type information about the cited source.
+
+  - `TYPE`, the file/media format (e.g., `text/plain`, `image/jpeg`). Equivalent to `FORM` in GEDCOM 7.
+
+- `URL`, the direct link to a web-hosted version of the source, if available. Equivalent to `URL` in GEDCOM-X and Zotero.
+
+- `LANGUAGE`, the language code of the source content (`en`, `nl`, `fr`, etc.). In Zotero this field is called `language` (lowercase).
+
+- `RECORDID`, an external or archival ID for the item, used by systems like FamilySearch, Ancestry, and in Family Historian exports.
+
+- `VOLUME`, the volume number or title within a multi-volume work or record group. Equivalent to `VOLUME` in Zotero and `RECORDDETAIL` in EE.
+
+- `CHAPTER`, a major subdivision within a source (e.g., book chapter, registry section). Not always used in citation managers, but valid structurally.
+
+- `SUBCHAPTER`, an optional subdivision within a `CHAPTER`. For deep-structured sources like law books, archives, or nested records.
+
+- `ITEMTYPE`, a controlled classification for the source (e.g., `Book`, `Letter`, `Church Register`). Matches `ITEMTYPE` in Zotero and `TYPE` in GEDCOM-X.
+
+- `CONTAINER`, the name of the larger holding work (e.g., journal title, series name). Equivalent to `PUBLICATIONTITLE` in Zotero, `CONTAINER-TITLE` in CSL.
+
+- `SHORTTITLE`, abbreviated title used internally or in compact lists. Matches `SHORTTITLE` in Zotero.
+
+- `WWWLINK`, a pointer to a specific web-hosted version or instance of the cited source.  
+  Used when the same source exists in multiple hosted locations (e.g., FamilySearch, Ancestry, Archive.org).  
+  Not the same as `URL`, which is a general field; `WWWLINK` allows for multiple variants.  
+  Each `WWWLINK` must contain a `VALUE` line holding a valid URL.  
+  - `VALUE`, the actual URL link to that external record.
+
+- `QUAY`, a quality estimate for the certainty and reliability of the cited source, from the perspective of the compiler.  
+  Inherited from GEDCOM 7 (p.83).  
+  Values range from 0 (unreliable) to 3 (highly reliable).  
+  This value does not reflect the credibility of the event itself, only the strength of the citation.  
+
+- `<<MULTIMEDIA_LINK>>`, pointer to scanned images or supporting documents. Same mechanism as GEDCOM 7.
+
+- `<<NOTE_STRUCTURE>>`, optional notes about this citation. For comments that don’t belong in structured fields.
+
 #### `CHANGE_DATE` :=
 
 ```gedstruct
@@ -580,9 +1954,12 @@ n RESN <List:Enum>                         {0:1}  g7:RESN
 n SDATE <DateValue>                        {0:1}  g7:SDATE
   +1 TIME <Time>                           {0:1}  g7:TIME
   +1 PHRASE <Text>                         {0:1}  g7:PHRASE
-n <<ASSOCIATION_STRUCTURE>>                {0:M}
 n <<NOTE_STRUCTURE>>                       {0:M}
-n <<SOURCE_CITATION>>                      {0:M}
+n QUAY <Enum>                              {0:1}  g7:QUAY
+n GEDC                                     {0:1}  g8:GEDC
+  +1 VERS <Special>                        {1:1}  g8:GEDC-VERS
+    +2 <<SOURCE_CITATION>>                 {1:M}
+    +2 <<ASSOCIATION_STRUCTURE>>           {0:M}
 n <<MULTIMEDIA_LINK>>                      {0:M}
 n UID <Special>                            {0:M}  g7:UID
 ```
@@ -592,6 +1969,16 @@ Substructures that may be shared by most individual and family events and attrib
 Note that many of these substructures are limited to 1 per event.
 Conflicting event information should be represented by placing them in separate event structures (with appropriate source citations) rather than by placing them under the same enclosing event.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` and the `ASSOCIATION_STRUCTURE` are now *behind* the same GEDCOM version tag as in the Header.  
+>Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` or the `ASSOCIATION_STRUCTURE` are allowed at this place.   
+>    - This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and all `ROLE`s and everything that belongs to it. (inside the `STICKY`s)  
+>    - Because of that **it is no longer allowed** for any of these 4 structures to point to a `SOURCE_CITATION` **from enywhere** inside the structure itself!
+>- `QUAY` is added to have a possibility to define the credibility of each event.  
+>- ✨ When this PR will be implemented, **it is possible another method will be chosen** to make sure `SOURCE_CITATION`  and `ASSOCIATION_STRUCTURE` can no longer be used as they were in GEDCOM 7 !
+
+
 #### `FAMILY_ATTRIBUTE_STRUCTURE` :=
 
 ```gedstruct
@@ -634,6 +2021,12 @@ n <<EVENT_DETAIL>>                         {0:1}
 
 Substructures shared by most family events and attributes.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+> **Important**
+>- In GEDCOM 8 the `FAMILY_EVENT_DETAIL` is no longer allowed to have the `HUSB` and/or `WIFE` tags, just the `<<EVENT_DETAIL>>`.  
+
+
 #### `FAMILY_EVENT_STRUCTURE` :=
 
 ```` {.gedstruct .long}
@@ -697,6 +2090,87 @@ Family event structures vary as follows:
 - `FAM`.`EVEN` requires `TYPE`; it's optional for others
 :::
 
+#### `FLEX_STRUCTURE` :=
+
+```gedstruct
+n FLEX <Text>                         {1:1}  g8:FLEX
+  +1 TYPE <Text>                      {1:M}  g8:FLEX-TYPE
+  +1 PHRASE <Text>                  {1:1}  g8:PHRASE
+    +2 LANG <Language>              {0:1}  g7:LANG
+  +1 CONTENTS <Text>                  {1:1}  g8:CONTENTS
+  +1 RESN <List:Enum>                 {0:1}  g8:RESN
+  +1 <<NOTE_STRUCTURE>>               {0:1}
+```
+
+A `FLEX` structure allows flexible encoding of additional typed values within records, that are specific to a document, template, or local practice. It supports structured value recording even when the type is not part of standard GEDCOM fields.
+
+- `FLEX` can only be used inside `TEMPLATE`, `STICKY`, `ASSET`, `PROOF` or `GROUP`. 
+
+It consists of a `FLEX` tag followed by one or more subordinate lines that define its meaning.
+
+By using `FLEX`, a lot of the maybe dozens and more widespread `_SILLYTAG`'s, can be changed into user readable information, while the software processing it, can deal with it, without having to know the real meaning, or its definition or otherwise. If a `FLEX` later will have to be replaced by an offcial GEDCOM tag, because that `FLEX` is so widespread and often used, it deserves its own tag, its likely that software can do that, without much user assistance. (By comparing the `PHRASE` of the FLEX, with the `_SILLYTAG`'s tagname.)
+
+- The `TYPE` line declares one or more types describing the structure of the `CONTENTS`. If multiple types are given, they must be separated by a comma and a space. The `TYPE`'s appear on the same line as `FLEX`, separated from `FLEX` by 1 space.
+- The `CONTENTS` line contains the value, matching the declared `TYPE`. In certain case this line can be followed by `2 CONT some text`, in case the `FLEX` type is a `NOTE`-type enum.
+- The `PHRASE` line must be present and must **exactly match** the label of the field on the original document or template. This ensures that software can display or print human-readable information even if it does not interpret the `TYPE` or `CONTENTS`. The `PHRASE` line appears directly after the `CONTENTS`line.
+
+ - `LANG`, defines the language of the `PHRASE`.
+- `NOTE` can be used for special remarks about this specific `FLEX`.
+- `RESN`, with this the user can decide if the information of this `FLEX` should be presented in the outputs.
+
+##### Rules:
+
+- `TYPE` values must be valid entries from the `FLEX-TYPE` enumeration. For readability they must be put directly behind the `FLEX`tag, separated from it by 1 space, like this: `FLEX DECIMAL, CURR, USD`. So the `TYPE`tag itself does not show. And, for instance with `CURR`, the chosen currency value itself, also goes on that same line. Same for `UNIT`.
+- The only allowed combination of `TYPE`s as for now is with `CURR` or `UNIT` behind `AMOUNT`, `DECIMAL`, or `INTEGER`.
+- Parsers must treat the contents as an ordered list.
+- Use of `TEXT` as a `TYPE` is allowed only if no more precise type is applicable. For instance, do **not** use `TEXT` to represent `"1944-06-06"` or `"12500.00"`; use `DATE` and `DECIMAL`, respectively.
+- The `PHRASE` must reflect the **exact label used on the source document** to help users recognize the field's meaning.
+  - **This allows software to:**
+    - display fields using user-recognizable labels,
+    - disambiguate similar fields (e.g., two different monetary amounts),
+    - and support output of human-readable versions even without interpreting the underlying `TYPE`/`CONTENTS`.
+
+$\color{Coral}\large{\textbf{Important! GEDCOM 8 changes:}}$
+
+
+>**In this PR `FLEX` has been given a restriction:**
+>- It can only be used inside `TEMPLATE`, `STICKY`, `ASSET`, or `GROUP`.  
+>This way it does not interfere with current GEDCOM7.  
+
+>**If this PR would be accepted, it is always possible to extend the use of `FLEX` to other places in GEDCOM.**
+
+
+##### Example 1: Single typed value
+
+```gedstruct
+1 FLEX DATE
+2 PHRASE "Date of Transfer"
+2 CONTENTS 1944-06-06
+```
+In this case "Date of Transfer" does NOT have its own GEDCOM tag, so a `FLEX` is used instead.
+
+##### Example 2: Combined typed value (decimal amount with currency)
+
+```gedstruct
+1 FLEX DECIMAL, CURR, USD
+2 PHRASE "Property Value."
+2 CONTENTS 12500.00
+2 NOTE "Transferred to widow"
+```
+Value of the property on a will.
+
+##### Example 3: Typed field in a STICKY from an inheritance template
+
+```gedstruct
+0 @ST0043@ STICKY
+1 TYPE FINANCE, ACCOUNTS "Inheritance Share: Savings Account at Miami Credit Union"
+2 PHRASE "Savings Account at Miami Credit Union"
+1 ROLE ASSET
+1 FLEX DECIMAL, CURR, USD
+2 PHRASE "Savings"            /* Text as on the original certificat */
+2 CONTENTS 12500.00
+1 NOTE "Savings inherited by Anna Harrison from George Harrison."
+```
 
 #### `IDENTIFIER_STRUCTURE` :=
 
@@ -918,6 +2392,13 @@ An event structure may be used to discuss an event even if the event is not know
 See [Events] for a discussion of how `DATE`, `PLAC`, and the optional `Y` payload indicate whether the structure is asserting the event occurred.
 See the `NON_EVENT_STRUCTURE` for how to state an event did not occur.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>**Important**
+>- `CHRC`, `BIRT` and `ADOP` in GEDCOM 8, are no longer allowed to have a `FAMC` link.
+
+
+
 :::note
 Individual event structures vary as follows:
 
@@ -952,6 +2433,12 @@ n SLGC                                     {1:1}  g7:SLGC
 
 Ordinances performed by members of The Church of Jesus Christ of Latter-day Saints; see [Latter-day Saint Ordinances] for descriptions of each ordinance type.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>**Important**
+> - In GEDCOM 8 `SLGC` no longer has a `FAMC` link.
+
+
 #### `LDS_ORDINANCE_DETAIL` :=
 
 ```gedstruct
@@ -962,12 +2449,21 @@ n STAT <Enum>                            {0:1}  g7:ord-STAT
   +1 DATE <DateExact>                    {1:1}  g7:DATE-exact
      +2 TIME <Time>                      {0:1}  g7:TIME
 n <<NOTE_STRUCTURE>>                     {0:M}
-n <<SOURCE_CITATION>>                    {0:M}
+  +1 GEDC                                {0:1}  g8:GEDC
+    +2 VERS <Special>                    {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>             {1:M}
 ```
 
 Dates for these ordinances should be in the default (`GREGORIAN`) calendar and be 1830 or later.
 These ordinances can be performed posthumously by proxy, and the date may reflect that posthumous date.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` is now *behind* the same GEDCOM version tag as in the Header.  
+Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` is allowed at this place.   
+This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and everything that belongs to it. (inside the `STICKY`s)  
+
+
 #### `LDS_SPOUSE_SEALING` :=
 
 ```gedstruct
@@ -1001,12 +2497,21 @@ n NO <Enum>                                {1:1}  g7:NO
   +1 DATE <DatePeriod>                     {0:1}  g7:NO-DATE
      +2 PHRASE <Text>                      {0:1}  g7:PHRASE
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 GEDC                                  {0:1}  g8:GEDC
+    +2 VERS <Special>                      {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>               {1:M}
 ```
 
 Indicates that a specific type of event, given in the payload, did not happen within a given date period
 (or never happened if there is no `DATE` substructure).
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` is now *behind* the same GEDCOM version tag as in the Header.  
+Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` is allowed at this place.   
+This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and everything that belongs to it. (inside the `STICKY`s)  
+
+
 Substructures may provide discussion about the non-occurrence of the event
 but must not limit the meaning of what did not occur.
 No substructure other than `DATE` may restrict the breadth of that negative assertion.
@@ -1033,7 +2538,9 @@ n NOTE <Text>                              {1:1}  g7:NOTE
   +1 TRAN <Text>                           {0:M}  g7:NOTE-TRAN
      +2 MIME <MediaType>                   {0:1}  g7:MIME
      +2 LANG <Language>                    {0:1}  g7:LANG
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 GEDC                                  {0:1}  g8:GEDC
+    +2 VERS <Special>                      {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>               {1:M}
 |
 n SNOTE @<XREF:SNOTE>@                     {1:1}  g7:SNOTE
 ]
@@ -1048,6 +2555,12 @@ See `SHARED_NOTE_RECORD` for advice on choosing between `NOTE` and `SNOTE`.
 
 A `NOTE_STRUCTURE` can contain a `SOURCE_CITATION`, which in turn can contain a `NOTE_STRUCTURE`, allowing potentially unbounded nesting of structures. Because each dataset is finite, this nesting is also guaranteed to be finite.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` is now *behind* the same GEDCOM version tag as in the Header.  
+Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` is allowed at this place.   
+This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and everything that belongs to it. (inside the `STICKY`s)  
+
 
 
 #### `PERSONAL_NAME_PIECES` :=
@@ -1090,12 +2603,21 @@ n NAME <PersonalName>                      {1:1}  g7:INDI-NAME
      +2 LANG <Language>                    {1:1}  g7:LANG
      +2 <<PERSONAL_NAME_PIECES>>           {0:1}
   +1 <<NOTE_STRUCTURE>>                    {0:M}
-  +1 <<SOURCE_CITATION>>                   {0:M}
+  +1 GEDC                                  {0:1}  g8:GEDC
+    +2 VERS <Special>                      {1:1}  g8:GEDC-VERS
+      +3 <<SOURCE_CITATION>>               {1:M}
 ```
 
 Names of individuals are represented in the manner the name is normally spoken, with the family name, surname, or nearest cultural parallel thereunto separated by slashes (U+002F `/`). Based on the dynamic nature or unknown compositions of naming conventions, it is difficult to provide a more detailed name piece structure to handle every case. The `PERSONAL_NAME_PIECES` are provided optionally for systems that cannot operate effectively with less structured information. The Personal Name payload shall be seen as the primary name representation, with name pieces as optional auxiliary information; in particular it is recommended that all name parts in `PERSONAL_NAME_PIECES` appear within the `PersonalName` payload in some form, possibly adjusted for gender-specific suffixes or the like.
 It is permitted for the payload to contain information not present in any name piece substructure.
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>- `SOURCE_CITATION` is now *behind* the same GEDCOM version tag as in the Header.  
+Only when the GEDCOM version of the file is a lower version than GEDCOM 8, a `SOURCE_CITATION` is allowed at this place.   
+This is done because GEDCOM 8 uses a `TEMPLATE` to fully describe the `SOURCE_CITATION` and everything that belongs to it. (inside the `STICKY`s)  
+
+
 The name may be translated or transliterated into different languages or scripts using the `TRAN` substructure.
 It is recommended, but not required, that if the name pieces are used, the same pieces are used in each translation and transliteration.
 
@@ -1182,6 +2704,13 @@ n SOUR @<XREF:SOUR>@                       {1:1}  g7:SOUR
   +1 <<NOTE_STRUCTURE>>                    {0:M}
 ```
 
+$\color{Coral}\large{\textbf{GEDCOM 8 changes:}}$
+
+>**IMPORTANT**
+>  
+> The `SOURCE_CITATION` in GEDCOM 8 is now "replaced" by the `CITA_STRUCTURE`, as in GEDCOM 8 everything from a document is now described in a `TEMPLATE`, of which the `CITA_STRUCTURE` is a part. So the important parts of the original `SOURCE_CITATION` are now in the `CITA_STRUCTURE`, and other parts, like the event, are now described in the `TEMPLATE` itself.  
+> More information can be found with the `CITA_STRUCTURE` and the `TEMPLATE`.
+
 A citation indicating that the pointed-to source record supports the claims made in the superstructure.
 Substructures provide additional information about how that source applies to the subject of the citation's superstructure:
 
@@ -1215,3 +2744,25 @@ Formal and informal repository name and addresses are stored in the
 More formal repositories, such as the Family History Library, should show a call number of the source at that repository.
 The call number of that source should be recorded using a `CALN` substructure.
 
+#### `TRANSFER_STRUCTURE` :=
+
+A `TRANSFER_STRUCTURE` describes the transfer of a `STICKY`-record from an origin to a destination.
+- The entity is pointing to an `ASSET STICKY` that "moves" from an original owner to a new owner, hence on a will, selling contract or otherwise. Example: a house that is given to an heir on a will, or a horse that is sold to a new owner via a purchase contract.
+- a `TRANSFER` structure can only be used inside a `TEMPLATE` record.
+
+```gedstruct
+n TRANSFER @<XREF:STICKY>@                 {1:1}
+  +1 GRANTOR @<XREF:STICKY>@               {1:1}  g8:STICKY
+  +1 GRANTEE @<XREF:STICKY>@               {1:M}  g8:STICKY
+    +2 SHARE <PercentLiteral>              {0:1}
+  +1 <<NOTE_STRUCTURE>>                    {0:1}
+```
+
+- `TRANSFER`: the referenced `STICKY` is the `ASSET` that "moves" from 1 owner to another owner.
+  - `GRANTOR`, must be a valid `pointer` to a person `STICKY`, who is the original owner of the asset in this `TRANSFER`. Grantor can be the deceased in a will, but also the seller or giver of something.
+  - `GRANTEE` describes 1 or more person `STICKY`'s representing those who recieved (a share of) the `ASSET`.
+  - all `pointers` in this `TRANSFER` structure must point to `STICKY`'s in the same `TEMPLATE` as the `TRANSFER` structure itself.
+  - `SHARE`, the part of the `ASSET` as a percent value, that this `GRANTEE` recieves.
+
+
+
diff --git a/specification/gedcom-3-structures-3-meaning.md b/specification/gedcom-3-structures-3-meaning.md
index 039bbb6c..9b3bf496 100644
--- a/specification/gedcom-3-structures-3-meaning.md
+++ b/specification/gedcom-3-structures-3-meaning.md
@@ -1366,6 +1366,79 @@ A family name passed on or used by members of a family.
 Information relating to a single extension tag as used in this document.
 See [Extensions](#extensions) for more details.
 
+#### `TDABOVI` (d'Aboville Number) `g8:TDABOVI`
+
+Provides a tree position number for each individual in a genealogical tree, using a modified d’Aboville system.  
+Used in combination with a `TDECUJUS`. 
+[`TDECUJUS`](#tdecujus-de-cujus-g8tdecujus)
+
+**Important:**
+
+- This structure allows temporary hierarchical numbering within one `TEMPLATE` to reflect family lineage relationships when multiple individuals appear, as annotated events, **in a complex family-centered** `TEMPLATE`-record — such as a family Bible, genealogical narrative, a Census or commemorative scroll.  
+- It is only allowed when that `TEMPLATE` contains these annotated events.
+- It is only valid also, when this `TEMPLATE` has 1 `TDECUJUS` defined.
+
+In all other `TEMPLATE`'s, `ROLE`'s show the family relations, and in those `TEMPLATE`s this numbering is not necessary.
+
+`TDABOVI` **Special Format:**  
+
+The d’Aboville-like numbering system expresses position using dot-separated integers.  
+- Each person’s number reflects their birth order among siblings.
+- Example values: 1, 1.2, 1.2.3, 2.1.2, etc.
+- The s suffix (e.g., 1s, 1.2s) may be added to indicate a spouse of the person bearing the primary number.
+- The system is **local to the `TEMPLATE`** only; numbers are not reused outside. (Thats why its called `TDABOVI` and not `DABOVI`)
+
+**Official Format Rules:**
+- **Pattern:** must match regex `^(\d+(\.\d+)*)(s?)$`
+- **Type:** Treated as `Text`, but format is controlled
+- **No leading zeros** in any segment
+- **Spouses** always marked with **`s`** directly after the person number (e.g., 1.1s)
+- **No duplicate TREEABOVI within same `TEMPLATE`**
+- **Ordering:** not required, but recommended for clarity
+
+**Examples of valid values:**  
+| Value | Meaning | Example |
+|-------|---------|---|
+| 1	     | Root person also De Cujus. | John, he is the head of this family, de "De Cujus". |
+| 1.1	   | First child | Andrew, son of John, and first child. |
+| 1.2s	 | Spouse of second child | Mary, wife of Peter (1.2), who is son and second child of John |
+| 1.2.1	 | First grandchild from second child | Helen, daughter of Peter (1.2) and Mary |
+| 1.3	   | Third child | Clara, daughter of John (1), and his third child. |
+| 1.2.2s | Spouse of second grandchild from second child | Anny, wife of William (1.2.2), son of Peter (1.2) and Mary |
+
+#### `TDECUJUS` (De Cujus) `g8:TDECUJUS`
+
+Identifies the root individual (starting point) of the d'Aboville numbering — typically the earliest ancestor recorded in the `TEMPLATE`.  
+It is used in combination with a `TDABOVI`. 
+[`TDABOVI`](#tdabovi-daboville-number-g8tdabovi)
+
+For the `TDECUJUS` the following applies:
+- It points to the `STICKY` of the root ancestor in the family unit described in 1 `TEMPLATE`.
+- Must appear only once if `TDABOVI` is used at all.
+- A `TEMPLATE` can not have multiple `TDECUJUS` values.
+
+:::example   
+```gedcom
+0 @ST0101@ STICKY
+1 TYPE PERSON, AN_BIRTH
+1 ROLE CHILD
+1 ENTRYTYPE MANUAL
+1 TDABOVI 1
+1 TEMPLATE @T0043@
+1 NAME
+2 FORM John Eldridge
+1 TDABOVI 1
+
+0 @T0043@ TEMPLATE
+1 TYPE SECONDARY, FAMILYBIBLE
+1 TITLE Eldridge Family Births, Deaths, and Notes
+1 NAME Eldridge Family Bible
+1 DATE 1870–1936
+1 PLAC Crystal Lake, Illinois
+1 TDECUJUS @ST0101@           /* John Eldridge is the De Cujus */
+```
+:::
+
 #### `TEMP` (Temple) `g7:TEMP`
 
 The name of a temple of The Church of Jesus Christ of Latter-day Saints.
diff --git a/specification/gedcom-3-structures-4-enumerations-entity.md b/specification/gedcom-3-structures-4-enumerations-entity.md
new file mode 100644
index 00000000..b86a0284
--- /dev/null
+++ b/specification/gedcom-3-structures-4-enumerations-entity.md
@@ -0,0 +1,336 @@
+
+### `g8:enumset-ENTITY-TYPE`
+
+Describes the kind of entity referred to by a `STICKY` or `ASSET` record.
+- `PERSON` is a special case usable only in `STICKY`s that describe people. All others describe entities.
+- This enumset is used in both `STICKY.TYPE` and `ASSET.TYPE`.  
+
+| ICO | TYPE           | Description |
+|-----|----------------|-------------|
+| 🖼️ | `ARTWORK`      | Works of art including paintings, sculptures, performances, and other creative items. Use PHRASE for detail: [painting, sculpture, drawing, embroidery]. |
+| 🏅 | `AWARD`        | Awards or recognitions, including military, civic, or honorary distinctions. Use PHRASE for detail: [medal, honor, prize]. |
+| ☂️ | `BELONGINGS`   | Household items, clothing, furniture, musical instruments, or everyday personal objects. Only those that do NOT fit into one of the other main categories! Use PHRASE for detail: [clothing, furniture, instrument]. |
+| 📖 | `BOOK`         | Manuscripts, scrolls, ledgers, or published books. Use PHRASE for detail: [Bible, ledger, diary, manuscript]. |
+| 🐎 | `CREATURES`    | Animals kept for use or pleasure, including livestock, dogs, horses, etc. Use PHRASE for detail: [horse, cattle, sheep, dog]. |
+| 🧬 | `DNA`          | Registered genetic profiles, test results, or kit IDs. Often linked to ancestry services, forensic reports, or medical archives. Use PHRASE for detail: [DNA kit, Y-DNA, mtDNA]. |
+| 📜 | `DOCUMENT`     | Official papers, certificates, letters, contracts, legal documents, or records. Use PHRASE for detail: [certificate, contract, letter, passport]. |
+| 🏡 | `ESTATE`       | A legally recognized unit combining land and its associated rights, which may include forests, islands, or agricultural areas such as farms or orchards. Use when emphasizing *ownership*, *inheritance*, or *named tracts*. Use PHRASE for detail: [farm, manor, island, vineyard]. |
+| 💰 | `FINANCE`      | Financial instruments and institutional holdings not held as physical cash. Includes accounts, insurance, bonds, investments, tax records, and debt instruments. Use PHRASE for detail: [account, bond, investment, insurance]. |
+| 💎 | `JEWELRY`      | Rings, crowns, brooches, necklaces, earrings, and other personal adornments. Refers to **worn or wearable items**. Does **not** include loose diamonds, gemstones, or precious metals held purely as financial assets — those belong in `MONEY`. Use PHRASE for detail: [ring, necklace, brooch, crown]. |
+| 🧠 | `INTANGIBLE`   | Non-physical property or rights that can be owned, transferred, or inherited. Includes intellectual property, shares, easements, and other valuable rights. Use PHRASE for detail: [copyright, patent, trademark, shareholding, franchise, easement, digital asset]. |
+| 🌿 | `LAND`         | Natural or cultivated areas not primarily defined by buildings or ownership, such as fields, forests, orchards, gardens, islands, cemeteries, or wilderness zones. Use when emphasizing *terrain, use*, or *natural classification*. Use PHRASE for detail: [field, orchard, forest, garden]. |
+| 🎞️ | `MEDIA`        | Any type of media: photos, recordings, videos, or publications. Use PHRASE for detail: [photograph, film, audio, postcard]. |
+| 🕊️ | `MEMORIAL`     | Physical or symbolic items created to honor or remember a deceased individual. Includes graves, urns, memorial trees, cards, inscriptions, and culturally-specific commemorative objects. These may record names, dates, relationships, or rituals, and can serve as primary or secondary genealogical evidence.<br>⚠️ MEMORIAL entity types are intended for commemorative, symbolic, or ceremonial objects.<br>Legal or administrative records related to death events should instead be categorized under DOCUMENT. Use PHRASE for detail: [grave, urn, plaque, monument]. |
+| 🪖 | `MILITARY`     | Items related to military service, such as uniforms, medals, etc. Use PHRASE for detail: [uniform, medal, sword, insignia]. |
+| 💶 | `MONEY`        | Coins, banknotes, and physical forms of value such as bullion, gems, or other portable wealth. Includes **loose diamonds**, **precious metals**, **rare coins**, and **treasured valuables** stored or traded for their financial worth. Excludes **worn jewelry** like rings or necklaces — those belong in `JEWELRY`. Use PHRASE for detail: [coin, gold, silver, diamond]. |
+| 🏢 | `ORGANIZATION` | Named institutions that issue, regulate, record, or otherwise appear as active agents in genealogical records. Examples: adoption agencies, schools, parishes, registries, consulates, courts, trade unions, and historical archives. Use PHRASE for detail: [school, court, parish, guild, archive]. |
+| 👤 | `PERSON`       | ⚠️ Only valid in STICKYs that refer to a person. Not valid in ASSETs‼️. Use PHRASE for detail: [individual name, title, alias]. |
+| 🏘️ | `PROPERTY`     | Man-made structures or built real estate, including homes, castles, stables, churches, and infrastructure. Use when emphasizing *buildings* or *constructs*. Does *not* include terrain or personal objects. Use PHRASE for detail: [house, church, castle, stable]. |
+| ✝️ | `RELIGIOUS`    | Religious items or assets, e.g., holy books, artifacts, relics. Use PHRASE for detail: [cross, chalice, icon, scripture]. |
+| 🛠️ | `TOOLS`        | Instruments, weapons, farming tools, or other useful objects. Use PHRASE for detail: [hammer, plough, sword, anvil]. |
+| 🚗 | `TRANSPORT`    | Cars, boats, carts, carriages, sleds, bikes, planes, trains, ferries, and any other transport vehicles. Use PHRASE for detail: [boat, carriage, bicycle, cart]. |
+| ❓ | `OTHER`        | Anything that does not fit in another category; must include a `PHRASE`. Use PHRASE for detail: [custom object, unique asset]. |
+
+#### 💡 Usage Notes
+
+- This enumset is used in both `STICKY.TYPE` and `ASSET.TYPE`.
+- In `STICKY` records, all types are valid — including `PERSON`, which is used when the `STICKY` points to a human individual.
+- In `ASSET` records, **all types are valid _except_ `PERSON`**. People are represented with `@INDI@` records instead.
+- The `OTHER` type can be used when none of the defined types fit. It **must always** be accompanied by a `PHRASE` that clarifies the nature of the object.
+- The `AN_OTHER` can be used for `PERSON` `STICKY`'s, in case of **secondary** events in a `TEMPLATE`. `AN_OTHER` is used in the same way as `OTHER`, and it also must have a `PHRASE`.
+
+### `g8:enumset-ENTITY-SUBTYPE`
+
+These values define the allowed `SUBTYPE` values for the `STICKY` and`ASSET` record.
+Each entity must declare exactly one `TYPE`, and refine it using one `SUBTYPE` value.  
+
+It is used as:  
+`TYPE ARTWORK, PAINTING`  
+So not just the `SUBTYPE`, but also the `TYPE` itself must be mentioned.  
+
+
+| ICO | TYPE | SUBTYPE | Description |
+|-----|------|---------|-------------|
+| 🖼️ | `ARTWORK` | `CALLIGRAPHY` | Decorative or meaningful handwriting and script: illuminated verses, framed (hand)writing, stylized characters |
+| 🖼️ | `ARTWORK` | `DECORATIVE` | Artistically crafted household items such as carved utensils, embellished vessels, or ornamental fixtures, embroidery, or artistic household items |
+| 🖼️ | `ARTWORK` | `DRAWING` | Graphite, ink, or chalk illustrations; includes sketches, drafts, design plans,  illustrations and artistic diagrams. |
+| 🖼️ | `ARTWORK` | `MINIATURE` | Small-scale paintings, sculptures, or models intended for detail and fine craftsmanship. Often portraiture or architectural. |
+| 🖼️ | `ARTWORK` | `MIXED` | Artworks combining multiple media (e.g., textile with wood, painting with carving, or metal with stone). |
+| 🖼️ | `ARTWORK` | `OTHER` | Any non-listed ARTWORK form; must include PHRASE to clarify |
+| 🖼️ | `ARTWORK` | `PAINTING` | Painted surfaces on canvas, wood, plaster, or parchment. Includes oil paintings, framed portraits, and wall art. |
+| 🖼️ | `ARTWORK` | `PERFORMANCE` | Ephemeral or live artistic acts such as dance, theater, or musical presentations. |
+| 🖼️ | `ARTWORK` | `SCULPTURE` | Carved, molded, or assembled three-dimensional forms, or statues. Including free-standing works and reliefs. |
+| 🖼️ | `ARTWORK` | `TEXTILE` | Embroidered or woven designs made to be admired or symbolic / Embroidered, woven, or stitched designs made primarily for aesthetic, symbolic, or ceremonial purposes. |
+| 🏅 | `AWARD` | `CIVILIAN` | Non-military honors granted for civil service, artistic, humanitarian, or academic achievement; may include certificates, framed documents, or symbolic objects. |
+| 🏅 | `AWARD` | `HONORARY` | Ceremonial or symbolic titles, often not involving a physical object; includes honorary degrees, symbolic memberships, or posthumous recognitions. |
+| 🏅 | `AWARD` | `INSTITUTIONAL` | Awards given by schools, universities, or professional organizations, such as diplomas, badges, or graduation medals. |
+| 🏅 | `AWARD` | `MILITARY` | Decorations or medals awarded for military service, bravery, rank, or campaigns; includes orders like "the Militaire Willems-Orde". |
+| 🏅 | `AWARD` | `ORDER` | Formal ranks of merit or chivalric orders, often linked to monarchy or state recognition; may be accompanied by insignia, titles, or ceremonial garments. |
+| 🏅 | `AWARD` | `OTHER` | Any award not covered by other categories; must include PHRASE to describe nature, issuer, or context of the honor. |
+| ☂️ | `BELONGINGS` | `BEDDING` | Mattresses, quilts, blankets, furniture or other items associated with sleeping comfort. |
+| ☂️ | `BELONGINGS` | `CLOTHING` | Garments, outerwear, undergarments, footwear, or accessories worn on the body. |
+| ☂️ | `BELONGINGS` | `DECOR` | Decorative but not artistic household objects: vases, figurines, wall hangings |
+| ☂️ | `BELONGINGS` | `FURNITURE` |  Larger household objects such as chairs, tables, mirrors and dressers. Includes carved or built furniture unless clearly ARTWORK. |
+| ☂️ | `BELONGINGS` | `HYGIENE` | Personal grooming or cleaning objects including mirrors, combs, basins, and toiletries. |
+| ☂️ | `BELONGINGS` | `KEEPSAKE` | Sentimental or inherited personal items |
+| ☂️ | `BELONGINGS` | `MUSICAL` | Musical instrument, use `PHRASE` to specify. |
+| ☂️ | `BELONGINGS` | `OTHER` | Any non-listed BELONGINGS item; must include PHRASE to clarify. |
+| ☂️ | `BELONGINGS` | `TEXTILE` | Everyday-use cloth or fabric items like towels, curtains, tablecloths, or cushions. Not primarily decorative or symbolic. |
+| ☂️ | `BELONGINGS` | `TOY` | Objects designed for play or amusement, such as dolls, figurines, or mechanical toys. May include both handmade and manufactured items. |
+| 📖 | `BOOK` | `ACCOUNT` | Ledgers, bookkeeping logs, financial records, or legal/inventory ledgers / Ledgers, bookkeeping logs, or financial records |
+| 📖 | `BOOK` | `DIARY` | Personal journals or memoirs |
+| 📖 | `BOOK` | `GENEALOGY` | Family trees, pedigree charts, or ancestor books |
+| 📖 | `BOOK` | `LEDGER` | Financial, legal, or inventory ledgers |
+| 📖 | `BOOK` | `LEGAL` | Statute books, law manuals, or legal codes |
+| 📖 | `BOOK` | `LITERATURE` | Poems, plays, novels, or literary works |
+| 📖 | `BOOK` | `MANUSCRIPT` | Handwritten books or scrolls |
+| 📖 | `BOOK` | `OTHER` | Any other type of book; must include PHRASE to clarify |
+| 📖 | `BOOK` | `PRINTED` | Published books, newspapers, or pamphlets |
+| 📖 | `BOOK` | `RELIGIOUS` | Scriptures, hymnals, or sacred texts |
+| 📖 | `BOOK` | `SCHOLARLY` | Academic texts, treatises, or scientific manuscripts |
+| 🐎 | `CREATURES` | `CATTLE` | Cows, oxen, or other bovines kept for meat, milk, or labor (livestock) |
+| 🐎 | `CREATURES` | `DOG` | Working or companion dogs |
+| 🐎 | `CREATURES` | `DOMESTIC` | Companion animals like dogs, cats, parrots, or rabbits |
+| 🐎 | `CREATURES` | `FEATHERED` | Poultry, game birds, or show birds (chickens, ducks, geese) |
+| 🐎 | `CREATURES` | `FLOCK` | Sheep, goats, or other small livestock herded for resources |
+| 🐎 | `CREATURES` | `HORSE` | Horses, donkeys, mules, ponies, or riding animals used for transport or labor |
+| 🐎 | `CREATURES` | `OTHER` | Any other creature; must include PHRASE to clarify |
+| 🐎 | `CREATURES` | `SYMBOLIC` | Mythical, ceremonial, or named animals with symbolic value |
+| 🐎 | `CREATURES` | `WILD` | Non-domesticated animals in captivity or known individual animals |
+| 📜  | `DOCUMENT` | `CERTIFICATE`  | Legal/verifiable document: birth, death, **burial**, **cremation**, **coroner’s** certificates; baptism or marriage records. Naturalization certificate|
+| 📜 | `DOCUMENT` | `CONTRACT` | Agreements: sales, employment, military service, indenture, etc. Wills, deeds, legal or business agreements |
+| 📜 | `DOCUMENT` | `CORRESPONDENCE` | Official correspondence, NO personal records |
+| 📜 | `DOCUMENT` | `DECREE` | Orders issued by a legal, military, or religious authority |
+| 📜 | `DOCUMENT` | `ID` | Identification: passports, licenses, permits, etc. |
+| 📜 | `DOCUMENT` | `INTELLECTUAL` | Patents, trademarks, copyrights, or other legally registered intellectual properties and creative rights. |
+| 📜 | `DOCUMENT` | `LIST` | Inventories, rosters, censuses, tax rolls |
+| 📜 | `DOCUMENT` | `OTHER` | Must include a PHRASE to clarify subtype not listed above |
+| 📜 | `DOCUMENT` | `PERSONAL` | Letters, diaries, or personal records |
+| 📜  | `DOCUMENT` | `RECORD`  | Entries in logs, court books, **inquest reports**, **death or burial registrations**, church registers, or compiled official documents. (official or legal records) |
+| 📜  | `DOCUMENT` | `TESTAMENT` | Wills, deeds, contracts, codicils, notarized records or related testamentary instructions. May include related **court files**. |
+| 📜 | `DOCUMENT` | `WRITTEN` | Formal written orders (summonses, mandates, authorizations). Includes **burial permits**, **interment or disinterment orders**, and official **municipal burial approvals**. |
+| 🧬 | `DNA`    | `TESTKIT`   | Identifiable genetic kit used in analysis (e.g., 23andMe barcode). |
+| 🧬 | `DNA`    | `PROFILE`   | Final interpreted profile (e.g., mtDNA, Y-DNA haplogroup). |
+| 🧬 | `DNA`    | `RESULT`    | Summary finding or match (e.g., paternity result, region). |
+| 🧬 | `DNA`    | `OTHER`     | Any other DNA-related record; must use PHRASE to clarify. |
+| 🏡 | `ESTATE` | `COMPOUND` | Legally defined residential or mixed-use parcel with multiple buildings |
+| 🏡 | `ESTATE` | `COUNTRYHOUSE` | A rural residence of notable size, typically encompassing a substantial house, outbuildings, and extensive grounds like gardens, farmland, and woodlands (often used seasonally or by the upper class). |
+| 🏡 | `ESTATE` | `DOMAIN`   | Historical or noble estate with named boundaries or jurisdiction |
+| 🏡 | `ESTATE` | `FARMHOUSE`| A central residential building in a rural estate, typically where the landowner or steward lives. |
+| 🏡 | `ESTATE` | `FREEHOLD` | Land or buildings held with full legal title |
+| 🏡 | `ESTATE` | `GAMEKEEP` | A structure or enclosed area used to house game animals, or where the gamekeeper resides. |
+| 🏡 | `ESTATE` | `HUNTGROUNDS` | Land set aside for organized hunting, often legally defined and inherited. |
+| 🏡 | `ESTATE` | `LEASED`   | Property or parcel held temporarily under a lease |
+| 🏡 | `ESTATE` | `LODGE`    | A smaller estate building used for temporary stays, especially in rural or forested properties. |
+| 🏡 | `ESTATE` | `MANOR`    | Large residential house with estate land |
+| 🏡 | `ESTATE` | `PARCEL`   | Defined unit of land, often registered or mapped |
+| 🏡 | `ESTATE` | `PARKLAND` | Landscaped grounds around a manor, sometimes extending into wild or semi-wild areas for hunting or grazing. |
+| 🏡 | `ESTATE` | `REAL`     | General term for legally owned land or real estate |
+| 🏡 | `ESTATE` | `RESIDENCE` | Primary or significant dwelling associated with land ownership |
+| 🏡 | `ESTATE` | `TERRITORY` | Broader named area under control of estate or title |
+| 🏡 | `ESTATE` | `VILLAGE`  | A self-contained estate-based hamlet, often with tenant housing, chapel, and service buildings. |
+| 🏡 | `ESTATE` | `OTHER`    | Any other estate-related asset or structure; must include PHRASE to clarify. |
+| 💰 | `FINANCE` | `ACCOUNTS` | Bank accounts, funds, savings books or similar holdings |
+| 💰 | `FINANCE` | `BOND` | Government or private debt instruments with maturity dates |
+| 💰 | `FINANCE` | `CREDIT` | Bonds, ledgers, debts or claims ( Claims, IOUs, or loans owed to the individual) |
+| 💰 | `FINANCE` | `DEBT` | Outstanding amounts owed by the individual |
+| 💰 | `FINANCE` | `INSURANCE` | Life or property policies with financial outcomes |
+| 💰 | `FINANCE` | `INVESTMENT` | Share certificates, company stakes, speculative holdings |
+| 💰 | `FINANCE` | `OTHER` | Any other finance-related item; must include `PHRASE` to clarify. |
+| 💰 | `FINANCE` | `SECURITY` | Stocks, bonds, or financial instruments |
+| 💰 | `FINANCE` | `STOCKS` | Tradable shares in companies or funds (Stocks, bonds, investments) |
+| 💰 | `FINANCE` | `TAX` | Tax records, obligations, or rebates |
+| 🧠 | `INTANGIBLE` | `AIR-RIGHT` | Rights to build or use space above property. Use PHRASE for detail: [overbuild, balcony, signage]. |
+| 🧠 | `INTANGIBLE` | `BUILDRIGHT` | **Build Construction**: Permits to erect structures. Use PHRASE for detail: [churches, mills]. |
+| 🧠 | `INTANGIBLE` | `COPYRIGHT`     | Legal right granting the creator of an original work exclusive rights to its use and distribution. Common in wills for authors, artists, or heirs to creative works. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`. Use PHRASE for detail: [book copyright, artwork copyright, software copyright]. |
+| 🧠 | `INTANGIBLE` | `DIGASSET` | **Digital Asset**: Non-physical assets stored electronically, including domain names, cryptocurrency, and NFTs. Increasingly appearing in modern wills and trusts. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`, `ADMINISTRATOR`. Use PHRASE for detail: [domain name, Bitcoin, NFT, social media account]. |
+| 🧠 | `INTANGIBLE` | `EXPLOITATION` | Right to commercially exploit a resource. Use PHRASE for detail: peat cutting, timber harvesting]. |
+| 🧠 | `INTANGIBLE` | `EASEMENT`      | Legal right to use another person’s land for a specific purpose without owning it. Can be transferred or inherited if tied to property rights. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`. Use PHRASE for detail: [right of way, water access, utility access]. |
+| 🧠 | `INTANGIBLE` | `FISHRIGHT` | **Fishing Right**: Exclusive rights to fish in a body of water. Often recorded alongside hunting rights in noble charters. Use PHRASE for detail: [river, lake, coastal]. |
+| 🧠 | `INTANGIBLE` | `FRANCHISE`     | Authorization to operate a business using the branding and model of an established company. Transfer may require guild, trade body, or franchisor approval. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`, `TRUSTEE`. Use PHRASE for detail: [restaurant franchise, retail franchise, service franchise]. |
+| 🧠 | `INTANGIBLE` | `GUILDRIGHT` | **Guild Right**: Membership rights in a trade or craft guild, including privileges to work, vote, or hold office. Use PHRASE for detail: [blacksmith, goldsmith, weaver]. |
+| 🧠 | `INTANGIBLE` | `HUNTRIGHT` | **Hunting Right**: Long-term or hereditary right to hunt in a defined region. Use PHRASE for detail: [forest, deer, boar]. |
+| 🧠 | `INTANGIBLE` | `MINERALRIGHT` | **Mineral Right**: Legal right to extract minerals from land without owning the land itself. Use PHRASE for detail: [coal, gold, salt]. |
+| 🧠 | `INTANGIBLE` | `MONOPRIGHT` | **Monopoly Right**: Historically granted exclusive rights to produce or sell specific goods. Use PHRASE for detail: [salt, beer, textiles]. |
+| 🧠 | `INTANGIBLE` | `NAVIGATION`   | Rights to use a river/port for trade. Use PHRASE for detail: [river passage, port access, toll exemption, customs privilege, waterway transit, bridge passage, ferry rights, wharf usage, anchorage, cargo loading, market access, trade route, channel navigation, harbor berth, quay rights, lock passage, weir transit, mill stream, tidal waters, international waters]. |
+| 🧠 | `INTANGIBLE` | `PATENT`        | Government grant giving the inventor exclusive rights to an invention for a set period. Often listed as an asset to be transferred to heirs or trusts. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`. Use PHRASE for detail: [mechanical patent, chemical patent, process patent]. |
+| 🧠 | `INTANGIBLE` | `PERFRIGHT` | **Performance Right**: Exclusive right to perform specific works or hold performances. Use PHRASE for detail: [Theatre, fairs, play, music, opera, market festival]. |
+| 🧠 | `INTANGIBLE` | `PROFLICENSE` | Professional License: Lifelong or transferable professional rights. Use PHRASE for detail: [medical, notary, surveyor]. |
+| 🧠 | `INTANGIBLE` | `ROYALTY`       | Payment received for the ongoing use of a property or right, such as intellectual property or natural resources. Often bequeathed with attached rights to collect future payments. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`, `TRUSTEE`. Use PHRASE for detail: [book royalty, music royalty, mining royalty]. |
+| 🧠 | `INTANGIBLE` | `SHAREHOLDING`  | Ownership interest in a company or corporation represented by shares. May require legal transfer documentation during probate. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`, `ADMINISTRATOR`. Use PHRASE for detail: [stock, equity stake, voting share]. |
+| 🧠 | `INTANGIBLE` | `TITLE` | Hereditary or granted noble titles and dignities. Use PHRASE for detail: [duke, baron, count]. |
+| 🧠 | `INTANGIBLE` | `TRADEMARK`     | Symbol, word, or phrase legally registered to represent a company or product. Can be inherited or transferred via business succession. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`, `TRUSTEE`. Use PHRASE for detail: [logo trademark, brand name, service mark]. |
+| 🧠 | `INTANGIBLE` | `TRADERIGHT` | **Trade right**: Certified right to trade in a specific commodity or region. Use PHRASE for detail: [spices, silk, town market]. |
+| 🧠 | `INTANGIBLE` | `WATERRIGHT` | **Water Right**: Right to use water for irrigation, milling, or other purposes. Use PHRASE for detail: [millstream, irrigation]. |
+| 🧠 | `INTANGIBLE` | `OTHER`         | Any other intangible property or right not listed above. Must use PHRASE to clarify. Related ROLEs: `BENEFICIARY`, `HEIR`, `EXECUTOR`, `TRUSTEE`. Use PHRASE for detail: [custom right, unusual intangible asset]. |
+| 💎 | `JEWELRY` | `BRACELET` | Wrist or arm bands, decorative or commemorative |
+| 💎 | `JEWELRY` | `BROOCH` | Decorative fastening pins or clasps / Fastening pins or brooches |
+| 💎 | `JEWELRY` | `CHAIN` | Neck or wrist chains, including medallions |
+| 💎 | `JEWELRY` | `CROWN` | Crowns, tiaras, or coronets |
+| 💎 | `JEWELRY` | `EARRING` | Pairs or singles of worn ear jewelry / Pierced or clip-on ear ornaments |
+| 💎 | `JEWELRY` | `LARGE` | Substantial or prominent jewelry (crowns, ceremonial pieces) |
+| 💎 | `JEWELRY` | `NECKLACE` | Worn around the neck; chains, beads, or pendants |
+| 💎 | `JEWELRY` | `OTHER` | Any other jewelry; must include PHRASE to clarify |
+| 💎 | `JEWELRY` | `RING` | Finger rings, signets, symbolic rings, or bands|
+| 💎 | `JEWELRY` | `SMALL` | Miscellaneous or miniature items (e.g. cufflinks, tie pins) |
+| 🌿 | `LAND` | `FIELD` | Specific cultivated or named open land plots (Open terrain used for crops or grazing) |
+| 🌿 | `LAND` | `FOREST` | Wooded area for hunting or timber |
+| 🌿 | `LAND` | `GARDEN` | Cultivated private or estate gardens, including ornamental, vegetable, or mixed-use areas. Also private gardens for ornamentals, vegetables |
+| 🌿 | `LAND` | `ISLAND` | Defined islands or riverbanks, or small natural landforms in a body of water |
+| 🌿 | `LAND` | `LAKE` | Freshwater bodies, enclosed ponds, or estate lakes |
+| 🌿 | `LAND` | `MEADOW` | Hayfields, wet grassland, flat or damp terrain with grass and wildflowers or flat pastures |
+| 🌿 | `LAND` | `ORCHARD` | Tree-based production areas such as apple or cherry orchards, vineyards |
+| 🌿 | `LAND` | `OTHER` | Other types of land. Must include a `PHRASE` to clarify subtype not listed above |
+| 🌿 | `LAND` | `TREE` | Singular marked trees (possibly commemorative), groves, or commemorative plantings |
+| 🌿 | `LAND` | `VINEYARD` | Cultivated grape-growing areas |
+| 🪪 | `LICENSE` | `HUNTING`   | Right to hunt in a specific region. Common in noble or rural records. |
+| 🪪 | `LICENSE` | `MARRIAGE`  | Formal license to marry, typically from church or municipality. |
+| 🪪 | `LICENSE` | `MEDICAL`   | Authority to practice medicine or related healing professions. |
+| 🪪 | `LICENSE` | `TRADE`     | Certification for commercial or craft activity. May be linked to guilds. |
+| 🪪 | `LICENSE` | `WEAPON`    | Legal permit to carry or own firearms or swords. |
+| 🪪 | `LICENSE` | `OTHER`     | Any other license; must use PHRASE to clarify. |
+| 🎞️ | `MEDIA` | `CLIPPING` | Cutouts from periodicals, often found in scrapbooks |
+| 🎞️ | `MEDIA` | `DIGITAL` | Purely digital assets, like image files or PDFs |
+| 🎞️ | `MEDIA` | `MANUSCRIPT` | Unpublished written/typed material |
+| 🎞️ | `MEDIA` | `OTHER` | Any other media; must include PHRASE to clarify |
+| 🎞️ | `MEDIA` | `PHOTO` | Photographs, negatives, or albums |
+| 🎞️ | `MEDIA` | `POSTER` | Visual print item, often event- or era-specific |
+| 🎞️ | `MEDIA` | `PUBLICATION` | Books, newspapers, or printed media |
+| 🎞️ | `MEDIA` | `RECORDING` | Audio or video recordings, tapes, or discs |
+| 🎞️ | `MEDIA` | `VIDEO` | Video recordings, films, or VHS tapes |
+| 🕊️ | `MEMORIAL` | `ANCESTORTABLET`    | East Asian — traditional altar tablets with names of ancestors |
+| 🕊️ | `MEMORIAL` | `BURIALPLOT`        | Designated area in cemetery where remains are interred |
+| 🕊️ | `MEMORIAL` | `CARD`              | Printed card formats used for remembrance or ceremony: includes `INVITATIONCARD` (inviting recipient to a memorial or funeral event), `NOTICECARD` (General printed notice about death, memorial, or event), `SERVICECARD` (Small printed handout from funeral or wake), and similar formats except `MEMORIALCARD`. |
+| 🕊️ | `MEMORIAL` | `CENOTAPH`          | Symbolic grave without remains |
+| 🕊️ | `MEMORIAL` | `INSCRIPTION`       | Wording etched or engraved onto stone/memorial |
+| 🕊️ | `MEMORIAL` | `MEMOIR`            | Published or private written remembrance of deceased |
+| 🕊️ | `MEMORIAL` | `MEMORIALCANDLE`    | Religious or commemorative candle lit in memory |
+| 🕊️ | `MEMORIAL` | `MEMORIALCARD`      | Bidprentje (Dutch), "memorial card", often handed out at funerals, sometimes mailed later |
+| 🕊️ | `MEMORIAL` | `MEMORIALTREE`      | Modern — planted in memory of someone, often with plaque |
+| 🕊️ | `MEMORIAL` | `MONUMENT`          | Statue or obelisk |
+| 🕊️ | `MEMORIAL` | `NICHE`             | Columbarium niche for storing urns |
+| 🕊️ | `MEMORIAL` | `OTHER`             | Anything that does not fit in these subtypes. Must have a `PHRASE` |
+| 🕊️ | `MEMORIAL` | `PLAQUE`            | Affixed plate or wall |
+| 🕊️ | `MEMORIAL` | `PRINTED`           | Funeralprogram (Printed service order or program from funeral), Memorial Notice (More generic – may refer to church bulletin, digital memorial, etc.), Obituary or probate clip (Printed newspaper obituary or probate or public posting about probate) (if clipped/saved), or Generic public announcement regarding a death or probate.)
+| 🕊️ | `MEMORIAL` | `RELIGIOUSOBJECT`   | Religious item associated with remembrance (rosary, tablet, candle) |
+| 🕊️ | `MEMORIAL` | `SHRINE`            | General — especially in Japan or indigenous cultures |
+| 🕊️ | `MEMORIAL` | `STUMBLINGSTONE`    | Stolperstein – Holocaust marker |
+| 🕊️ | `MEMORIAL` | `TOMBSTONE`         | Inscribed stone marking a grave; or gravestone (Physical headstone) |
+| 🕊️ | `MEMORIAL` | `URN`               | Container for cremated remains, possibly with attached label, inscription, or ID |
+| 🕊️ | `MEMORIAL` | `YAHRZEITBOARD`     | Jewish — wall of lights in synagogue for death anniversaries |
+| 🪖 | `MILITARY` | `BADGE`     | Emblems indicating rank, unit, qualification, or skill (distinct from medals). |
+| 🪖 | `MILITARY` | `DOCUMENT` | Service records or honorable discharge papers |
+| 🪖 | `MILITARY` | `EQUIPMENT` | Military-issued gear such as field packs, binoculars, entrenching tools, or radios. |
+| 🪖 | `MILITARY` | `MEDALS` | Military medals, awards, badges, or official decorations |
+| 🪖 | `MILITARY` | `OTHER` | Any other military; must include PHRASE to clarify |
+| 🪖 | `MILITARY` | `PASS`      | Military leave papers, deployment orders, or identification documents. |
+| 🪖 | `MILITARY` | `UNIFORMS` | Military uniforms, clothing or gear issued during military service |
+| 💶 | `MONEY`    | `BANKNOTE` | Paper currency including bills and notes. |
+| 💶 | `MONEY`    | `COIN` | Minted metal currency for trade or collection. |
+| 💶 | `MONEY`    | `CURRENCY`| Tangible cash assets: coins, paper, or historic money. |
+| 💶 | `MONEY`    | `CREDIT` | Bonds, ledgers, debts or claims |
+| 💶 | `MONEY`    | `DIAMOND`  | Loose or set diamonds held as assets or heirlooms. |
+| 💶 | `MONEY`    | `GOLD`  | Bullion, coins, or gold-based valuables. |
+| 💶 | `MONEY`    | `JEWEL`  | High-value individual gems (rubies, emeralds, sapphires). |
+| 💶 | `MONEY`    | `OTHER` | Any other money; must include PHRASE to clarify |
+| 💶 | `MONEY`    | `SILVER`     | Silver coins, bullion, or silverware with monetary value. |
+| 💶 | `MONEY`    | `TREASURE`   | Hoards, strongboxes, or unrecovered stored wealth. |
+| 🏢 | `ORGANIZATION` | `ADOPTIONAGENCY` | Organization that issued or facilitated an adoption certificate or placement. Use PHRASE for detail: [adoption office, placement agency, foster bureau] |
+| 🏢 | `ORGANIZATION` | `ARCHIVE` | Repository for official or historical documents. Use PHRASE for detail: [city archive, family archive, digital archive] |
+| 🏢 | `ORGANIZATION` | `CHARITY` | Nonprofit organization offering aid, shelter, or social care. Use PHRASE for detail: [soup kitchen, shelter, mutual aid society] |
+| 🏢 | `ORGANIZATION` | `CHURCH` | Religious body or denomination functioning as a certifier or recorder. Use PHRASE for detail: [diocese, parish, synod, membership, vows] Also see `MONASTERY` or `RELIGIOUSORDER` |
+| 🏢 | `ORGANIZATION` | `CIVILREGISTRY` | Government office recording births, deaths, marriages, etc. Use PHRASE for detail: [register office, population register, vital records bureau, ID, emigration permit, birth/death certificate, marriage record, drivers license, passport, emigration permit, exit stamp] Also see `GOVERNMENT` or `COURT`|
+| 🏢 | `ORGANIZATION` | `COMPANY` | Named employer, business, corporate entity, or commercial institution that may act as employer, landowner, colonizer, or contractor. Use PHRASE for detail: [factory, shop, shipyard, publishing house, trading company, colonial company, plantation owner, land lease office, chartered company, brand, land lease, employer, charter, colonizing company] |
+| 🏢 | `ORGANIZATION` | `CONSULATE` | Foreign affairs or consular office that handles migration, identification, and legal documents for citizens abroad. Use PHRASE for detail: [embassy, visa office, passport service, passport, visa, identity certificate, emigration service, immigration office/checkpoint, border control/crossing, birth abroad] |
+| 🏢 | `ORGANIZATION` | `COURT` | Legal body issuing decisions, rulings, licenses, decrees, or certifications. Use PHRASE for detail: [family court, guardianship, name change, adoption decree, naturalization court, probate court, tribunal, will, inheritance]  Also see `GOVERNMENT` or `CIVILREGISTRY` |
+| 🏢 | `ORGANIZATION` | `CROWN` | Sovereign authority or ruling monarchy acting as grantor, endorser, or legal arbiter. Granting rights, privileges, or land. Use PHRASE for detail: [kingdom, crown estate, monarch, colonial crown office, (royal) patent, crown/land grant, sovereign authority] |
+| 🏢 | `ORGANIZATION` | `GOVERNMENT` | Named government body or agency not covered elsewhere, often involved in citizenship, identification, or administration. Sometimes responsible for military reward, land grant, or surveying not covered by `COURT` or `CIVILREGISTRY`. Use PHRASE for detail: [municipality, land grant office, cabinet, national agency, legislative body, colonial authority, parliament, agency, immigration office, citizenship service, tax office/records, building permit, trade license, homestead, zoning, registration, charter, passport, ID card, military discharge, pensions, social rights (widow claims), border control, visa center, naturalization (certificate), emigration permit, exit stamp, customs, residence permit, social security, ministry] |
+| 🏢 | `ORGANIZATION` | `LANDOFFICE` | Designated office for managing, granting, or surveying public land. Use PHRASE for detail: [land grant board, homestead bureau, general land office, royal surveyor, appropriation bureau, allotment office, (house) contract, land deed, property transfer] |
+| 🏢 | `ORGANIZATION` | `MEDICAL` | Institution related to health, treatment, or (DNA) testing. Can also be listed as a place of birth, death, or treatment (appearing in death, birth, or illness records). Use PHRASE for detail: [hospital, clinic, sanatorium, (DNA) laboratory, testing center] |
+| 🏢 | `ORGANIZATION` | `MILITARY` | Armed services institution or unit listed on military records. Use PHRASE for detail: [infantry, regiment, navy bureau, discharge] |
+| 🏢 | `ORGANIZATION` | `MONASTERY` | Religious residence or authority that records vows, ordinations, or membership. Use PHRASE for detail: [abbey, convent, priory, membership, vows] Also see `CHURCH` |
+| 🏢 | `ORGANIZATION` | `NOTARY` | Office where a public officer called a notary public provides services related to document authentication and witnessing of legal documents. Use PHRASE for detail: [notarial archive, deed office, legal desk, will, deed, marriage contract, guardianship, property deed, land deed, power of attorney, business contract, affidavits, loan documents, partnership, inheritance] |
+| 🏢 | `ORGANIZATION` | `OTHER` | Any organization not covered above. Must include a PHRASE. Use PHRASE for detail: [commission, taskforce, cooperative] |
+| 🏢 | `ORGANIZATION` | `PRISON` | Penal institution mentioned in legal or identity documents. Use PHRASE for detail: [penitentiary, correctional facility, jail] |
+| 🏢 | `ORGANIZATION` | `REGISTRY` | Civil registry or governmental record-holding or administrative body, sometimes involved in ownership transfer or land survey. Use PHRASE for detail: [land registry, property register/transfer, cadastral archive, trade register, record office, land title office, civil registration, ownership archive, title, land ownership] |
+| 🏢 | `ORGANIZATION` | `RELIGIOUSORDER` | Specific religious group distinct from `CHURCH`. Use PHRASE for detail: [Jesuits, Benedictines, Franciscans] |
+| 🏢 | `ORGANIZATION` | `RIGHT` | Organization or authority granting legal, civic, natural, or usage rights. Use PHRASE for detail: [(fishing- hunting- grazing- etc right, mineral right, logging permit, canal access, building right, broadcast license, licenses, airspace, toll right, franchise, water right, trademark, copyright, brand, patent, usage permit, access right, zoning right] |
+| 🏢 | `ORGANIZATION` | `SCHOOL` | Academic or degree-granting institution where education occurs or credentials are issued. Use PHRASE for detail: [school, college, university, seminary, academy, institute] |
+| 🏢 | `ORGANIZATION` | `TRADEUNION` | Guild, craft organization, or labor union involved in employment, advocacy, or disputes. Use PHRASE for detail: [apprenticeship record, (guild)certification board, professional license, worker association, work permit, carpenter’s guild, miners’ union, textile association, workers’ council] |
+| 🏢 | `ORGANIZATION` | `UNION` | Group formed for representation, support, or shared interests. Use PHRASE for detail: [marriage registrar, trade union, brotherhood, Masonic lodge, labor union, professional guild, trade license] |
+| 👤 | `PERSON`   | `AN_ADOPTION` | Annotated: Adoption status noted or changed (e.g., “now adopted by X”). |
+| 👤 | `PERSON`   | `AN_ALIAS`    | Annotated: Alternative or assumed name noted. |
+| 👤 | `PERSON`   | `AN_ARRIVE`   | Annotated: Person appears as newly arrived in the household or area. |
+| 👤 | `PERSON`   | `AN_BAPTISM`  | Person babtized during the record’s timeframe (e.g., family marginal note). |
+| 👤 | `PERSON`   | `AN_BIRTH`    | Person born during the record’s timeframe (e.g., census marginal note). |
+| 👤 | `PERSON`   | `AN_DEATH`    | Annotated: Person died during the record’s timeframe (often as marginal or side entry). |
+| 👤 | `PERSON`   | `AN_DEPORTATION`| Annotated: Person forcibly removed or relocated (e.g., institutional or state record). |
+| 👤 | `PERSON`   | `AN_DISCHARGE`| Annotated: Person officially released from service, duty, or institution. |
+| 👤 | `PERSON`   | `AN_DIVORCE`  | Annotated: Person is divorced , often also gives the date |
+| 👤 | `PERSON`   | `AN_INHERIT`  | Annotated: Gift, Inheritance or succession noted. Use PHRASE for detail: [Gift, Inheritance or Succession] (e.g., on land or property registers) |
+| 👤 | `PERSON`   | `AN_LEAVE`    | Annotated: Person moved out or left the location, household, or institution. |
+| 👤 | `PERSON`   | `AN_MARRIAGE` | Annotated: Marriage note about this person (e.g., “now wife of X” — not the main event). |
+| 👤 | `PERSON`   | `AN_MENTION`  | Annotated: Person mentioned in a marginal note or side entry, with no event detail. |
+| 👤 | `PERSON`   | `AN_MOVE`     | Annotated: Informal address or location change noted. |
+| 👤 | `PERSON`   | `MAIN`        | Primary individual described by the document (e.g., census row, applicant, owner). |
+| 👤 | `PERSON`   | `AN_OCCUPATION`| Annotated: Occupation or role added informally (e.g., “now a carpenter”).  |
+| 👤 | `PERSON`   | `AN_OTHER`    | Annotated: Involved in an annotated non-standard way; use `PHRASE` to clarify. |
+| 👤 | `PERSON`   | `OTHER`       | Involved in a non-standard way; use `PHRASE` to clarify. |
+| 👤 | `PERSON`   | `AN_PROMOTION`| Annotated: Person noted as promoted in rank or job (e.g., in military, employment). |
+| 👤 | `PERSON`   | `AN_RETURN`   | Annotated: Person noted as returned to household or prior location. |
+| 👤 | `PERSON`   | `AN_TRANSFER` | Annotated: Relocated between units, schools, prisons, or institutions. Could also be the original owner for gifts or inheritance. Use PHRASE for detail: [Gift, Inheritance or Succession, land, benefit, unit, school, prison, institution and more] |
+| 👤 | `PERSON`   | `AN_WITNESS`  | Annotated: Present in official or witnessing capacity (e.g., signer, observer). |
+| 🏘️ | `PROPERTY` | `BUILDING` | Houses, barns, or other standalone structures |
+| 🏘️ | `PROPERTY` | `BUSINESS` | Commercial premises or named shops |
+| 🏘️ | `PROPERTY` | `COTTAGE` | Small dwellings or single-family homes |
+| 🏘️ | `PROPERTY` | `ESTATE` | Named residential estates or manors |
+| 🏘️ | `PROPERTY` | `FARM` | Agricultural land with functional buildings |
+| 🏘️ | `PROPERTY` | `HOMESTEAD` | Self-sufficient dwellings, often family-run |
+| 🏘️ | `PROPERTY` | `HOUSE` | Individual dwellings, including townhouses |
+| 🏘️ | `PROPERTY` | `OTHER` | Any other property; must include PHRASE to clarify |
+| 🏘️ | `PROPERTY` | `PLOT` | Undeveloped or minimally developed parcels of land |
+| 🏘️ | `PROPERTY` | `SHED` | Outbuildings for storage or minor functions |
+| 🏘️ | `PROPERTY` | `STABLE` | Horse or livestock buildings |
+| 🏘️ | `PROPERTY` | `STRUCTURE` | Built items not fitting other categories (sheds, windmills, etc.) |
+| 🏘️ | `PROPERTY` | `TOWER` | Watchtowers, bell towers, or isolated structures |
+| 🏘️ | `PROPERTY` | `WORKSHOP` | Places used for craft or trade activities |
+| ✝️ | `RELIGIOUS` | `ALTAR` | Fixed or movable altars |
+| ✝️ | `RELIGIOUS` | `ARTIFACT` | Ritual objects or relics |
+| ✝️ | `RELIGIOUS` | `BIBLE` | Sacred book — can also be a family-held Bible recording vital events, often annotated by multiple generations |
+| ✝️ | `RELIGIOUS` | `BOOK` | Bound volumes used in liturgy or instruction — such as hymnals, prayer books, or printed scriptures. |
+| ✝️ | `RELIGIOUS` | `ICON` | Painted or sculpted sacred images |
+| ✝️ | `RELIGIOUS` | `OTHER` | Any other religious; must include PHRASE to clarify |
+| ✝️ | `RELIGIOUS` | `RELIQUARY` | Containers or holders of relics |
+| ✝️ | `RELIGIOUS` | `TEXT` | Sacred writings or manuscript excerpts — including scrolls, copied passages, or unbound religious documents. |
+| ✝️ | `RELIGIOUS` | `VESTMENT` | Religious clothing or priestly or ceremonial garments |
+| 🛠️ | `TOOLS` | `AGRICULTURE` | Implements for farming or animal care (plow, scythe, shears, yoke) – includes FARMING / Implements for farming or animal care (plow, scythe, shears, yoke) – includes FARMING |
+| 🛠️ | `TOOLS` | `BLACKSMITH` | Tools used in smithing or forging (anvil, tongs, bellows, hammer) – part of TRADESMAN / Tools used in smithing or forging (anvil, tongs, bellows, hammer) – part of TRADESMAN |
+| 🛠️ | `TOOLS` | `CARPENTRY` | Woodworking or joinery tools (saw, plane, chisel, square, lathe) – part of TRADESMAN / Woodworking or joinery tools (saw, plane, chisel, square, lathe) – part of TRADESMAN |
+| 🛠️ | `TOOLS` | `DOMESTIC` | Household implements (butter churn, spinning wheel, mangle, iron) – includes KITCHEN / Household implements (butter churn, spinning wheel, mangle, iron) – includes KITCHEN |
+| 🛠️ | `TOOLS` | `EQUIPMENT` | Machinery, tools, or business-related gear used in production, repair, or trade. |
+| 🛠️ | `TOOLS` | `FARMING` | Plows, hoes, scythes, or similar instruments |
+| 🛠️ | `TOOLS` | `KITCHEN` | Household tools for preparing food |
+| 🛠️ | `TOOLS` | `MEASUREMENT` | Devices for length, weight, volume, time (scale, clock, astrolabe) |
+| 🛠️ | `TOOLS` | `MEDICAL` | Surgical or diagnostic tools (forceps, lancet, stethoscope) |
+| 🛠️ | `TOOLS` | `MILITARY` | Swords, muskets, or other weapons / Weapons and related gear (sword, musket, pike, bayonet, powder horn, cartridge pouch, scabbard, training sabres) |
+| 🛠️ | `TOOLS` | `MUSICAL` | Tuners, bows, metronomes, pipe reamers — not the instruments, just the tools |
+| 🛠️ | `TOOLS` | `NAVIGATION` | Compasses, sextants, maps, logbooks used for travel and sea navigation |
+| 🛠️ | `TOOLS` | `OTHER` | Specialized tools not covered above (e.g., glassblowing pipe, cobbler’s last) |
+| 🛠️ | `TOOLS` | `TEXTILE` | Looms, needles, shuttles, distaffs, and thread winders – part of TRADESMAN |
+| 🛠️ | `TOOLS` | `TRADESMAN` | Artisan tools, tailor’s kit, smith gear, bakery, butcher etc. Use `PHRASE` to clarify. |
+| 🛠️ | `TOOLS` | `WEAPON` | Any possible weapon, use `PHRASE` to clarify. |
+| 🛠️ | `TOOLS` | `WRITING` | Inkwells, styluses, typewriters, wax tablets, rulers, scribal gear |
+| 🚗 | `TRANSPORT` | `BICYCLE` | Two- or three-wheeled pedal-powered vehicles, including bicycles, tricycles, tandems and cargo cycles. |
+| 🚗 | `TRANSPORT` | `BOAT` | Watercraft of any size — from small rowboats to yachts or fishing vessels. Includes personal or commercial use. |
+| 🚗 | `TRANSPORT` | `CARRIAGE` | Traditional horse-drawn vehicles for people or cargo |
+| 🚗 | `TRANSPORT` | `CART` | Two-wheeled or utility carts, often for manual or animal use |
+| 🚗 | `TRANSPORT` | `COACH` | Passenger or ceremonial transport, often enclosed |
+| 🚗 | `TRANSPORT` | `OTHER` | Any other transport; must include PHRASE to clarify |
+| 🚗 | `TRANSPORT` | `SHIP` | Large sea-going vessels, often named — used in immigration, military, or long-distance commercial transport. |
+| 🚗 | `TRANSPORT` | `SLED` | Land or snow-based sleds, sleighs |
+| 🚗 | `TRANSPORT` | `VEHICLE` | General motorized or wheeled transport (unspecified) |
+| 🚗 | `TRANSPORT` | `WAGON` | Larger transport, often four-wheeled, cargo or passenger use |
+| 🚗 | `TRANSPORT` | `WHEELCHAIR` | Self-propelled or assisted mobility chairs |
+| 🌀 | `OTHER`     | `OTHER` | Any other entity; must include PHRASE to clarify |
+
+
diff --git a/specification/gedcom-3-structures-4-enumerations-events.md b/specification/gedcom-3-structures-4-enumerations-events.md
new file mode 100644
index 00000000..a2e6f9f5
--- /dev/null
+++ b/specification/gedcom-3-structures-4-enumerations-events.md
@@ -0,0 +1,442 @@
+
+### `g8:enumset-EVENT-TYPE` 
+
+Each `TEMPLATE` must declare a `TYPE`. These are the main categories of life events, legal actions, affiliations, or other documented situations that a template can represent.
+
+| ICO | TYPE         | Description |
+|--|----------------|-------------|
+| 👶 | `CHILD`     | Births, baptisms, christenings, adoptions, foundlings — any record focused on the appearance of a child. |
+| 🏛️ | `CIVIL`     | State or municipal processes like registrations, citizen declarations, civic permits, or local obligations. May include stepchild declarations or civil status. |
+| ⚰️ | `DEATH`     | Deaths, burials, funerals, probates, wills, and related documents marking the end of life or its aftermath. |
+| 📚 | `EDUCATIONAL` | Records of schooling, degrees, apprenticeships, certifications, or academic achievements. |
+| 👨‍👩‍👧 | `FAMILY`    | Marriages, banns, divorces, separations, engagements, and formal unions — plus notices, contracts, and filings. |
+| 🛡️ | `GROUP`     | Membership or interaction with a social group, clan, caste, tribe, guild, political body, or religious sect. Often includes joining, exiting, or holding a position. |
+| 🪪 | `IDENTITY`  | DNA, Name changes, nationalities, IDs, passports, or any documentation of personal or cultural identity. |
+| 🖋️ | `LEGAL`     | Legal or judicial documents: trials, court rulings, testimonies, lawsuits, licenses, contracts, etc. |
+| 🎞️ | `MEDIA`     | Items with genealogical value that appear in print or media — photos, articles, portraits, posters, publications. |
+| 🩺 | `MEDICAL`    | Health-related documents such as illness reports, surgeries, hospitalizations, autopsies, and DNA summaries. |
+| 🕯️ | `MEMORIAL`  | Posthumous recognitions: gravestones, obituaries, memorial plaques, funeral cards, digital tributes. |
+| ✈️ | `MIGRATION` | Moves, emigrations, immigration, travel, arrival/departure, border crossings, visas, ship manifests. |
+| 🪖 | `MILITARY`  | Enlistment, service records, deployment, draft, pensions, weapons, awards, discharges, and military tribunals. |
+| 🏗️ | `OCCUPATIONAL` | Employment, trades, job titles, licenses, guild activity, or professional qualifications. |
+| 🛍️ | `PERSONAL`  | Biographical or introspective records: diaries, autobiographies, statements, or personal descriptions. |
+| 🏘️ | `PROPERTY`  | Property deeds, transfers, ownership, inventory lists, estate sales, or asset-related events. |
+| ✝️ | `RELIGIOUS` | Baptisms, confirmations, ordinations, blessings, LDS-specific ordinances, or ritual ceremonies. |
+| ⚓ | `RESIDENCE` | Addresses, housing, relocation records, census entries showing place of living. |
+| 📚 | `SECONDARY` | Published or culturally transmitted sources that interpret, compile, retell, or reflect on primary events. Includes oral tradition, family lore, books, and inferred information not derived from direct evidence.|
+| 🌐 | `SOCIAL`    | Club memberships, community roles, awards, honors, participation in events or social recognition. |
+| 🌈 | `STATUSCHANGE` | Namechange, naturalization, graduation, enslavement, retirement, discharge, elected etc |
+| 🌀 | `OTHER`     | Any event type not captured above. A `PHRASE` field must be used to clarify the event. |
+
+### `g8:enumset-EVENT-SUBTYPE`
+
+Each `TEMPLATE` of a given `TYPE` must also specify a more specific `SUBTYPE` to better describe the nature of the event or record. These subtypes help clarify the function, format, or context of the template, especially for complex or recurring categories.  
+Both, `TYPE` and `SUBTYPE` must be mentioned. So for instance;  
+`TYPE CHILD, BIRTH`
+
+## In the below table, correct filling of the column `TAG` is not finished
+
+| ICO |  `TYPE` |  `SUBTYPE`       |  Description | TAG |
+|---|-------------|------------------|----------------|--|
+| 👶 | `CHILD`   | `ABORTION`    | Intentional termination of pregnancy, typically elective and legally recorded. |  |
+| 👶 | `CHILD`   | `ADOPTION`    | Legal process in which a person becomes the child of someone other than their biological parent. |  |
+| 👶 | `CHILD`   | `BIRTH`       | Documented birth of a person, typically via a certificate, registry, or hospital record. |  |
+| 👶 | `CHILD`   | `BIRTHNOTICE` | Public or official announcement of birth, such as in a newspaper or church bulletin. |  |
+| 👶 | `CHILD`   | `CHRISTENING` | Religious naming or infant baptism shortly after birth. Use `ADULTCHRISTENING` for later-life ceremonies. |  |
+| 👶 | `CHILD`   | `CONCEPTION`  | Documented or estimated date of conception (e.g., in fertility cases or religious contexts). |  |
+| 👶 | `CHILD`   | `FOUNDLING`   | Abandoned infant with unknown parents, typically documented by a parish, orphanage, or municipal office. Distinct from standard birth registration. |  |
+| 👶 | `CHILD`   | `GUARDIANSHIP`| Assignment or change of legal guardianship for a minor, distinct from adoption. May appear in court or municipal records. |  |
+| 👶 | `CHILD`   | `MISCARRIAGE` | Spontaneous loss of a pregnancy before viability; not a stillbirth. |  |
+| 👶 | `CHILD`   | `MULTIPLE`    | Indicates birth as part of a multiple (twin, triplet, etc.) set. May appear on certificates or medical files. |  |
+| 👶 | `CHILD`   | `RECOGNITION` | Legal or social acknowledgment of parentage by one or both parents, often retroactive. |  |
+| 👶 | `CHILD`   | `STEPCHILD`   | Declaration or recognition of a stepchild within a family context. Not a birth or adoption — often noted at marriage or legal guardianship. |  |
+| 👶 | `CHILD`   | `STILLBIRTH`  | Non-viable birth recorded officially; child did not survive birth. |  |
+| 👶 | `CHILD`   | `SURROGACY`   | Child born via a surrogate; may be recorded in medical, legal, or contractual documents. Modern but increasingly present. |  |
+| 👶 | `CHILD`   | `OTHER`       | Child-related event not captured by other subtypes. Use with caution and consider context-specific naming. Must use PHRASE to clarify. |  |
+| 🏛️ | `CIVIL`   | `APPOINTMENT` | Official assignment to a civil position, post, or government office. |  |
+| 🏛️ | `CIVIL`   | `CITATION`    | Official warning or minor civil penalty, such as traffic or public order citations. Can appear in administrative registries. |  |
+| 🏛️ | `CIVIL`   | `COMMISSION`  | Formal grant of power or responsibility, such as to a military or civic commission. |  |
+| 🏛️ | `CIVIL`   | `LICENSE`     | Granting of official permits for business, firearms, vehicles, or other regulated rights, excluding marriage. |  |
+| 🏛️ | `CIVIL`   | `NOMINATION`  | Named as candidate for honor, election, or position. May not result in appointment. |  |
+| 🏛️ | `CIVIL`   | `OATH`        | Oath of service or office — common for judges, civil servants, mayors. May include pledges of allegiance or public duty. |  |
+| 🏛️ | `CIVIL`   | `RECALL`      | Removed from civil office by authority or process, such as a vote or decree. |  |
+| 🏛️ | `CIVIL`   | `RESIGNATION` | Formal withdrawal from public or civil office, often documented with date and role. May appear in council or personnel registers. |  |
+| 🏛️ | `CIVIL`   | `OTHER`       | Other civil events or appointments not described by specific subtypes. Must use PHRASE to clarify. |  |
+| ⚰️ | `DEATH` | `BURIAL` | Disposition of remains after death. |  |
+| ⚰️ | `DEATH` | `CREMATION` | A cremation event. Burning of remains after death. |  |
+| ⚰️ | `DEATH` | `DEATH` | A death event. Record of life termination. |  |
+| ⚰️ | `DEATH` | `DEATHNOTICE` | Formal or public announcement of death. |  |
+| ⚰️ | `DEATH` | `DISAPPEARED` | Unresolved or unexplained vanishing of a person. May or may not involve presumed death. |  |
+| ⚰️ | `DEATH` | `DISINTERMENT` | Exhumation or removal of remains after initial burial. |  |
+| ⚰️ | `DEATH` | `ENTOMBMENT` | Burial in a tomb or mausoleum. Alternative to in-ground burial. |  |
+| ⚰️ | `DEATH` | `FUNERAL` | A funeral event. Ceremony held after death, often associated with burial or memorial. |  |
+| ⚰️ | `DEATH` | `FUNERALNOTICE` | Notification or announcement of a funeral service. |  |
+| ⚰️ | `DEATH` | `INQUEST` | Legal investigation into the cause or circumstances of a death. Often conducted when suspicious. |  |
+| ⚰️ | `DEATH` | `INURNMENT` | Placement of cremated remains into an urn. |  |
+| ⚰️ | `DEATH` | `LOST` | Person or remains never found or recovered. May involve presumed death. |  |
+| ⚰️ | `DEATH` | `OBITUARY` | Public death announcement, often in a newspaper. Summary of life and passing. |  |
+| ⚰️ | `DEATH` | `PROBATE` | Granting of legal authority over a deceased person's estate. |  |
+| ⚰️ | `DEATH` | `PROBATENOTICE` | Public notice of pending or granted probate action. |  |
+| ⚰️ | `DEATH` | `WILL` | Legal will or testament. Creation, registration, or execution of final wishes, including inheritance of property, titles, and symbolic assets. Use STICKYs and TRANSFER to model specific elements. |  |
+| ⚰️ | `DEATH` | `YAHRZEIT` | Anniversary of death on the Hebrew calendar. Jewish memorial tradition. |  |
+| ⚰️ | `DEATH` | `OTHER` | Death-related events not covered by other subtypes. May include alternative customs or unknown disposition. |  |
+ 📚| `EDUCATIONAL` | `AWARD` | A recognition of academic achievement, merit, or service. Includes honors, prizes, or scholarships. |  |
+ 📚| `EDUCATIONAL` | `ACHIEVEMENT` | Educational achievement such as a diploma, graduation, or scholarship. |  |
+ 📚| `EDUCATIONAL` | `APPRENTICESHIP` | Structured skill-learning program under supervision. Often trade-based. |  |
+ 📚| `EDUCATIONAL` | `CERTIFICATE` | Completion of a formal course or professional training resulting in certification. |  |
+ 📚| `EDUCATIONAL` | `ENROLLMENT` | Enrollment in an educational institution or program. Includes first-time enrollment or reenrollment. |  |
+ 📚| `EDUCATIONAL` | `OTHER` | Educational events not covered elsewhere. May include exams, field schools, or informal learning. |  |
+| 👨‍👩‍👧 | `FAMILY` | `ANNIVERSARY` | Published notice or event commemorating a couple's marriage anniversary. |  |
+| 👨‍👩‍👧 | `FAMILY` | `ANNULMENT` | Formal annulment of a marriage. Declares marriage legally void. |  |
+| 👨‍👩‍👧 | `FAMILY` | `BREAKUP` | The termination of a domestic partnership or civil union, without formal divorce. (Parthership dissolution) | DIV |
+| 👨‍👩‍👧 | `FAMILY` | `CENSUS` | Census entry listing household or family members. Overlaps with RESIDENCE. | CENS |
+| 👨‍👩‍👧 | `FAMILY` | `CIVILUNION` | Legal civil union. Recognized partnership without the title of marriage. |  |
+| 👨‍👩‍👧 | `FAMILY` | `CLMARRIAGE` | Non-ceremonial marital union (Common-law marriage). Recognized marriage through cohabitation or time. |  |
+| 👨‍👩‍👧 | `FAMILY` | `COHABITATION` | Two people living together in a long-term relationship without formal marriage. May appear in housing records or census. |  |
+| 👨‍👩‍👧 | `FAMILY` | `DIVORCE` | Dissolution of a marriage. Legal termination of spousal relationship. | DIV |
+| 👨‍👩‍👧 | `FAMILY` | `DIVORCEFILING` | Filing for divorce. Legal beginning of divorce proceedings. | DIVF |
+| 👨‍👩‍👧 | `FAMILY` | `ENGAGEMENT` | Formal declaration or promise to marry. | ENGA |
+| 👨‍👩‍👧 | `FAMILY` | `ENG_NOTICE` | Public or formal announcement of engagement. | ENGA |
+| 👨‍👩‍👧 | `FAMILY` | `MARRIAGE` | Marriage event. Legal or religious union of two people. | MARR |
+| 👨‍👩‍👧 | `FAMILY` | `MARRIAGEBANNS` | Public proclamation of intended marriage, often in religious context. | MARB |
+| 👨‍👩‍👧 | `FAMILY` | `MARRIAGECONTRACT` | Legal or religious agreement detailing terms of marriage. | MARC |
+| 👨‍👩‍👧 | `FAMILY` | `MARRIAGELICENSE` | Government-issued license permitting a marriage. | MARL |
+| 👨‍👩‍👧 | `FAMILY` | `MARRIAGENOTICE` | Public announcement or posting of intended marriage. |  |
+| 👨‍👩‍👧 | `FAMILY` | `PARTNERSHIP` | Partnership or cohabiting couple without formal marriage. (domestic partnership) |  |
+| 👨‍👩‍👧 | `FAMILY` | `RECONCILIATION` | Formal or informal event where a previously separated couple resumes their relationship. |  |
+| 👨‍👩‍👧 | `FAMILY` | `SEPARATION` | Marital or partnership separation, with or without legal divorce. | DIV |
+| 👨‍👩‍👧 | `FAMILY` | `OTHER` | Family-related events not covered by other subtypes. Could include legal status changes, failed engagements, or partnership revisions. |  |
+| 🛡️ | `GROUP` | `CASTE-MEM`   | Membership in a caste or hereditary status group. Typically cultural or social in nature. Examples: caste registry, census caste column, social classification roll. |  |
+| 🛡️ | `GROUP` | `CHARTER`     | Founding or regulatory document of a group. Examples: charter, constitution, covenant, manifesto, founding deed, bylaws, articles of association, guild registration. |  |
+| 🛡️ | `GROUP` | `CLAN-MEM`    | Cultural or lineage-based group affiliation. Examples: clan registers, ancestral rolls, kinship group entries, family branch listings. |  |
+| 🛡️ | `GROUP` | `DISSOLUTION` | Official end of a society, guild, or group. Examples: dissolution decree, registry closure, church deconsecration, guild disbandment notice. |  |
+| 🛡️ | `GROUP` | `ENTERING`    | Entry into a group or affiliation. Examples: guild enrollment forms, monastery entry scrolls, union admission certificates (military unit), sworn brotherhood oaths. |  |
+| 🛡️ | `GROUP` | `EXITING`     | Voluntary or forced departure from a group or affiliation. Examples: retirement, expulsion notice, resignation letter, excommunication decree, discharge record. |  |
+| 🛡️ | `GROUP` | `FARM-MEM`    | Membership or registration in a farming community or co-op. Examples: farm roll, land-allocation list, peasant commune register, rural collective record. |  |
+| 🛡️ | `GROUP` | `GROUP-MEM`   | Generic group or community not covered elsewhere. Examples: club rosters, association cards, lodge directories, union lists, social fellowship rolls. |  |
+| 🛡️ | `GROUP` | `GUILD-MEM`   | Individual’s registration or certification from a guild. Examples: apprenticeship contract, membership scroll, guild stamp, journeyman’s certificate. |  |
+| 🛡️ | `GROUP` | `HEIR`        | Named as a successor or group-designated inheritor. Often part of tribal, guild, or clan succession. Examples: tribal succession listing, guild inheritance certificate, heirship nomination scroll. |  |
+| 🛡️ | `GROUP` | `INITIATION`  | Ritual or formal process of acceptance into a group. Examples: initiation rite record, lodge oath, bar mitzvah certificate, religious conversion form, apprentice entry document. |  |
+| 🛡️ | `GROUP` | `MEMBERSHIP`  | Proof of joining or belonging to a group. Examples: membership card, congregation register, enrollment ledger, tribal roll, church book, scout registration. |  |
+| 🛡️ | `GROUP` | `OTHER`       | Other affiliation-related event not captured elsewhere. Use a `PHRASE` to clarify nature or context of the record. |  |
+| 🛡️ | `GROUP` | `PARTICIPATION` | Documentation of involvement in group activity. Examples: minutes of meetings, group event roll, attendance sheet, committee participation form. |  |
+| 🛡️ | `GROUP`  | `PLACE`     | Indicates the person's rank or role within the group (e.g., `LEADER`, `FOUNDER`, `HONORARY`, `REPRESENTATIVE`, ). Use `ROLE` to specify. |  |
+| 🛡️ | `GROUP` | `REJOINING`   | Re-entering a group after prior departure. Often includes a formal readmission process. Examples: reinitiation scroll, renewed union card, second guild entry, readmission petition. |  |
+| 🛡️ | `GROUP` | `ROLE`        | Indicates the person's role, title or rank in the group. Examples: appointment letter, leadership decree, founder acknowledgment, honorary membership plaque. Use `ROLE` structure to specify. |  |
+| 🛡️ | `GROUP` | `SECT-MEM`    | Religious subgroup affiliation. a sect or division within a larger religious tradition. Examples: sect registry, church division listing, doctrinal certificate, sect enrollment form, ordination certificate. |  |
+| 🛡️ | `GROUP` | `SUSPENSION`  | Temporary removal or inactive status in the group. Examples: disciplinary letter, suspended union card, guild inactivity notice. |  |
+| 🛡️ | `GROUP` | `TRIBE-MEM`   | Documented link to an ethnic or tribal group. Examples: tribal enrollment, census appearance, group register, tribal land allocation, kinship confirmation letter. |  |
+| 🪪 | `IDENTITY` | `ALIAS` | A declared alternative or assumed name used by the individual. May appear on official documents, employment, or residence records. |  |
+| 🪪 | `IDENTITY` | `BLOODTYPE`   | Stated or documented blood type (e.g., on IDs or medical certificates). |  |
+| 🪪 | `IDENTITY` | `CITIZENSHIP` | Legal belonging to a nation or state. Right to participate in civic life. |  |
+| 🪪 | `IDENTITY` | `DNATEST`     | Certified or formally reported DNA results used in official identity resolution. |  |
+| 🪪 | `IDENTITY` | `ETHNICITY` | Stated or documented cultural, ethnic, or racial identity. |  |
+| 🪪 | `IDENTITY` | `GENDERMARKER` | Declared or legal gender marker as recorded on an official document. Can be relevant in transitions, adoptions, or mismatches. |  |
+| 🪪 | `IDENTITY` | `IDENTITY` | General identification record. Could include identity cards or papers. |  |
+| 🪪 | `IDENTITY` | `NAMECHANGE` | Legal name change or declaration of a new identity. Could include marriage-related name changes, adoption, or witness protection. |  |
+| 🪪 | `IDENTITY` | `NATIONALID` | Government-issued national identification number. |  |
+| 🪪 | `IDENTITY` | `NATIONALITY` | Declared or assigned national affiliation. |  |
+| 🪪 | `IDENTITY` | `PASSPORT` | Issuance or use of a passport or travel document. |  |
+| 🪪 | `IDENTITY` | `RESIDENCYPERM` | Official record granting permission to live in a certain country or region, "residency permission" (e.g., visa, green card). |  |
+| 🪪 | `IDENTITY` | `OTHER` | Identity-related events or documents not otherwise categorized. Examples: alias, name corrections, or biometric records. |  |
+| 🖋️ | `LEGAL` | `ARREST`           | Detainment by legal authorities. Legal event of being taken into custody. |  |
+| 🖋️ | `LEGAL` | `BANKRUPTCY`       | Legal declaration of insolvency. |  |
+| 🖋️ | `LEGAL` | `CONTRACT`         | Legal agreement between parties. |  |
+| 🖋️ | `LEGAL` | `COURT`            | Appearance of a person in a court proceeding. Legal court appearance or judicial hearing. |  |
+| 🖋️ | `LEGAL` | `CUSTODIANSHIP`    | Legal or informal designation of someone to care for another. |  |
+| 🖋️ | `LEGAL` | `DEPOSITION`       | Sworn statement or pre-trial testimony. |  |
+| 🖋️ | `LEGAL` | `ESTATESALE`       | Sale of property from a deceased person’s estate. |  |
+| 🖋️ | `LEGAL` | `GUARDIANSHIP`     | Legal responsibility or authority over another individual. |  |
+| 🖋️ | `LEGAL` | `IMPEACHMENT`      | Formal charges brought against a public official. |  |
+| 🖋️ | `LEGAL` | `INDENTURE`        | Binding contract, typically for labor or service, often historical. |  |
+| 🖋️ | `LEGAL` | `JUDGMENT`         | Court ruling or final legal decision. |  |
+| 🖋️ | `LEGAL` | `LAWSUIT`          | Legal dispute or case involving a person. |  |
+| 🖋️ | `LEGAL` | `LICENSE`          | Document granting permission (e.g., business, weapon, marriage). |  |
+| 🖋️ | `LEGAL` | `PARDON`           | Formal legal forgiveness; distinct from amnesty. |  |
+| 🖋️ | `LEGAL` | `PROBATION`        | Conditional release with legal supervision. |  |
+| 🖋️ | `LEGAL` | `REGISTRATION`     | Official recording or certification of a legal event. |  |
+| 🖋️ | `LEGAL` | `TESTIMONY`        | Eyewitness account or formal statement given under oath. |  |
+| 🖋️ | `LEGAL` | `TRANSCRIPT`       | Verbatim record or full copy of legal proceedings. |  |
+| 🖋️ | `LEGAL` | `TRANSFER`         | Legal shift in possession, rights, or custody of an item or person. |  |
+| 🖋️ | `LEGAL` | `TRIAL`            | Judicial examination of facts and law. |  |
+| 🖋️ | `LEGAL` | `OTHER`            | Any other legal document; should include a PHRASE to explain specifics. |  |
+| 🎞️ | `MEDIA`    | `AUDIO`               | Oral or musical source passed down without formal recording. |  |
+| 🎞️ | `MEDIA`    | `AUDIOVISUAL` | Combined audio and video material (e.g., recordings, family movies, interviews on tape). |  |
+| 🎞️ | `MEDIA`    | `BOOK`                | Book excerpt or citation relevant to genealogical events or people. |  |
+| 🎞️ | `MEDIA`    | `EXHIBIT` | Museum or public display item with genealogical or historical relevance (e.g., exhibit placards, curated artifacts). |  |
+| 🎞️ | `MEDIA`    | `INTERVIEW`           | Transcript or notes of an interview; may include oral history. |  |
+| 🎞️ | `MEDIA`    | `NEWSPAPER`           | Newspaper clipping or article used as a source. |  |
+| 🎞️ | `MEDIA`    | `NOTICE`              | Printed or digital announcements such as posters, flyers, event notices, or proclamations. |  |
+| 🎞️ | `MEDIA`    | `OBJECT`              | Tangible item like jewelry, clothing, or furniture with genealogical context. |  |
+| 🎞️ | `MEDIA`    | `PHOTO`               | Photograph with genealogical value. |  |
+| 🎞️ | `MEDIA`    | `PORTRAIT`            | Paintings, busts, or likenesses that identify or represent an individual. |  |
+| 🎞️ | `MEDIA`    | `PUBLISHMENT`         | Appearance in magazine or formal publication (excluding newspapers). |  |
+| 🎞️ | `MEDIA`    | `RECORDING` | Digitized or analog recording of voice, music, or spoken biography. |  |
+| 🎞️ | `MEDIA`    | `TRACES`  | Archived media sources with genealogical value — obituaries, online trees, memorials. |  |
+| 🎞️ | `MEDIA`    | `WEBSITE` | Online resource with genealogical value (e.g., personal family pages, grave index sites). |  |
+| 🎞️ | `MEDIA`    | `OTHER`  | Any other media item; must include a PHRASE to describe its significance. |  |
+| 🩺| `MEDICAL`  | `ADMISSION`| Admission to a hospital for medical care. |  |
+| 🩺| `MEDICAL`  | `AUTOPSY` | Postmortem examination performed to determine cause of death. |  |
+| 🩺| `MEDICAL`  | `CAUSEOFDEATH` | Official or noted cause of death from a record (e.g., death cert, autopsy, family note). |  |
+| 🩺| `MEDICAL`  | `DISABILITY` | Declared or documented disability with genealogical implications. (e.g., pension claim, census disability marker). |  |
+| 🩺| `MEDICAL`  | `DISCHARGE`| Discharge from hospital. |  |
+| 🩺| `MEDICAL`  | `DNA` | Non-documentary genetic source, such as resemblance or home DNA kits. |  |
+| 🩺| `MEDICAL`  | `DNAMATCH` | Genetic connection confirmed between individuals. |  |
+| 🩺| `MEDICAL`  | `HOSPITAL` | Official document from a health institution. |  |
+| 🩺| `MEDICAL`  | `ILLNESS` | Record or mention of significant illness. |  |
+| 🩺| `MEDICAL`  | `IMMUNIZATION` | Vaccination or immunization record. May include historical smallpox, polio, or modern vaccines. |  |
+| 🩺| `MEDICAL`  | `LIVING`              | Confirmation or evidence of life status — such as proof of life during wartime or legal proceedings. May appear in official registries or notarized statements. |  |
+| 🩺| `MEDICAL`  | `MEDICAL`  | General health-related event or condition. |  |
+| 🩺| `MEDICAL`  | `MEDICALTRAITS` | Inherited traits confirmed by examination or report — used in diagnosis or eligibility. |  |
+| 🩺| `MEDICAL`  | `PROCEDURE` | Medical or therapeutic procedure performed. |  |
+| 🩺| `MEDICAL`  | `SURGERY` | Operative medical procedure. |  |
+| 🩺| `MEDICAL`  | `OTHER` | Any other medical event; must include a PHRASE to clarify. |  |
+| 🕯️ | `MEMORIAL` | `COMMEMORATION` | Formal or informal event commemorating a person (e.g., memorial day, annual remembrance). |  |
+| 🕯️ | `MEMORIAL` | `COMMEM_OBJECT` | Symbolic item like a bench, medal, or statue dedicated to someone deceased. |  |
+| 🕯️ | `MEMORIAL` | `FUNERALPROGRAM`      | Printed leaflet or booklet from a funeral, including biography and service order. |  |
+| 🕯️ | `MEMORIAL` | `GRAVESTONE`          | Traditional headstone or tombstone at a burial site, inscribed with genealogical info. |  |
+| 🕯️ | `MEMORIAL` | `HONORING` | Act or record of publicly honoring someone posthumously (e.g., honorary name, street sign). |  |
+| 🕯️ | `MEMORIAL` | `INSCRIPTION`         | Memorial text carved or engraved on stone, buildings, or monuments. |  |
+| 🕯️ | `MEMORIAL` | `MEMNOTICE`      | Public remembrance such as newspaper notices or anniversary bulletins. |  |
+| 🕯️ | `MEMORIAL` | `ONLINEMEM`      | Digital tribute page "online memorial" (e.g., FindAGrave, social platforms) with biographical elements. |  |
+| 🕯️ | `MEMORIAL` | `PLAQUES`             | Plaques on walls or monuments (e.g., war memorials, honorary dedications). |  |
+| 🕯️ | `MEMORIAL` | `PRAYERPICTURE`       | Small devotional card from funerals, often with photo and dates. |  |
+| 🕯️ | `MEMORIAL` | `TRIBUTE` | Written or spoken tribute honoring someone’s memory (e.g., speech, poem, story). |  |
+| 🕯️ | `MEMORIAL` | `OTHER` | Any other memorial item or practice; must include a PHRASE for interpretation. |  |
+| ✈️ | `MIGRATION` | `ARRIVAL` | Arriving at a destination. Entering a place for travel, work, or relocation (non-immigration). |  |
+| ✈️ | `MIGRATION` | `BORDER` | Border crossing or customs control. Includes documentation at entry/exit points, inspections, or customs declarations. |  |
+| ✈️ | `MIGRATION` | `DEPARTURE` | Leaving a location, not necessarily for emigration. Travel away from a place of residence. |  |
+| ✈️ | `MIGRATION` | `DEPORTED` | Forced removal from a country or region by legal or governmental order. |  |
+| ✈️ | `MIGRATION` | `EMIGRATION` | Event where someone moves out of a country or region to live elsewhere. |  |
+| ✈️ | `MIGRATION` | `FLIGHT` | Travel by air, either as part of migration or movement. Can include flight manifests or boarding records. |  |
+| ✈️ | `MIGRATION` | `GROUP-MIGR` | Group Migration Manifest/List. Like a Mennonite trek family list or a shared relocation journey. |  |
+| ✈️ | `MIGRATION` | `HEIMAT` | Cultural or ancestral place of origin. May refer to legal place of citizenship or clan affiliation. |  |
+| ✈️ | `MIGRATION` | `IMMIGRATION` | Entering a country to reside. May include naturalization intent or documents. |  |
+| ✈️ | `MIGRATION` | `MOVE` | General move from one residence to another. |  |
+| ✈️ | `MIGRATION` | `MOVEFROM` | Departure from a specific location (e.g., “moved away from Rotterdam”). |  |
+| ✈️ | `MIGRATION` | `MOVETO` | Arrival at a new location (e.g., “moved to Amsterdam”). |  |
+| ✈️ | `MIGRATION` | `QUARANTINE` | Temporary confinement due to travel regulations or health concerns. |  |
+| ✈️ | `MIGRATION` | `REENTRY` | Returning to a previous country or region after temporary departure. |  |
+| ✈️ | `MIGRATION` | `RELOCATION` | Permanent or semi-permanent move to a new residence. |  |
+| ✈️ | `MIGRATION` | `SHIP` | Ship manifest or passenger list. Maritime travel documentation. |  |
+| ✈️ | `MIGRATION` | `TRANSIT` | Temporary movement through a country or zone without settling. |  |
+| ✈️ | `MIGRATION` | `TRAVEL` | General travel documentation not tied to permanent relocation. |  |
+| ✈️ | `MIGRATION` | `VACATION` | Leisure travel or temporary recreational relocation. |  |
+| ✈️ | `MIGRATION` | `VISA` | Entry, exit, or travel visa. May include permits or endorsements. |  |
+| ✈️ | `MIGRATION` | `VISIT` | A temporary visit to a location different from the person’s residence. |  |
+| ✈️ | `MIGRATION` | `VOYAGE` | Long journey by sea or land. May include documentation of migration or exploration. |  |
+| ✈️ | `MIGRATION` | `OTHER` | Any other migration-related document or event; must include a PHRASE. |  |
+| 🪖 | `MILITARY` | `AWARD` | Military honor or decoration granted for service, merit, bravery, or achievement. Includes medals, citations, and formal recognitions. |  |
+| 🪖 | `MILITARY` | `CAMPAIGN` | Participation in a named or numbered military campaign. May include medals, unit actions, or citations. |  |
+| 🪖 | `MILITARY` | `CONSCRIPTION` | Mandatory enlistment in military service. A situation imposed by law, typically at a certain age.  (Drafted without voluntary enlistment) |  |
+| 🪖 | `MILITARY` | `DEMOTION` | Reduction in rank due to disciplinary or administrative reason. |  |
+| 🪖 | `MILITARY` | `DEPLOYMENT` | Assignment to an active duty location or military station. May include departure/arrival orders. |  |
+| 🪖 | `MILITARY` | `DESERTION` | Leaving service without authorization. Considered a punishable offense. |  |
+| 🪖 | `MILITARY` | `DISCHARGE` | Official release from military service. May include honorable, dishonorable, or medical discharge. |  |
+| 🪖 | `MILITARY` | `DRAFTREG` | Enrollment into a registry of military-eligible individuals. (Draft registration) |  |
+| 🪖 | `MILITARY` | `ENLISTMENT` | Voluntary or accepted entry into military service. May include contract or oath. |  |
+| 🪖 | `MILITARY` | `INDUCTION` | Official incorporation into military ranks after acceptance. (through draft or voluntary process) Often follows `DRAFTREG`. |  |
+| 🪖 | `MILITARY` | `MILDRAFTREG` | Registration for compulsory military service. Similar to `DRAFTREG`. |  |
+| 🪖 | `MILITARY` | `MILSERVICE` | Period of active duty in the military. A general situation covering unspecified events. May include enlistment, duty period, deployments, battles, unit assignments or campaigns. |  |
+| 🪖 | `MILITARY` | `MUSTERROLL` | Roster of service members; includes lists like regimental rolls. |  |
+| 🪖 | `MILITARY` | `PENSION` | Record of application for or receipt of military pension. May include eligibility, duration, and amount. |  |
+| 🪖 | `MILITARY` | `PRISONEROFWAR` | Capture or detainment during conflict. |  |
+| 🪖 | `MILITARY` | `PROMOTION` | Advancement in rank, position, or pay grade during military service. Typically based on merit, time served, or vacancy. |  |
+| 🪖 | `MILITARY` | `RANKSTATUS` | A fact of a person’s military role or position (e.g., Lieutenant, General, Field Medic). Use this to capture `ROLE` titles in a `STICKY`. |  |
+| 🪖 | `MILITARY` | `RECRUITMENT` | Event or document related to the process of attracting individuals for voluntary military service. May include advertisements, posters, or oral accounts. |  |
+| 🪖 | `MILITARY` | `SERVICE` | General term for a person’s service record. May overlap with `MILITARYSERVICE`, but used in narrative or informal sources. |  |
+| 🪖 | `MILITARY` | `TRANSFER` | Reassignment within or between military units or locations. |  |
+| 🪖 | `MILITARY` | `UNIT` | Unit affiliation without full muster roll. |  |
+| 🪖 | `MILITARY` | `UNIT-ROLL` | Roster or muster list of a military unit. Useful for establishing presence at a location and role within unit. Like a Muster roll of the 12th Infantry. |  |
+| 🪖 | `MILITARY` | `OTHER` | Any other military-related document or record; must include a `PHRASE`. |  |
+| 🏗️ | `OCCUPATIONAL` | `APPRENTICESHIP` | Training period under a mentor to learn a skilled trade or profession. |  |
+| 🏗️ | `OCCUPATIONAL` | `APPOINTMENT` | Assignment or nomination to an office or post. |  |
+| 🏗️ | `OCCUPATIONAL` | `CERTIFICATION` | Credential earned for a skill or profession (e.g., teaching, trade license, midwife license, guild license). |  |
+| 🏗️ | `OCCUPATIONAL` | `EMPLOYMENT` | Job or career participation. May include contracts, roles, or employer data. |  |
+| 🏗️ | `OCCUPATIONAL` | `FREELANCE` | Independent work engagement (e.g. traveling barber, document writer). |  |
+| 🏗️ | `OCCUPATIONAL` | `GUILD` | Reference to a historical trade or craft guild membership (see also AFFILIATION). |  |
+| 🏗️ | `OCCUPATIONAL` | `LICENSE` | Professional or trade license (e.g., medical, legal, barber). (may overlap with certification |  |
+| 🏗️ | `OCCUPATIONAL` | `OCCUPATION` | Statement or source identifying profession or trade, often as listed in a document. |  |
+| 🏗️ | `OCCUPATIONAL` | `OFFICEHOLDING` | Serving in an official post, especially civic, religious, or guild-related. |  |
+| 🏗️ | `OCCUPATIONAL` | `OFFICEHOLDER` | Role or title in a workplace (e.g. Mayor, Overseer, Bailiff). |  |
+| 🏗️ | `OCCUPATIONAL` | `PARTNERSHIP` | Professional partnership record (e.g. law firm, business co-founder). |  |
+| 🏗️ | `OCCUPATIONAL` | `PENSION` | Retirement benefits record related to a former occupation. |  |
+| 🏗️ | `OCCUPATIONAL` | `RANK` | Job classification, hierarchy level (e.g., foreman, journeyman, master). |  |
+| 🏗️ | `OCCUPATIONAL` | `RESIGNATION` | Resignation or leaving an official or occupational role. |  |
+| 🏗️ | `OCCUPATIONAL` | `RETIREMENT` | Exit from employment due to age or tenure. |  |
+| 🏗️ | `OCCUPATIONAL` | `SERVICEBOOK` | Logbook or document tracking duties, often military or maritime. |  |
+| 🏗️ | `OCCUPATIONAL` | `TAXASSESSMENT` | Property or income tax evaluation. |  |
+| 🏗️ | `OCCUPATIONAL` | `TENURE` | Holding a specific role or job over a period of time. |  |
+| 🏗️ | `OCCUPATIONAL` | `TITLE` | Job title (e.g., Miller, Master Smith, Doctor, Parish Clerk). Use `ROLE` in STICKY to capture the `TITLE` itself. |  |
+| 🏗️ | `OCCUPATIONAL` | `UNION` | Documented labor union membership or activity. |  |
+| 🏗️ | `OCCUPATIONAL` | `WAGE` | Payment records or salary history. |  |
+| 🏗️ | `OCCUPATIONAL` | `WORKPLACE` | Document referencing location of work (e.g. factory, mill, print shop). |  |
+| 🏗️ | `OCCUPATIONAL` | `OTHER` | Any other occupation-related document; must include a `PHRASE`. |  |
+| ☂️ | `PERSONAL` | `ADULTSTATUS` | A fact of reaching adulthood or majority. |  |
+| ☂️ | `PERSONAL` | `BIRTHORDER` | Relative order of birth (e.g., "first son", "third child"). |  |
+| ☂️ | `PERSONAL` | `BIOGRAPHY` | Summary or narrative life account. |  |
+| ☂️ | `PERSONAL` | `CHARACTER` | Notation of moral or social behavior (e.g., "of good character", "troublesome youth"). |  |
+| ☂️ | `PERSONAL` | `FAVORITE` | Individual favored by someone of status (e.g., "King’s Favorite"). |  |
+| ☂️ | `PERSONAL` | `INTERESTS` | Hobbies, passions, or recurring topics mentioned in documents. |  |
+| ☂️ | `PERSONAL` | `LOOKS` | Appearance or traits noted in documents, "Physical appearance" (e.g., scars, height). |  |
+| ☂️ | `PERSONAL` | `REPUTATION` | Social standing, fame, notoriety. |  |
+| ☂️ | `PERSONAL` | `STATUS` | Social position or condition (e.g. illegitimacy, social class, marital status if not covered elsewhere). (or a descriptive label used in source (e.g., "widow") |  |
+| ☂️ | `PERSONAL` | `TITLES` | Honorifics, noble titles, or inherited rank (e.g. Baron, Sir, Countess). use `ROLE` in `STICKY` for title itself. (Also see ` DEATH, WILL`) |  |
+| ☂️ | `PERSONAL` | `WEALTH` | Statement of financial or material condition (e.g. property, fortune, poverty). |  |
+| ☂️ | `PERSONAL` | `OTHER` | Other personal data not listed above; must include a `PHRASE`. |  |
+| 🏘️ | `PROPERTY` | `ACQUISITION` | Gaining ownership through purchase, inheritance, or other means. |  |
+| 🏘️ | `PROPERTY` | `APPRAISAL` | Document assigning monetary value to property or estate. Often used in legal, insurance, or probate contexts. |  |
+| 🏘️ | `PROPERTY` | `AUCTION` | Public sale event for property or goods, typically to the highest bidder. |  |
+| 🏘️ | `PROPERTY` | `BOUNDARYCHANGE` | Legal redrawing or adjustment of property lines, often filed with land or cadastral registers. |  |
+| 🏘️ | `PROPERTY` | `CONFISCATION` | Seizure of property by authority or force. Often without compensation. |  |
+| 🏘️ | `PROPERTY` | `DEED` | Legal document transferring property ownership. |  |
+| 🏘️ | `PROPERTY` | `DONATION` | Transfer of property without compensation; gift or bequest. |  |
+| 🏘️ | `PROPERTY` | `ESTATERECORD` | Document describing contents or value of an estate. May include multiple assets. |  |
+| 🏘️ | `PROPERTY` | `GRANT` | Land or property grant issued by authority (e.g., crown or government). |  |
+| 🏘️ | `PROPERTY` | `INHERITANCE` | Receipt of property or possessions from a deceased person. (Also see ` DEATH, WILL`)  |  |
+| 🏘️ | `PROPERTY` | `INVENTORY` | List of possessions or estate property. May accompany probate or guardianship. |  |
+| 🏘️ | `PROPERTY` | `LANDTRANS` | Legal recording of a land-related change "Land transaction" (e.g., sale, trade, claim). Transaction tied to land rights. |  |
+| 🏘️ | `PROPERTY` | `LEASE` | Temporary granting of use or access to property, usually in exchange for payment. |  |
+| 🏘️ | `PROPERTY` | `LIEN` | Legal claim on property as security for a debt or obligation. |  |
+| 🏘️ | `PROPERTY` | `LOSS` | Property lost due to disaster, war, expropriation, or abandonment. |  |
+| 🏘️ | `PROPERTY` | `MAP` | Map or diagram showing property layout, boundaries, or structures. May accompany land deed or plan. |  |
+| 🏘️ | `PROPERTY` | `MORTGAGE` | Loan secured by property as collateral. Record of lien or obligation. |  |
+| 🏘️ | `PROPERTY` | `OWNERSHIP` | Evidence of ownership without explicit transfer (e.g. tax records). |  |
+| 🏘️ | `PROPERTY` | `PURCHASE` | Buying of land, goods, or other assets. May include price, date, parties involved. |  |
+| 🏘️ | `PROPERTY` | `RECORD` | General-purpose document about property or real estate. Use when no other subtype applies and context is limited. |  |
+| 🏘️ | `PROPERTY` | `RENTAL` | Property rented or leased, not owned. May include terms or occupant info. |  |
+| 🏘️ | `PROPERTY` | `SALE` | Event or document indicating transfer of ownership in exchange for money. |  |
+| 🏘️ | `PROPERTY` | `TRANSFER` | General term for shifting property rights, ownership, or stewardship. Duplicate of LEGAL:TRANSFER, but placed here for easier discovery. |  |
+| 🏘️ | `PROPERTY` | `WARRANTYDEED` | Specific form of deed with legal guarantee of clear title. |  |
+| 🏘️ | `PROPERTY` | `ZONING` | Zoning or land-use designation record. May include permitted uses or restrictions. |  |
+| 🏘️ | `PROPERTY` | `OTHER` | Any other property-related document; must include a `PHRASE`. |  |
+| ✝️ | `RELIGIOUS` | `ADULTBAPT`    | Christian baptism performed on an adult, usually after personal faith declaration. Use PHRASE for detail: [adult baptism, convert, declaration, late baptism, water rite] |  |
+| ✝️ | `RELIGIOUS` | `ANATHEMA`     | Formal ecclesiastical (church-related) condemnation or curse, typically to excommunicate or denounce someone. Use PHRASE for detail: [curse, ban, excommunication, heresy, condemnation, spiritual penalty] |  |
+| ✝️ | `RELIGIOUS` | `BAPTISM`      | Standard Christian rite of spiritual cleansing and entry into the faith, often for infants. See also `CHRISTENING`. Use PHRASE for detail: [infant baptism, sacrament, water blessing, faith entry] |  |
+| ✝️ | `RELIGIOUS` | `BAPTISM_LDS`  | LDS Church baptism performed at age 8 or later by priesthood authority. Use PHRASE for detail: [Mormon baptism, LDS, church ordinance, age 8 rite, convert ritual] |  |
+| ✝️ | `RELIGIOUS` | `BARMITZVAH`   | Jewish coming-of-age ceremony for boys at age 13, marking full religious responsibility. Use PHRASE for detail: [Jewish rite, adulthood, synagogue, Torah reading, male ceremony] |  |
+| ✝️ | `RELIGIOUS` | `BATMITZVAH`   | Jewish coming-of-age ceremony for girls at age 12, signifying religious maturity. Use PHRASE for detail: [Jewish rite, daughter, synagogue, female adulthood, bat mitzvah] |  |
+| ✝️ | `RELIGIOUS` | `BLESSING`     | Formal spiritual or religious invocation of grace, protection, or approval. Use PHRASE for detail: [benediction, favor, invocation, sacred wish, religious approval] |  |
+| ✝️ | `RELIGIOUS` | `BRITMILAH`    | Jewish circumcision ritual for male infants on the eighth day after birth. Use PHRASE for detail: [circumcision, Jewish covenant, mohel, infant rite, bris] |  |
+| ✝️ | `RELIGIOUS` | `CHRISTENING`  | Infant baptism or naming rite in Christian traditions. See also `BAPTISM`. Use PHRASE for detail: [naming, baby blessing, infant baptism, godparent, sacred naming] |  |
+| ✝️ | `RELIGIOUS` | `CIRCUMC`      | Religious or cultural circumcision, often linked to birth or adult conversion. ("Circumcision"). Use PHRASE for detail: [ritual cutting, foreskin, male rite, convert, cultural surgery] |  |
+| ✝️ | `RELIGIOUS` | `CONFIRM`      | Religious rite affirming one's faith, typically after baptism; symbolizes spiritual maturity and personal commitment. Use PHRASE for detail: [confirmation, rite of passage, affirmation, Holy Spirit, church membership] |  |
+| ✝️ | `RELIGIOUS` | `CONL`         | LDS confirmation of church membership following baptism. Use PHRASE for detail: [LDS, laying on of hands, church entry, Mormon rite, confirmation] |  |
+| ✝️ | `RELIGIOUS` | `CONVERSION` | Change of religion or entry into a new faith tradition. May involve adult baptism, public declaration, or vows. Use PHRASE for detail: [convert, change of faith, new religion, religious transition] |  |
+| ✝️ | `RELIGIOUS` | `DECLARATION`  | Public affirmation of faith or religious status, often before a rite like baptism or confirmation. Use PHRASE for detail: [faith statement, belief declaration, spiritual vow, verbal affirmation, creed] |  |
+| ✝️ | `RELIGIOUS` | `ENDOWMENT`    | LDS temple ceremony granting spiritual knowledge, covenants, and blessings. Use PHRASE for detail: [LDS rite, Mormon temple, spiritual gift, sacred knowledge, priesthood covenant] |  |
+| ✝️ | `RELIGIOUS` | `ENTRY` | Entry into a religious institution, such as a monastery, convent, or seminary. May include initial vows or commitment to religious formation. Use PHRASE for detail: [monastery, seminary, convent, religious life, postulant, entry ceremony, vows] |  |
+| ✝️ | `RELIGIOUS` | `EXCOMMUN`     | Formal removal or exclusion from a religious community. Use PHRASE for detail: [ban, exclusion, excommunication, excision, censure, rejection, church penalty, expulsion] |  |
+| ✝️ | `RELIGIOUS` | `FIRSTCOM`     | First communion: Catholic rite of receiving the Eucharist for the first time, usually in childhood. Use PHRASE for detail: [Eucharist, Holy Communion, Catholic rite, child sacrament, mass] |  |
+| ✝️ | `RELIGIOUS` | `HAJJ`         | Islamic pilgrimage to Mecca, required once in a lifetime for able Muslims. Use PHRASE for detail: [Mecca, pilgrimage, Five Pillars, sacred journey, Islam] |  |
+| ✝️ | `RELIGIOUS` | `INIL`         | LDS initiatory ordinance performed in temples; preparation for further rites. Use PHRASE for detail: [LDS initiation, anointing, Mormon temple, ordinance, washing] |  |
+| ✝️ | `RELIGIOUS` | `KIDDUSHIN`    | First stage of a traditional Jewish wedding, involving legal betrothal. Use PHRASE for detail: [Jewish marriage, engagement, betrothal, ketubah, contract] | ENGA |
+| ✝️ | `RELIGIOUS` | `LASTRITES`    | Catholic sacrament before death, including confession, anointing, and Eucharist. Use PHRASE for detail: [dying rite, anointing, viaticum, Catholic, final sacrament] |  |
+| ✝️ | `RELIGIOUS` | `MISSION`      | Assignment or period of religious service, often evangelical or aid-based. Use PHRASE for detail: [missionary, religious service, outreach, evangelism, deployment] |  |
+| ✝️ | `RELIGIOUS` | `MONMOVE`    | Transfer of a monk or nun between monastic institutions or orders. Use PHRASE for detail: [convent move, monastic transfer, reassignment, cloister change, abbey shift] |  |
+| ✝️ | `RELIGIOUS` | `NISSUIN`      | Second part of a Jewish wedding ceremony, focused on consummation and shared home. Use PHRASE for detail: [Jewish marriage, canopy, chuppah, home blessing, union] |  |
+| ✝️ | `RELIGIOUS` | `OBSERVANCE`    | Participation in a religious event, ritual, or holy day. Use PHRASE for detail: [holy day, feast, sabbath, ritual, participation] |  |
+| ✝️ | `RELIGIOUS` | `ORDINATION`    | Ceremony conferring spiritual office (e.g., priest, rabbi, imam). Use PHRASE for detail: [clergy, spiritual authority, religious title, ordain, investiture] |  |
+| ✝️ | `RELIGIOUS` | `PILGRIMAGE`    | Sacred journey to a religious site or destination. Use PHRASE for detail: [pilgrim, sacred travel, holy place, devotion journey, shrine visit] |  |
+| ✝️ | `RELIGIOUS` | `REASSIGNMENT`  | Change of religious office or transfer of clerical duties. Use PHRASE for detail: [clergy move, new post, parish shift, office change, appointment] |  |
+| ✝️ | `RELIGIOUS` | `RECONV`        | Reconversion: re-adopting a previous faith after leaving it. Use PHRASE for detail: [return to faith, religious renewal, reconvert, rejoin religion] |  |
+| ✝️ | `RELIGIOUS` | `RELIGION`      | Declaration or registration of religious affiliation. Use PHRASE for detail: [faith, belief, religious status, religion stated, change of belief] |  |
+| ✝️ | `RELIGIOUS` | `ORDER`         | Joining a religious order or congregation. Use PHRASE for detail: [convent, brotherhood, nunnery, society, vows] |  |
+| ✝️ | `RELIGIOUS` | `RENOUNCE`      | Formal rejection or departure from a religion. Use PHRASE for detail: [leave faith, withdraw, religious resignation, reject belief, renunciation, apostasy] |  |
+| ✝️ | `RELIGIOUS` | `RETREAT`       | Period of spiritual reflection, often in isolation. Use PHRASE for detail: [sabbatical, prayer retreat, silent stay, meditative period, cloister] |  |
+| ✝️ | `RELIGIOUS` | `SACRAMENTAL`   | Receiving a sacrament not separately listed (e.g., anointing, confession). Use PHRASE for detail: [rite, Catholic sacrament, spiritual act, blessing] |  |
+| ✝️ | `RELIGIOUS` | `SEALING`       | LDS ordinance binding family members for eternity. Use PHRASE for detail: [eternal marriage, LDS temple, family sealing, spiritual bond] |  |
+| ✝️ | `RELIGIOUS` | `SEPARATION`    | Leaving or removal from a religious group, voluntary or not. Use PHRASE for detail: [expulsion, resignation, departure, removal from congregation] |  |
+| ✝️ | `RELIGIOUS` | `SHUNNING`      | Social or religious ostracism, especially without formal excommunication. Use PHRASE for detail: [exile, avoidance, exclusion, anabaptist, Amish] |  |
+| ✝️ | `RELIGIOUS` | `SPIRITCALL`    | Recognition of a perceived divine calling or mission. Use PHRASE for detail: [vocation, divine summons, spiritual mission, spiritual calling, call to service] |  |
+| ✝️ | `RELIGIOUS` | `VOWS`          | Formal sacred vows such as chastity, poverty, or obedience. Use PHRASE for detail: [religious promise, oath, commitment, monastery, celibacy] |  |
+| ✝️ | `RELIGIOUS` | `OTHER`         | Any religious event not covered by other entries; must use PHRASE. Use PHRASE for detail: [custom, rare rite, local tradition, undefined religious act] |  |
+| ⚓ | `RESIDENCE` | `ADDRESS` | Document explicitly listing an individual’s residence; e.g. ID card, driver’s license, or utility bill. |  |
+| ⚓ | `RESIDENCE` | `CENSUSOTHER` | Residence-based census not falling under household or tax types; e.g. lodging census, institutional census. | CENS |
+| ⚓ | `RESIDENCE` | `DOMICILIECENSUS` | Older or regional term for place-based listing; e.g. French "recensement de domicile" showing household occupancy. | CENS |
+| ⚓ | `RESIDENCE` | `DWELLINGCERT` | Official certificate confirming where a person lives; e.g. municipal residence proof, "Wohnsitzbescheinigung". |  |
+| ⚓ | `RESIDENCE` | `FARM-OCCU` | Farm residency register; e.g. Scandinavian husmann lists or tenant farmer records. |  |
+| ⚓ | `RESIDENCE` | `HOUSINGLIST` | Urban housing or rental occupancy listing; e.g. Amsterdam housing ledger or rent control rosters. |  |
+| ⚓ | `RESIDENCE` | `HOUSEHOLDREG` | Record showing residents at a specific address, often over time; e.g. Swedish “husförhörslängd”, Dutch "Bevolkingsregister". (Household register) |  |
+| ⚓ | `RESIDENCE` | `MILCENSUS` | (MILITARYCENSUS) Enrollment lists tied to place of residence for conscription; e.g. draft boards, military eligibility censuses. | CENS |
+| ⚓ | `RESIDENCE` | `POPCENSUS` | (POPULATIONCENSUS) General household or population census; e.g. U.S. Federal Census, UK census returns. | CENS |
+| ⚓ | `RESIDENCE` | `REGISTRATION` | Government or institutional registry of residence; e.g. Anmeldung in Germany, civil residence registry. |  |
+| ⚓ | `RESIDENCE` | `TAXCENSUS` | Census used for tax purposes including residence data; e.g. hearth tax lists, poll tax registers. | CENS |
+| ⚓ | `RESIDENCE` | `OTHER` | Any other residence-related record not listed above; must include a PHRASE. |  |
+| 📚 | `SECONDARY` | `ADOPT-FOSTER`   | Adoption or fostering customs — informal, cultural, or undocumented practices. |  |
+| 📚 | `SECONDARY` | `BLOODTYPE`      | Reported or assumed blood type used in family context or paternity speculation. |  |
+| 📚 | `SECONDARY` | `DNATEST`        | Unverified DNA test results, notes, or discussions, including home kits or shared interpretations. |  |
+| 📚 | `SECONDARY` | `FAMILYBIBLE` | A family Bible used as a multigenerational record of births, marriages, and deaths — often handwritten by relatives. May include marginal notes about migrations, household members (e.g. servants), land ownership, heirlooms, or religious customs. Treated as a secondary source. |  |
+| 📚 | `SECONDARY` | `FARM-LAND`      | Usage patterns of farmland passed within families — noted through tradition, not deed. |  |
+| 📚 | `SECONDARY` | `HEIRLOOMS`      | Family items with historical significance — clocks, rings, etc. — identified via memory or tradition. |  |
+| 📚 | `SECONDARY` | `HISTORY-LORE`   | Portraits or items attributed by family tradition or oral story, not documented evidence. |  |
+| 📚 | `SECONDARY` | `HOUSE`          | Residence continuity across generations — identified through habit, not official record. |  |
+| 📚 | `SECONDARY` | `INHERITANCE`    | Traditional craft or occupational inheritance — passed generationally, not certified. |  |
+| 📚 | `SECONDARY` | `JEWELRY`        | Jewelry identified as significant by engraving or memory — e.g., family crest ring. |  |
+| 📚 | `SECONDARY` | `LANG-DIALECT`   | Regional language or dialect retention, used as cultural or genealogical clue. |  |
+| 📚 | `SECONDARY` | `LORE`           | General cultural or familial traditions that influence understanding of ancestry. |  |
+| 📚 | `SECONDARY` | `MARR-TRADITIONS`| Customs such as cousin marriage, dowry, or bride price — preserved orally. |  |
+| 📚 | `SECONDARY` | `MEDICALTRAITS`  | Shared inherited traits or conditions mentioned in family context. |  |
+| 📚 | `SECONDARY` | `NAMING`         | Naming conventions across generations (e.g., patronymics, suffixes, repeated names). |  |
+| 📚 | `SECONDARY` | `NICKNAMES`      | Inherited or family-based nicknames that serve as alternate identifiers. |  |
+| 📚 | `SECONDARY` | `PATTERNS`       | Migration, religious, or social patterns inferred from broader community behavior. |  |
+| 📚 | `SECONDARY` | `SONG-TOTEM`     | Clan-specific songs, totems, or symbolic items passed through memory. |  |
+| 📚 | `SECONDARY` | `STORIES`        | Family stories or narratives about people, places, or events — not directly evidenced. |  |
+| 📚 | `SECONDARY` | `TATTOO`         | Cultural or generational tattoo practices referenced in oral or visual tradition. |  |
+| 📚 | `SECONDARY` | `TRACES`         | Online artifacts (photos, social media, blogs) that inform family history without certification. |  |
+| 🌐 | `SOCIAL` | `ACCIDENT` | Documented incident causing injury, damage, or death — often public or recorded for insurance/legal/social purposes. |  |
+| 🌐 | `SOCIAL` | `AWARD` | A non-military award or recognition received. Examples: civic medals, academic honors, public commendations. |  |
+| 🌐 | `SOCIAL` | `COMMUNITYSERVICE` | Involvement in community or volunteer service. Sometimes documented in local newsletters or recognition forms. |  |
+| 🌐 | `SOCIAL` | `GIFT` | Uncompensated transfer of item, land, or benefit. Can include ceremonial or formal gift-giving. |  |
+| 🌐 | `SOCIAL` | `GUESTBOOK` | Signed presence in an event guestbook. May include location, occasion, and date. |  |
+| 🌐 | `SOCIAL` | `INITIATION` | Entry into a social club, order, or association. Often tied to rituals or certificates. |  |
+| 🌐 | `SOCIAL` | `MEETING` | Participation in a public or organizational meeting. May be recorded in minutes or attendance rolls. |  |
+| 🌐 | `SOCIAL` | `PARTY` | Documented social gathering, such as invitations, event photos, or commemorative cards. |  |
+| 🌐 | `SOCIAL` | `RECEPTION` | Public or ceremonial reception event. Often follows weddings, retirements, or promotions. |  |
+| 🌐 | `SOCIAL` | `REUNION` | Event bringing together family, veterans, alumni, or communities. Frequently documented. |  |
+| 🌐 | `SOCIAL` | `SOCIALSTATUS` | Declared social standing or role (e.g., nobility, caste membership). Sometimes appears in formal listings. |  |
+| 🌐 | `SOCIAL` | `SPONSORING` | Supportive role in social or religious context (e.g., godparent, witness). May be listed in event records. |  |
+| 🌐 | `SOCIAL` | `TRAGEDY` | Record of disasters, crimes, or public accidents involving the person. Examples: arson reports, public mourning, disaster registries. |  |
+| 🌐 | `SOCIAL` | `OTHER` | Any other social-related record not listed above; must include a `PHRASE`. |  |
+| 🌈 | `STATUSCHANGE` | `AMNESTY` | Official pardon for people convicted of political or civil offenses. Legal absolution. |  |
+| 🌈 | `STATUSCHANGE` | `DEMOTION` | Loss of rank or formal downgrade in position, often occupational or military. |  |
+| 🌈 | `STATUSCHANGE` | `ELECTED` | Appointment via public or official vote to a role or office. |  |
+| 🌈 | `STATUSCHANGE` | `EMANCIPATION` | Legal freedom from parental or guardianship control. Often marks adulthood or independence. |  |
+| 🌈 | `STATUSCHANGE` | `ENSLAVEMENT` | Formal record or recognition of being enslaved. Includes purchase, sale, or status documentation. |  |
+| 🌈 | `STATUSCHANGE` | `EXCOMMUNICATION` | Formal religious expulsion or loss of group standing. May involve public or clerical declaration. |  |
+| 🌈 | `STATUSCHANGE` | `GENDERCHANGE` | Transition of gender identity. May include legal, medical, or social recognition. |  |
+| 🌈 | `STATUSCHANGE` | `GRADUATION` | Completion of an academic program or degree conferral. Can mark social or career status change. |  |
+| 🌈 | `STATUSCHANGE` | `IMPRISONMENT` | Period of incarceration. Legal detainment by judicial or political authority. |  |
+| 🌈 | `STATUSCHANGE` | `INDUCTION` | Official entry into a recognized role, group, or service. May involve oath, ceremony, or legal act. |  |
+| 🌈 | `STATUSCHANGE` | `MANUMISSION` | Release from slavery. Granting of freedom through official decree or document. |  |
+| 🌈 | `STATUSCHANGE` | `MIL_DISCHARGE` | Completion or termination of military service. May be honorable, dishonorable, or other. |  |
+| 🌈 | `STATUSCHANGE` | `MIL_INDUCTION` | Entry into military via official process or draft. Beginning of service. |  |
+| 🌈 | `STATUSCHANGE` | `NAMECHANGE` | Legal or official change of personal name. May involve court record or announcement. |  |
+| 🌈 | `STATUSCHANGE` | `NATURALIZATION` | Legal acquisition of new citizenship or nationality. May include renunciation of former. |  |
+| 🌈 | `STATUSCHANGE` | `ORDINATION` | Formal recognition as religious leader or clergy. Typically follows training or calling. |  |
+| 🌈 | `STATUSCHANGE` | `PROMOTION` | Advancement in rank, position, or title. Often used in military, government, or clergy. |  |
+| 🌈 | `STATUSCHANGE` | `RESIGNATION` | Voluntary departure from official position or membership. Can include letter or formal notice. |  |
+| 🌈 | `STATUSCHANGE` | `RETIREMENT` | Withdrawal from occupation or role, often due to age or service completion. |  |
+| 🌈 | `STATUSCHANGE` | `TITLEOFNOBILITY` | Recognition or grant of a noble title. Use STICKY `ROLE` to indicate title specifics (e.g., Baron, Countess). (Also see ` DEATH, WILL`) |  |
+| 🌈 | `STATUSCHANGE` | `OTHER` | Any other personal status-shift not listed here; must include a `PHRASE`. |  |
+| 🌀 | `OTHER`        | `OTHER` | Any other category not listed here; must include a `PHRASE`. |  |
+
+- Each `SUBTYPE` is only valid in combination with the `TYPE` shown in the left column. You may not use a `SUBTYPE` under a different `TYPE` unless explicitly allowed. The `OTHER` value under each type provides an escape hatch for non-standard subtypes; it must always be accompanied by a `PHRASE`.
+
+- Although censuses capture a wide range of personal data, they are categorized under `RESIDENCE` because their core organizing principle is the enumeration of individuals at a particular place and time.
+
+- `TYPE`and `SUBTYPE` work together, and must be written on one and the same line, separated by ", ".
+
+- Subtypes are intended to assist in organizing and interpreting source documents more accurately. The set is open-ended; implementations may extend it using `OTHER` when a more specific match is unavailable. In that case a  `PHRASE` must be included.
+
+:::example  
+How to use `OTHER` for a non mentioned `PROPERTY`:
+```gedstruct
+0 @T0093@ TEMPLATE
+1 TYPE PROPERTY, OTHER, "This is some other Property."
+```
+- Instead of `PROPERTY` any other of the above mentioned `TYPE`s can be used.
+- When using `OTHER` there must always be a `PHRASE` to further specify.   
+:::
+
+
diff --git a/specification/gedcom-3-structures-4-enumerations-roles.md b/specification/gedcom-3-structures-4-enumerations-roles.md
new file mode 100644
index 00000000..4f5b18ec
--- /dev/null
+++ b/specification/gedcom-3-structures-4-enumerations-roles.md
@@ -0,0 +1,451 @@
+
+
+### `g8:enumset-STICKY-MAINROLE`
+
+There is a `STICKY-MAINROLE` table and a `STICKY_ROLE` table. That is only done to be able to divide the `STICKY-ROLE` table in **"bite-sized chunks"**. So we can more easily see what `ROLE`'s we can choose from.   
+As for a `ROLE`-tag inside a `STICKY` we only put **1 or more `ROLE`'s from the `STICKY-ROLE` table**, after the `SUBROLE` tag.  
+We dont put values from the `STICKY-MAINROLE` table after the `ROLE` tag in a `STICKY`! So we **never** put a `STICKY-MAINROLE` there.
+
+This table describes the high-level category of function or relationship this `STICKY` had in the context of the `TEMPLATE`. Roles describe a person's or entity's involvement in a given event or situation, and determine what kind of roles are valid.
+
+| ICO | MAINROLE     | Description                                                                |
+|-----| ------------ | ----------------------------------------------------------------------- |
+| 🗂️ | `ADMIN`      | Person acted in an administrative or bureaucratic role (e.g. official, clerk, registrar, census). |
+| 🧱 | `ASSET`      | Person or Asset who/that was connected to the possession, transfer, or status of a non-human entity (e.g., land, object). |
+| 👶 | `BIRTH`      | Person was born or played a key role in a birth event. (child, parent, midwife)|
+| 🏢 | `CORPORATION`| Person was involved in an institution (e.g. school, guild, company). |
+| 🔁 | `CROSSROLE`  | Role applicable in multiple contexts (e.g., witness, guardian). |
+| ⚰️ | `DEATH`      | Person died or had a role in the context of death (e.g. deceased, undertaker, mourner). |
+| 🧬 | `DNA`        | Roles related to genetic testing in analysis labs or research programs, genealogical matching, lab processing, and interpretation of DNA test results. Includes both professional and familial participation  — with focus on identity, inheritance, and kinship confirmation. |
+| 📚 | `EDUCATIONAL`| Person acted in an educational setting (e.g. teacher, student, examiner). |
+| 🗓️ | `EVENT`      | Person participated in a general event (e.g. spectator, officiant). |
+| 👨‍👩‍👧 | `FAMILY`     | Role defines kinship or household relationship. (parent, child, spouse) |
+| 🛡️ | `GROUP`      | Role in a collective or institutional context (e.g. tribe, church, farm, guild). |
+| 🪪 | `IDENTITY`   | Roles associated with formal or legal identification (e.g. renamed, declared), such as declared identity, proven relationships, or official recognitions. Includes DNA-based identity roles such as matched individual or inferred parent. |
+| 📜 | `INHERITANCE`| Person was involved in inheritance or estate transfer. |
+| ⚖️ | `JUDICIAL`   | Role in legal or courtroom setting. (judge, magistrate, court officer, plaintiff) |
+| 🖋️ | `LEGAL`      | Role in legal matters outside court (e.g., agent, claimant, notary, lawyer). |
+| 💍 | `MARRIAGE`   | Person participated in a marriage or similar union. |
+| 🎞️ | `MEDIA`      | Person involved in creation, subject, or handling of media (e.g., author, illustrator, subject). |
+| 🩺 | `MEDICAL`    | Roles related to medical, clinical, or biological activities, including examination, treatment, testing, and sample collection. Includes roles related to DNA testing, sample handling, or biological analysis. |
+| 🪖 | `MILITARY`   | Person served in or was affected by military service. (soldier, officer, commander, or veteran) |
+| 📜 | `OFFICIAL`   | Government or civic ceremonial role (e.g., mayor, consul). |
+| 🏘️ | `PROPERTY`   | Person held or transferred ownership, use, or involvement in real estate. |
+| ✝️ | `RELIGIOUS`  | Person participated in or officiated religious rites. (priest, nun, initiate) |
+| 🌐 | `SOCIAL`     | Participant in social events, ceremonies, or symbolic roles. |
+| 🌀 | `OTHER`      | Everything that does not fit a standard category; must include a `PHRASE`. |
+
+### `g8:enumset-STICKY-ROLE`
+
+This table defines all standardized combinations of `MAINROLE` and `ROLE` used in the `STICKY` structure. Each row represents a unique pairing allowed in the model. The third column explains the usage context and includes examples where relevant. Categories are alphabetized by `ROLE` and `SUBROLE`. Use this as a master reference or pruning sheet.
+
+| ICO | MAINROLE      | ROLE              | Description (with examples) |
+|---|---------------|-------------------|-----------------------------|
+| 🗂️ | `ADMIN`       | `ARCHIVIST`       | Keeper of records  |
+| 🗂️ | `ADMIN`       | `BUREAUCRAT`      | Managed procedural or governmental duties  |
+| 🗂️ | `ADMIN`       | `CHART`           | Diagram or tabular record used for tracking, planning, or reporting. Use PHRASE for detail: [chart type, purpose, date] |
+| 🗂️ | `ADMIN`       | `CONSUL`          | Held a state or municipal office with civic duties    |
+| 🗂️ | `ADMIN`       | `ENUMARATOR`      | An enumerator is an official data recorder — usually employed by a state, church, or institution to record households or individuals |
+| 🗂️ | `ADMIN`       | `INSPECTOR`       | Government or institutional inspector, e.g., for emigration or public health.  |
+| 🗂️ | `ADMIN`       | `INVENTORYM`      | INVENTORYMAKER — Compiles asset list (also appears in legal) |
+| 🗂️ | `ADMIN`       | `ISSUER`          | Person officially authorized to issue a certificate, license, or document. Often |overlaps with registrar. |
+| 🗂️ | `ADMIN`       | `LEDGER`          | Book or record of accounts, transactions, or inventories. Use PHRASE for detail: [ledger type, date range, archive] |
+| 🗂️ | `ADMIN`       | `MAP`             | Cartographic representation of a location or area. Use PHRASE for detail: [map type, date, creator] |
+| 🗂️ | `ADMIN`       | `MESSENGER`       | Courier or person delivering                            |
+| 🗂️ | `ADMIN`       | `RECIPIENT`       | Person formally receiving an object, credential, or authorization — such as a passport, certificate, permit, or official document. Use when granted something in an administrative or governmental context. |
+| 🗂️ | `ADMIN`       | `REGISTER`       | Official or historical register listing people, events, or items. Use PHRASE for detail: [register type, date range, archive] |
+| 🗂️ | `ADMIN`       | `ROLL`            | Historical roll (e.g., tax roll, muster roll). Use PHRASE for detail: [roll type, date, jurisdiction] |
+| 🗂️ | `ADMIN`       | `SITE`| General-purpose administrative or bureaucratic workplace.<br>Use PHRASE for detail: [office, registry, administration wing, civil desk, records department] |
+| 🗂️ | `ADMIN`       | `TRANSCRIBER`     | Enters information  |
+| 🗂️ | `ADMIN`       | `VERIFIER`        | Verifies document authenticity  |
+| 🧱 | `ASSET`       | `ASSIGNEE`        | Assigned asset  |
+| 🧱 | `ASSET`       | `AUCTION`         | Asset offered for sale via auction (e.g. toolset or furniture in probate)  |
+| 🧱 | `ASSET`       | `AWARD`           | Prize or honor, given in recognition or as a prize. Use PHRASE for detail: [medal, certificate, award name, event, date]  |
+| 🧱 | `ASSET`       | `BENEFICIARY`     | Legal or named recipient of an object, particularly in the context of a will or deed. |
+| 🧱 | `ASSET`       | `BEQUEST`         | Asset being inherited through a will or succession document   |
+| 🧱 | `ASSET`       | `CERTIFICATE`     | Asset representing the document itself.  |
+| 🧱 | `ASSET`       | `COLLATERAL`      | Asset pledged as security for a loan or legal agreement (e.g. land in a bond)  |
+| 🧱 | `ASSET`       | `CREATOR`         | Original maker or fabricator of the item (e.g., artisan who crafted the medal). |
+| 🧱 | `ASSET`       | `DONOR`           | Person who gives or gifts the item voluntarily. |
+| 🧱 | `ASSET`       | `GIFT`            | Asset being donated or given or ceremonially transferred(e.g. a cow given to a daughter on marriage) |
+| 🧱 | `ASSET`       | `HOLDER`          | Person who was the **recipient**, **bearer**, or **user** of an item such as a passport, license, or medal. Includes **legal**, **formal**, or **official** document reception. Posession can be pemanent or temporarely. |
+| 🧱 | `ASSET`       | `ISSUER`          | Person (or organization) who created, issued, awarded, or granted the item. Often official or institutional. (e.g., organization issuing a medal, license, passport, testresult)|
+| 🧱 | `ASSET`       | `ITEM`            | Catch-all for miscellaneous movable assets (e.g. book, cart, sword) |
+| 🧱 | `ASSET`       | `LISTED`          | Mentioned in a record but not transferred, often for valuation or record (e.g. farm in a will) |
+| 🧱 | `ASSET`       | `LOT`             | Grouped or undivided set of items treated as a unit (e.g. “lot of 6 chairs”) |
+| 🧱 | `ASSET`       | `OTHER`           | Catch-all; must clarify with `PHRASE`  |
+| 🧱 | `ASSET`       | `PROPERTY`        | General asset (real estate or fixed structure) being transferred between parties (e.g. house, land parcel) |
+| 🧱 | `ASSET`       | `RECIPIENT`       | Person receiving the asset.   |
+| 🧱 | `ASSET`       | `REPAIRER`        | Person tasked with maintaining or restoring the object. |
+| 🧱 | `ASSET`       | `STOCKRENTAL`     | Asset temporarily assigned or rented (e.g. oxen or horse or cart lent for a season) |
+| 🧱 | `ASSET`       | `USER`            | Individual actively using the item (e.g., someone operating a machine or using a passport). |
+| 🧱 | `ASSET`       | `WITNESS`         | Person who observed or certified the object’s issuance, transfer, or destruction. |
+| 👶 | `BIRTH`       | `CHILD`           | Child being born    |
+| 👶 | `BIRTH`       | `DOULA`           | Provided non-medical support to the mother during labor, birth, and early postpartum. Focused on emotional, physical, and informational care. |
+| 👶 | `BIRTH`       | `FATHER`          | Biological father    |
+| 👶 | `BIRTH`       | `MATERNITY-AST`   | (maternity assistant) Assisted with newborn care, mother recovery, household support during NL-"kraamtijd" (postnatal period). |
+| 👶 | `BIRTH`       | `MIDWIFE`         | Midwife or person assisting at birth   |
+| 👶 | `BIRTH`       | `MULTIPLE`        | A sibling from the same pregnancy (twin, triplet, quadruplet, and so on). A PHRASE can be used to specify the kind of multiple birt|
+| 👶 | `BIRTH`       | `MOTHER`          | Biological mother   |
+| 👶 | `BIRTH`       | `SITE`| Location where the birth occurred (indoors or outdoors).<br>Use PHRASE for detail: [maternity ward, midwife house, roadside, ship] |
+| 👶 | `BIRTH`       | `WITNESS`         | Legal or informal witness to the birth    |
+| 🏢 | `CORPORATION` | `ASSOCIATED`      | Linked but unclear role    |
+| 🏢 | `CORPORATION` | `BONDHOLDER`      | person owning a bond or bonds issued by a government or a public company |
+| 🏢 | `CORPORATION` | `CLIENT`          | Organization receiving goods or services from another party. Use PHRASE for detail: [service/product, provider, date] |
+| 🏢 | `CORPORATION` | `CONTRACTOR`      | Organization engaged to perform a service or project. Use PHRASE for detail: [project type, client, location] |
+| 🏢 | `CORPORATION` | `EMPLOYEE`        | Works for the institution     |
+| 🏢 | `CORPORATION` | `EMPLOYER`        | Entity that offers jobs and compensates individuals for their work with salary or wages. Also offering a workplace and often "tools" to work withand sometimes health insurance and retirement plans. Use `PHRASE` for detail [boss, manager, patron, director, principal, president, proprietor, chief, executive, supervisor, foreman, master, leader]|
+| 🏢 | `CORPORATION` | `EXPELLED`        | Forced removal or banishment     |
+| 🏢 | `CORPORATION` | `FOUNDER`         | Person who initiated or created the institution     |
+| 🏢 | `CORPORATION` | `ISERVANT`        | Indentured person: legally bound to work for another, for a fixed period, in exchange for passage to a new country, payment of a debt, or training in a trade  |
+| 🏢 | `CORPORATION` | `JOINED`          | Entry into the group or institution |
+| 🏢 | `CORPORATION` | `LEADER`          | Official or informal leader    |
+| 🏢 | `CORPORATION` | `LEFT`            | Voluntary or general departure |
+| 🏢 | `CORPORATION` | `LICENSOR`        | Organization granting rights to use something (e.g., software, patent). Use PHRASE for detail: [licensed item, jurisdiction, term] |
+| 🏢 | `CORPORATION` | `LICENSEE`        | Organization receiving rights under a license agreement. Use PHRASE for detail: [licensed item, licensor, jurisdiction] |
+| 🏢 | `CORPORATION` | `MANUFACTURER`    | Organization producing goods or products. Use PHRASE for detail: [product type, brand, facility location] |
+| 🏢 | `CORPORATION` | `MEMBER`          | Person belongs to group (school, club, church, etc.)     |
+| 🏢 | `CORPORATION` | `PARTNER`         | Organization collaborating in a joint venture or partnership. Use PHRASE for detail: [partner name, project, date] |
+| 🏢 | `CORPORATION` | `PUBLISHER`       | Entity releasing books, newspapers, maps, or other published materials. Use PHRASE for detail: [publication name, medium, date range] |
+| 🏢 | `CORPORATION` | `RETIRED`         | Ceased formal role due to age or tenure      |
+| 🏢 | `CORPORATION` | `SITE`| Workplace or professional facility connected to the organization.<br>Use PHRASE for detail: [factory, headquarters, lab, facility, warehouse, shop] |
+| 🏢 | `CORPORATION` | `SPONSOR`         | Organization providing financial or resource support. Use PHRASE for detail: [sponsored event, amount/type, date] |
+| 🏢 | `CORPORATION` | `STUDENT`         | Learns or trains there      |
+| 🏢 | `CORPORATION` | `SUPPLIER`        | Organization providing materials or goods to others. Use PHRASE for detail: [materials supplied, client type, delivery region] |
+| 🏢 | `CORPORATION` | `TRANSFERRED`     | Moved from one institution to another (e.g., schools, prisons)      |
+| 🏢 | `CORPORATION` | `VENDOR`          | Entity selling goods or services, often in a retail context. Use PHRASE for detail: [goods/service type, sales method, location] |
+| 🔁 | `CROSSROLE`   | `ADVOCATE`        | Spoke or acted on behalf of another in multiple contexts |
+| 🔁 | `CROSSROLE`   | `BENEFACTOR`      | Donated or supported across legal, asset, or social settings |
+| 🔁 | `CROSSROLE`   | `FRIEND`          | Social companion, friend, often mentioned in wills, letters, etc. |
+| 🔁 | `CROSSROLE`   | `GUARDIAN`        | Person acting in a protective or decision-making role for another (e.g., legal guardian, sponsor). May appear in both legal and informal settings. Person also took legal/parental responsibility in inheritance, custody, etc. |
+| 🔁 | `CROSSROLE`   | `HEALER`          | Provided healing across religious, medical, or folk contexts. |
+| 🔁 | `CROSSROLE`   | `INTERPRETER`     | Provided translation or language assistance during testimony, legal process, or religious rite. |
+| 🔁 | `CROSSROLE`   | `JUDGE`           | May appear in both legal and group contexts; adjudicated disputes |
+| 🔁 | `CROSSROLE`   | `MAIN`            | Primary person of the event; not specific to event type |
+| 🔁 | `CROSSROLE`   | `NEIGHBOUR`       | Nearby resident; often witness, helper, or informant |
+| 🔁 | `CROSSROLE`   | `OBSERVER`        | Passive witness to an event, without formal testimony. Often included for context or reporting. |
+| 🔁 | `CROSSROLE`   | `OWNER`           | Owner of land, a property or otherwise |
+| 🔁 | `CROSSROLE`   | `SITE`| General site, location, locus, origin or scene when no specific mainrole applies.<br>Use PHRASE for detail: [cemetery, cave, hill, bridge, crossroads, villa, castle, embassy, station, mansion, outdoors] |
+| 🔁 | `CROSSROLE`   | `TESTATOR`        | Wrote or signed a will; usually a deceased individual |
+| 🔁 | `CROSSROLE`   | `TRUSTEE`         | Appointed to manage property/assets for others |
+| 🔁 | `CROSSROLE`   | `WORKER`          | Generic laborer; unclear if military, farm, domestic, etc. |
+| 🔁 | `CROSSROLE`   | `WITNESS`         | Saw or verified an act across many domains |
+| ⚰️ | `DEATH`       | `BURIAL_OFFICIANT`| Clergy or person leading burial rituals  |
+| ⚰️ | `DEATH`       | `CREMATION`       | Process of disposing of a deceased person's body by burning it   |
+| ⚰️ | `DEATH`       | `DECEASED`        | Person who died   |
+| ⚰️ | `DEATH`       | `DECEDENT`        | Person who died (official twerminology)  |
+| ⚰️ | `DEATH`       | `FUNERAL`         | A ceremony held in remembrance of a deceased person, typically involving a gathering of family and friend |
+| ⚰️ | `DEATH`       | `INFORMANT`       | Person who reported the death  |
+| ⚰️ | `DEATH`       | `NOTICE`          | Notice of death  |
+| ⚰️ | `DEATH`       | `OBITUARY`        | Notice of death.  |
+| ⚰️ | `DEATH`       | `PALLBEARER`      | A person who helps carry the casket at a funeral.   |
+| ⚰️ | `DEATH`       | `SITE`| Place of death; can include institution, home, or natural setting.<br>Use PHRASE for detail: [hospice, roadside, forest, sea] |
+| ⚰️ | `DEATH`       | `WITNESS`         | Person present at death  |
+| 🧬 | `DNA`         | `ANALYST`     | Trained technician or geneticist, staff or forensic worker comparing DNA profiles or evaluating result reliability, or performing or supervising the analysis. |
+| 🧬 | `DNA`         | `COLLECTOR`   | Staff or person who physically collected or registered the DNA sample (e.g., nurse, lab aide, swab taker, medical staff). |
+| 🧬 | `DNA`         | `EXPLAINER`   | Person (interpreter) who explained or translated DNA results to others (e.g., family member, caseworker). |
+| 🧬 | `DNA`         | `GENETICIST`  | Certified specialist who reviewed, confirmed, or interpreted the DNA results. |
+| 🧬 | `DNA`         | `KITOWNER`    | Registered owner or account holder of the DNA test kit, possibly different from the test subject. |
+| 🧬 | `DNA`         | `LABTECH`  | Laboratory or technical worker responsible for processing or validating the DNA sample. |
+| 🧬 | `DNA`         | `MATCH`       | Individual whose genetic material matched the subject’s, either fully or partially. (e.g. relative match, segment overlap) |
+| 🧬 | `DNA`         | `PARENTAL`    | Biological parent, ancestor or presumed biological contributor, confirmed through DNA evidence (e.g. paternity test). |
+| 🧬 | `DNA`         | `SITE`| Location connected to testing, analysis, or reporting of DNA.<br>Use PHRASE for detail: [lab, laboratory, testing center, facility, analysis center, clinic] |
+| 🧬 | `DNA`         | `SPONSOR`     | Person or organization that funded or facilitated the DNA test. (e.g. gift, project, third-party study) |
+| 🧬 | `DNA`         | `SUBJECT`     | Person whose DNA was tested, submitted, or reported. May include self-testers or individuals analyzed by third parties; may also appear as "testee" or "donor". |
+| 📚 | `EDUCATIONAL` | `EXAMINER`        | Official evaluating exams (inspecting, certifying, examining)  |
+| 📚 | `EDUCATIONAL` | `SITE`| Site where instruction or academic activity took place.<br>Use PHRASE for detail: [school, university, boarding school, classroom, academy] |
+| 📚 | `EDUCATIONAL` | `STUDENT`         | Person recieving instruction. Enrolled or studying ; pupil, student, apprentice |
+| 📚 | `EDUCATIONAL` | `TEACHER`         | Delivered lessons or instruction; includes instructors, tutors |
+| 🗓️ | `EVENT`       | `OFFICIANT`       | Conducts ceremony or signs something, e.g. priest, registrar    |
+| 🗓️ | `EVENT`       | `ORGANIZER`       | Person coordinating or arranging the event                                      |
+| 🗓️ | `EVENT`       | `PARTICIPANT`     | General event role, not further specified           |
+| 🗓️ | `EVENT`       | `PARTYMEMBER`     | Someone who is part of a group celebrating a specific even |
+| 🗓️ | `EVENT`       | `RECORDER`        | Person who documented or recorded details of the event.     |
+| 🗓️ | `EVENT`       | `SPECTATOR`       | Passive observer                                           |
+| 🗓️ | `EVENT`       | `TARGET`          | Person affected by the event, e.g. victim or beneficiary               |
+| 🗓️ | `EVENT`       | `WITNESS`         | Person who saw the event (e.g. accident, birth, signing)             |
+| 👨‍👩‍👧 | `FAMILY`      | `ADOPTEE`         | The child being adopted  |
+| 👨‍👩‍👧 | `FAMILY`      | `ADOPTER`         | Legal adoptive parent  |
+| 👨‍👩‍👧 | `FAMILY`      | `AUNT`            | Aunt  |
+| 👨‍👩‍👧 | `FAMILY`      | `BIRTHPARENT`     | Biological parent  |
+| 👨‍👩‍👧 | `FAMILY`      | `BOARDER`         | Person receiving regular meals somewhere, in return for payment or services |
+| 👨‍👩‍👧 | `FAMILY`      | `BROTHER`         | Brother   |
+| 👨‍👩‍👧 | `FAMILY`      | `CHILD`           | [Listed as child of someone in family grouping] [Biological, adoptive, or recognized child] |
+| 👨‍👩‍👧 | `FAMILY`      | `COUSIN`          | Cousin  |
+| 👨‍👩‍👧 | `FAMILY`      | `DAUGHTER`        | Daughter |
+| 👨‍👩‍👧 | `FAMILY`      | `FAMILYHEAD`      | Person acts as the representative of a household — responsible for legal, social, or census identification of the family unit |
+| 👨‍👩‍👧 | `FAMILY`      | `FATHER`          | Father  |
+| 👨‍👩‍👧 | `FAMILY`      | `FRIEND`          | Friend |
+| 👨‍👩‍👧 | `FAMILY`      | `GRANDCHILD`      | Grandchild  |
+| 👨‍👩‍👧 | `FAMILY`      | `GRANDFATHER`     | Grandfather  |
+| 👨‍👩‍👧 | `FAMILY`      | `GRANDMOTHER`     | Grandmother  |
+| 👨‍👩‍👧 | `FAMILY`      | `GRANDPARENT`     | Grandparent  |
+| 👨‍👩‍👧 | `FAMILY`      | `GUARDIAN`        | Legal guardian. Person with legal responsibility, not necessarily parent (foster parent) |
+| 👨‍👩‍👧 | `FAMILY`      | `HUSBAND`         | Husband   |
+| 👨‍👩‍👧 | `FAMILY`      | `MAIN`            | Points to the main person from a `TEMPLATE`.| 
+| 👨‍👩‍👧 | `FAMILY`      | `MOTHER`          | Mother   |
+| 👨‍👩‍👧 | `FAMILY`      | `NEPHEW`          | Nephew  |
+| 👨‍👩‍👧 | `FAMILY`      | `NIECE`           | Niece  |
+| 👨‍👩‍👧 | `FAMILY`      | `PARENT`          | [Listed as parent of someone (birth, adoptive, foster if known)] [General parent-child link; can be refined with SEX] [Biological, adoptive, or acknowledged paren] |
+| 👨‍👩‍👧 | `FAMILY`      | `SIBLING`         | Listed as brother, sister, or half-siblin; same generation |
+| 👨‍👩‍👧 | `FAMILY`      | `SISTER`          | Sister                               |
+| 👨‍👩‍👧 | `FAMILY`      | `SITE`| Residential or domestic setting central to household life or event.<br>Use PHRASE for detail: [home, house, apartment, flat, garden, yard, dwelling, kitchen] |
+| 👨‍👩‍👧 | `FAMILY`      | `SON`             | Son                                  |
+| 👨‍👩‍👧 | `FAMILY`      | `SOCIOPARENT`     | Sociological Parent: an adult who functions as a parent to a child, but is not legally or biologically related to the child |
+| 👨‍👩‍👧 | `FAMILY`      | `SPOUSE`          | Spouse                               |
+| 👨‍👩‍👧 | `FAMILY`      | `STEP`            | Step-parent, step-child, step-sibling  |
+| 👨‍👩‍👧 | `FAMILY`      | `STEPCHILD`       | Stepchild                            |
+| 👨‍👩‍👧 | `FAMILY`      | `STEPPARENT`      | Stepparent                           |
+| 👨‍👩‍👧 | `FAMILY`      | `SURPARENT`       | Surrogate parent: a person who makes educational decisions for a child when the child's parents or guardians are unavailable or unable to fulfill this role |
+| 👨‍👩‍👧 | `FAMILY`      | `UNCLE`           | Uncle                                |
+| 👨‍👩‍👧 | `FAMILY`      | `WARD`            | The child or dependent in a guardianship relationship  |
+| 👨‍👩‍👧 | `FAMILY`      | `WIDOW`           | A surviving spouse (female) |
+| 👨‍👩‍👧 | `FAMILY`      | `WIDOWER`         | A surviving spouse (male) |
+| 👨‍👩‍👧 | `FAMILY`      | `WIFE`            | Wife   |
+| 🛡️ | `GROUP`       | `AFFILIATE`       | Member or casual participant in group or event |
+| 🛡️ | `GROUP`       | `APPRENTICE`      | In training under a master in a trade or craft   |
+| 🛡️ | `GROUP`       | `ASSOCIATED`      | Linked but unclear role    |
+| 🛡️ | `GROUP`       | `COUNSELOR`       | Advisor, spiritual guide, or emotional support figure|
+| 🛡️ | `GROUP`       | `DEPUTY`          | Second-in-command or acting authority|
+| 🛡️ | `GROUP`       | `EMPLOYEE`        | Works for the institution     |
+| 🛡️ | `GROUP`       | `EXPELLED`        | Forced removal or banishment|
+| 🛡️ | `GROUP`       | `FOUNDER`         | Helped establish or formalize the group |
+| 🛡️ | `GROUP`       | `GUEST`           | The person temporarily stayed, studied, or worked in the group context. |
+| 🛡️ | `GROUP`       | `HEALER`	        | Role of caregiver or medical staff (religious sects)|
+| 🛡️ | `GROUP`       | `HONOREE`         | Granted status for ceremonial or recognition reasons
+| 🛡️ | `GROUP`       | `INITIATE`        | New entrant, often still in training or probation|
+| 🛡️ | `GROUP`       | `JOINED`          | Entry into the group or institution|
+| 🛡️ | `GROUP`       | `JUDGE`           | Arbitrator or internal adjudicator (guild court, tribal dispute)|
+| 🛡️ | `GROUP`       | `LANDLORD`        | Granted tenancy or rights to others   |
+| 🛡️ | `GROUP`       | `LEADENTITY`      | Principal non-human entity in a group (e.g., flagship, headquarters building). Use PHRASE for detail: [entity name, group, date] |
+| 🛡️ | `GROUP`       | `LEADER`          | Primary figure of authority (chief, headmaster, familyhead (in a group), warden, etc.)|
+| 🛡️ | `GROUP`       | `LEFT`            | Voluntary or general departure|
+| 🛡️ | `GROUP`       | `MASTER`          | Skilled person mentoring others  |
+| 🛡️ | `GROUP`       | `MEMBER`          | Person belongs to a kin-based lineage or extended family group  |
+| 🛡️ | `GROUP`       | `MEMBERENTITY`    | Non-human entity that is part of a group (e.g., ship in a fleet, building in a monastery). Use PHRASE for detail: [group name, entity type, date] |
+| 🛡️ | `GROUP`       | `NOVICE`          | Religious/semi-religious entry level (monasteries, sects)|
+| 🛡️ | `GROUP`       | `OFFICER`         | Formal administrator, guard, or enforcer (esp. in guilds)|
+| 🛡️ | `GROUP`       | `PATRON`          | Financial or moral supporter, not necessarily active
+| 🛡️ | `GROUP`       | `REJECTED`        | The person applied but was not accepted or was expelled.                |
+| 🛡️ | `GROUP`       | `REMEMBERED`      | Deceased figure held in group memory (e.g., tribal ancestors)
+| 🛡️ | `GROUP`       | `RESIDENT`        | Lived within institutional group (e.g., Farm, Sect).  |
+| 🛡️ | `GROUP`       | `RETIRED`         | Ceased formal role due to age or tenure|
+| 🛡️ | `GROUP`       | `SAINTED`         | Canonized or revered figure (esp. SECT)
+| 🛡️ | `GROUP`       | `SERVANT`         | Subordinate function role (esp. historical guilds)
+| 🛡️ | `GROUP`       | `SITE`| Communal or organizational setting used by a defined group.<br>Use PHRASE for detail: [farm, commune, compound, guildhall, tribe center, association building] |
+| 🛡️ | `GROUP`       | `SPOKESMAN`       | Spoke or acted on behalf of the group (representative) |
+| 🛡️ | `GROUP`       | `SPONSOR`         | Acted as spiritual or legal backer (e.g., godparent, confirmation)    |
+| 🛡️ | `GROUP`       | `SPONSORED`       | The person was vouched for or introduced by someone else.               |
+| 🛡️ | `GROUP`       | `STUDENT`         | Learns or trains there      |
+| 🛡️ | `GROUP`       | `TEACHER`         | Knowledge provider (esp. in sects)|
+| 🛡️ | `GROUP`       | `TENANT`          | Inhabited land or property under lease from institution or estate     |
+| 🛡️ | `GROUP`       | `TRANSFERRED`     | Moved from one group to another |
+| 🛡️ | `GROUP`       | `WORKER`          | General laborer or active contributor|
+| 🪪 | `IDENTITY`    | `APPLICANT`       | Person who filed or initiated an application for identity-related documents (e.g., passport, visa, name change). |
+| 🪪 | `IDENTITY`    | `ASSIGNED`        | Someone else gives the identity, e.g. "He is John Smith"        |
+| 🪪 | `IDENTITY`    | `DECLARED`        | Person says who they are, e.g. "I am John Smith"   |
+| 🪪 | `IDENTITY`    | `EXAMINER`        | Person responsible for inspecting or verifying submitted identity documents or biometric records. |
+| 🪪 | `IDENTITY`    | `INTERPRETER`     | Present to assist in cases where language barriers existed during identity proceedings (common in immigration or legal name change). |
+| 🪪 | `IDENTITY`    | `NAMED`           | A name is stated without a formal declaration              |
+| 🪪 | `IDENTITY`    | `RECORDER`        | Person who entered or copied the identity data into a formal register (e.g., civil clerk, church scribe). |
+| 🪪 | `IDENTITY`    | `RENAMED`         | Explicit change of name, e.g. adoption, alias, name change    |
+| 🪪 | `IDENTITY`    | `SPONSOR`         | Person vouching for or supporting the identity/residency claim of another, especially in immigration or residency permission cases. |
+| 🪪 | `IDENTITY`    | `WITNESS`         | Individual attesting to someone’s identity (e.g., in affidavit, oath, or testimony). Often required for birth, alias, or passport paperwork. |
+| 📜 | `INHERITANCE` | `ATTORNEY`        | Attorny, also called Solicitor. The legal professional who provides legal advice during will creation and ensures it meets all legal requirements. |
+| 📜 | `INHERITANCE` | `ASSET`           | Specific items (e.g., a house, jewelry, money) that are part of the inheritance. |
+| 📜 | `INHERITANCE` | `BENEFICIARY`     | Person receiving inheritance, bequest, legacy or transferred asset. |
+| 📜 | `INHERITANCE` | `BENEFACTOR`      | Person granting or donating something
+| 📜 | `INHERITANCE` | `BEQUEATHER`      | Legacy/Will donor  |
+| 📜 | `INHERITANCE` | `BEQUEST`         | Asset specifically passed on through a will or legal instrument. Use PHRASE for detail: [item type, recipient, date] |
+| 📜 | `INHERITANCE` | `CLAIMANT`        | Person claiming (or contesting) rights to the inheritance |
+| 📜 | `INHERITANCE` | `CUSTODIAN`       | Person named to manage property inherited by a minor |
+| 📜 | `INHERITANCE` | `DIGNITY`         | Hereditary or conferred title being passed on through inheritance. Use PHRASE for detail: [title name, rank, jurisdiction, Title holding, Style] |
+| 📜 | `INHERITANCE` | `ENTAIL`          | Property bound to pass along a defined line of succession. Use PHRASE 
+for detail: [property name, heir, date] |
+| 📜 | `INHERITANCE` | `ENTERINGH`       | Entering heir: The person who is first in line to inherit a title, property, or estate, and whose claim cannot be superseded by the birth of another heir.
+| 📜 | `INHERITANCE` | `ESTATE`          | The entire collection of assets and liabilities owned by the deceased person at the time of death. Use PHRASE for detail: [property name, heir, date] |
+| 📜 | `INHERITANCE` | `EXECUTOR`        | The person executing the will (may or may not be heir). Responsible for executing a will |
+| 📜 | `INHERITANCE` | `EXITINGH`        | Exiting heir: The person who is next in line to inherit a title or property, and whose right of inheritance is not subject to being defeated by the birth of a closer relative. 
+| 📜 | `INHERITANCE` | `GARDIAN`         | Appointed for minor heirs |
+| 📜 | `INHERITANCE` | `GRANTEE`         | One who receives a right or property |
+| 📜 | `INHERITANCE` | `GRANTOR`         | Establishes trust or grants asset One who grants a right or property|
+| 📜 | `INHERITANCE` | `HEIR`            | Designated recipient of legacy or estate. Inheritor, may have legal or familial tie |
+| 📜 | `INHERITANCE` | `HEIRLOOM`        | An item of sentimental or historical value passed down through the family for generations.  |
+| 📜 | `INHERITANCE` | `INHERITANCE`     | General term for anything received from a deceased person's estate, including both assets and liabilities.  |
+| 📜 | `INHERITANCE` | `NOTARY`          | Official who legally authenticates the will, administers oaths to witnesses, and ensures proper legal formalities are followe |
+| 📜 | `INHERITANCE` | `SCRIVENER`       | Historically, this was the person who physically wrote out the will, especially in times when literacy was limited. They were often legal professionals skilled in proper legal language and formatting |
+| 📜 | `INHERITANCE` | `SITE`| Location where inheritance was managed or distributed.<br>Use PHRASE for detail: [law office, reading room, executor’s house] |
+| 📜 | `INHERITANCE` | `TESTATOR`        | Manages property/assets on behalf of a beneficiary |
+| 📜 | `INHERITANCE` | `TRUSTEE`         | The person who made the will (often the deceased) |
+| ⚖️   | `JUDICIAL`     | `ARBITRATOR`    | Neutral third party appointed to resolve a dispute outside of court. Use PHRASE for detail: [mediation, dispute resolution, settlement] |
+| ⚖️   | `JUDICIAL`     | `BONDSMAN`      | Provided bail or financial guarantee for release from custody. Use PHRASE for detail: [surety, bail, guarantor] |
+| ⚖️   | `JUDICIAL`     | `COURTCLERK`    | Maintained legal records for the court. Use PHRASE for detail: [record keeping, docket, case files] |
+| ⚖️   | `JUDICIAL`     | `DECLARANT`     | Made a declaration. Use PHRASE for detail: [statement, affidavit, deposition] [also as: LEGAL, DECLARANT — meaning: Person who made a formal statement or sworn declaration, e.g., for identity, relationship, property, or DNA test results. Use PHRASE for detail: [identity, property, age, allegiance]] |
+| ⚖️   | `JUDICIAL`     | `HEARSAY`       | Mentioned indirectly by another; not a primary witness but appears by reference in a record. Use PHRASE for detail: [rumor, secondhand, indirect testimony] |
+| ⚖️   | `JUDICIAL`     | `INFORMANT`     | Provided information for a record. Use PHRASE for detail: [tip, report, statement] |
+| ⚖️   | `JUDICIAL`     | `INMATE`        | Person who is (involuntarily) confined or held in a prison, hospital, or other institution. Use PHRASE for detail: [prisoner, detainee, confined] |
+| ⚖️   | `JUDICIAL`     | `INTERPRETER`   | Witness acting in a translation capacity. Use PHRASE for detail: [translator, language, interpreter] |
+| ⚖️   | `JUDICIAL`     | `INTERVIEWER`   | Person tasked with gathering information through questioning. Use PHRASE for detail: [questioner, investigator, interviewer, police, census, journalist] |
+| ⚖️   | `JUDICIAL`     | `INTERVIEWEE`   | Person providing information when questioned. Use PHRASE for detail: [respondent, suspect, source, witness] |
+| ⚖️   | `JUDICIAL`     | `JUDGE`         | Rendered legal decisions. Use PHRASE for detail: [court, ruling, verdict] [also as: LEGAL, JUDGE — meaning: Legal authority who ruled or confirmed. Use PHRASE for detail: [decision, confirmation, judgment]] |
+| ⚖️   | `JUDICIAL`     | `LAWENFORCEMENT`| Enforced legal orders (e.g., bailiff, constable). Use PHRASE for detail: [police, constable, sheriff] |
+| ⚖️   | `JUDICIAL`     | `OBSERVER`      | Passive presence at a legal act or proceeding. Observed but did not testify. Use PHRASE for detail: [spectator, bystander, attendee] |
+| ⚖️   | `JUDICIAL`     | `PLAINTIFF`     | Person seeking legal redress — recipient of court attention. Use PHRASE for detail: [complainant, claimant, petitioner] [also as: LEGAL, PLAINTIFF — meaning: Person initiating a legal case. Use PHRASE for detail: [claimant, initiator, complainant]] |
+| ⚖️   | `JUDICIAL`     | `PROOF`         | Asset that proves a legal fact or event. Use PHRASE for detail: [certificate, document, evidence] |
+| ⚖️   | `JUDICIAL`     | `SCRIBE`        | Person who handwrites or copies legal documents, often for record keeping. Use PHRASE for detail: [copier, transcriber, clerk] |
+| ⚖️   | `JUDICIAL`     | `SIGNATORY`     | Signed something with legal/social force. Use PHRASE for detail: [contract, treaty, agreement] [also as: LEGAL, SIGNATORY — meaning: Person whose signature confirms agreement, consent, or validation. Use PHRASE for detail: [consent, agreement, validation]] |
+| ⚖️ | `JUDICIAL`    | `SITE`| Legal or procedural setting linked to the act or ruling.<br>Use PHRASE for detail: [courtroom, courthouse, tribunal, notary office, justice hall. jail, prison] |
+| ⚖️   | `JUDICIAL`     | `STENOGRAPHER`  | Recorded proceedings in shorthand during a legal event. Use PHRASE for detail: [court reporter, shorthand, transcript] |
+| ⚖️   | `JUDICIAL`     | `WITNESS`       | Person attesting to a legal act or document. Use PHRASE for detail: [testimony, observation, affidavit] [also as: LEGAL, WITNESS — meaning: Attested to a legal act or document. Use PHRASE for detail: [legal act, signature, evidence]] |
+| 🖋️ | `LEGAL`       | `ACCUSED`         | Person accused in a criminal case. Use PHRASE for detail: [accused, defendant, suspect] |
+| 🖋️ | `LEGAL`       | `AGENT`           | Legal or official representative acting on behalf of another. Use PHRASE for detail: [agent, representative, proxy] |
+| 🖋️ | `LEGAL`       | `ALDERMAN`        | A member of a city or town government (Dutch "Schepen"). Use PHRASE for detail: [alderman, council, town government] |
+| 🖋️ | `LEGAL`       | `ATTORNEY`        | An attorney is a lawyer who has been admitted to the bar and is licensed to practice law. This includes the ability to represent clients in legal proceedings and provide legal advice. Use PHRASE for detail: lawyer, advocate, counsellor, solicitor, prosecutor, representative, counsel] |
+| 🖋️ | `LEGAL`       | `BAILIFF`         | Enforcement agent. An official who takes possession of someone's property when they cannot pay their debts (Dutch "Schout"). Use PHRASE for detail: [bailiff, enforcement, property seizure] |
+| 🖋️ | `LEGAL`       | `BENEFACTOR`      | Person granting or donating something. Use PHRASE for detail: [benefactor, donor, grantor] |
+| 🖋️ | `LEGAL`       | `BENEFICIARY`     | Named person entitled to assets or rights through legal process (will, trust, insurance). Use PHRASE for detail: [beneficiary, heir, recipient] |
+| 🖋️ | `LEGAL`       | `CLAIMANT`        | Person filing a legal claim (applicant). Use PHRASE for detail: [claimant, applicant, petitioner] |
+| 🖋️ | `LEGAL`       | `CLIENT`          | Engaged legal representative. Use PHRASE for detail: [client, represented party] |
+| 🖋️ | `LEGAL`       | `DEFENDANT`       | Person defending a case. Use PHRASE for detail: [defendant, accused, respondent] |
+| 🖋️ | `LEGAL`       | `DEFENSE`         | Attorney, advocate, or representative acting on behalf of the accused in a legal case. Use PHRASE for detail: [defense, lawyer, counsel] |
+| 🖋️ | `LEGAL`       | `EXECUTOR`        | Person executing a will. Use PHRASE for detail: [executor, estate administrator] |
+| 🖋️ | `LEGAL`       | `FOREMAN`         | Designated leader or spokesperson of a jury, often responsible for delivering the verdict. Use PHRASE for detail: [jury foreman, spokesperson] |
+| 🖋️ | `LEGAL`       | `GUARDIAN`        | Legal guardian or custodian for a child or adult. Use PHRASE for detail: [guardian, custodian, caregiver] |
+| 🖋️ | `LEGAL`       | `HEIR`            | A person legally entitled to inherit the property or title of another person, typically after their death. Named or acknowledged as heir in will or succession. Use PHRASE for detail: [heir, successor, inheritor] |
+| 🖋️ | `LEGAL`       | `INVENTORYM`      | INVENTORYMAKER — Compiles asset list (also appears in ADMIN). Use PHRASE for detail: [inventory, asset list, record keeper] |
+| 🖋️ | `LEGAL`       | `ISSUER`          | The individual, organization, or entity that creates and releases the document (e.g., corporation issuing financial statements, government issuing identity documents, university issuing transcripts). Use PHRASE for detail: [issuer, creator, publisher] |
+| 🖋️ | `LEGAL`       | `JURY`            | Member of the jury responsible for evaluating evidence and reaching a verdict. Legal authority who ruled or confirmed. Use PHRASE for detail: [jury, juror, verdict] |
+| 🖋️ | `LEGAL`       | `LAWYER`          | Represented party in legal matters; legal representative or advocate. Use PHRASE for detail: [lawyer, advocate, counsel] |
+| 🖋️ | `LEGAL`       | `NOTARY`          | A public official authorized to authenticate and certify the validity of legal documents and transactions, often involving an international element.  Use PHRASE for detail: [notary, certification, witness, powers of attorney, property transactions, including deeds and mortgages, testament, documents for: immigration; emigration; company registration; business transactions. oaths, affirmations, protests, bills of exchange] |
+| 🖋️ | `LEGAL`       | `PARTY`           | Formal participant in a legal action (e.g., plaintiff, defendant). Use PHRASE for detail: [party, participant, litigant] |
+| 🖋️ | `LEGAL`       | `PROBATEJUDGE`   | A judicial official who presides over legal matters related to the estates of deceased individuals, handles guardianship cases for minors or incapacitated adults. Ensure the proper administration and distribution of assets according to the will or, if there isn't one, according to state law. Use PHRASE for detail: [probate, judge, estate] |
+| 🖋️ | `LEGAL`       | `PROSECUTOR`      | Legal representative or authority pursuing charges against an accused individual. Use PHRASE for detail: [prosecutor, attorney, district attorney] |
+| 🖋️ | `LEGAL`       | `RECIPIENT`       | Person who received a legal document, status, or authorization — such as a license, permit, court summons, or adoption order. Use PHRASE for detail: [recipient, grantee, licensee] |
+| 🖋️ | `LEGAL`       | `RULER`           | Monarch or governing authority confirming a right/title (Confirmant). Use PHRASE for detail: [ruler, monarch, confirmant] |
+| 🖋️ | `LEGAL`       | `TESTATOR`        | Person whose will is recorded. Use PHRASE for detail: [testator, will, estate] |
+| 🖋️ | `LEGAL`       | `VICTIM`          | Person harmed or affected by a criminal act or civil dispute; subject of the case. Use PHRASE for detail: [victim, harmed, injured party, underdog] |
+| 💍 | `MARRIAGE`    | `BESTMAN`         | Witness or supporter for groom   |
+| 💍 | `MARRIAGE`    | `BRIDE`           | Female partner in marriage-type event   |
+| 💍 | `MARRIAGE`    | `ENGAGED`         | Betrothed or fiancée/fiancé  |
+| 💍 | `MARRIAGE`    | `EX-SPOUSE`       | Previously married to the person; now separated or divorced |
+| 💍 | `MARRIAGE`    | `FIANCÉ(E)`       | Engaged to be married; may not result in marriage |
+| 💍 | `MARRIAGE`    | `GROOM`           | Male partner in marriage-type event   |
+| 💍 | `MARRIAGE`    | `MAIDOFHONOR`     | Witness or supporter for bride   |
+| 💍 | `MARRIAGE`    | `MARRIAGE-WITNESS`| Someone witnessing the marriage, e.g. best man       |
+| 💍 | `MARRIAGE`    | `OFFICIANT`       | Person leading the ceremony                         |
+| 💍 | `MARRIAGE`    | `PARTNER`         | Unmarried long-term partner, registered or informal. Or one of the marrying persons                                          |
+| 💍 | `MARRIAGE`    | `SPOUSE`          | Married partner, legally recognized. Used where sex or role is unspecified or later in life |
+| 💍 | `MARRIAGE`    | `WITNESS`         | Witnesses signing or present at marriage                          |
+| 🎞️ | `MEDIA`       | `ARCHIVE`         | Media stored as part of a permanent collection. Use PHRASE for detail: [archive name, location, reference code] |
+| 🎞️ | `MEDIA`       | `AUTHOR`          | Wrote accompanying text, article, caption, or media description |
+| 🎞️ | `MEDIA`       | `COPYRIGHT`       | Media holding copyright status. Use PHRASE for detail: [copyright holder, jurisdiction, term] |
+| 🎞️ | `MEDIA`       | `CURATOR`         | Organized or selected items for publication/exhibit |
+| 🎞️ | `MEDIA`       | `EDITOR`          | Reviewed or prepared content for publication or release |
+| 🎞️ | `MEDIA`       | `ILLUSTRATOR`     | Visual artist or designer of the media object (e.g. sketch, diagram, enhancement) |
+| 🎞️ | `MEDIA`       | `INTERVIEWEE`     | Provided personal answers or narrative used in the media content |
+| 🎞️ | `MEDIA`       | `MENTIONED`       | Referenced inside the media                          |
+| 🎞️ | `MEDIA`       | `PHOTOGRAPHER`    | Took or captured the photo or visual image |
+| 🎞️ | `MEDIA`       | `PUBLISHER`       | Released, printed, or distributed the media item |
+| 🎞️ | `MEDIA`       | `SIGNATORY`       | Signed a text or formal communication (can differ from author) |
+| 🎞️ | `MEDIA`       | `SITE`| Creative or performance environment tied to recording or presentation.<br>Use PHRASE for detail: [studio, concert hall, sound booth, stage, newsroom, gallery, concert hall] |
+| 🎞️ | `MEDIA`       | `SOURCE`          | Provided original information, artifacts, or stories used in the media  |
+| 🎞️ | `MEDIA`       | `SOURCEITEM`      | Physical or digital media serving as the primary source for information. Use PHRASE for detail: [media type, origin, date] |
+| 🎞️ | `MEDIA`       | `SUBJECT`         | Subject of the image, article, or portrayal (e.g., in photo, portrait or article, named in piece)|
+| 🎞️ | `MEDIA`       | `TRANSLATOR`      | Translator involved                                                   |
+| 🩺 | `MEDICAL`     | `CORONER`         | Investigated death                   |
+| 🩺 | `MEDICAL`     | `DOCTOR`          | Provided medical care (Physician or healer)     |
+| 🩺 | `MEDICAL`     | `MIDWIFE`         | Assisted in childbirth               |
+| 🩺 | `MEDICAL`     | `NURSE`           | Assisted medical care                |
+| 🩺 | `MEDICAL`     | `PATIENT`         | Received medical care or diagnosis |
+| 🩺 | `MEDICAL`     | `PRACTITIONER`    | Gave medical care; doctor, nurse, healer |
+| 🩺 | `MEDICAL`     | `REPORTER`       | Person filing a medical report   |
+| 🩺 | `MEDICAL`     | `SITE`| Medical setting tied to diagnosis, care, or treatment.<br>Use PHRASE for detail: [hospital, clinic, infirmary, sanatorium, ER, maternity ward, surgery room] |
+| 🪖 | `MILITARY`    | `CASUALTY`       | Person who is wounded, missing, killed  |
+| 🪖 | `MILITARY`    | `COMMANDER`      | Leader (Officer) of group or unit; may be temporary |
+| 🪖 | `MILITARY`    | `CONSCRIPT`      | Drafted into service; may include limited service duration |
+| 🪖 | `MILITARY`    | `ENLISTED`       | Non-officer member of military (e.g. private, corporal) Signed up for military service |
+| 🪖 | `MILITARY`    | `OFFICER`        | Held formal military role; rank may be known |
+| 🪖 | `MILITARY`    | `RECIPIENT`      | Person awarded a medal, rank insignia, commendation, or military honor. |
+| 🪖 | `MILITARY`    | `RECRUITOR`      | Recruits others |
+| 🪖 | `MILITARY`    | `SITE`| Locations of military relevance or deployment.<br>Use PHRASE for detail: [barracks, base, fort, battlefield, warzone, military camp, trench] |
+| 🪖 | `MILITARY`    | `SOLDIER`        | Member of armed forces] [Any enlisted person]               |
+| 🪖 | `MILITARY`    | `SUPPORT`        | Logistics, admin, medical support                    |
+| 🪖 | `MILITARY`    | `VETERAN`        | Former soldier or combatant (Served previously), often linked to pension or memorial |
+| 🪖 | `MILITARY`    | `VICTIM`         | Civilian or soldier harmed or killed      |
+| 📜 | `OFFICIAL`    | `CONSUL`         | Consul or diplomatic agent           |
+| 📜 | `OFFICIAL`    | `MAYOR`          | Mayor                                |
+| 📜 | `OFFICIAL`    | `NOTARY`         | Notary or legal recorder             |
+| 📜 | `OFFICIAL`    | `OFFICER`        | Generic official                     |
+| 📜 | `OFFICIAL`    | `PROCLAMATION`   | Document or object formally declaring an action or status. Use PHRASE for detail: [topic, issuing body, date] |
+| 📜 | `OFFICIAL`    | `REGISTRAR`      | Civil registrar (issuer)   |
+| 📜 | `OFFICIAL`    | `SCRIBE`         | Official writer or record keeper     |
+| 📜 | `OFFICIAL`    | `SEAL`           | Physical seal or emblem representing authority. Use PHRASE for detail: [seal type, issuing body, date] |
+| 📜 | `OFFICIAL`    | `SITE`| Government or civil authority locations.<br>Use PHRASE for detail: [municipality, passport bureau, city hall, records office, agency, consulate] |
+| 🏘️ | `PROPERTY`    | `AGENT`          | Real estate agent or similar mediator                      |
+| 🏘️ | `PROPERTY`    | `BUILDER`        | Architect, builder, or renovator                 |
+| 🏘️ | `PROPERTY`    | `BUYER`          | Purchased the property. (Buyer in a transaction) Party purchasing or receiving ownership  |
+| 🏘️ | `PROPERTY`    | `DESTINATION`    | Location where an event or journey ends. Use PHRASE for detail: [event, location, date] |
+| 🏘️ | `PROPERTY`    | `GUEST`          | Temporary occupant or visitor              |
+| 🏘️ | `PROPERTY`    | `HOLDING`        | Property owned or controlled as part of an estate or organization. Use PHRASE for detail: [owner, type, location] |
+| 🏘️ | `PROPERTY`    | `LESSOR`         | a person who leases or lets a property to another; a landlord. |
+| 🏘️ | `PROPERTY`    | `LESSEE`         | a person who holds the lease of a property; a tenant.             |
+| 🏘️ | `PROPERTY`    | `OWNER`          | Person or group who owns the property (Landowner or leaseholder) (legal or practical owner) |
+| 🏘️ | `PROPERTY`    | `OCCUPANT`       | Current inhabitant of a property  |
+| 🏘️ | `PROPERTY`    | `ORIGIN`         | Location where an event or journey begins. Use PHRASE for detail: [event, location, date] |
+| 🏘️ | `PROPERTY`    | `RECORDED-BY`    | Someone listing or describing the property/asset (e.g. inventoried it)        |
+| 🏘️ | `PROPERTY`    | `RESIDENT`       | Lives on the property (house, farm, etc.)           |
+| 🏘️ | `PROPERTY`    | `SCENE`          | Location where a notable event occurred. Use PHRASE for detail: [event type, location, date] |
+| 🏘️ | `PROPERTY`    | `SELLER`         | Sold the property. (Seller in a transaction) Party selling or transferring ownership |
+| 🏘️ | `PROPERTY`    | `SITE`| Physical site associated with land, ownership, or property transfer.<br>Use PHRASE for detail: [farm, estate, parcel, homestead, land tract, dwelling] |
+| 🏘️ | `PROPERTY`    | `TENANT`         | Has use or lease of the property without owning |
+| 🏘️ | `PROPERTY`    | `VENUE`          | Property used as the location for an event. Use PHRASE for detail: [event type, location, date] |
+| 🏘️ | `PROPERTY`    | `WITNESS`        | Attested to the transaction involving property |
+| 🏘️ | `PROPERTY`    | `WORKER`         | Employed or active on the property (farmer, tenant, servant) 
+| ✝️ | `RELIGIOUS`   | `BELIEVER`       | Identified with the religion but not formally initiated. <br>Use PHRASE for detail: [faith, layperson, religion, affiliation] |
+| ✝️ | `RELIGIOUS`   | `CATECHUMEN`     | Unbaptized person receiving instruction before entry into the faith. <br>Use PHRASE for detail: [catechism, instruction, baptism, preparation] |
+| ✝️ | `RELIGIOUS`   | `CELEBRANT`      | Person who performs a rite, especially a priest at the Eucharist. <br>Use PHRASE for detail: [mass, eucharist, rite, officiant] |
+| ✝️ | `RELIGIOUS`   | `CLERGY`         | Religious official in event; implies OFFICIATOR. General role for priest, pastor, monk, etc. <br>Use PHRASE for detail: [priest, minister, pastor, officiant] |
+| ✝️ | `RELIGIOUS`   | `COMMUNICANT`    | Recipient of communion. <br>Use PHRASE for detail: [eucharist, sacrament, mass, recipient] |
+| ✝️ | `RELIGIOUS`   | `CONFIRMEE`      | A person who is receiving the religious sacrament of confirmation. <br>Use PHRASE for detail: [confirmation, rite, sacrament, initiation] |
+| ✝️ | `RELIGIOUS`   | `CONFSPONSOR`    | (Confirmation sponsor) Guided initiate through rite of passage. <br>Use PHRASE for detail: [confirmation, sponsor, spiritual guide, mentor] |
+| ✝️ | `RELIGIOUS`   | `CONVERT`        | Adopted the religion, often in a ritual or noted event. <br>Use PHRASE for detail: [conversion, faith change, baptism, religious shift] |
+| ✝️ | `RELIGIOUS`   | `DEACON`         | Ordained assistant below priest; helps in services.Is in the final stage to become a priest<br>Use PHRASE for detail: [assistant clergy, liturgy, transitional, church] |
+| ✝️ | `RELIGIOUS`   | `EXPELLED`       | Excommunicated, renounced, banished, or excluded from Church fellowship. <br>Use PHRASE for detail: [excommunicated, shunned, disfellowshipped, renounced] |
+| ✝️ | `RELIGIOUS`   | `GODPARENT`      | Named sponsor in baptism or confirmation. <br>Use PHRASE for detail: [baptism, godmother, godfather, sponsor, witness] |
+| ✝️ | `RELIGIOUS`   | `IMAM`           | Muslim religious leader. <br>Use PHRASE for detail: [mosque, islamic cleric, friday prayer] |
+| ✝️ | `RELIGIOUS`   | `INITIATE`       | Recipient of religious rite or spiritual inclusion. <br>Use PHRASE for detail: [baptism, entry, vows, inclusion, rite] |
+| ✝️ | `RELIGIOUS`   | `MINISTER`       | Religious minister. <br>Use PHRASE for detail: [pastor, church leader, protestant, service] |
+| ✝️ | `RELIGIOUS`   | `MONK`           | Monastic religious figure. <br>Use PHRASE for detail: [abbey, cloister, vows, friar, monastic] |
+| ✝️ | `RELIGIOUS`   | `NOVICE`         | Person in early stage of religious life, not yet fully vowed or ordained. <br>Use PHRASE for detail: [initiate, training, probation, monastery] |
+| ✝️ | `RELIGIOUS`   | `NUN`            | Female monastic. <br>Use PHRASE for detail: [convent, sister, habit, cloister, vows] |
+| ✝️ | `RELIGIOUS`   | `OFFICIANT`      | Performed a religious function (e.g. marriage, baptism). <br>Use PHRASE for detail: [marriage, baptism, religious duty, clergy] |
+| ✝️ | `RELIGIOUS`   | `ORDAINER`       | Someone who has the right to ordain deacons and others. <br>Use PHRASE for detail: [ordination, bishop, authority, consecrate] |
+| ✝️ | `RELIGIOUS`   | `PASTOR`         | Pastor or church leader. <br>Use PHRASE for detail: [preacher, leader, service, congregation] |
+| ✝️ | `RELIGIOUS`   | `PRIEST`         | Religious officiant or cleric. <br>Use PHRASE for detail: [mass, church, clergy, ordination] |
+| ✝️ | `RELIGIOUS`   | `RABBI`          | Jewish religious leader. <br>Use PHRASE for detail: [synagogue, torah, teacher, sermon] |
+| ✝️ | `RELIGIOUS`   | `REVEREND`       | A person who is ordained (to a diocese). <br>Use PHRASE for detail: [ordination, bishop, pastor, deacon, Father, vicar, rector, church] |
+| ✝️ | `RELIGIOUS`   | `SITE`| Sacred or religious building where a rite or ceremony was held.<br>Use PHRASE for detail: [church, temple, mosque, monastery, cloister, convent, chapel, sanctuary] |
+| ✝️ | `RELIGIOUS`   | `SUPERIOR`       | Monastic or religious leader of a community (male or female). Use PHRASE for detail: [abbot, abbess, prior, prioress, mother superior, convent leader, monastic head, cloister] |
+| ✝️ | `RELIGIOUS`   | `VOW`            | Made a solemn promise or commitment in a religious context. <br>Use PHRASE for detail: [monastic, commitment, oath, devotion] |
+| ✝️ | `RELIGIOUS`   | `WITNESS`        | For example, godparent or spiritual sponsor. <br>Use PHRASE for detail: [witness, sponsor, ceremony, signature] |
+| 🌐 | `SOCIAL`      | `ATTENDEE`      | Person present at a ceremony, unveiling, memorial event    |
+| 🌐 | `SOCIAL`      | `AUDIENCE`      | Present at the event    |
+| 🌐 | `SOCIAL`      | `COWORKER`      | Participated in joint task or work; not hierarchical |
+| 🌐 | `SOCIAL`      | `DEDICATOR`     | Person who organized or dedicated the memorial    |
+| 🌐 | `SOCIAL`      | `ENSLAVER`      | Person who held others in involuntary servitude or bondage. |
+| 🌐 | `SOCIAL`      | `GUEST`         | Attended or featured at the event |
+| 🌐 | `SOCIAL`      | `HONOREE`       | [The person being commemorated (e.g. on a gravestone or memorial)]  [Person being honored in a tribute event]|
+| 🌐 | `SOCIAL`      | `HOST`          | Gave the party, reception, or event |
+| 🌐 | `SOCIAL`      | `INSCRIBED`     | Person named in writing, e.g. on a war memorial      |
+| 🌐 | `SOCIAL`      | `MENTOR`        | Guided or advised another; includes apprenticeships |
+| 🌐 | `SOCIAL`      | `PARTICIPANT`   | Present in public or semi-public event marking something, e.g. parade, unveiling |
+| 🌐 | `SOCIAL`      | `REPRESENTATIVE`| Portrayed or represented another person, usually in a theatrical or ceremonial setting. |
+| 🌐 | `SOCIAL`      | `SITE`| Setting of public or private gatherings and social events.<br>Use PHRASE for detail: [ballroom, village square, party tent, pub, dining hall, cinema] |
+| 🌐 | `SOCIAL`      | `SLAVE`         | Person held in bondage or forced labor; property of another. |
+| 🌐 | `SOCIAL`      | `SPEAKER`       | Person giving a speech                                             |
+| 🌐 | `SOCIAL`      | `SUBJECT`       | The person being remembered (e.g. named on grave or monument)             |
+| 🌐 | `SOCIAL`      | `TARGET`        | Person being commemorated (e.g. war dead, founder, jubilee) |
+| 🌐 | `SOCIAL`      | `TITLED`        | Holder of a hereditary or civic title (e.g., baron, alderman, viscount). Reflects social rank or status. |
+| 🌀 | `OTHER`       | `OTHER`         | Role not yet categorized or too vague;  Must include a `PHRASE` |
+
+
diff --git a/specification/gedcom-3-structures-4-enumerations.md b/specification/gedcom-3-structures-4-enumerations.md
index bf70b9a4..b666b57f 100644
--- a/specification/gedcom-3-structures-4-enumerations.md
+++ b/specification/gedcom-3-structures-4-enumerations.md
@@ -49,6 +49,231 @@ these are given generic definitions with URIs constructed by concatenating
 | `EVEN` | A generic event; either `g7:INDI-EVEN` or `g7:FAM-EVEN` |
 
 
+### `g8:enumset-FLEXTYPE` 
+
+### `g8:enumset-FLEXTYPE`
+
+This enumset defines the type of the `CONTENTS` that follows the tag `FLEX`.  
+Each `FLEX` block includes a `PHRASE` and a `CONTENTS` line, optionally followed by one or more `CONT` lines. This table describes how `CONTENTS` is interpreted based on its `TYPE`.
+
+| TYPE        | Description                                                                 | Multiline | NOTE-type | CONTENTS Value |
+|-------------|-----------------------------------------------------------------------------|-----------|------------|----------------|
+| `ACCOUNTNR` | An account number, such as for a bank account. Interpreted as a string.    | ➖        | ➖         | value          |
+| `ADDRESS`   | Structured address data. `ADDRESS_STRUCTURE` follows under `CONTENTS`.      | ✅        | ➖         | ADDR           |
+| `ADDRPLUS`  | Extended address structure. `ADDRPLUS_STRUCTURE` follows under `CONTENTS`.  | ✅        | ➖         | ADDR           |
+| `AMOUNT`    | Raw numeric quantity or size.                                               | ➖        | ➖         | value          |
+| `ANNOTATION`| Annotated remark, such as in a census or bible. Treated like an inline `NOTE`. | ✅    | ✅         | NOTE           |
+| `ARRAY`     | A tuple array. Only simple 2-column tuples allowed. Multiline required.     | ✅        | ➖         | ARRAY          |
+| `BOOLEAN`   | A truth value: `TRUE` or `FALSE`.                                           | ➖        | ➖         | value          |
+| `CURR`      | Currency code (ISO 4217), e.g., USD, EUR.                                   | ➖        | ➖         | value          |
+| `DATETIME`  | A DateValue, combined date and time using `1 DATE` and `2 TIME`.            | ✅        | ➖         | DATE + TIME    |
+| `DATExx`    | GEDCOM-compliant date where `xx` clarifies intent: `DATEV`, `DATEE`, `DATEP`, etc. | ➖ | ➖         | DATE           |
+| `DECIMAL`   | Decimal number, e.g., 12500.00                                              | ➖        | ➖         | value          |
+| `DESCRIPT`  | Short description. One-liner. For longer text, use `NOTE`.                  | ➖        | ➖         | value          |
+| `HEX`       | Hexadecimal string.                                                         | ➖        | ➖         | value          |
+| `INTEGER`   | Whole number without decimals.                                              | ➖        | ➖         | value          |
+| `LANDSIZE`  | Area or size of land or estate. May include units (e.g., "5 acres").       | ➖        | ➖         | value          |
+| `MATERIAL`  | Material of an object (e.g., "wood", "linen").                            | ➖        | ➖         | value          |
+| `NAME`      | Full name without structure parsing.                                        | ➖        | ➖         | value          |
+| `NOTE`      | Free-text remark. Treated like an inline `NOTE`.                            | ✅        | ✅         | NOTE           |
+| `OBJECT`    | Label or ID of a tangible item. Not a pointer.                              | ➖        | ➖         | value          |
+| `PERCENT`   | Percent (0–100), can include decimals.                                      | ➖        | ➖         | value          |
+| `PERCENTR`  | Percent ratio, may exceed 100%.                                             | ➖        | ➖         | value          |
+| `REGNUMBER` | Identifying registration or case number. May include alphanumerics.        | ➖        | ➖         | value          |
+| `ROLE`      | Functional role or designation (e.g., heir, witness).                       | ➖        | ➖         | value          |
+| `TEXT`      | Fallback free-text. Not for structured data.                                | ✅        | ✅         | NOTE           |
+| `TITLE`     | Honorific or title (e.g., "Dr.", "Queen").                               | ➖        | ➖         | value          |
+| `UNIT`      | Unit of measurement (e.g., acre, meter, foot, pennyweight).                 | ➖        | ➖         | value          |
+| `URL`       | Valid file path or web URL.                                                 | ➖        | ➖         | value          |
+
+#### 🧾 Notes
+
+- The **`Multiline`** column indicates whether the type supports/encourages `CONT` lines after `CONTENTS`.
+- The **`NOTE-type`** column marks types that behave like inline `NOTE`s — they render and wrap identically and allow `CONT`.
+- The **`CONTENTS Value`** column shows what the `CONTENTS` line itself should contain:
+  - `value` means raw content (e.g., number, string).
+  - `NOTE`, `ADDR`, or `ARRAY` means that tag name appears literally in the `CONTENTS` line.
+- ⚠️ Parsers must distinguish between `value` and tagname in `CONTENTS`.
+- 🧠 `DATExx` supports disambiguation when the DATE's meaning (exact/approx/range/etc.) isn't clear from context, unlike regular GEDCOM event structures.
+
+#### 💬 Suffixes for `DATExx`
+
+| Suffix   | Meaning                            |
+|----------|-------------------------------------|
+| `DATEV`  | General DateValue                   |
+| `DATEE`  | Exact date                          |
+| `DATEA`  | Approximate date                    |
+| `DATEP`  | Period (e.g., "BET 1890 AND 1900") |
+| `DATER`  | Date range                          |
+| `DATERs` | Date restriction (e.g., "BEF 1860") |
+
+***
+### `g8:enumset-FLEXTYPE`
+
+This enumset defines the type of the `CONTENTS` that follows the tag `FLEX`.  
+Each `FLEX` block includes a `PHRASE` and a `CONTENTS` line, optionally followed by one or more `CONT` lines. This table describes how `CONTENTS` is interpreted based on its `TYPE`.
+
+| TYPE        | Description   | Multiline | NOTE-type | CONTENTS Value |
+|-------------|---------------|-----------|-----------|----------------|
+| `ACCOUNTNR` | An account number, such as for a bank account. Interpreted as a string. | ➖ | ➖ | value |
+| `ADDRESS`   | Structured address data. `ADDRESS_STRUCTURE` follows under `CONTENTS`.| ✅ | ➖ | ADDR   |
+| `ADDRPLUS`  | Extended address structure. `ADDRPLUS_STRUCTURE` follows under `CONTENTS`. | ✅ | ➖ | ADDR |
+| `AMOUNT`    | Raw numeric quantity or size.    | ➖        | ➖         | value          |
+| `ANNOTATION`| Annotated remark, such as in a census or bible. Treated like an inline `NOTE`. | ✅ | ✅ | NOTE|
+| `ARRAY`     | A tuple array. Only simple 2-column tuples allowed. Multiline required. | ✅| ➖ | ARRAY  |
+| `BOOLEAN`   | A truth value: `TRUE` or `FALSE`.     | ➖        | ➖         | value          |
+| `CURR`      | Currency code (ISO 4217), e.g., USD, EUR. | ➖        | ➖         | value          |
+| `DATETIME`  | A DateValue, combined date and time using `1 DATE` and `2 TIME`. | ✅   | ➖  | DATE + TIME |
+| `DATExx`    | GEDCOM-compliant date where `xx` clarifies intent: `DATEV`, `DATEE`, `DATEP`, etc.|➖|➖| DATE|
+| `DECIMAL`   | Decimal number, e.g., 12500.00 | ➖        | ➖         | value          |
+| `DESCRIPT`  | Short description. One-liner. For longer text, use `NOTE`.  | ➖ | ➖ | value          |
+| `HEX`       | Hexadecimal string.    | ➖        | ➖         | value          |
+| `INTEGER`   | Whole number without decimals. | ➖        | ➖         | value          |
+| `LANDSIZE`  | Area or size of land or estate. May include units (e.g., "5 acres").| ➖ | ➖ | value    |
+| `MATERIAL`  | Material of an object (e.g., "wood", "linen").   | ➖        | ➖         | value          |
+| `NAME`      | Full name without structure parsing.  | ➖        | ➖         | value          |
+| `NOTE`      | Free-text remark. Treated like an inline `NOTE`.| ✅        | ✅         | NOTE           |
+| `OBJECT`    | Label or ID of a tangible item. Not a pointer.  | ➖        | ➖         | value          |
+| `PERCENT`   | Percent (0–100), can include decimals. | ➖        | ➖         | value          |
+| `PERCENTR`  | Percent ratio, may exceed 100%.   | ➖        | ➖         | value          |
+| `REGNUMBER` | Identifying registration or case number. May include alphanumerics.| ➖ | ➖ | value     |
+| `ROLE`      | Functional role or designation (e.g., heir, witness).| ➖        | ➖         | value          |
+| `TEXT`      | Fallback free-text. Not for structured data.| ✅        | ✅         | NOTE           |
+| `TITLE`     | Honorific or title (e.g., "Dr.", "Queen").  | ➖        | ➖         | value          |
+| `UNIT`      | Unit of measurement (e.g., acre, meter, foot, pennyweight). | ➖  | ➖  | value   |
+| `URL`       | Valid file path or web URL.   | ➖        | ➖         | value          |
+
+#### 🧾 Notes
+
+- The **`Multiline`** column indicates whether the type supports/encourages `CONT` lines after `CONTENTS`.
+- The **`NOTE-type`** column marks types that behave like inline `NOTE`s — they render and wrap identically and allow `CONT`.
+- The **`CONTENTS Value`** column shows what the `CONTENTS` line itself should contain:
+  - `value` means raw content (e.g., number, string).
+  - `NOTE`, `ADDR`, or `ARRAY` means that tag name appears literally in the `CONTENTS` line.
+- ⚠️ Parsers must distinguish between `value` and tagname in `CONTENTS`.
+- 🧠 `DATExx` supports disambiguation when the DATE's meaning (exact/approx/range/etc.) isn't clear from context, unlike regular GEDCOM event structures.
+
+#### 💬 Suffixes for `DATExx`
+
+| Suffix   | Meaning                            | TAGS |
+|----------|-------------------------------------|--|
+| `DATE`   | date                                |  [calendar D] [[day D] month D] year [D epoch] |
+| `DATEV`  | General DateValue                   |  [ date / DatePeriod / dateRange / dateApprox ] |
+| `DATEE`  | Exact date                          | day D month D year  |
+| `DATEA`  | Approximate date                    |  (%s"ABT" / %s"CAL" / %s"EST") D date |
+| `DATEP`  | Period (e.g., "BET 1890 AND 1900") |  [ %s"TO" D date ] <br> / %s"FROM" D date [ D %s"TO" D date ] |
+| `DATER`  | Date range                          |  %s"BET" D date D %s"AND" D date<br> / %s"AFT" D date<br> / %s"BEF" D date |
+| `DATERS` | Date restriction (e.g., "BEF 1860") |  %s"FROM" / %s"TO" / %s"BET" / %s"AND" / %s"BEF" <br>/ %s"AFT" / %s"ABT" / %s"CAL" / %s"EST" |
+
+- This enumeration defines the list of valid types that can appear in a `FLEX` structure's `TYPE` line.
+- New types may be added over time. Unrecognized types must be ignored or flagged.
+- Each type adds meaning to the associated `CONTENTS` value(s). Parsers and tools must validate types against this list for interoperability.
+- 🧾 `TEXT` must not be used to encode structured values (like numbers, currency, or dates) in string form. Always use the appropriate type. `TEXT` is a fallback only.  
+- (`NOTE`-like enum value), this means this `FLEX`-type is to be handled like an **inline** `NOTE` including the tag `NOTE`.
+- **Multiline**, this `FLEX` type is a multiline type, like `NOTE` or `ARRAY`, see the examples.
+
+#### 💬 Comments on FLEX Type Handling
+
+- ⚠️ Parsers must validate that the number of `TYPE` entries matches the structure of `CONTENTS` values.
+- ⚖️ `LANDSIZE` may include implicit or explicit units (e.g., `10.5 ACRE`), but software should gracefully handle unitless values when the historical context is uncertain.
+  - The units are only present because they appeared on the original document, and do not have to be interpreted by software.
+- ♾️ `UNIT`, for old measurements see: https://en.wikipedia.org/wiki/Medieval_weights_and_measures or https://en.wikipedia.org/wiki/List_of_obsolete_units_of_measurement.
+  - Here too: units do not have to be interpreted by software.
+
+:::example  
+These are examples for a `NOTE`, an `ARRAY`, and an `ANNOTATION`:
+```gedcom
+1 FLEX NOTE                   /* FLEX re4placement of a normal inline NOTE */
+2 PHRASE description on form
+2 CONTENTS NOTE
+3 CONT First line of text
+3 CONT another textline
+```
+```gedcom
+1 FLEX ARRAY                  /* DNA values */
+2 PHRASE DNA values
+2 CONTENTS ARRAY
+3 CONT (rs123456, A)
+3 CONT (rs234567, T)
+3 CONT (rs345678, G)
+```
+```gedcom
+1 FLEX ANNOTATION             /* An annotation, which is always of type NOTE */
+2 PHRASE Annotation in a Census
+2 CONTENTS NOTE
+3 CONT First line of annotation
+3 CONT another annotated line
+```
+These are examples for `DATEP`, `DATETIME` and an `ADDRESS`:
+```gedcom
+1 FLEX DATEP                  /* A Dateperiod */
+2 PHRASE Dateperiod of event
+2 CONTENTS FROM 1850 TO 1880
+
+1 FLEX DATETIME
+2 PHRASE Birth Date and time
+2 CONTENTS DATETIME
+3 DATE 18 SEP 1832
+3 TIME 12:45
+
+1 FLEX ADDRESS
+2 PHRASE Address of laboratory
+2 CONTENTS ADDR 43 Mainstreet /* ADDR1, ADDR2, ADDR3 are deprecated so street and nr follow ADDR!! */
+3 CITY Cristal Lake
+~ ~ ~                         /* Other lines of the address structure */
+```
+:::  
+
+:::note  
+During draft there was also an `ENUM`:
+- ENUM: A value from a predefined list of allowed values. (Use cautiously.)
+- If used, `CONTENTS` must reference a known enum value, and we’d likely need a way to specify which enum set is being used (like `PEDI`, `SEX`, or a user-defined list).
+- 🚫 `ENUM` has been excluded for now due to the need for explicit reference to an enumeration list, which is not yet defined in the spec. It could be used/defined as `1 FLEX ENUM, PEDI, ADOPTED`
+
+$\color{Coral}{\textsf{`ENUM` might be too ambiguous. Might want to drop for now unless a specific use-case exists.}}$
+
+:::
+
+#### Some other `FLEX-TYPE` Specifications
+
+- Each `FLEX-TYPE` value defines the structure and interpretation of the associated `CONTENTS`. This section describes the expected format and usage rules for common `FLEX-TYPE` values.
+- Each value in a multi-part `CONTENTS` line must exactly match its corresponding type in the `FLEX` declaration, by position.
+
+| `FLEX-TYPE` | Description     | Example  |
+|-------------|-----------------|----------|
+| **BOOLEAN** | Must be one of: `TRUE`, `FALSE` (uppercase).| Example: `1 CONTENTS TRUE` |
+| **CODE** | A short, predefined value from a controlled vocabulary or government list.| Example: `1 CONTENTS "C-01"` (case and format depend on the code system used)|
+| **CURR** | Currency code following [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217). Always combined with `DECIMAL` or `INTEGER`| Example: `1 CONTENTS INTEGER, USD` or `1 CONTENTS DECIMAL, EUR`|
+| **LANDSIZE** | Land size measurement. First value must be numeric (`DECIMAL`); second value is a unit label (`TEXT`).| Example: `1 CONTENTS 3.75, ACRE`<br> Non-SI or historical units (e.g., `"BUNDER"`, `"MORGEN"`, `"MUD"`) are permitted as quoted text.|
+| **PERCENT** | A numeric value representing a percentage. | Example: `1 CONTENTS 25.0` (meaning 25%)|
+
+### `g8:enumset-GROUP-TYPE`
+
+These values define the allowed `TYPE` values for the `GROUP` record.  
+A `GROUP` represents a named social, ancestral, or occupational unit that may span across families and generations — such as a clan, caste, guild, religious order, or a sports team etc. that may span across families and generations.  
+Each individual `GROUP` must declare exactly one `TYPE` value.
+
+| ICO | `TYPE`    | Description          | Examples (with  PHRASE)    |
+|-----|-----------|----------------------|--------------|
+| 🧬 | `CASTE`   | Stratified hereditary social class, tied to status, often with legal or ritual restrictions; commonly used in hierarchical societies. | Brahmin (India), Burakumin (Japan), artisan castes in West Africa. "Vaishya trading caste of Bengal" or "Brahmin priestly caste of Varanasi"|
+| 🏞️ | `CLAN`    | Kin-based lineage group, typically connected to shared ancestry and territorial rights   | Clan MacLeod (Scotland), O'Neill (Ireland), Dlamini clan (Eswatini)  "MacKenzie clan of the Highlands" or "Clan Donnachaidh (Robertsons)"|
+| ⚔️ | `FACTION` | Political or ideological group formed for power, dissent, or advocacy | Jacobites (UK), Bolsheviks (Russia), modern activist coalitions.  "Anti-Reform Resistance, 1832" or "Bolsheviks, 1917"|
+| 🚜 | `FARM`    | Family unit associated with a named homestead or farmstead |   Gården "Storlien" (Norway), Boerderij "De Veenhof" (Netherlands)  "Boerderij De Veenhof, Overijssel" or "Gården Storlien, Trøndelag"|
+| 🛠️ | `GUILD`   | Occupational or trade-based group with formal training, rights, or charters. May include rank.  | Blacksmiths, merchants, tailors, trade societies, craftsman. E.g.: Weavers' Guild (Leiden), Worshipful Company of Goldsmiths' Guild (UK), Hanseatic League. "Butchers' Guild of Bruges" or "Guild of Tailors, Haarlem"|
+| ⛪ | `ORDER`   | Religious, spiritual, monastic, or honorary group with a shared mission  | Knights Templar, Jesuit Order, Benedictines, Order of the Garter. "Order of Saint John, Malta" or "Order of Saint Augustine"|
+| 🗳️ | `PARTY`   | Political party, faction, or electoral group |  Labour Party (UK), Democrats (USA) "Green Progressive Alliance, Utrecht chapter" or "Labour Party, UK"|
+| 🔯 | `SECT`    | Religious subgroup or denomination, often with distinctive doctrine or practices. Often diverging from a mainstream belief system   | Old Order Amish, Sufi orders, Hasidic sects, Sunni, Cathars, Shakers "Old Order Amish of Lancaster" or "Old Order Mennonites, Lancaster County"|
+| 🎓 | `SOCIETY` | Voluntary cultural, social, scholarly, or scientific association  | Royal Astronomical Society, Esperanto Club  "Historical Society of Drenthe" or "Royal Astronomical Society"|
+| 🏅| `TEAM`    |  Group formed for sport, art, cooperative performance, or competition-based group  | 1908 Dutch Olympic Rowing Team, Harlem Globetrotters, FC Barcelona, Comédie-Française acting troupe. "Royal Ballet touring company, 1951" or "Rijksmuseum Curling Club"|
+| 🐾| `TRIBE`   |  Ethnic or ancestral group often encompassing multiple clans; with shared language and territory, and cultural or linguistic unity.    | Cherokee Nation, Navajo, Berber, Dakota Sioux, Zulu, Sámi    "Dakota Sioux of the Great Plains|
+| 🌀 | `OTHER`   | Custom type not listed here (must include a `PHRASE`)  | Fellowship of Historical Gardeners, or "Ski Patrol volunteers"  |"Fellowship of Historical Gardeners" or "Railway Enthusiasts of East Anglia"|
+
+> 🧠 **Note on `FARM` and `CLAN` crossovers**:  
+> In rural Norway 🇳🇴, Germany 🇩🇪, and the Netherlands 🇳🇱, individuals were historically identified by the **name of the farm** they lived on, often replacing or supplementing surnames.  
+> - In **Norway**, a man might be called "Ole Storlien" after the farm, even if unrelated to previous residents.  
+> - In **the Netherlands**, farms like “De Veenhof” or “Klein Westeinde” became identity anchors; children or workers living there might be recorded under the farm name in local records.  
+> This creates a **quasi-clan** identity centered on a *location* rather than a bloodline or kinship — blending elements of family, estate, and group affiliation.
+
 ### `g7:enumset-MEDI`
 
 | Value        | Meaning                           |
@@ -230,6 +455,51 @@ and applications should be prepared to encounter non-current values.
 | `SUBMITTED` | All | Ordinance was previously submitted. | Deprecated. This status was defined for use with TempleReady which is no longer in use. |
 | `UNCLEARED` | All | Data for clearing the ordinance request was insufficient. | Deprecated. This status was defined for use with TempleReady which is no longer in use. |
 
+### `g8:enumset-TORIGIN`
+
+Specifies **how** a `TEMPLATE` or `STICKY` was originally created or derived.  
+This describes the **construction method** — whether automated, copied, inferred, or transcribed.  
+It is not the same as the trust level, but is used to assess credibility and compatibility.  
+
+Multiple values may be listed if applicable (e.g. `1 TORIGIN REVERSENG, INCOMPLETE`).
+
+| Trust | Icon | Tag           | Description |
+|-------|------|----------------|-------------|
+| 🟢    | 📄  | `ORIGDOC`      | Created directly from a physical or digital document that is **available, cited, and traceable in this GEDCOM file**. `CITA` structure must point to a `SOUR` in this GEDCOM. |
+| 🟢    | ✍️  | `TRANSCRIBED`  | Manually transcribed from a known document. Can apply to individual facts or full documents. Must include a `CITA` structure pointing to a `SOUR` in this GEDCOM. |
+| 🟡    | 📥  | `IMPORTED`     | Fully structured record or subtree was **mechanically loaded** from a GEDCOM 8-compatible source or system. |
+| 🟡    | 🧬  | `MERGED`       | Created by combining overlapping records from multiple sources into a unified record. Often applies to families, clusters, or trees. |
+| 🟡    | 🛠️  | `REVERSENG`    | Reverse-engineered manually or semi-automatically from legacy data (notes, citations, or prior GEDCOM), poorly structured, or incompatible data (e.g. GEDCOM 5.x). |
+| 🟡    | 🪶  | `INCOMPLETE`   | Known to be partial or fragmentary, with gaps or missing fields. Can be added alongside any other tag to indicate incompleteness. |
+| 🟠    | 🧩  | `COPIEDFRAG`   | Manually copied or extracted from another public tree, online profile, or website — **without verifying original sources**. Applies to selected facts or small clusters. |
+| 🟠    | ℹ️  | `INDIFAM`      | **Reverse engineered** from **1 (one)** `INDI` or **1 (one)** `FAM` record from a file containing GEDCOM version 7.x or below. This is to be used in case a file is reverse engineered, and certain data from the older file has no proper connection (source-citation) to any `SOUR`ce. In that case that data from this 1 `INDI` or this 1 `FAM` will be put together in a temp-`TEMPLATE` and 1 (one) accompanying temp-`STICKY` until a `TAG` inside it, can later be properly connected to an existing `SOUR`. Then that data will be taken out, `TAG` by `TAG`, and put in the correct `STICKY`. This process continues until all data from that temp-`STICKY` marked with `INDIFAM` is processed, and the `STICKY` is "empty". After that the temp-`STICKY` and the temp-`TEMPLATE` that it belongs to, can be deleted. This ensures no data is lost from older files. |   
+| 🟠    | ℹ️  | `INDIFAM`      | Reverse-engineered from a single `INDI` or `FAM` record in a pre-GEDCOM 8 file **without a valid `SOUR` link**. Data is stored in a temporary `TEMPLATE` and `STICKY` until each `TAG` is linked to a verified source. |
+| 🔴    | 🎲  | `GUESSED`      | Constructed by logic, guesswork, deduction or inference without supporting documentation. |
+| 🔴    | ❓  | `UNKNOWN`      | No record of how this data was created or obtained. Method is unclear or lost. |
+
+---
+
+**Special notes:**
+
+- **`INDIFAM` handling process:**  
+  When reverse-engineering a pre-GEDCOM 8 file, some data from an `INDI` or `FAM` record may have no proper source-citation link.  
+  In such cases, all unlinked data from **one** `INDI` or **one** `FAM` is placed into a temporary `TEMPLATE` and **one** accompanying temporary `STICKY`, both marked with `TORIGIN INDIFAM`.  
+  Over time, each `TAG` is linked to a verified `SOUR`. As each `TAG` is moved to its correct `STICKY`, it is removed from the temporary one.  
+  When the temporary `STICKY` is empty, both it and its `TEMPLATE` are deleted.  
+  This ensures that no unlinked data from older files is lost during migration while clearly flagging it as lacking verified sources at the time of import.  
+- **If a `TEMPLATE` does not have a proper `SOUR` connected from inside this GEDCOM itself, `TORIGIN` cannot be `ORIGDOC`or `TRANSCRIBED`.**
+
+---
+
+Applies to:
+- `TEMPLATE` records
+- `STICKY` records
+
+Used by:
+- quality-assessment tools
+- compatibility checks
+- documentation and interface hints
+
 ### `g7:enumset-NAME-TYPE`
 
 | Value | Meaning                       |
diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
new file mode 100644
index 00000000..050049ab
--- /dev/null
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -0,0 +1,6130 @@
+# Appendix B: GEDCOM Examples
+
+
+## General Remarks
+
+This appendix collects practical GEDCOM 8 examples to help users and developers see how the data structures can be applied in realistic (and sometimes lightly humorous) situations. Each example is tied to a specific `TEMPLATE` type and includes participants (via `STICKY`s), showing how GEDCOM 8 organizes complex, real-life, historical or genealogical data.
+
+Use the index below to jump to an example that matches the kind of `TEMPLATE` you're working with.  
+All examples follow the same pattern: a short explanation, followed by the full GEDCOM structure using fenced **gedcom** blocks for clarity.  
+
+Click 🔝 to return here from any example.
+
+### Things to remember:
+- As the examples are really large, on some places the end part of a structure is removed, and replaced bij a line with **~ ~ ~**. So that means the examples can not be validated as correct GEDCOM 8. Some examples have complete records, they are recognizable by the end-lines `CREA` and `CHAN`.
+- As `SPLAC` is now assigned to be implemented for GEDCOM 8, we use `SPLAC` here for places, and no longer the GEDCOM 7 `PLAC` tags.
+- For the same reason as for `SPLAC`, Names are represented in the new GEDCOM 8 `NAME` format. But as a name like `John de Wit` can have many lines in the new format, here too the last lines of the new `NAME_STRUCTURE` are sometimes replaced by **~ ~ ~**.
+- The examples make heavy use of the newly proposed Comment format that is also in this PR. So lines might look like:
+  - `1 STICKY @ST0005@  /* here some explanatory comments */`
+- As there are many examples for many different situations, below this **General Remarks** there is a link-list in a table, with short descriptions. That way a certain example is easier to find without scrolling.  
+
+**Every example has a link back to the start of this page.**
+
+---
+
+## 📚 Examples Index
+
+| 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
+|-----------|------------------|-------------------------------------------------------------------|
+| [💍 Example 01](#💍-example-01-wedding-certificate-with-family-necklace-transfer) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
+| [👧🏻 Example 02](#👧🏻-example-02-international-adoption-certificate) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
+| [🍼 Example 03](#🍼-example-03-medical-birth-certificate) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
+| [💍🧒 Example 04](#💍🧒-example-04-wedding-with-step-children-from-both-sides) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |
+| [🧮 Example 05](#🧮-example-05-census-with-annotated-events) | FAMILY, CENSUS |  **🧮 Example 05: Census with Annotated Events**<br>Census of a family: Father, Mother, Son, Daughter, Enumerator, Boarder. Includes **annotated "events"** (`AN_BIRTH`, and `AN_MOVE`) |
+| [🎖️ Example 06](#🎖️-example-06-medal-awarded-to-individual) | ASSET, MEDAL        | **🎖️ Example 06: Medal awarded to individual**<br>A medal (`ASSET`) given to a soldier, using `STICKY` links and `FLEX` fields. The `TEMPLATE` is of type `MILITARY, AWARD` and connects a tangible object (the medal itself) with the recipient using `STICKY` roles. |
+| [🌿 Example 07](#🌿-example-07-land-grant-record) | PROPERTY, GRANT | **🌿 Example 07: Land Grant Record**<br>This example models a royal land grant issued in 1811 to a private citizen as a reward for military service. It includes a structured `TRANSFER` with a defined `GRANTOR`, `GRANTEE`, and land parcel `ASSET`, as well as a properly detailed `CITA` section with archival metadata.|
+| [🪪 Example 08](#🪪-example-08-naturalization-and-passport) | ORGANIZATION, COURT and<br>IDENTITY, PASSPORT | **🪪 Example 08: Naturalization and Passport**<br>**A `TEMPLATE` pair** modeling naturalization and passport issuance for Leopold Federwitz in early 1900s USA. Includes legal authority roles, asset `STICKY`s (Naturalization certificate and passport), and showcases how to store both under the `ASSETS` section of the `INDI`. The `TEMPLATE`s events are: `NATU` (official GEDCOM) and `EVEN IDENTITY, PASSPORT` (no official GEDCOM event present)|
+| [⛪ Example 09](#⛪-example-09-adult-baptism-and-religious-roles) | RELIGIOUS and BAPTISM | **⛪ Example 09: Adult baptism and Religious roles**<br>A combination of multi-role religious events: includes adult convert, clergy, ordination backstory, and baptism with an `ASSET` (baptism gown) use. It has: Adult conversion (Hans and Johannes); Infant baptism (Johannes); Ordination (Einar Voss); Clergy participation (Henrik Brodahl); Godparent and family witness roles (Marta, Karl); Religious assets (Baptism gown) |
+| [📙 Example 10](#📙-example-10-family-bible) | SECONDARY, FAMILYBIBLE | **📙 Example 10: Family Bible**<br>A richly annotated family Bible (TYPE SECONDARY, FAMILYBIBLE) spanning 3 generations of the Eldridge family (1869–1936). Uses `AN_xxx` `STICKY` types to model secondary handwritten events (with `FLEX ANNOTATION`) like births, deaths, illnesses, and gifts. Includes the Bible's `ASSET`-record, a beloved butler and a midwife, and shows `TDABOVI` lineage, and emotional historical record-keeping in `FLEX`. Includes period photos. |
+| [🧬 Example 11](#🧬-example-11-dna-test-results-match-comparison-and-genotype-report) | IDENTITY, DNATEST | **🧬 Example 11: DNA Test Results – Match Comparison & Genotype Report**<br>A pair of `TEMPLATE`s modeling both a DNA match comparison report, using `FLEX` entries for shared segments and relationship estimates. And a direct genotype report. Includes `STICKY` for the match report (`ASSET`), uses `ADDRPLUS` for lab and test center contacts, and demonstrates `FLEX ARRAY` for tabular genotype values. Shared entities like individuals are reused across both reports. |
+| [🛖 Example 12](#🛖-example-12-norwegian-farm-membership) | RESIDENCE, FARM-OCCU | **🛖 Example 12: Norwegian Farm Membership**<br>This example demonstrates how to use a `GROUP` record to represent **a traditional Norwegian farm** in a historical context (Lien Farm Census, 1832, Valdres, Norway), and how to associate both family and non-family individuals with that group using `STICKY` roles like `LEADER`, `MEMBER`, `WORKER`, and `RESIDENT`. |
+| [🏥 Example 13](#🏥-example-13-hospital-admission-and-discharge-record) | MEDICAL, ADMISSION and DISCHARGE | **🏥 Example 13: Hospital Admission and Discharge Record**<br>Two `TEMPLATE`s modeling a patient's hospital stay in 1933 for acute appendicitis. An admission and a discharge `TEMPLATE`. Shows the hospital as an organization and roles like `PATIENT`, `PHYSICIAN`, and `SITE` (for the hospital itself), with `FLEX`, `SPLAC`, and a scanned source register. |
+| [🛠️ Example 14](#🛠️-example-14-mid-century-employment-transfer-order) | OCCUPATIONAL, EMPLOYMENT | **🛠️ Example 14: Mid Century Employment Transfer Order**<br>This `TEMPLATE` records the formal transfer of employee Gertrude Elmsbottom from the Leiden Branch to the Rotterdam HQ of Western Office Supplies Co. in 1954. Includes `STICKY` records for the employee, both originating and receiving workplaces, and the issuing officer. Demonstrates `EMPLOYER` roles for organizations, sequential `OCCU` facts for old and new positions, structured `FLEX DESCRIPT` for the new job title, and integration of `SOURCE` with scanned memo evidence. |
+| [🧾 Example 15](#🧾-example-15-legal-will-creation-and-execution-with-estate-transfers) | DEATH, WILL | **🧾 Example 15: Legal Will Creation and Execution with Estate Transfers**<br>This dual-`TEMPLATE` example models the two-stage legal will process for Emil Rothenbühler: will creation (while alive) and will execution (after death). It includes `STICKY`s for the decedent across both stages, a notary, legal executor, multiple heirs, and detailed `TRANSFER` structures for assets. Also demonstrates `FLEX VALUE` for appraisal, `SHARE` for proportional distribution, and a realistic asset division process. Includes dedicated `STICKY` and `TRANSFER` for each asset to track inheritance lineage and value allocation. |
+| [⚔️ Example 16](#⚔️-example-16-historical-title-and-nobility-inheritance) | DEATH, WILL, Title | **⚔️ Example 16:  Historical Title and Nobility Inheritance**<br>This `TEMPLATE` models the inheritance of a noble title and estate following the death of a titled individual. Features include a `STICKY` for the title holder, an heir receiving both property and title, symbolic artifacts, and a ruling monarch confirming the transfer. Demonstrates `TITLE, Baron`, land size, annotations, and an `ASSET` history of previous holders. Includes a dedicated `STICKY` and `TRANSFER` for the title itself (`ROLE DIGNITY`), showing how titles can be modeled as independent assets with full lineage tracking.
+| [🛡️ Example 17](#🛡️-example-17-guild-membership-certificate) | GROUP, GUILD-MEM | **🛡️ Example 17: Guild Membership Certificate**<br>Guild admission certificate for John Smith in 1702 London, issued by the Worshipful Company of Blacksmiths in London, including the original oath and rights text<br>(“Be it knowne unto all men by these presentes…”),<br>modeled as both `TEMPLATE` event and asset `STICKY`. Includes structured membership details. |
+[⚖️ Example 18](#⚖️-example-18-court-trial-record-humorous-fictional-case) | LEGAL, JUDGMENT | **⚖️ Example 18: Court Trial Record – Humorous Fictional Case**<br>Illustrates a fictional court trial modeled in GEDCOM 8, focusing on the use of `STICKY` roles in legal records. Includes `ROLE` types like `DEFENDANT`, `JUDGE`, `JURY FOREMAN`, and `WITNESS`, showing how to link individuals to a single `TEMPLATE`. Playfully absurd, but structurally correct. |
+| [🪦 Example 19](#🪦-example-19-gravestone-with-named-and-implied-persons) | MEMORIAL, GRAVESTONE | **🪦 Example 19: Gravestone with Named and Implied Persons**<br>Shows multiple individuals on a shared tombstone: two named (with roles `MAIN` and `WIDOW`) and two implied (`CHILD`, `GRANDCHILD`). Includes annotations, a Bible verse, estimated marriage date, and `QUAY` levels. `TEMPLATE` has `1 TORIGIN ORIGDOC, INCOMPLETE` |
+
+
+
+
+
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+
+---
+
+<a name="example-01"></a>  
+## 💍 Example 01: "Wedding Certificate with Family Necklace Transfer  
+
+This example demonstrates a marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. 
+
+- It shows how **`ASSET`** types and **`FLEX`** entries can be used to capture contextual information about assets involved in life events.
+- The `STICKY`'s in this example have a lot of Tags: like NAME, BIRT, MARR, OCCU, RELI and more. This clearly shows the function of a `STICKY`, it holds **all information** that can be derived from a certain event, or `TEMPLATE`.
+- The `MARR` tag is only present in the `STICKY` of the bride and the groom, as it is their marriage. It is **not present** in the other `STICKY`s. They attend the marriage, but it is not theirs.
+
+**💍 @T0042@ – Wedding Certificate with Family Necklace Transfer**
+```gedcom
+0 @T0042@ TEMPLATE
+1 TYPE MARRIAGE, CIVIL
+1 TITL Wedding Certificate Springfield
+2 PHRASE Wedding "Certificate with Family Necklace Transfer"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 SPLAC @SP0085@              /* Springfield, Illinois, USA */
+1 MARR                        /* MARR tag is official tag for marriage */
+2 DATE 18 JUN 1954            /* Date of marriage */
+2 SPLAC @SP0521@              /* Springfield, Illinois, USA */
+1 ROLES
+2 STICKY @ST0142@             /* MAIN, BRIDE */
+2 STICKY @ST0143@             /* MAIN, GROOM */
+2 STICKY @ST0241@             /* FATHER, BRIDE Father of the Bride */
+2 STICKY @ST0242@             /* MOTHER, GROOM, Mother of the Groom */
+2 STICKY @ST0341@             /* UNCLE, BRIDE, Uncle of the Bride */
+2 STICKY @ST0342@             /* FRIEND, GROOM, Friend of the Groom */
+2 STICKY @ST0441@             /* OFFICIANT of the Marriage */
+2 STICKY @ST0541@             /* JEWELRY, NECKLACE, Family Necklace */
+1 TRANSFER @ST0541@           /* Transferred: JEWELRY, NECKLACE, Family Necklace */
+1 GRANTOR @ST0241@            /* GRANTOR: FATHER, BRIDE  */
+1 GRANTEE @ST0142@            /* GRANTEE: MAIN, BRIDE  */
+1 CITA
+2 SOUR @S0371@
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 CREA 20 JUL 2025
+1 CHAN 29 APR 2025
+```
+**👰‍♀️ @ST0142@ STICKY – Bride**
+```gedcom
+0 @ST0142@ STICKY
+1 TYPE PERSON
+1 TITL "Emily Johnson, bride"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE MAIN, BRIDE
+1 NAME
+2 FORM Emily Johnson
+2 PART Emily
+3 TYPE GIVN
+2 PART Johnson
+3 TYPE SURN
+1 SEX F
+1 BIRT
+2 DATE 2 OCT 1930
+2 SPLAC @SP0521@              /* Springfield, Illinois, USA */
+1 MARR                        /* MARR tag now inside the STICKY of the bride !! */
+2 DATE 18 JUN 1954
+2 SPLAC @SP006@               /* Springfield */
+1 RELI Protestant             /* relifion was only mentioned for the bride */
+1 OCCU "Librarian (who secretly reshelves alphabet soup cans for fun)"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🤵 @ST0143@ STICKY – Groom**
+```gedcom
+0 @ST0143@ STICKY
+1 TYPE PERSON
+1 TITL "Robert Green, groom"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE MAIN, GROOM
+1 NAME
+2 FORM Robert Green
+2 PART Robert
+3 TYPE GIVN
+2 PART Green
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 18 JAN 1929
+2 SPLAC @SP006@               /* Edinburg */
+1 MARR                        /* MARR tag now inside the STICKY of the groom !! */
+2 DATE 18 JUN 1954
+2 SPLAC @SP006@               /* Springfield */
+1 RESI                        /* Address was only mentioned for the groom */
+2 ADDR Mainstreet
+3 CITY Springfield, ILL, USA
+2 NOTE "Repair specialist, third class."
+1 OCCU "Accordion repair technician (self-taught)"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**👨‍🦳 @ST0241@ STICKY – Father of the Bride**
+```gedcom
+0 @ST0241@ STICKY
+1 TEMPLATE @T0042@
+1 TITL "Harold Johnson, Father of the Bride"
+1 SUBM @B001@
+1 TYPE PERSON
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE FATHER, BRIDE
+1 NAME
+2 FORM Harold Johnson
+2 PART Harold
+3 TYPE GIVN
+2 PART Johnson
+3 TYPE SURN
+1 SEX M
+1 AGE 58
+1 OCCU "Professional coffee reheater (retired)"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**👩‍🦳 @ST0242@ STICKY – Mother of the Groom**
+```gedcom
+0 @ST0242@ STICKY
+1 TYPE PERSON
+1 TITL "Margaret Green, Mother of the Groom"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE MOTHER, GROOM
+1 NAME
+2 FORM Margaret Green
+2 PART Margaret
+3 TYPE GIVN
+2 PART Green
+3 TYPE SURN
+1 SEX F
+1 AGE 60
+1 OCCU "Former opera critic (known for falling asleep during Act II)"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**👨‍🦰 @ST0341@ STICKY – Uncle of the Bride**
+```gedcom
+0 @ST0341@ STICKY
+1 TYPE PERSON
+1 TITL "Temperance McKinley, Uncle of the Bride"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE UNCLE, BRIDE
+1 NAME
+2 FORM Temperance McKinley
+2 PART Temperance
+3 TYPE GIVN
+2 PART McKinley
+3 TYPE SURN
+1 SEX M
+1 AGE 55
+1 OCCU "Inventor of the silent kazoo (never caught on)"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🧑‍🦱 @ST0342@ STICKY – Friend of the Groom**
+```gedcom
+0 @ST0342@ STICKY
+1 TYPE PERSON
+1 TITL "Jingle Bell, Friend of the Groom"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE FRIEND, GROOM
+1 NAME
+2 FORM Jingle Bell
+2 PART Jingle
+3 TYPE GIVN
+2 PART Bell
+3 TYPE SURN
+1 SEX M
+1 AGE 26
+1 OCCU "Amateur philosopher (mostly at the pub)"
+1 NOTE "Claims to be the best man, but no one asked him."
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🧑‍⚖️ @ST0441@ STICKY – Officiant**
+```gedcom
+0 @ST0441@ STICKY
+1 TYPE PERSON
+1 TITL "Mayor Winifred Spoon, Officiant"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 ROLE OFFICIANT
+1 NAME
+2 FORM Mayor Winifred Spoon
+2 PART Winifred
+3 TYPE GIVN
+2 PART Spoon
+3 TYPE SURN
+1 SEX F
+1 OCCU "Mayor and amateur wedding poet"
+1 NOTE "Performed the ceremony in rhyme. No one asked for that either."
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**💍 @ST0541@ STICKY – Wedding Necklace (Transferred Gift)**
+```gedcom
+0 @ST0541@ STICKY
+1 TYPE JEWELRY, NECKLACE "Victorian Silver Necklace with blue topaz"
+1 TITL "Wedding Necklace"
+1 SUBM @B001@
+1 TEMPLATE @T0042@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954            /* Event date of this TEMPLATE */
+1 FLEX DECIMAL, CURR, USD
+2 PHRASE "Value of the item"
+2 CONTENTS 185.00
+1 FLEX DESCRIPT
+ PHRASE "Description:"
+2 CONTENTS Victorian Silver Necklace with blue topaz
+1 FLEX MATERIAL
+2 PHRASE "Material it is made of"
+2 CONTENTS Silver
+1 NOTE "Passed down from Harold Johnson (father of the bride) to Emily Johnson on wedding day."
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-02"></a>  
+## 👧🏻 Example 02: International Adoption Certificate  
+
+This GEDCOM 8 example models an international adoption certificate, issued in 1992.  
+It includes the adoptive parents, the adopted child (born in another country), and the issuing authority.  
+
+The record captures the child's birth name and new adoptive name, the place of birth and adoption, and legal roles involved.
+This example reuses:
+- ROLE ADOPTIVE_PARENT, ROLE CHILD, ROLE ISSUER
+- FLEX DESCRIPT
+- NAME structure (as previously defined) With BIRTH name and ADOPTED name.
+- TEMPLATE TYPE CHILD, ADOPTION
+>- **`ADOP` is in the childs `STICKY` now**, and in the `TEMPLATE`, all info that used to go under the `ADOP` tag, now is in the `TEMPLATE` and the parents `STICKY`'s. 
+>- The adopted child is also added **to the `INDI` of both adopting parents!!** 
+>- **`PEDI`** is in the `TEMPLATE`. In this case it says the type of adoption is `ADOPTION`. But in case of an LDS sealing, the type of `PEDI` would be `SEALING`.
+
+The adoption certificate is stored in the @S0047@ source record with a digital scan link.
+    
+**👧🏻 @T0045@ – International Adoption Certificate**
+```gedcom
+0 @T0047@ TEMPLATE
+1 TYPE CHILD, ADOPTION, "Certificate of International Adoption"
+1 TITL Certificate of International Adoption 1985
+2 PHRASE "Adoption of Sofia Maria Petrova"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 MAR 1992
+1 SPLAC @SP0082@              /* The Hague, Netherlands */
+1 ADOP                        /* This is an Adoption Event! */
+2 DATE  12 MAR 1992
+2 SPLAC @SP0082@              /* The Hague, Netherlands */
+1 PEDI ADOPTED                /* Adoption of type Adopted */
+1 FLEX DESCRIPT
+2 PHRASE "Description"
+2 CONTENTS "Sofia Petrova was formally adopted by Johan de Waal and Marijke van Oosterhout on 12 March 1992."
+1 ROLES
+2 STICKY @ST0146@             /* This "replaces" in fact her real birth certificate */
+2 STICKY @ST0147@             /* MAIN, CHILD, ADOPTEE */
+2 STICKY @ST0247@             /* FATHER, ADOPTER */
+2 STICKY @ST0248@             /* MOTHER, ADOPTER */
+2 STICKY @ST0347@             /* ORGANIZATION, ISSUER (Adoption Court) */
+1 CITA
+2 SOURCE @S0047@              /* Adoption Certificate */
+2 TITL Certificate of International Adoption – Sofia Petrova
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🥈 @ST0146@ STICKY – Sofiya Mariya Stoyanova, real name at birth**
+```gedcom
+0 @ST0146@ STICKY             /* This "replaces/adds to" her real birth certificate */
+1 TYPE PERSON, AN_BIRTH       /* Annotated, as this TEMPLATE is about adoption */
+1 TEMPLATE @T0047@
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE MAIN, CHILD
+1 NAME
+2 TYPE BIRTH                  /* Name at birth, before adoption */
+2 FORM Sofiya Mariya Stoyanova
+2 PART Sofia
+3 TYPE GIVN
+2 PART Maria
+3 TYPE GIVN
+2 PART Petrova
+3 TYPE SURN
+1 SEX F
+1 BIRT
+2 DATE 5 MAY 1989
+2 SPLAC @SP0042@              /* Plovdiv, Bulgaria */
+1 FLEX DESCRIPT 
+2 PHRASE "Original name at birth"
+2 CONTENTS "Sofiya Mariya Stoyanova"
+1 NOTE "Renamed after adoption and given Dutch citizenship."
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🥈 @ST0147@ STICKY – Sofia Maria Petrova, adopted child**
+```gedcom
+0 @ST0147@ STICKY
+1 TYPE PERSON
+1 TEMPLATE @T0047@
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE MAIN, CHILD, ADOPTEE
+1 NAME
+2 TYPE ADOPTED                /* Name after adoption */
+2 FORM Sofia Maria Petrova
+2 PART Sofia
+3 TYPE GIVN
+2 PART Maria
+3 TYPE GIVN
+2 PART Petrova
+3 TYPE SURN
+1 ADOP                        /* This child is adopted */
+2 DATE  12 MAR 1992
+2 SPLAC @SP0082@              /* The Hague, Netherlands */
+1 PEDI ADOPTED                /* Adoption of type Adopted */
+2 DATE  12 MAR 1992
+2 SPLAC @SP0082@              /* The Hague, Netherlands */
+1 SEX F
+1 BIRT
+2 DATE 5 MAY 1989
+2 SPLAC @SP0042@              /* Plovdiv, Bulgaria */
+1 FLEX DESCRIPT 
+2 PHRASE "Original name at birth"
+2 CONTENTS "Sofiya Mariya Stoyanova"
+1 NOTE "Renamed after adoption and given Dutch citizenship."
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🥈 @ST0247@ STICKY – Johan de Waal, adopting father**
+```gedcom
+0 @ST0247@ STICKY
+1 TYPE PERSON
+1 TEMPLATE @T0047@
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE FATHER, ADOPTER
+1 NAME
+2 FORM Johan de Waal
+2 PART Johan
+3 TYPE GIVN
+2 PART de Waal
+3 TYPE SURN
+1 SEX M
+1 OCCU "Physics teacher and cheese enthusiast"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🥈 @ST0248@ STICKY – Marijke van Oosterhout, adopting mother**
+```gedcom
+0 @ST0248@ STICKY
+1 TYPE PERSON
+1 TEMPLATE @T0047@
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE MOTHER, ADOPTER
+1 NAME
+2 FORM Marijke van Oosterhout
+2 PART Marijke
+3 TYPE GIVN
+2 PART van Oosterhout
+3 TYPE SURN
+1 SEX F
+1 OCCU "Municipal librarian and puzzle queen"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**🥈 @ST0347@ STICKY – Hague District Family Court**
+```gedcom
+0 @ST0347@ STICKY
+1 TYPE ORGANIZATION, ADOPTIONAGENCY, "Hague District Family Court"
+1 TEMPLATE @T0047@
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE ISSUER
+1 NAME
+2 FORM Hague District Family Court
+1 NOTE "Authorized under the 1993 Hague Adoption Convention"
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**👤 INDI @I501@ for Sofia Maria Petrova**
+```gedcom
+0 @I501@ INDI
+1 NAME
+2 FORM Sofia Maria Petrova
+2 PART Sofia Maria
+3 TYPE GIVN
+2 PART Petrova
+3 TYPE SURN
+1 ROLES
+2 STICKY @ST0147@             /* ALL info is in the STICKY, No Longer in the INDI */
+1 CHAN 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**👤 INDI @I501@ for Marijke van Oosterhout**
+```gedcom
+0 @I502@ INDI                 /* The adopted child is ALSO added to the ROLES section of BOTH parents */
+1 NAME
+2 FORM Marijke van Oosterhout
+~ ~ ~
+1 ROLES
+2 STICKY @ST0147@             /* Sofia Maria Petrova, adopted child */
+1 CHAN 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**👤 INDI @I501@ for Johan de Waal**
+```gedcom
+0 @I503@ INDI                 /* The adopted child is ALSO added to the ROLES section of BOTH parents */
+1 NAME
+2 FORM Johan de Waal
+~ ~ ~
+1 ROLES
+2 STICKY @ST0147@             /* Sofia Maria Petrova, adopted child */
+1 CHAN 29 APR 2025
+1 CHAN 29 APR 2025
+```
+**💾 SOURCE for Adoption Certificate**
+```gedcom
+0 @S0047@ SOUR
+1 TITL Certificate of International Adoption – Sofia Petrova
+1 AUTH Hague District Family Court
+1 PUBL "Filed under case #INT-ADOP-92112"
+1 ABBR "Adoption Certificate – Sofia"
+1 DATA
+2 EVEN ADOP
+3 DATE 12 MAR 1992            /* Date of adoption */
+4 PHRASE "Certificate of international adoption of child born in Bulgaria"
+3 SPLAC @SP0008@              /* The Hague, Netherlands */
+2 AGNC Hague District Family Court
+~ ~ ~
+1 OBJE @O0321@                /* Scan of original Hague certificate */
+1 CHAN 29 APR 2025
+1 CHAN 13 AUG 2025
+```
+**💾 OBJE Scan of Adoption Certificate**
+```gedcom
+0 OBJE @O0321@                /* Multimedia record with file link  */
+1 FILE https://example.org/adoptions/petrova-1992.pdf
+2 FORM application/pdf
+2 TITL Scan of original Hague certificate
+1 CREA 29 APR 2025
+1 CHAN 29 APR 2025
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-03"></a>  
+## 🍼 Example 03: Medical Birth Certificate
+
+This example has a birth certificate of a child born in a hospital.
+- With father, mother, doctor and nurse `STICKY`'s.
+- The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. 
+- The `TEMPLATE` has a lot of info in the `CITA` structure.
+- The childs `STICKY` is also added to the `INDI` of both his parents !!
+
+```gedcom
+0 @T1020@ TEMPLATE
+1 TYPE CHILD, BIRTH, Medical
+1 TITL Medical Birth Certificate from St. Mary's Hospital, London
+2 PHRASE Birth certificate of David Michael Johnson with medical details 
+1 SUBM @B0003@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 5 MAY 1915             /* Date of the document */
+1 SPLAC @SP042@               /* St. Mary's Hospital, London, England */
+2 NOTE Hospital Birth Record
+1 BIRT                        /* event this TEMPLATE is about */
+2 DATE 5 MAY 1915
+2 SPLAC @SP042@               /* St. Mary's Hospital, London, England */
+1 ROLES
+2 STICKY @ST9201@             /* MAIN, CHILD: Baby David Michael Johnson */
+2 STICKY @ST9202@             /* MOTHER: Susan Johnson */
+2 STICKY @ST9203@             /* FATHER: Michael Johnson */
+2 STICKY @ST9204@             /* DOCTOR, WITNESS: Attending Physician: Dr. John Pricklebone */
+2 STICKY @ST9205@             /* NURSE, WITNESS: Nurse Wiggle */
+1 CITA
+2 SOUR @S0444@                /* St. Mary's Hospital Birth Register */
+2 PAGE Volume 12, Entry 449B
+2 DATA
+3 DATE 5 MAY 1915
+3 TEXT “Infant David Michael Johnson born to Susan Johnson”
+4 MIME text/plain
+4 LANG en
+2 AUTHOR St. Mary's Hospital
+2 TITL Birth Register, 1910–1920
+2 DATES
+3 RECORDED 5 MAY 1915
+2 TEXTDISPLAY “St. Mary's Hospital Birth Register, Vol 12, Entry 449B”
+2 TRANSCRIPT “Infant David Michael Johnson born 5 May 1915 to Susan Johnson, attended by Dr. John Pricklebone and nurse Wiggle.”
+2 FORMAT
+3 TYPE image/jpeg
+2 URL https://archive.londonhospitals.uk/stmarys/births/vol12-entry449B.jpg
+2 LANGUAGE en
+2 RECORDID NHS-BR-STMARYS-449B
+2 CONTAINER Hospital Archives Division
+2 ITEMTYPE Medical Birth Record
+2 SHORTTITLE St. Mary's Births 1915
+2 WWWLINK
+3 VALUE https://nhs.uk/birthrecords/stmarys1915
+2 QUAY 3
+2 OBJE @O1020@               /* Scanned certificate image */
+1 CREA 20 JUL 2025
+1 CHAN 25 JUL 2025
+```
+**🧑🏼 @I0537@ INDI – David Michael Johnson**
+```gedcom
+0 @I0537@ INDI                /* David Michael Johnson, MAY 5 1915 */
+1 NAME
+2 FORM David Michael Johnson
+~ ~ ~
+1 SEX M
+1 ROLES
+2 STICKY @ST9201@             /* Birth with roles - MAIN, CHILD */
+```
+**👶 @ST9201@ STICKY – Baby David Michael Johnson**
+```gedcom
+0 STICKY @ST9201@             /* Many FLEXes for non GEDCOM information */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1020@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM David Michael Johnson
+~ ~ ~
+1 BIRT
+2 DATE 5 MAY 1915
+2 SPLAC @0006@                /* St. Mary's Hospital, London, England */
+1 DATE 5 MAY 1915
+2 TIME 04:32                  /* Time of bearth */
+1 FLEX DESCRIPT
+2 PHRASE "Room/Ward of birth"
+2 CONTENTS "Maternity Ward, Room 12B"
+1 FLEX DECIMAL
+2 PHRASE "Weight at Birth in kg"
+2 CONTENTS 3.2
+1 FLEX INTEGER
+2 PHRASE "Length at Birth in cm"
+2 CONTENTS 50
+1 FLEX DESCRIPT
+2 PHRASE "Type of Birth"
+2 CONTENTS "Single"
+1 FLEX DESCRIPT
+2 PHRASE "Birth Complications"
+2 CONTENTS "None"
+1 FLEX INTEGER
+2 PHRASE "APGAR Score at 1 Minute"
+2 CONTENTS 9
+1 FLEX INTEGER
+2 PHRASE "APGAR Score at 5 Minutes"
+2 CONTENTS 10
+~ ~ ~
+```
+**👩🏻‍🦱 @ST9201@ STICKY – Mother Susan Johnson**
+```gedcom
+0 @ST9202@ STICKY             /* Mother Susan Johnson */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1020@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 AGE 32
+1 OCCU Housewife
+1 ROLE MOTHER
+1 NAME
+2 FORM Susan Johnson
+~ ~ ~
+```
+**👨🏼‍🦰 @ST9201@ STICKY – Father Michael Johnson**
+```gedcom
+0 @ST9203@ STICKY             /* Father Michael Johnson */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1020@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 AGE 35
+1 OCCU Farmer
+1 ROLE FATHER
+1 NAME
+2 FORM Michael Johnson
+~ ~ ~
+```
+**🧑🏼 @I0537@ INDI – David Michael Johnson**
+```gedcom
+0 @I0537@ INDI                /* David Michael Johnson, MAY 5 1915 */
+1 NAME
+2 FORM David Michael Johnson
+~ ~ ~
+1 SEX M
+1 ROLES
+2 STICKY @ST9201@             /* Birth with roles - MAIN, CHILD */
+```
+**👩🏻‍🦱🧑🏼 @I0537@ INDI – Mother Susan Johnson, baby David added to her ROLES section**
+```gedcom
+0 @I0538@ INDI                /* Mother Susan Johnson */
+1 NAME
+2 FORM David Michael Johnson
+~ ~ ~
+1 SEX M
+1 ROLES
+2 STICKY @ST9201@             /* Baby David Michael Johnson */
+```
+**👨🏼‍🦰 @I0537@ INDI – Father Michael Johnson, baby David added to her ROLES section**
+```gedcom
+0 @I0539@ INDI                /* Father Michael Johnson */
+1 NAME
+2 FORM David Michael Johnson
+~ ~ ~
+1 SEX M
+1 ROLES
+2 STICKY @ST9201@             /* Baby David Michael Johnson */
+```
+**🩺 @ST9201@ STICKY – Attending Physician: Dr. John Pricklebone**
+```gedcom
+0 @ST9204@ STICKY             /* Attending Physician */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1020@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE DOCTOR, WITNESS
+1 NAME
+2 FORM Dr. John Pricklebone
+~ ~ ~
+```
+**👩‍⚕️ @ST9201@ STICKY – Nurse: Nurse Wiggle**
+```gedcom
+0 @ST9205@ STICKY             /* Nurse Witness */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1020@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE NURSE, WITNESS
+1 NAME
+2 FORM Nurse Wiggle
+~ ~ ~
+```
+**📚 SOURCE block — St. Mary’s Hospital Birth Register**
+```gedcom
+0 @S0444@ SOUR
+1 TITL Birth Register of St. Mary's Hospital, London (1910–1920)
+1 AUTH St. Mary's Hospital
+1 PUBL Hospital Archives Division, London NHS Trust
+1 ABBR St. Mary's Birth Register
+1 TEXT Original handwritten entries for births occurring at the hospital, Recorded by attending staff at time of birth
+1 DATA
+~ ~ ~
+1 REPO @R0001@
+2 CALN A32 756 nr3
+3 MEDI ELECTRONIC
+4 PHRASE Image/jpg
+1 NOTE Register includes birth records with medical annotations and attending staff signatures.
+```
+**🖼️ OBJE block — Scanned certificate image**
+```gedcom
+0 @O1020@ OBJE
+1 FILE https://archive.londonhospitals.uk/stmarys/births/vol12-entry449B.jpg
+2 FORM image/jpeg
+3 MEDI Image
+2 TITL Scanned Birth Register Entry for David Michael Johnson, 5 MAY 1915
+1 NOTE Digitized from St. Mary's Hospital Birth Register, volume 12.
+```
+**🏛️ REPO block — Hospital Archives**
+```gedcom
+0 @R0001@ REPO
+1 NAME Hospital Archives Division, London NHS Trust
+1 ADDR 221B Baker Street
+2 CITY London
+2 POST NW1 6XE
+2 CTRY United Kingdom
+1 EMAIL archives@londonhospitals.uk
+1 WWW https://londonhospitals.uk/archives
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+
+
+---
+
+<a name="example-04"></a>  
+## 💍🧒 Example 04: Wedding with step children from both sides  
+
+### 🧾 Example: A Dual Blended Family Marriage
+
+This example models a remarriage where both spouses bring two children from prior relationships.  
+Each child is marked as a `STEPCHILD` **to the new spouse**, and the marriage `TEMPLATE` shows all relevant relationships.
+
+**Included in this example:**
+- 1 `TEMPLATE`
+- 7 `STICKYs` (bride, groom, 4 children, registrar)
+- 7 `INDI` records
+
+**Notes:**
+- `INDI` records of the children list the `STICKY` they gain from this marriage (`TEMPLATE`),  
+  but also include earlier `STICKYs` such as their births.
+- The birth `STICKY` of each child connects them to their original birth parents.
+- **Those earlier `TEMPLATE`s are not shown in this example**.
+- Each child has a `ROLE` looking like this: `1 ROLE CHILD2, STEPCHILD, GROOM`. This `STICKY` will also be linked into the `ROLES` section of the child itself. Now looking at that `ROLE` from inside the `STICKY` in the `INDI` of the child, one could say this is the `GROOM` itself, but thats not possible, as the real `GROOM` of a marriage **always** has a `MAIN` in its `ROLE` line.<br>And this child has not! So the child is somehow related to the `GROOM`, **but is not the `GROOM` himself.**
+-**All children own and stepchildren** are mentioned in the `ROLES`section of their parents.
+- As the registrar of this marriage is only mentioned in a sidenote, and apparantly not officially on this cerificate, his `STICKY` is of type `PERSON, AN_MENTION`.
+
+**📜 @T09901@ TEMPLATE – Marriage of Johanna van Loon & Willem de Zwart**
+```gedcom
+0 @T09901@ TEMPLATE
+1 TYPE MARRIAGE, CIVIL
+1 TITL Standard Dutch Marriage Certificate (1823-1890)
+2 PHRASE "Marriage Certificat of Johanna van Loon and Willem de Zwart, JUNE 15 1888, Delft "
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 15 JUN 1888
+1 SPLAC @SP006@               /* Delft Town Hall, Netherlands */
+1 MARR                        /* MARR tag also in TEMPLATE */
+2 DATE 15 JUN 1888
+2 SPLAC @SP006@               /* Delft Town Hall, Netherlands */
+1 ROLES
+2 STICKY @ST1010@ /* ROLE MAIN, BRIDE — Johanna van Loon */
+2 STICKY @ST1011@ /* ROLE MAIN, GROOM — Willem de Zwart */
+2 STICKY @ST1012@ /* ROLE CHILD1, STEPCHILD, GROOM — Anna van Loon (bride’s daughter) */
+2 STICKY @ST1013@ /* ROLE CHILD2, STEPCHILD, GROOM — Bastiaan van Loon (bride’s son) */
+2 STICKY @ST1014@ /* ROLE CHILD3, STEPCHILD, BRIDE — Lisette de Zwart (groom’s daughter) */
+2 STICKY @ST1015@ /* ROLE CHILD4, STEPCHILD, BRIDE — Marius de Zwart (groom’s son) */
+2 STICKY @ST1016@ /* ROLE REGISTRAR — Bastiaan van den Akten */
+1 FLEX ANNOTATION
+2 PHRASE Note added later.
+2 CONTENTS Amb. Burg.Stand is Bastiaan van den Akten
+3 LANG nl
+1 CITA
+2 SOUR @S0373@
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 NOTE "Marriage between Johanna and Willem. Both brought children from previous relationships."
+```
+**👩🏻 @ST1010@ STICKY – MAIN, BRIDE, Johanna van Loon**
+```gedcom
+0 @ST1010@ STICKY             /* MAIN, BRIDE, Johanna van Loon */
+1 TYPE PERSON
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 SPLAC @SP006@               /* Delft Town Hall, Netherlands */
+1 ROLE MAIN, BRIDE
+1 NAME
+2 FORM Johanna van Loon
+~ ~ ~
+1 AGE 38
+1 SEX F
+1 MARR                        /* MARR tag now in STICKY */
+2 DATE 15 JUN 1888
+2 SPLAC @SP006@               /* Delft Town Hall, Netherlands */
+1 RESI
+2 DATE BEF 1888               /* Residence at time of marriage */
+2 SPLAC @SP042@               /* Delft, NH, Netherlands */
+1 NOTE "Bride, widow with two children from earlier marriage."
+```
+**👨🏻 @ST1011@ STICKY – MAIN, GROOM, Willem de Zwart**
+```gedcom
+0 @ST1011@ STICKY             /* MAIN, GROOM, Willem de Zwart */
+1 TYPE PERSON
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 ROLE MAIN, GROOM
+1 NAME
+2 FORM Willem de Zwart
+~ ~ ~
+1 AGE 40
+1 MARR                        /* MARR tag now in STICKY */
+2 DATE 15 JUN 1888
+2 SPLAC @SP006@               /* Delft Town Hall, Netherlands */
+1 RESI
+2 DATE BEF 1888               /* Residence at time of marriage */
+2 SPLAC @SP042@               /* Delft, NH, Netherlands */
+1 NOTE "Groom, widower with two children from earlier marriage."
+```
+**🧒🏻 @ST1012@ STICKY – CHILD1, STEPCHILD, GROOM – Anna van Loon**
+```gedcom
+0 @ST1012@ STICKY             /* Anna van Loon - CHILD1, STEPCHILD, GROOM  */
+1 TYPE PERSON
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 ROLE CHILD1, STEPCHILD, GROOM
+1 NAME
+2 FORM Anna van Loon
+~ ~ ~
+1 AGE 12
+1 NOTE "Daughter of Johanna; became stepchild of Willem upon marriage."
+```
+**👦🏻 @ST1013@ STICKY – CHILD2, STEPCHILD, GROOM – Bastiaan van Loon**
+```gedcom
+0 @ST1013@ STICKY             /* Bastiaan van Loon - CHILD2, STEPCHILD, GROOM  */
+1 TYPE PERSON
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 ROLE CHILD2, STEPCHILD, GROOM
+1 NAME
+2 FORM Bastiaan van Loon
+1 AGE 9
+1 NOTE "Son of Johanna; became stepchild of Willem upon marriage."
+```
+**👧🏻 @ST1014@ STICKY – CHILD3, STEPCHILD, BRIDE – Lisette de Zwart**
+```gedcom
+0 @ST1014@ STICKY             /* Lisette de Zwart - CHILD3, STEPCHILD, BRIDE  */
+1 TYPE PERSON
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 ROLE CHILD3, STEPCHILD, BRIDE
+1 NAME
+2 FORM Lisette de Zwart
+~ ~ ~
+1 AGE 10
+1 NOTE "Daughter of Willem; became stepchild of Johanna upon marriage."
+```
+**👦🏼 @ST1015@ STICKY – CHILD4, STEPCHILD, BRIDE – Marius de Zwart**
+```gedcom
+0 @ST1015@ STICKY             /* Marius de Zwart - CHILD4, STEPCHILD, BRIDE  */
+1 TYPE PERSON
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 ROLE CHILD4, STEPCHILD, BRIDE
+1 NAME
+2 FORM Marius de Zwart
+~ ~ ~
+1 AGE 7
+1 NOTE "Son of Willem; became stepchild of Johanna upon marriage."
+```
+**🧾 @ST1016@ STICKY – REGISTRAR – Bastiaan van den Akten**
+```gedcom
+0 @ST1016@ STICKY             /* REGISTRAR, Bastiaan van den Akten */
+1 TYPE PERSON, AN_MENTION
+1 TEMPLATE @T09901@
+1 DATE 15 JUN 1888
+1 ROLE REGISTRAR
+1 NAME
+2 FORM Bastiaan van den Akten
+~ ~ ~
+1 NOTE "Official registrar recording the marriage."
+```
+### INDI records for all people
+
+**👩🏻‍🦰 @I1010@ INDI – Johanna van Loon**
+```gedcom
+0 @I1010@ INDI                /* Johanna van Loon, Bride, widow, kids: Anna and Bastiaan */
+1 NAME
+2 FORM Johanna van Loon
+~ ~ ~
+1 ROLES
+1 STICKY @ST0800@             /* Marriage to her former husband */
+1 STICKY @ST0953@             /* Birth of her own child: Anna van Loon */
+1 STICKY @ST0999@             /* Birth of her own child: Bastiaan van Loon */
+1 STICKY @ST1010@             /* Here she is: MAIN, BRIDE, when she marries Willem de Zwart */
+1 STICKY @ST1014@             /* After marriage becomes stepmom of: Lisette de Zwart */
+2 STICKY @ST1015@             /* After marriage becomes stepmom of: Marius de Zwart */
+~ ~ ~
+```
+**👨🏻‍🦰 @I1011@ INDI – Willem de Zwart**
+```gedcom
+0 @I1011@ INDI                /* Willem de Zwart, Groom, widower, kids: Lisette and Marius */
+1 NAME
+2 FORM Willem de Zwart
+~ ~ ~
+1 ROLES
+1 STICKY @ST0800@             /* Marriage to his former wife */
+1 STICKY @ST0853@             /* Birth of his own child: Lisette de Zwart */
+1 STICKY @ST0899@             /* Birth of his own child: Marius de Zwart */
+1 STICKY @ST1011@             /* Here he is: MAIN, GROOM, when he marries Johanna van Loon */
+1 STICKY @ST1012@             /* After marriage becomes stepdad of: Anna van Loon */
+2 STICKY @ST1013@             /* After marriage becomes stepdad of: Bastiaan van Loon */
+~ ~ ~
+```
+**👧🏻 @I1012@ INDI – Anna van Loon**
+```gedcom
+0 @I1012@ INDI                /* Anna van Loon, Johanna's daughter */
+1 NAME
+2 FORM Anna van Loon
+~ ~ ~
+1 ROLES
+2 STICKY @ST0951@             /* Birth of Anna */
+2 STICKY @ST1012@             /* CHILD1, STEPCHILD, GROOM, Anna van Loon */
+~ ~ ~
+```
+**👦🏻 @I1013@ INDI – Bastiaan van Loon**
+```gedcom
+0 @I1013@ INDI                /* Bastiaan van Loon, Johanna's son */
+1 NAME
+2 FORM Bastiaan van Loon
+~ ~ ~
+1 ROLES
+2 STICKY @ST0998@             /* Birth of Bastiaan */
+2 STICKY @ST1013@             /* CHILD2, STEPCHILD, GROOM, Bastiaan van Loon */
+~ ~ ~
+```
+**👧🏻 @I1014@ INDI – Lisette de Zwart**
+```gedcom
+0 @I1014@ INDI                /* Lisette de Zwart, Willem's daughter */
+1 NAME
+2 FORM Lisette de Zwart
+~ ~ ~
+1 ROLES
+2 STICKY @ST0805@             /* Birth of Lisette */
+2 STICKY @ST1014@             /* CHILD3, STEPCHILD, BRIDE, Lisette de Zwart */
+~ ~ ~
+```
+**👦🏼 @I1015@ INDI – Marius de Zwart**
+```gedcom
+0 @I1015@ INDI                /* Marius de Zwart, Willem's son */
+1 NAME
+2 FORM Marius de Zwart
+~ ~ ~
+1 ROLES
+2 STICKY @ST0823@             /* Birth of Marius */
+2 STICKY @ST1015@             /* CHILD4, STEPCHILD, BRIDE, Marius de Zwart */
+~ ~ ~
+```
+**📋 @I1016@ INDI – Bastiaan van den Akten**
+```gedcom
+0 @I1016@ INDI                /* Bastiaan van den Akten, Registrar */
+1 NAME
+2 FORM Bastiaan van den Akten
+~ ~ ~
+1 ROLES
+2 STICKY @ST1016@             /* REGISTRAR at the marriage of Johanna and Willem */
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-05"></a>  
+## 🧮 Example 05: Census with Annotated Events
+
+Imagine: a 1920 household census in Boston, featuring:  
+- One multigenerational household (parents, kids, orphaned niece, maid, boarder, grandfather)  
+- A live-in maid who arrived later, with annotated recommendation from bishop
+- Several annotated events: death, departure, name alias, marriage  
+- Lots of `FLEX` for page-level and person-specific details  
+- All roles defined using `STICKY` + annotations (no `INDI` records)
+- Uses special `FLEX` type `ANNOTATION` for all annotated notes in the census. That way user/software can decide to print these annotations or not.
+
+**📜 @T1920@ TEMPLATE – 1920 household census in Boston**
+```gedcom
+0 @T1920@ TEMPLATE
+1 TYPE RESIDENCE, POPCENSUS   /* PopulationCensus */
+1 TITL 1920 US Federal Census – Deduction Household
+2 PHRASE Household census, with later annotations in margins.
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 01 JAN 1920
+1 SPLAC @SP1000@              /* Boston, Suffolk County, Massachusetts, USA */
+1 CENS                        /* Event of the TEMPLATE */
+2 TYPE Population
+2 DATE 01 JAN 1920
+2 SPLAC @SP1000@              /* Boston, Suffolk County, Massachusetts, USA */
+2 ADDR
+3 123 Main Street
+3 CITY Boston
+3 STAE MA
+3 CTRY USA
+1 FLEX REGNUMBER
+2 PHRASE Dwelling Number
+2 CONTENTS 17A
+1 FLEX REGNUMBER
+2 PHRASE Household ID
+2 CONTENTS 4
+1 FLEX ADDRESS
+2 PHRASE Street and number
+2 CONTENTS 123 Main Street
+1 FLEX DESCRIPT
+2 PHRASE Page note
+2 CONTENTS "Top margin: 'Subdistrict 7A, Sheet 3A, Supervisor: E. Snoreworthy'"
+1 ROLES
+2 STICKY @ST0100@             /* Barnabas Deduction –  MAIN, HEAD, RESIDENT */
+2 STICKY @ST0101@             /* Penny Deduction – SPOUSE, RESIDENT */
+2 STICKY @ST0102@             /* Orville Deduction – Son - CHILD, RESIDENT */
+2 STICKY @ST0103@             /* Edwina Deduction – Daughter - CHILD, RESIDENT */
+2 STICKY @ST0104@             /* Willa Tinywhistle – Orphaned Niece - NIECE, RESIDENT */
+2 STICKY @ST0105@             /* Augustus Deduction – Grandfather */
+2 STICKY @ST0106@             /* Mabel Scrubbs – Live-in Maid - MAID, RESIDENT */
+2 STICKY @ST0107@             /* Augustus Crumb - BOARDER, RESIDENT */
+2 STICKY @ST0110@             /* Edwina's DEPARTURE - AN_LEAVE */
+2 STICKY @ST0111@             /* Willa's ARRIVAL */
+2 STICKY @ST0112@             /* Augustus's DEATH - AN_DEATH */
+2 STICKY @ST0113@             /* Mabel's ARRIVAL */
+2 STICKY @ST0114@             /* Barnabas's NAME ALIAS */
+2 STICKY @ST0115@             /* Penny's MARRIAGE annotation */
+1 NOTE Census household appears orderly. Marginal note mentions: "Excellent curtains."
+1 CITA
+2 SOUR @S0374@
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 CREA 18 JUL 2025
+1 CHAN 18 JUL 2025
+```
+### 🏠 Household Members
+
+**🧓 @ST0026@ STICKY – Head of Household: Barnabas Deduction**
+```gedcom
+0 @ST0100@ STICKY             /* Barnabas Deduction: Head of Household */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE MAIN, FAMILYHEAD, RESIDENT
+1 NAME
+2 TYPE BIRTH                  /* Name at birth */
+2 FORM Barnabas Deduction
+2 PART Barnabas
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 12 JUN 1878
+2 SPLAC @SP1001@              /* Concord, New Hampshire */
+1 OCCU Tailor
+1 RELI Unitarian
+1 CENS
+2 TYPE Population
+2 DATE 01 JAN 1920
+2 SPLAC @SP1000@              /* Boston, Suffolk County, Massachusetts, USA */
+2 ADDR
+3 123 Main Street
+3 CITY Boston
+3 STAE MA
+3 CTRY USA
+~ ~ ~
+```
+**👩 @ST0027@ STICKY – Wife: Penny Deduction**
+```gedcom
+0 @ST0101@ STICKY             /* Penny Deduction: Wife */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE SPOUSE, RESIDENT
+1 NAME
+2 FORM Penny Deduction
+2 PART Penny
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 SEX F
+1 BIRT
+2 DATE 03 FEB 1880
+2 SPLAC @SP1002@              /* Medford, MA */
+1 OCCU Seamstress
+1 RELI Methodist
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🧒 @ST0028@ STICKY – Son: Orville Deduction**
+```gedcom
+0 @ST0102@ STICKY             /* Orville Deduction: Son */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE CHILD, RESIDENT
+1 NAME
+2 FORM Orville Deduction
+2 PART Orville
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 19 SEP 1905
+2 SPLAC @SP1000@              /* Boston */
+1 OCCU Newsboy
+1 RELI Unitarian
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**👧 @ST0029@ STICKY – Daughter: Edwina Deduction**
+```gedcom
+0 @ST0103@ STICKY             /* Edwina Deduction: Daughter */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE CHILD, RESIDENT
+1 NAME
+2 FORM Edwina Deduction
+2 PART Edwina
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 SEX F
+1 BIRT
+2 DATE 05 NOV 1907
+2 SPLAC @SP1000@              /* Boston */
+1 RELI Unitarian
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🧭 @ST0030@ STICKY – Niece: Willa Tinywhistle**
+```gedcom
+0 @ST0104@ STICKY             /* Willa Tinywhistle: Orphaned Niece */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE NIECE, RESIDENT
+1 NAME
+2 FORM Willa Tinywhistle
+2 PART Willa
+3 TYPE GIVN
+2 PART Tinywhistle
+3 TYPE SURN
+1 SEX F
+1 BIRT
+2 DATE 20 APR 1913
+2 SPLAC @SP1003@              /* Wobbleton, VT */
+1 RELI Catholic
+1 FLEX ANNOTATION
+2 PHRASE Clerk’s note
+2 CONTENTS Lives with aunt and uncle since parents’ death in 1918.
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**👴 @ST0105@ STICKY – Augustus Deduction: Grandfather**
+```gedcom
+0 @ST0105@ STICKY             /* Augustus Deduction: Grandfather */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE GRANDFATHER, RESIDENT
+1 NAME
+2 FORM Augustus Deduction
+2 PART Augustus
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 01 MAR 1840
+2 SPLAC @SP1004@              /* Lowell, MA */
+1 NOTE Slightly deaf; always mishears census taker.
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🧽 @ST0106@ STICKY – Maid: Mabel Scrubbs**
+```gedcom
+0 @ST0106@ STICKY             /* Mabel Scrubbs: Maid */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE SERVANT, RESIDENT
+1 NAME
+2 FORM Mabel Scrubbs
+2 PART Mabel
+3 TYPE GIVN
+2 PART Scrubbs
+3 TYPE SURN
+1 SEX F
+1 AGE 24
+1 OCCU Maid
+1 RELI Presbyterian
+1 FLEX ANNOTATION
+2 PHRASE Side-entry remark
+2 CONTENTS Joined household from Turnip Junction after mother’s passing.
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🧳 @ST0101@ STICKY – Boarder: Augustus Crumb**
+```gedcom
+0 @ST0101@ STICKY             /* Augustus Crumb - BOARDER, RESIDENT */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE BOARDER, RESIDENT
+1 NAME
+2 FORM Augustus Crumb
+2 PART Augustus
+3 TYPE GIVN
+2 PART Crumb
+3 TYPE SURN
+1 SEX M
+1 AGE 52
+1 RESI
+2 DATE 01 FEB 1923
+2 SPLAC @SP0134@              /* Cluttsville, Arkansas */
+1 FLEX ANNOTATION
+2 PHRASE Recorded comment
+2 CONTENTS "Moved into the Deduction household after losing his boarding contract with the Flapjack sisters."
+1 OCCU Traveling Salesman
+1 FLEX ANNOTATION
+2 PHRASE Margin note
+2 CONTENTS "Nominally a 'traveling salesman', though rarely seen selling anything."
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🪦 @ST0112@ STICKY – Augustus Dies**
+```gedcom
+0 @ST0112@ STICKY             /* Augustus Dies */
+1 TYPE PERSON, AN_DEATH       /* A secondary "event" */
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE RESIDENT
+1 NAME
+2 FORM Augustus Deduction
+2 PART Augustus
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 01 MAR 1840
+2 SPLAC @SP1004@              /* Lowell, MA */
+1 DEAT
+2 DATE 14 SEP 1920
+2 SPLAC @SP1000@              /* Boston */
+1 FLEX ANNOTATION
+2 PHRASE Side annotation
+2 CONTENTS Passed quietly during afternoon nap. Marginal note: 'Gone but still snoring'.
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🟰 @ST0114@ STICKY – Alias for Barnabas**
+```gedcom
+0 @ST0114@ STICKY             /* Alias for Barnabas DOES NOT HAVE A DATE assigned on the TEMPLATE */
+1 TYPE PERSON, AN_ALIAS       /* A secondary "event" */
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE RESIDENT
+1 NAME
+2 TYPE AKA                    /* Alias */
+2 FORM Barnabas Deduction
+2 PART Barnabas
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+2 FORM Barney
+2 PART Barney
+3 TYPE INFORMAL
+1 SEX M
+1 BIRT
+2 DATE 12 JUN 1878
+2 SPLAC @SP1001@              /* Concord, New Hampshire */
+1 OCCU Tailor
+1 RELI Unitarian
+1 FLEX ANNOTATION
+2 PHRASE Registry note
+2 CONTENTS Also known informally as "Barney" in neighborhood.
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+
+### 📝 Annotated Events
+
+**🚂 @ST0110@ STICKY – Edwina Leaves**
+```gedcom
+0 @ST0110@ STICKY             /* Edwina Leaves */
+1 TYPE PERSON, AN_LEAVE       /* A secondary "event" */
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE RESIDENT
+1 NAME
+2 FORM Edwina Deduction
+2 PART Edwina
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 RESI                        /* Move from (leave) */
+2 DATE UNTIL 10 NOV 1921
+2 SPLAC @SP1000@              /* Boston */
+1 RESI                        /* Move to */
+2 DATE 18 NOV 1921
+2 SPLAC @SP0052@              /* Scrubbington */
+1 FLEX ANNOTATION
+2 PHRASE Registry note
+2 CONTENTS "Edwina moved to Scrubbington on 18 NOV 1920 to work as housemaid."
+1 FLEX ANNOTATION
+2 PHRASE Margin note
+2 CONTENTS "Marginal note: 'Left home to work for Mrs. Butterworth in Scrubbington'."
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🛍️ @ST0111@ STICKY – Willa Arrives**
+```gedcom
+0 @ST0111@ STICKY             /* Willa Arrives */
+1 TYPE PERSON, AN_ARRIVE      /* A secondary "event" */
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE NIECE, RESIDENT
+1 NAME
+2 FORM Willa Tinywhistle
+2 PART Willa
+3 TYPE GIVN
+2 PART Tinywhistle
+3 TYPE SURN
+1 SEX F
+1 BIRT
+2 DATE 20 APR 1913
+2 SPLAC @SP1003@              /* Wobbleton, VT */
+1 RELI Catholic
+1 RESI                        /* Moved in from unknown place (arrives) */
+2 DATE
+1 RESI
+2 DATE 1922
+2 SPLAC @SP1000@              /* Boston */
+1 FLEX ANNOTATION
+2 PHRASE Side annotation
+2 CONTENTS Arrived in household 1922.
+1 FLEX ANNOTATION
+2 PHRASE Margin note
+2 CONTENTS "Orphaned in influenza outbreak; moved in with Deduction family."
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**🚌 @ST0113@ STICKY – Mabel Moves In**
+```gedcom
+0 @ST0113@ STICKY             /* Mabel Moves In */
+1 TYPE PERSON, AN_ARRIVE      /* A secondary "event" */
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE SERVANT, RESIDENT
+1 NAME
+2 FORM Mabel Scrubbs
+2 PART Mabel
+3 TYPE GIVN
+2 PART Scrubbs
+3 TYPE SURN
+1 RESI                        /* arrived in early 1920 in the household */
+2 DATE spring 1920
+2 SPLAC @SP1000@              /* Boston */
+1 SEX F
+1 AGE 24
+1 OCCU Maid
+1 RELI Presbyterian
+1 RESI
+2 DATE BEFORE spring 1920     /* she arrived from Turnip Junction (previous resi) */
+2 SPLAC @SP750@               /* Turnip Junction, NH */
+1 FLEX ANNOTATION
+2 PHRASE Side-entry remark
+2 CONTENTS From Turnip Junction. Reference from local Bishop Snugglesworth.
+1 FLEX ANNOTATION
+2 PHRASE Marginal scribble
+2 CONTENTS Hired maid, moved in spring 1920.
+1 FLEX ANNOTATION
+2 PHRASE Clerk’s note
+2 CONTENTS "Mabel Scrubbs, housemaid, arrived from Turnip Junction in early 1920."
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+**💍 @ST0114@ STICKY – Penny’s Marriage Note**
+```gedcom
+0 @ST0115@ STICKY             /* Penny’s Marriage Note */
+1 TYPE PERSON, AN_MARRIAGE    /* A secondary "event" */
+1 SUBM @B001@
+1 TEMPLATE @T1920@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE RESIDENT  /* annotation about Penny's marriage date */
+1 NAME
+2 FORM Penny Deduction
+2 PART Penny
+3 TYPE GIVN
+2 PART Deduction
+3 TYPE SURN
+1 MARR
+2 DATE 20 AUG 1903
+2 SPLAC @SP1005@              /* Nashua, NH */
+1 FLEX ANNOTATION
+2 PHRASE Clerk’s note
+2 CONTENTS Separate record from town clerk attached to page.
+1 CENS                        /* Identical to CENS for Barnabas */
+~ ~ ~
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+
+
+---
+
+<a name="example-06"></a>  
+## 🎖️ Example 06: Medal awarded to individual
+
+This GEDCOM 8 example models a military medal awarded to a soldier for bravery.  
+The `TEMPLATE` is of type `MILITARY, AWARD` and connects a tangible object (the medal itself) with the recipient using `STICKY` roles.  
+The example uses:  
+- `ROLE GRANTOR` and `ROLE GRANTEE`, used in a `TRANSFER`.  
+- Two `FLEX` entries to store the medal’s name and inscription  
+- A fictional `SPLAC` record with dramatic flair
+- An event of type `MILITARY, AWARD`.
+- A `CITA` record with a lot of (fictional) info.
+- A sober SOURCE — because someone has to be official  
+- This example does NOT use an `ASSET` record, as the medal is only for this person and will not be granted to another.
+
+**🪪 Awardings: @T0001@ – Medal for Bravery**
+
+```gedcom
+0 @T0001@ TEMPLATE            /* Awarding of Medal for Bravery */
+1 TYPE MILITARY, AWARD
+1 TITL Awarding of Medal for Bravery
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 07 JUN 1944
+1 SPLAC @SP00213@             /* Battle Museum Archive */
+1 EVEN MILITARY, AWARD
+2 DATE 07 JUN 1944
+2 SPLAC @SP00213@             /* Battle Museum Archive */
+1 ROLES
+2 STICKY @ST0001@             /* AWARD, MILITARY, Silver Star medal */
+2 STICKY @ST0002@             /* MAIN, GRANTEE, James Bronson */
+2 STICKY @ST0003@             /* ORGANIZATION, MILITARY, GRANTOR, Department of War */
+1 TRANSFER @ST0001@           /* The medal itself */
+2 GRANTOR @ST0003@            /* GRANTOR, Department of War  */
+2 GRANTEE @ST0002@            /* GRANTEE, James Bronson */
+1 CITA
+2 SOUR @S0001@                /* U.S. Army Decorations Record, 1944 */
+2 PAGE 88
+2 DATA
+3 DATE 1944-06-07
+3 TEXT Official transcript describing the Silver Star award
+4 MIME text/plain
+4 LANG en
+2 AUTHOR Department of War
+2 TITL Awarding of the Silver Star to Pvt. James Bronson
+2 DATES
+3 CREATED 07 JUN 1944
+3 RECORDED 08 JUN 1944
+2 REPOSITORY National Archives, Boomtown
+2 TEXTDISPLAY "Award issued for gallantry during the Normandy invasion"
+2 TRANSCRIPT "Private Bronson distinguished himself by acts of bravery under enemy fire..."
+2 FORMAT
+3 TYPE application/pdf
+2 URL https://www.archives.fake/us/bronson-silverstar.pdf
+2 LANGUAGE en
+2 RECORDID BRONSON19440607
+2 VOLUME 29
+2 CHAPTER Infantry Awards
+2 SHORTTITLE Silver Star – Bronson
+2 WWWLINK
+3 VALUE https://valor.fake/wiki/Bronson_SilverStar
+2 QUAY 3
+2 NOTE Transcribed from original paper certificate
+1 CREA 15 APR 2025
+1 CHAN 15 APR 2025
+```
+**🥈 @ST0001@ STICKY – Silver Star medal**
+```gedcom
+0 @ST0001@ STICKY
+1 TYPE AWARD, MILITARY
+1 TEMPLATE @T0001@            /* Belongs to this TEMPLATE */
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 JUN 1944
+1 FLEX DESCRIPT
+2 PHRASE "Award Type"
+2 CONTENTS "Silver Star medal"
+1 FLEX MATERIAL
+2 PHRASE "Award Material"
+2 CONTENTS "Silver"
+1 FLEX DESCRIPT
+2 CONTENTS "Awarded after Normandy landing"
+1 PHRASE "Inscription"
+1 FLEX DESCRIPT
+2 PHRASE "Award Reason"
+2 CONTENTS "For gallantry in action"
+~ ~ ~
+```
+**🪖 @ST0001@ STICKY – James Bronson**
+```gedcom
+0 @ST0002@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0001@            /* Belongs to this TEMPLATE */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 ROLE MAIN, RECIPIENT
+1 EVEN MILITARY, AWARD
+2 DATE 07 JUN 1944
+2 SPLAC @SP00213@             /* Battle Museum Archive */
+1 DATE 06 JUN 1944
+1 NAME
+2 FORM James Bronson
+2 PART JAMES
+3 TYPE GIVN
+2 PART Bronson
+3 TYPE SURN
+1 SEX M
+1 OCCU Private, 29th Infantry Division
+1 EVEN                        /* Same eventtype as the TEMPLATE type. */
+2 TYPE MILITARY, AWARD
+2 DATE 07 JUN 1944
+2 SPLAC @SP00213@             /* Battle Museum Archive */
+~ ~ ~
+```
+**🏢 @ST0001@ STICKY – Department of War**
+```gedcom
+0 @ST0003@ STICKY
+1 TYPE ORGANIZATION, MILITARY, GRANTOR
+1 SUBM @B001@
+1 TEMPLATE @T0001@            /* Belongs to this TEMPLATE */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 JUN 1944
+1 NAME Department of War
+2 ROLE GRANTOR
+1 ADDRPLUS
+2 ADDR Explosives Division, Bureau of Bravery 1 Heroism Plaza
+3 CITY Boomtown
+3 STAE BLZ
+3 POST 99999
+3 CTRY USA
+2 PHON +1-202-555-1944
+3 TITL War Medals Desk
+2 PHON +1-202-555-1945
+3 TITL Complaint Hotline (Unmonitored)
+2 EMAIL medals@boom.gov
+3 TITL Medal Distribution
+~ ~ ~
+```
+**💾 @S0001@ SOURCE U.S. Army Decorations Record, 1944**
+```gedcom
+0 @S0001@ SOUR
+1 TITL U.S. Army Decorations Record, 1944
+1 AUTH "Department of War"
+1 PUBL "National Archives"
+1 DATA
+~ ~ ~
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+
+---
+
+<a name="example-07"></a>  
+## 🌿 Example 07: Land Grant Record
+
+This GEDCOM 8 example demonstrates a **nearly complete TEMPLATE** of type `PROPERTY, GRANT`, representing a **royal land grant** issued in 1811 to a private citizen, Hiram Mudshoe, as a reward for military service.  
+It includes a structured `TRANSFER` with a defined `GRANTOR`, `GRANTEE`, and land parcel `ASSET`, as well as a properly detailed `CITA` section with archival metadata.  
+The record balances formal archival clarity with a subtle touch of humor in names and phrasing.  
+Useful for illustrating how property ownership and rights are modeled using the GEDCOM 8 `TRANSFER` structure.
+
+**📜 @T0043@ TEMPLATE – Land Grant to Hiram Mudshoe**
+```gedcom
+0 @T0043@ TEMPLATE
+1 TYPE PROPERTY, GRANT "Royal Land Grant for Service"
+1 TITL Royal Land Grant Dossier: Parcel 98
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 MAY 1811
+1 SPLAC @SP0392@              /* Crown Colony of Upper Fenshire */
+1 EVEN PROPERTY, GRANT        /* Land Grant event */
+2 DATE 12 MAY 1811
+2 SPLAC @SP0392@              /* Crown Colony of Upper Fenshire */
+1 ROLES
+2 STICKY @ST0144@             /* MAIN, PERSON, GRANTEE Hiram Mudshoe */
+2 STICKY @ST0244@             /* ORGANIZATION, GRANTOR */
+2 STICKY @ST0344@             /* LAND, MEADOW (Land Parcel) */
+1 TRANSFER @ST0344@           /* The land itself */
+2 GRANTOR @ST0244@            /* GRANTOR Royal Survey and Appropriations Office */
+2 GRANTEE @ST0144@            /* GRANTEE Hiram Mudshoe */
+1 CITA
+2 SOUR @S0043@                /* Royal Land Grant Dossier: Parcel 98 */
+2 PAGE Volume 7, Folio 19
+2 DATA
+3 DATE 12 MAY 1811
+3 TEXT "Deed issued to Mr. Hiram Mudshoe by crown order."
+2 AUTHOR Clerk Tiddlebreech
+2 TITL Royal Land Grant Archive Entry
+2 DATES
+3 RECORDED 12 MAY 1811
+2 REPOSITORY "Royal Survey Archive, Box 7B"
+2 SHORTTITLE "Land Grant: Parcel 98"
+2 FORMAT
+3 TYPE application/pdf
+2 QUAY 3
+2 TEXTDISPLAY "Land Grant entry for Parcel 98 – grantee: Hiram Mudshoe"
+2 TRANSCRIPT "This document certifies the grant of Parcel 98 to Mr. Hiram Mudshoe, effective 12 MAY 1811."
+2 RECORDID RG-1811-F98-MUD
+2 LANGUAGE en
+2 ITEMTYPE deed
+2 WWWLINK
+3 VALUE https://royalarchive.fenshire.gov/grants/parcel98
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🧑🏼‍🌾 @ST0144@ STICKY – Grantee: Hiram Mudshoe**
+```gedcom
+0 @ST0144@ STICKY             /* PERSON, Hiram Mudshoe */
+1 TYPE PERSON
+1 TEMPLATE @T0043@
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 MAY 1811
+1 SPLAC @SP0392@              /* Crown Colony of Upper Fenshire */
+1 EVEN PROPERTY, GRANT        /* Land Grant event */
+2 DATE 12 MAY 1811
+2 SPLAC @SP0392@              /* Crown Colony of Upper Fenshire */
+1 ROLE GRANTEE
+1 NAME
+2 FORM Hiram Mudshoe
+2 PART Hiram
+3 TYPE GIVN
+2 PART Mudshoe
+3 TYPE SURN
+1 SEX M
+1 AGE 38
+1 OCCU "Mosquito frontier defense strategist (unpaid)"
+1 NOTE "Awarded land for bravery during the Foggy Skirmish of '09."
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🏛️ @ST0244@ STICKY – Grantor: Royal Survey and Appropriations Office**
+```gedcom
+0 @ST0244@ STICKY             /* ORGANIZATION, GRANTOR, Royal Survey and Appropriations Office */
+1 TYPE ORGANIZATION, CROWN, Royal Survey and Appropriations Office
+1 TITL Royal Survey and Appropriations Office
+1 SUBM @B001@
+1 TEMPLATE @T0043@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 MAY 1811
+1 SPLAC @SP0392@              /* Crown Colony of Upper Fenshire */
+1 ROLE GRANTOR
+1 NAME
+2 FORM Royal Survey and Appropriations Office
+1 NOTE "Issued the grant under warrant #428-FogSouth-1811"
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🌾 @ST0344@ STICKY – Land Parcel: Lower Bogside (Parcel 98)**
+```gedcom
+0 @ST0344@ STICKY             /* LAND, MEADOW, Parcel 98 – Lower Bogside */
+1 TYPE LAND, MEADOW, "Parcel 98 – Lower Bogside"
+1 TITL Parcel 98 – Lower Bogside
+1 SUBM @B001@
+1 TEMPLATE @T0043@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 MAY 1811
+1 SPLAC @SP0392@              /* Crown Colony of Upper Fenshire */
+1 FLEX DECIMAL, CURR, GBP
+2 PHRASE "Value"
+2 CONTENTS 12.00
+1 FLEX UNIT
+2 PHRASE "Size"
+2 CONTENTS 14 acres
+1 FLEX DESCRIPT
+2 PHRASE "Boundaries"
+2 CONTENTS "North: Crooked Tree; South: Whispering Ditch; East: Sogstone Path; West: Unnamed Mound"
+1 NOTE "Soggy but legally fertile. Includes exclusive fishing rights on Tuesdays."
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**👤 @I201@ INDI – Hiram Mudshoe**
+```gedcom
+0 @I201@ INDI                 /* INDI: Hiram Mudshoe */
+1 NAME
+2 FORM Hiram Mudshoe
+2 PART HIRAM
+3 TYPE GIVN
+2 PART Mudshoe
+3 TYPE SURN
+1 SEX M
+1 AGE 38
+1 ROLES
+2 STICKY @ST0144@             /* PERSON, GRANTEE */
+1 ASSETS
+2 STICKY @ST0344@             /* LAND, MEADOW (Land Parcel) */
+2 DATE 12 MAY 1811
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+
+**📦 @S0043@ SOUR – Land Grant Source**
+```gedcom
+0 @S0043@ SOUR
+1 TITL Royal Land Grant Dossier: Parcel 98
+1 AUTH Clerk Tiddlebreech
+1 DATA
+2 EVEN PROPERTY, GRANT
+3 DATE 12 MAY 1811
+3 SPLAC @SP0391@              /* Upper Fenshire Registry */
+~ ~ ~
+1 NOTE "Stored in the Royal Survey Archive, Box 7B. Filing clerk noted to beware ink spills."
+1 REPO Royal Survey Archive   /* Not present in example */
+2 CALN 13B-1234.01
+1 CHAN 31 JUL 2025
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-08"></a>  
+## 🪪 Example 08: Naturalization and Passport
+
+This example models the legal and bureaucratic trail of a European immigrant becoming a U.S. citizen and receiving a passport in the early 1900s. The individual, Leopold “Leo” Federwitz, was born in Kraków, naturalized in 1905, and received a passport in 1907.  
+It uses **two separate TEMPLATES** — one for the naturalization certificate and one for the passport — both including roles, a STICKY asset for the physical document, and a separate SOURce each. This example is **fully updated for GEDCOM 8**, including structured CITA blocks, SPLAC tags, document assets, humorous notes, and proper QUAY levels.
+
+🔖 **New feature shown here:** The `INDI` block now includes an **`ASSETS` section**, referencing both the **naturalization certificate** and the **passport** as document STICKYs. This is one of the few examples that demonstrates how personal document holdings can be tracked directly under an individual.
+
+The updated template type lines use specific enums like `ORGANIZATION, COURT` or `IDENTITY, PASSPORT`. This version includes:
+- Dual role mentions for Leopold Federwitz (naturalization and passport).
+- Organizational roles: Immigration Court and Passport Bureau.
+- Physical document tracking with STICKYs of type `ASSET, DOCUMENT`.
+- Structured notes and sources.
+- Playful yet informative annotation for testing, teaching, and demo purposes.
+    
+**🪪 @T0045@ TEMPLATE – Naturalization Certificate**
+```gedcom
+0 @T0045@ TEMPLATE
+1 TYPE ORGANIZATION, COURT "Certificate of Naturalization"
+1 TITL Certificate of Naturalization – Leopold Federwitz
+2 PHRASE "Leopold Federwitz naturalized as U.S. citizen"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 3 OCT 1905
+1 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+1 NATU                        /* Naturalization event */
+2 DATE 3 OCT 1905
+2 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+2 AGNC United States Immigration Court, Cleveland
+1 ROLES
+2 STICKY @ST0146@             /* PERSON, SUBJECT */
+2 STICKY @ST0246@             /* ORGANIZATION, AUTHORITY (Immigration Office) */
+2 STICKY @ST0347@             /* Naturalization Certificat */
+1 CITA
+2 SOUR @S0045@
+2 TITL Certificate of Naturalization – Leopold Federwitz
+2 PAGE 1
+1 DATA
+~ ~ ~
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🧍 @ST0146@ STICKY – Person Leopold Federwitz**
+```gedcom
+0 @ST0146@ STICKY             /* PERSON, Leopold Federwitz */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0045@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 3 OCT 1905
+1 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+1 ROLE MAIN, RECIPIENT        /* Recieves that certificate */
+1 NAME
+2 FORM Leopold Federwitz
+2 PART Leopold
+3 TYPE GIVN
+2 PART Federwitz
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 28 FEB 1878
+2 SPLAC @SP055@               /* Kraków, Austria-Hungary */
+1 OCCU "Importer of educational teas and mustache oils"
+1 NATU                        /* Naturalization event */
+2 DATE 3 OCT 1905
+2 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+2 AGNC United States Immigration Court, Cleveland
+1 NOTE "Naturalized after confusing Cleveland with Lisbon. Decided to stay."
+1 OBJE @O0751@                /* Multimedia record with file link  */
+2 TITL Scanned certificate of naturalization
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🏛️ @ST0246@ STICKY – Organization: Immigration Authority**
+```gedcom
+0 @ST0246@ STICKY
+1 TYPE ORGANIZATION, COURT, Immigration Court
+1 TITLE United States Immigration Court, Cleveland
+1 SUBM @B001@
+1 TEMPLATE @T0045@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 3 OCT 1905
+1 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+1 ROLE JUDGE, ISSUER          /* Released the document */
+1 NATU                        /* Naturalization event */
+2 DATE 3 OCT 1905
+2 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+2 AGNC United States Immigration Court, Cleveland
+1 NOTE "Processed oath of allegiance, filed under case #1905-328C"
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🪪 @ST0347@ STICKY – Naturalization Certificat as physical asset**
+```gedcom
+0 @ST0457@ STICKY             /* Naturalization Certificate as physical asset */
+1 TYPE DOCUMENT, CERTIFICATE, "Naturalization Certificate"
+1 TITL Naturalization Certificate of Leopold Federwitz
+1 SUBM @B001@
+1 TEMPLATE @T0045@            /* Naturalization Certificate for Leopold Federwitz */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE  3 OCT 1905            /* Date of issue on document */
+1 SPLAC @SP592@               /* Cleveland, Ohio, USA */
+1 NAME "Naturalization Certificate of Leopold Federwitz"
+1 NOTE "Issued by United States Immigration Court, Cleveland"
+1 CREA 1 JUL 2025
+1 CHAN 31 JUL 2025
+```
+**🛄 @T0046@ TEMPLATE – Passport Issuance**
+```gedcom
+0 @T0046@ TEMPLATE
+1 TYPE IDENTITY, PASSPORT "United States Passport"
+1 TITL U.S. Passport for Leopold Federwitz
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 21 JUL 1907
+1 SPLAC @SP843@               /* Washington, D.C., USA */
+1 EVEN IDENTITY, PASSPORT
+2 DATE  21 JUL 1907
+2 SPLAC @SP843@               /* Washington, D.C., USA */
+1 ROLES
+2 STICKY @ST0746@             /* MAIN, RECIPIENT Leopold Federwitz */
+2 STICKY @ST0046@             /* ORGANIZATION, role ISSUER (Passport Office) */
+2 STICKY @ST0456@             /* DOCUMENT, ID, "passport" */
+1 CITA
+2 SOUR @S0046@
+2 TITL U.S. Passport for Leopold Federwitz
+~ ~ ~
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🏢 @ST0346@ STICKY – Organization: Passport Bureau**
+```gedcom
+0 @ST0346@ STICKY
+1 TYPE ORGANIZATION, GOVERNMENT, U.S. Department of State
+1 TITL United States Passport Bureau
+1 SUBM @B001@
+1 TEMPLATE @T0046@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 21 JUL 1907
+1 SPLAC @SP843@               /* Washington, D.C., USA */
+1 ROLE ISSUER
+1 NOTE "Issued under file #P-88311. Destination vaguely listed as ‘abroad.’"
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🪪 @ST0346@ STICKY – Passport as physical asset**
+```gedcom
+0 @ST0456@ STICKY             /* Passport as physical asset */
+1 TYPE DOCUMENT, ID, "passport"
+1 TITL Passport of Leopold Federwitz
+2 PHRASE "Issued by U.S. Passport Bureau after naturalization"
+1 SUBM @B001@
+1 TEMPLATE @T0146@            /* U.S. Passport for Leopold Federwitz */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 21 JUL 1907            /* Date of issue on document */
+1 SPLAC @SP843@               /* Washington, D.C., USA */
+1 NOTE "Physical document; original possibly stored in cigar box held by great-grandniece"
+1 OBJ @O003@                  /* Photo of passport */
+1 CREA 1 JUL 2025
+1 CHAN 31 JUL 2025
+```
+**🧍 @ST0146@ STICKY – Person Leopold Federwitz**
+```gedcom
+0 @ST0746@ STICKY             /* PERSON, Leopold Federwitz */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0746@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 21 JUL 1907
+1 SPLAC @SP843@               /* Washington, D.C., USA */
+1 EVEN IDENTITY, PASSPORT
+2 DATE  21 JUL 1907
+2 SPLAC @SP843@               /* Washington, D.C., USA */
+1 ROLE MAIN, RECIPIENT        /* Recieves that passport */
+1 NAME
+2 FORM Leopold Federwitz
+~ ~ ~
+1 SEX M
+1 BIRT
+2 DATE 28 FEB 1878
+2 SPLAC @SP3810@              /* Kraków, Austria-Hungary */
+1 OCCU "Importer of educational teas and mustache oils"
+1 NOTE "Naturalized after confusing Cleveland with Lisbon. Decided to stay."
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**👤 @I401@ INDI for Leopold Federwitz**
+```gedcom
+0 @I401@ INDI
+1 NAME
+2 FORM Leopold Federwitz
+2 PART Leopold
+3 TYPE GIVN
+2 PART Federwitz
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 28 FEB 1878
+2 SPLAC @SP3810@              /* Kraków, Austria-Hungary */
+1 ROLES
+2 STICKY @ST0146@             /* Leopold Federwitz, recieves Naturalization Certificate */
+2 STICKY @ST0746@             /* Leopold Federwitz, recieves passport */
+1 ASSETS
+2 @ST0456@ STICKY             /* Passport as physical asset */
+2 @ST0457@ STICKY             /* Naturalization Certificate as physical asset *
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**💾 SOURCE @S0045@ for Naturalization**
+```gedcom
+0 @S0045@ SOUR
+1 TITL Certificate of Naturalization – Leopold Federwitz
+1 AUTH United States Immigration Court
+1 PUBL "Filed in U.S. National Archives, case #1905-328C"
+1 ABBR "Federwitz Naturalization 1905"
+1 NOTE "Federwitz swore allegiance and was granted citizenship on 3 October 1905."
+1 DATA
+2 EVEN NATU                   /* Naturalization */
+3 DATE 3 OCT 1905
+4 PHRASE "Naturalization of Leopold Federwitz under U.S. law"
+3 SPLAC @SP001@               /*  Cleveland, Ohio, USA */
+2 AGNC U.S. Immigration Court, Cleveland
+2 NOTE "Preserved in U.S. National Archives, box 12, folder 3"
+~ ~ ~
+1 OBJE @O0751@
+2 TITL Scanned certificate of naturalization
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🖼️ OBJE @O0751@ – Scan of Naturalization Certificate**
+```gedcom
+0 OBJE @O0751@                /* Multimedia record with file link  */
+1 FILE https://example.org/naturalizations/federwitz-1905-cert.pdf
+2 FORM application/pdf
+3 MIME application/pdf
+2 TITL Scanned certificate of naturalization
+1 NOTE "Photo slightly faded; corner stamped with embassy seal."
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**💾 SOURCE @S0046@ for Passport**
+```gedcom
+0 @S0046@ SOUR
+1 TITL U.S. Passport for Leopold Federwitz
+2 PHRASE "Passport issued to Leopold Federwitz"
+1 AUTH United States Passport Bureau          /* created/authored the document */
+1 PUBL "U.S. Department of State Records, 1907"
+1 ABBR "Federwitz Passport 1907"
+1 DATA                                        /* Info about the data inside the document */
+2 EVENT IDENTITY, PASSPORT
+3 DATE 21 JUL 1907
+3 SPLAC @SP0006@                              /* Washington, D.C., USA */
+2 AGNC United States Passport Bureau          /* handled or executed the event */
+2 NOTE "Passport issued after naturalization"
+~ ~ ~
+1 OBJ @O003@                                  /* Picture of the passport */
+2 TITL Scan of 1907 passport for Leopold Federwitz
+1 NOTE "Original held by great-grandniece, possibly in a cigar box"
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-09"></a>  
+## ⛪ Example 09: Adult baptism and religious roles
+
+### ⛪ Full Example Bundle: Religious Roles in Action
+
+📌 **Summary:** This example bundle demonstrates full lifecycle participation in religious roles, from infant baptism and conversion to ordination, with cross-linked individuals and heirlooms across decades.
+
+### 📜 Explanation: Baptism, Confirmation, Ordination, Conversion
+These four religious rites may appear across many traditions and have distinct purposes:
+
+| Term       | Usual Age      | Purpose        | One-time? | Common `ROLE` / `SUBROLE` | Notes |
+|------------|----------------|----------------|-----------|---------------------------|-------|
+| `Baptism`     | Infant or Adult | Ritual of entry into the faith; often involves water |✅ | `RELIGIOUS` / `CHILD` or `INITIATE` | May be performed on newborns (infant baptism) or adults (convert baptism) |
+| `Confirmation`| Teen or Adult   | Affirmation of earlier baptism; signifies maturity in faith | ✅ | `RELIGIOUS` / `INITIATE` | Often follows infant baptism; typical in Catholic, Anglican, Lutheran rites |
+| `Ordination`  | Adult           | Designation as clergy or spiritual leader        | ✅ | `RELIGIOUS` / `CLERGY`    | Grants authority to lead services or administer sacraments |
+| `Conversion`  | Any             | Formal switch of religious affiliation   | ✅ | `RELIGIOUS` / `INITIATE`  | May involve adult baptism and profession of faith |
+
+### Overview
+This combined example illustrates **all religious roles** in GEDCOM 8 `STICKY`'s, including:
+- Adult conversion (Hans and Johannes)
+- Infant baptism (Johannes)
+- Ordination (Einar Voss)
+- Clergy participation (Henrik Brodahl)
+- Godparent and family witness roles (Marta, Karl)
+- Religious assets (Baptism gown)
+
+### 🧵 Main Participants
+
+**Johannes Thomassen** (b. 1797)  
+Baptized as a Catholic infant in Bergen, Johannes grows up in a Catholic household. As a young adult, he is confirmed and later undergoes a spiritual transformation, converting to Lutheranism in 1821 under Pastor Einar Voss, a close mentor figure.
+
+**Einar Voss** (b. ~1790s)  
+A devout Lutheran who entered theological seminary in 1814 and was ordained in 1820. Einar serves as a Lutheran pastor in Bergen and plays a pivotal role in receiving new converts, including Johannes and Hans Kristensen.
+
+| Temp-ID | Date      | Event Type<br> and person         | Role/Notes         | TEMPLATE EVENT         | SPLAC (place) |
+|--------|------------|--------------------|---------------------|------------------------|---------------|
+|   —    | 14 MAY 1797| Birth<br>Johannes Thomassen  | —      | —   | SPLAC @SP0063@ Bergen Parish Church (Catholic) |
+| @T771@ | 17 MAY 1797| Baptism<br>Johannes Thomassen | MAIN,<br>CHILD  | RELIGIOUS, BAPTISM | SPLAC @SP0063@ Bergen Parish Church (Catholic) |
+| @T772@ | 30 JAN 1805| Rel.Commitment/ Vow<br>Einar Voss| MAIN,<br>INITIATE, VOW| RELIGIOUS,<br>ENTRY  | SPLAC @SP0123@ Stavanger Theological Seminary (Lutheran) |
+| @T773@ | 30 JUL 1809| Confirmation<br>Johannes Thomassen| MAIN, CONFIRMEE | RELIGIOUS, CONFIRM  | SPLAC @SP0063@ Bergen Parish Church (Catholic) |
+| @T774@ | 10 APR 1812| Ordination<br>Einar Voss| MAIN,<br>DEACON | RELIGIOUS, ORDINATION  | SPLAC @SP0081@ Stavanger Diocese Seminary (Lutheran) |
+| @T775@ | 25 SEP 1814| Conversion<br>Hans Kristensen  | MAIN, CONVERT | RELIGIOUS, CONVERSION  | SPLAC @SP0097@ Oslo Cathedral (Vår Frelsers kirke) (Lutheran) |
+| @T776@ | 12 JUL 1821| Conversion<br>Johannes Thomassen | MAIN, CONVERT  | RELIGIOUS, CONVERSION  | SPLAC @SP0044@ Lutheran Parish of Bergen (Lutheran) |
+
+
+### Templates dates, places and information:
+```
+17 MAY 1797	@T771@	Infant baptism of Johannes Thomassen  SPLAC @SP0063@ Bergen Parish Church (Catholic)
+                    baptism of Johannes as child, by Father Lucien Marceau (with baptism gown)
+30 JAN 1805 @T772@  Entry of Einar Voss in SPLAC @SP0123@ Stavanger Theological Seminary (Lutheran)
+30 JUL 1809 @T773@  Confirmation of Johannes Thomassen to Catholicism, at 12 years old
+                    in SPLAC @SP0063@ Bergen Parish Church (Catholic)
+10 APR 1812 @T774@	Ordination of Pastor Einar Voss   SPLAC @SP0081@ Stavanger Diocese Seminary (Lutheran)
+                    by bishop Henrik Brodahl
+25 SEP 1814 @T775@	Conversion of Hans Kristensen from Catholicism to Lutheranism SPLAC @SP0097@ Oslo Cathedral
+                    (Vår Frelsers kirke) (Lutheran) Pastor is Einar Voss
+12 JUL 1821 @T776@	Conversion of Johannes Thomassen 24 (adult), from Catholicism to Lutheranism
+                    in SPLAC @SP0044@ Lutheran Parish of Bergen (Lutheran), Norway
+                    Johannes Thomassen converting to Lutheranism by pastor Einar Voss, with friend Hans Kristensen.
+```
+
+### 📜 Example GEDCOM 
+---
+**💧 @T771@ – Nr 1: Religious Baptism - Johannes Thomassen as infant**
+
+```gedcom
+0 @T771@ TEMPLATE             /* RELIGIOUS, BAPTISM */
+1 TYPE RELIGIOUS, BAPTISM
+1 TITL Parish Register: Baptisms 1790–1800
+2 PHRASE Baptism of Johannes Thomassen as a child in the Catholic Church of Bergen
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the ceremony */
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 BAPM
+2 DATE 17 MAY 1797
+2 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLES
+2 STICKY @ST0101@             /* MAIN, CHILD (Johannes as infant) */
+2 STICKY @ST0102@             /* FATHER Ivar Thomassen */
+2 STICKY @ST0103@             /* MOTHER Solveig Thomassen */
+2 STICKY @ST0104@             /* GODPARENT, AUNT, WITNESS (Marta) */
+2 STICKY @ST0105@             /* CLERGY Father Lucien Marceau */
+2 STICKY @ST0909@             /* RELIGIOUS, VESTMENT (baptism gown) */
+2 STICKY @ST0118@             /* FRIEND, SPONSOR, WITNESS Karl Mikkelsen */
+1 NOTE "Infant baptism of Johannes Thomassen"
+1 CITA
+2 SOUR @S0378@                /* Not written out in this example */
+2 PAGE 5
+2 DATA
+~  ~ ~
+```
+**🍼 @ST0101@ – Johannes Thomassen (MAIN, CHILD): tiny toes and sacred water**
+```gedcom
+0 @ST0101@ STICKY             /* Johannes Thomassen MAIN, CHILD */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T771@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the TEMPLATE, so ceremony date */
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Johannes Thomassen
+1 BIRT
+2 DATE 14 MAY 1797
+2 SPLAC @SP0063@              /* Bergen Parish Church */
+1 BAPM
+2 DATE 17 MAY 1797
+2 SPLAC @SP0063@              /* Bergen Parish Church */
+1 AGE 3 days
+1 RELI Catholic
+1 NOTE "Baptized in family tradition with lace gown, later converted to Lutheranism in 1821"
+~ ~ ~
+```
+**👨‍👦 @ST0102@ – Ivar Thomassen (FATHER): steady hands, family guide**
+```gedcom
+0 @ST0102@ STICKY             /* FATHER Ivar Thomassen */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T771@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the TEMPLATE, so ceremony date */
+1 ROLE FATHER
+1 NAME
+2 FORM Ivar Thomassen
+1 AGE 32
+1 RELI Catholic
+~ ~ ~
+```
+**👩‍🍼 @ST0103@ – Solveig Thomassen (MOTHER): warmth wrapped in linen**
+```gedcom
+0 @ST0103@ STICKY             /* MOTHER Solveig Thomassen */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T771@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the ceremony */
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLE MOTHER
+1 NAME
+2 FORM Solveig Thomassen
+1 AGE 29
+1 RELI Catholic
+~ ~ ~
+```
+**🧣 @ST0104@ – Marta Thomassen (SISTER, FATHER, WITNESS, GODPARENT): brought the heirloom gown**
+```gedcom
+0 @ST0104@ STICKY             /* Marta Thomassen SISTER, FATHER, WITNESS, GODPARENT */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T771@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the ceremony */
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLE SISTER, FATHER, WITNESS, GODPARENT
+1 NAME
+2 FORM Marta Thomassen
+1 AGE 28
+1 NOTE "Named on document as sister of Johannes’s father, so aunt of Johannes; carried lace gown"
+```
+**⛪ @ST0105@ – Father Lucien Marceau (CLERGY): visiting priest from abroad**
+```gedcom
+0 @ST0105@ STICKY             /* Father Lucien Marceau */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T771@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the ceremony */
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLE CLERGY
+1 NAME
+2 FORM Father Lucien Marceau
+1 OCCU Visiting Catholic Priest
+1 NOTE "Presided over Catholic baptism. Performed the baptism as guest clergy"
+```
+**👗 @ST0909@ – Baptism Gown (RELIGIOUS, VESTMENT): lace, linen, legacy**
+```gedcom
+0 @ST0909@ STICKY             /* RELIGIOUS, VESTMENT */
+1 TYPE RELIGIOUS, VESTMENT
+1 SUBM @B001@
+1 TEMPLATE @T00807@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE FROM 1780 TO 1800
+1 ROLE ITEM
+1 NOTE "Baptismal Gown of the Thomassen Family; lace trim hand-sewn heirloom gown."
+1 NOTE "Wool gown with hand-embroidered cross and initials J.T., worn by three generations"
+1 NOTE "Stored in a wooden box behind the altar since 1790. Slight moth nibble at hem."
+```
+**🥾 @ST0118@ – Karl Mikkelsen (FRIEND, SPONSOR, WITNESS): friend with muddy boots and clean faith**
+```gedcom
+0 @ST0118@ STICKY             /* Karl Mikkelsen */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T771@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 17 MAY 1797            /* Date of the ceremony */
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLE FRIEND, SPONSOR, WITNESS
+1 NAME
+2 FORM Karl Mikkelsen
+1 NOTE "Former Lutheran; sponsored Johannes’s baptism, known for sturdy boots"
+1 NOTE "Family friend and sponsor of Johannes' baptism"
+```
+---
+
+**✝️ @T772@ – Nr 2: Religious Commitment - Einar Voss enters Lutheran seminary**
+
+```gedcom
+0 @T772@ TEMPLATE             /* RELIGIOUS, ENTRY */
+1 TYPE RELIGIOUS, ENTRY
+1 TITL Seminary Entry Logbook: Stavanger Lutheran Seminary
+2 PHRASE Entry of Einar Voss into Lutheran seminary as novice initiate
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 30 JAN 1805            /* Date of the ceremony */
+1 SPLAC @SP0123@              /* Stavanger Theological Seminary */
+1 EVEN RELIGIOUS, ENTRY
+2 DATE 30 JAN 1805
+2 SPLAC @SP0123@              /* Stavanger Theological Seminary */
+1 ROLES
+2 STICKY @ST0101@             /* MAIN, INITIATE (Einar Voss) */
+2 STICKY @ST0105@             /* CLERGY — Professor Ibsen Lindahl registered Einar */
+1 NOTE "Einar Voss entered Lutheran seminary in presence of Registrar Prof. Ibsen Lindahl.
+2 CONT Ceremony simple but formal."
+1 CITA
+2 SOUR @S0379@                /* Not written out in this example */
+2 PAGE 2
+2 DATA
+~  ~ ~
+```
+**🎓 @ST0203@ – Einar Voss (MAIN, INITIATE): novice steps, big faith**
+```gedcom
+0 @ST0203@ STICKY             /* MAIN, INITIATE, Einar Voss */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T772@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 EVEN RELIGIOUS, ENTRY
+2 DATE 30 JAN 1805
+2 SPLAC @SP0123@              /* Stavanger Theological Seminary */
+1 ROLE MAIN, INITIATE
+1 NOTE "Entered Stavanger Theological Seminary as a Lutheran novice"
+1 SEX M
+1 BIRT
+2 DATE 03 MAR 1787             /* around 18 years old now */
+2 SPLAC @SP0119@               /* Åmøy, Rogaland, Island village near Stavanger */
+1 RELI Lutheran
+```
+**📋 Professor Ibsen Lindahl – Seminary Registrar at Stavanger Lutheran Seminary**
+```gedcom
+0 @ST0105@ STICKY             /* CLERGY Professor Ibsen Lindahl */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T772@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 30 JAN 1805
+1 SPLAC @SP0123@              /* Stavanger Theological Seminary */
+1 ROLE CLERGY
+1 NAME
+2 FORM Professor Ibsen Lindahl
+~ ~ ~
+1 OCCU Seminary Registrar
+1 NOTE "Recorded Einar’s entry into the Lutheran Seminary (firm hand, excellent penmanship).
+2 CONT Ceremony simple but formal."
+```
+---
+
+
+**🪪 @T773@ – Nr 3: Religious Confirmation - Johannes Thomassen as Catholic**
+
+```gedcom
+0 @T773@ TEMPLATE           /* RELIGIOUS, CONFIRM */
+1 TYPE RELIGIOUS, CONFIRMATION
+1 TITL Confirmation Register: Bergen Parish
+2 PHRASE Religious confirmation of Johannes Thomassen as a young adult Catholic
+1 DATE 30 JUL 1809
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 EVEN RELIGIOUS, CONFIRM
+2 DATE 30 JUL 1809
+2 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLES
+2 STICKY @ST0307@             /* MAIN, CONFIRMEE Johannes Thomassen 12, confirming */
+2 STICKY @ST0325@             /* PRIEST, CLERGY Father Gustav Lunde  */
+1 NOTE "Johannes confirmed into Catholic faith by Father Gustav Lunde after period of catechism study"
+1 CITA
+2 SOUR @S0329@                /* Not written out in this example */
+2 PAGE 23
+2 DATA
+~  ~ ~
+```
+**🕯️ @ST0301@ – Johannes Thomassen (MAIN, CONFIRMEE): youth confirmed, light embraced**
+```gedcom
+0 @ST0307@ STICKY             /* Johannes Thomassen MAIN, CONFIRMEE */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T773@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 30 JUL 1809            /* Date of the TEMPLATE, so ceremony date */
+1 ROLE MAIN, CONFIRMEE
+1 NAME
+2 FORM Johannes Thomassen
+1 BIRT
+2 DATE 14 MAY 1797
+2 SPLAC @SP0063@              /* Bergen Parish Church */
+1 EVEN RELIGIOUS, CONFIRM
+2 DATE 30 JUL 1809
+2 SPLAC @SP0063@              /* Bergen Parish Church */
+1 RELI Catholic
+~ ~ ~
+```
+**📖 @ST0302@ – Confirming Clergy (PRIEST, CLERGY Father Gustav Lunde): steady hand on sacred word**
+```gedcom
+0 @ST0302@ STICKY             /* Father Gustav Lunde, PRIEST, CLERGY */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T773@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 30 JUL 1809            /* Date of the TEMPLATE, so ceremony date */
+1 SPLAC @SP0063@              /* Bergen Parish Church */
+1 ROLE PRIEST, CLERGY
+1 NAME
+2 FORM Father Gustav Lunde
+1 NOTE "Conducted confirmation of Johannes at age 12, known for strict catechism lessons"
+```
+---
+
+
+**✝️ @T774@ – Nr 4: Religious Ordination - Einar Voss becomes Pastor**
+
+```gedcom
+0 @T774@ TEMPLATE             /* RELIGIOUS, ORDINATION */
+1 TYPE RELIGIOUS, ORDINATION
+1 TITL Ordination Dossier: Diocese of Stavanger
+2 PHRASE Religious ordination of Einar Voss as Lutheran pastor by Bishop Brodahl
+1 SUBM @B001@
+1 DATE 10 APR 1812
+1 SPLAC @SP7751@              /* Stavanger Diocese, Norway */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 EVEN RELIGIOUS, ORDINATION
+2 DATE 10 APR 1812
+2 SPLAC @SP7751@              /* Stavanger Diocese, Norway */
+1 ROLES
+2 STICKY @ST0412@             /* MAIN, DEACON, becomes Pastor Einar Voss */
+2 STICKY @ST0406@             /* CLERGY, ORDAINER, Bishop: Bishop Henrik Brodahl */
+1 NOTE "Ordination of Pastor Einar Voss"
+1 CITA
+2 SOUR @S0377@
+2 PAGE 5
+2 DATA
+~  ~ ~
+```
+**📯 @ST0412@ – Einar Voss (DEACON): robed and ready for calling**
+```gedcom
+0 @ST0412@ STICKY             /* DEACON, Pastor Einar Voss */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T774@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 10 APR 1812
+1 EVEN RELIGIOUS, ORDINATION
+2 DATE 10 APR 1812
+2 SPLAC @SP7751@              /* Stavanger Diocese, Norway */
+1 ROLE MAIN, DEACON
+1 NAME
+2 FORM Pastor Einar Voss
+~ ~ ~
+1 OCCU Lutheran priest
+1 NOTE "Becomes Pastor of the Lutheran Parish of Bergen, Norway"
+1 NOTE "Newly ordained pastor; took vows of chastity, obedience, and an impressive vow of punctuality"
+```
+**🎩 @ST0406@ – Bishop Henrik Brodahl (ORDINATION): hat of responsibility, staff of guidance**
+```gedcom
+0 @ST0406@ STICKY             /* CLERGY, ORDAINER, Bishop: Bishop Henrik Brodahl */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T774@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 10 APR 1812
+1 SPLAC @SP7751@              /* Stavanger Diocese, Norway */
+1 ROLE CLERGY, ORDAINER, Bishop
+1 NAME
+2 FORM Bishop Henrik Brodahl
+1 OCCU Bishop of Stavanger
+1 SPLAC Stavanger
+1 NOTE "Conducted the ordination ceremony for Deacon Einar Voss, to become a Pastor."
+```
+---
+
+**✝️ @T775@ – NR 5: Religious Conversion - Hans Kristensen from Catholicism to Lutheranism**
+
+```gedcom
+0 @T775@ TEMPLATE             /* RELIGIOUS, CONVERSION Hans Kristensen */
+1 TYPE RELIGIOUS, CONVERSION
+1 TITL Register of Religious Conversions (Early 1800s)
+2 PHRASE Religious conversion of Hans Kristensen from Catholicism to Lutheranism
+1 DATE 25 SEP 1814
+1 SPLAC @SP333@               /* Oslo Mission House */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 EVEN RELIGIOUS, CONVERSION
+2 DATE 25 SEP 1814
+2 SPLAC @SP333@               /* Oslo Mission House */
+1 ROLES
+2 STICKY @ST0507@             /* MAIN, CONVERT Hans Kristensen, converting */
+2 STICKY @ST0525@             /* CLERGY receiving Pastor Einar Voss */
+1 NOTE "Conversion of Hans Kristensen from Catholicism to Lutheranism"
+1 CITA
+2 SOUR @S0379@
+2 PAGE 5
+2 DATA
+~  ~ ~
+```
+**🧭 @ST0507@ – Hans Kristensen (MAIN, CONVERT): changing direction to Lutheran**
+```gedcom
+0 @ST0507@ STICKY             /* MAIN, CONVERT, Hans Kristensen */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T775@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 25 SEP 1814
+1 SPLAC @SP333@               /* Oslo Mission House */
+1 EVEN RELIGIOUS, CONVERSION
+2 DATE 25 SEP 1814
+2 SPLAC @SP333@               /* Oslo Mission House */
+1 ROLE MAIN, CONVERT
+1 NAME
+2 FORM Hans Kristensen
+1 RELI Lutheran
+1 AGE 19
+1 NOTE "Former Lutheran, embraced Catholic faith"
+```
+**📜 @ST0525@ – Pastor Einar Voss (CLERGY): giving guidance, again**
+```gedcom
+0 @ST0525@ STICKY             /* Pastor Einar Voss */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T775@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 25 SEP 1814
+1 SPLAC @SP333@               /* Oslo Mission House */
+1 ROLE CLERGY
+1 NAME
+2 FORM Pastor Einar Voss
+~ ~ ~
+1 NOTE "Received Hans Kristensen into the Lutheran Church"
+```
+---
+
+
+**🪪 @T776@ – Nr 6: Religious Conversion - Johannes Thomassen becomes Lutheran**
+
+```gedcom
+0 @T776@ TEMPLATE             /* RELIGIOUS, CONVERSION */
+1 TYPE RELIGIOUS, CONVERSION
+1 TITL Adult Conversion Certificate: Lutheran Parish of Bergen
+2 PHRASE Adult conversion of Johannes Thomassen from Catholicism to Lutheranism
+1 SUBM @B001@
+1 DATE 12 JUL 1821
+1 SPLAC @SP0033@              /* Lutheran Parish of Bergen, Norway */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 EVEN RELIGIOUS, CONVERSION
+2 DATE 12 JUL 1821
+2 SPLAC @SP0033@              /* Lutheran Parish of Bergen, Norway */
+1 ROLES
+2 STICKY @ST0601@             /* MAIN, CONVERT Johannes Thomassen 24 (adult), converting to Lutheranism */
+2 STICKY @ST0602@             /* CLERGY Pastor Einar Voss, receiving */
+2 STICKY @ST0603@             /* FRIEND, WITNESS Hans Kristensen */
+1 NOTE "Conversion of Johannes Thomassen from Catholicism to Lutheranism"
+1 CITA
+2 SOUR @S0376@
+2 PAGE 5
+2 DATA
+~  ~ ~
+```
+**🌊 @ST0601@ – Johannes Thomassen (MAIN, CONVERT): plunged into new light**
+```gedcom
+0 @ST0601@ STICKY             /* Johannes Thomassen, MAIN, CONVERT */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T776@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 JUL 1821
+1 SPLAC @SP0033@              /* Lutheran Parish of Bergen, Norway */
+1 EVEN RELIGIOUS, CONVERSION
+2 DATE 12 JUL 1821
+2 SPLAC @SP0033@              /* Lutheran Parish of Bergen, Norway */
+1 ROLE MAIN, CONVERT
+1 NAME
+2 FORM Johannes Thomassen
+~ ~ ~
+1 AGE 24
+1 RELI Lutheran
+1 NOTE "Converted from Catholicism, baptized in public ceremony in presence of friends and clergy"
+```
+**🧑‍🏫 @ST0602@ – Pastor Einar Voss (CLERGY): giving guidance, again, calm voice, firm faith**
+```gedcom
+0 @ST0602@ STICKY             /* CLERGY Pastor Einar Voss */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T776@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 JUL 1821
+1 SPLAC @SP0033@              /* Lutheran Parish of Bergen, Norway */
+1 ROLE CLERGY
+1 NAME
+2 FORM Pastor Einar Voss
+~ ~ ~
+1 OCCU Lutheran priest
+1 NOTE "Performed baptism and received Johannes’s declaration of faith"
+```
+**🪗 @ST0603@ – Hans Kristensen (FRIEND, WITNESS): faithful companion, again by his side**
+```gedcom
+0 @ST0603@ STICKY             /* Hans Kristensen, FRIEND, WITNESS */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T776@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 12 JUL 1821
+1 SPLAC @SP0033@              /* Lutheran Parish of Bergen, Norway */
+1 ROLE FRIEND, WITNESS
+1 NAME
+2 FORM Hans Kristensen
+~ ~ ~
+1 NOTE "Supported Johannes during conversion, shared similar experience"
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-10"></a>  
+## 📙 Example 10: Family Bible
+
+Example 10 – Family Bible
+
+
+### ✝️ GEDCOM 8 Example: “The Eldridge Family Bible” 🏡  
+
+This GEDCOM 8 example models a multigenerational family Bible with handwritten entries spanning from 1869 to 1936.  
+It captures personal milestones—births, deaths, marriages, gifts, and illnesses—annotated over decades by members of the Eldridge household. The Bible includes decorative elements like inked messages, dried flowers, and affectionate symbols.
+
+**Family context:**  
+Walter and Martha Eldridge began recording family events upon their marriage in 1869. The Bible passed through generations, reflecting both factual and sentimental entries—from births and wedding dates to handwritten blessings, heirlooms, and personal notes. Even the household butler, Isaac, is remembered with affection.
+
+**📜 This example demonstrates: 📜**
+- A `SECONDARY, FAMILYBIBLE` TEMPLATE, with rich annotation support treated as the **single source**, with each STICKY anchored in the same template context.
+- `STICKY TYPE` uses `AN_xxx` (e.g., `AN_BIRTH`, `AN_MARRIAGE`) to mark the annotated nature of **each person event**  
+- `STICKY` sequencing using `TDABOVI`  
+- Cross-role participation: parents, children, midwife, butler, witnesses  
+- A full `ASSET` block representing the Bible, including `HISTORY` and owner `STICKY` references  
+- Inheritance and non-inheritance gifting (`NECKLACE`, `BIBLE`)  
+- Use of `FLEX ANNOTATION` to preserve original Bible phrasing and ink style  
+- Emotional and material detail captured in annotations (e.g. hairlocks, pressed flowers)
+- **It has some pictures to get into the atmosphere and mood 😁 🏡**
+
+**Due to example length constraints:**
+- Some `INDI` records are omitted  
+- Many blocks end with **~ ~ ~** to indicate unshown lines  
+- `NAME` structures use the new GEDCOM 8 format, but only partially expanded  
+- No `CREA` or `CHAN` lines are shown
+
+---
+
+### 📸 Source: 🏡 Eldridge Homestead at Crystal Lake
+
+#### The Eldridge family home might have looked a bit like this estate.
+
+![Lakeland Farm / Eldridge Homestead](https://images.squarespace-cdn.com/content/v1/6385233d5c99740c75651c5c/f34c1ba7-ce82-4688-8dab-2ef44eee7c77/Dole+House?format=2500w)
+
+#### Original: "The Dole Mansion" in Crystal Lake, Illinois. From:  https://www.thedole.org/history
+
+```gedcom
+0 @S0100@ SOUR
+1 TITL Eldridge Homestead, Crystal Lake 
+1 DATA
+2 EVEN RESI
+3 SPLAC @SP0100@              /* Crystal Lake, Illinois */
+2 AGNC Unknown photographer / K.I.Co. photo archive
+2 NOTE Originally labeled “Lakeland Farm, Crystal Lake Ill.”
+~ ~ ~
+1 OBJ @O0100@                 /* Photograph link or thumbnail in digital form */
+1 NOTE Image chosen to visually represent the Eldridge family home in the Bible example.
+1 NOTE Historical match — image reused from Lakeland Farm near Crystal Lake, IL.
+~ ~ ~
+```
+---
+### 🏘️ Places as `SPLAC` Structures
+**🌐 @SP0008@ SPLAC – Eldridge Homestead in Crystal Lake, Illinois**
+```gedcom
+0 @SP0008@ SPLAC              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 LANG en
+1 TYPE LOCATION, POLI, 121, Estate 
+1 NOTE in German: "121=Gut" : "Manor farm or large landed estate, often owned by wealthy families."
+ ~ ~ ~
+```
+**🌐 @SP0009@ SPLAC – Chicago**
+```gedcom
+0 @SP0009@ SPLAC              /* Chicago */
+1 TYPE LOCATION, POLI, 51 , City (Chicago around those days )
+ ~ ~ ~
+```
+**🌐 @SP0100@ SPLAC – Crystal Lake, Illinois, United States**
+```gedcom
+0 @SP0100@ SPLAC              /* Crystal Lake, Illinois, United States */
+1 TYPE LOCATION, POLI, 55 , Village (55 = Village )
+ ~ ~ ~
+```
+```gedcom
+0 @SP051@ SPLAC               /* Nunda, Illinois, United States */
+1 TYPE LOCATION, POLI, 55 , Village (55 = Village )
+```
+---
+
+### 📚 TEMPLATE Structure
+This `TEMPLATE` has some empty lines in between sections of `STICKY`s. This is done to keep it readable. In an original `TEMPLATE` in a GEDCOM file there ought to be **NO** empty lines.  
+**📕🪶 TEMPLATE @T00003@ TEMPLATE NOTE: “Passed through 3 generations” — final entry by Marian Eldridge 📕🪶 📝**
+```gedcom
+0 @T00003@ TEMPLATE
+1 TYPE SECONDARY, FAMILYBIBLE
+1 TITLE Eldridge Family Bible with Births, Deaths, and Notes
+1 SUBM @B0003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+2 NOTE Latest entries by Marian Eldridge
+1 DATE 1870–1936              /* Time period the Bible was used and written in */
+1 SPLAC @SP0100@              /* Crystal Lake, Illinois */
+1 EVEN SECONDARY, FAMILYBIBLE
+2 DATE 1870–1936              /* Time period the Bible was used and written in */
+2 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 TDECUJUS @ST0001@           /* Walter Eldridge is the De Cujus */
+1 ROLES
+2 STICKY @ST0660@             /* Eldridge Family Bible */
+2 STICKY @ST0001@             /* MAY 3 1838 Birth Walter Eldridge Patriarch of the family */
+2 STICKY @ST0002@             /* JAN 1 1843 Birth Martha Green  Matriarch of the family */
+2 STICKY @ST0003@             /* SEP 7 1869 Marriage Walter Eldridge */
+2 STICKY @ST0004@             /* SEP 7 1869 Marriage Martha Green */
+2 STICKY @ST0100@             /* Irene Green, Mother of Martha, hands Martha the Bible as a wedding present */
+
+2 STICKY @ST0005@             /* JAN 1 1872 Birth John */
+2 STICKY @ST0006@             /* OCT 4 1875 Birth Eleanor */
+2 STICKY @ST0007@             /* JAN 3 1877 Birth Alfred */
+2 STICKY @ST0008@             /* JAN 15 1877 Baptism Alfred*/
+2 STICKY @ST0009@             /* MAY 31 1879 Birth Ruth*/
+2 STICKY @ST0010@             /* FEB 2 1875 Birth Clara Watson */
+
+2 STICKY @ST0011@             /* JUN 5 1893 Marriage John Eldridge */
+2 STICKY @ST0012@             /* JUN 5 1893 Marriage Clara Watson */
+2 STICKY @ST0013@             /* SEP 12 1899 Birth Edward */
+2 STICKY @ST0014@             /* JAN 3 1902 Birth Mary */
+2 STICKY @ST0015@             /* JAN 15 1902 Death Mary */
+2 STICKY @ST0016@             /* Jan 19 1902 Martha hands Clare the Family Bible */
+
+2 STICKY @ST0017@             /* Aug 8 1904 Birth Susan */
+2 STICKY @ST0975@             /* Aug 8 1904 Midwife: Mrs. Abigail Dorsey assisted at birth Susan */
+2 STICKY @ST0018@             /* Apr 26 1907 Birth William */
+2 STICKY @ST0976@             /* Aug 8 1904 Midwife: Mrs. Abigail Dorsey assisted at William's birth */
+
+2 STICKY @ST0019@             /* ABT OCT 8  1912 Death Isaac the Butler and friend of the family */
+2 STICKY @ST0020@             /* MAR 17 1918 Marriage Edward Eldridge */
+2 STICKY @ST0021@             /* MAR 17 1918 Marriage Rose Jacobs */
+2 STICKY @ST0022@             /* DEC 2 1919 Birth Marian Eldridge */
+2 STICKY @ST0977@             /* DEC 2 1919 Midwife: Mrs. Abigail Dorsey assisted at Marian's birth */
+2 STICKY @ST0023@             /* 1923 Move: Susan Eldridge moves to Evanston */
+
+2 STICKY @ST0035@             /* FEB 15 1922: Martha dies */
+2 STICKY @ST0036@             /* NOV 18 1922: Walter dies */
+2 STICKY @ST0024@             /* JAN 29 1936 Annotation from Marian about illness of Clara */
+2 STICKY @ST0025@             /* JAN 29 1936 Clare hands Marian her Necklace */
+2 STICKY @ST0026@             /* FEB 2 1936 death Clara Eldridge */
+2 STICKY @ST0027@             /* FEB 3 1936 heir Marian Eldridge (gets the bible) */
+
+1 TRANSFER @ST0660@           /* The transferred Bible */
+2 GRANTOR @ST0100@            /* Irene Green, Mother of Martha, original owner of the Bible */
+2 GRANTEE @ST0004@            /* SEP 7 1869 Marriage Martha Green, she gets the bible from her mother Irene */
+
+1 TRANSFER @ST0660@           /* The transferred Bible */
+2 GRANTOR @ST0002@            /* Martha Eldridge - Green, Mother */
+2 GRANTEE @ST0016@            /* Clara, her daughter gets the Bible after her newborn Mary dies */
+2 NOTE The bible is gifted by Martha to Clara
+
+1 TRANSFER @ST0660@           /* The transferred Bible */
+2 GRANTOR @ST0026@            /* Clara dies of pneumonia */
+2 GRANTEE @ST0027@            /* Marian, as an heir, gets the Bible */
+2 NOTE Marian gets the bible after her mother Clara died
+
+1 NOTE "Passed through 3 generations of Eldridges. Final entry by Marian Eldridge."
+1 CITA
+2 SOUR @S0100@                /* Eldridge Homestead, Crystal Lake */
+2 TITL Eldridge Homestead, Crystal Lake 
+2 PAGE 5
+2 DATA
+~ ~ ~                         /* Further info left out to shorten example */
+1 CREA 28 JUN 2025
+1 CHAN 06 AUG 2025
+```
+
+---
+### 📚 STICKY Structures
+**📔 The family ✝️ Bible as an `ASSET - STICKY` Its holding the family events from 3 generations Eldridges. 📖 ✝️**
+```gedcom
+0 @ST0660@ STICKY             /* Eldridge Family Bible. Belonging to "Eldridge Homestead, Illinois" */
+1 TYPE RELIGIOUS, BIBLE, Family Bible
+2 PHRASE "Eldridge Family Bible from around 1850, leather bound."
+1 TITL "Eldridge Family Bible from around 1850, leather bound."
+2 PHRASE "The Bible is annotated with decorative script, side notes, and pressed flowers."
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE HEIRLOOM
+1 EVEN RELIGIOUS, BIBLE, Family Bible
+2 DATE SEP 7 1869
+2 SPLAC @SP0100@              /* Crystal Lake, Illinois  */
+1 ASSET @A0001@               /* The Eldridge Family Bible */
+1 FLEX ANNOTATION
+2 PHRASE Side-entry remark
+2 CONTENTS Annotated first note inside the bible:
+2 CONT September 7 1869
+2 CONT "This bible is a gift to my daughter Martha and my son-in-law Walter
+2 CONT on their beautifull sunny  weddingday on the Eldridge Homestead.
+2 CONT With love and kisses, mom (Irene Green)"
+2 CONT 
+2 CONT It is followed by Irene's signature and a handdrawn heart with flowers around it.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+### 👨‍👩‍👧‍👦 Walter Eldridge and Martha Green📖, with their children: John, Eleanor, Alfred and Ruth. Generation 1
+**🧔🏻‍♂️ 🎩 STICKY @ST0001@ Birth of Walter Eldridge on MAY 3 1838 — would one day manage orchards with quiet pride 🧔🏻‍♂️ 🎩 🍼**
+```gedcom
+0 @ST0001@ STICKY             /* MAY 3 1838 Birth Walter Eldridge */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Walter Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 BIRT
+2 DATE MAY 3 1838
+1 TDABOVI 1
+1 FLEX ANNOTATION
+2 PHRASE Written in dark brown ink on fine vellum
+2 CONTENTS May 3rd, 1838 — Our son Walter was born beneath spring skies at the Eldridge Homestead.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏻 🧵 STICKY @ST0002@ Birth of Martha Green on JAN 1 1843 — gifted in embroidery and gentle wisdom 👩🏻 🧵 🍼** 
+```gedcom
+0 @ST0002@ STICKY             /* JAN 1 1843 Birth Martha Green */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Martha Green           /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE JAN 1 1843
+2 SPLAC @SP051@               /* Nunda, Illinois */
+1 TDABOVI 1s
+1 FLEX ANNOTATION
+1 PHRASE Written in soft strokes with dark ink
+2 CONTENTS January 1st, 1843 — Our darling Martha arrived in Nunda, Illinois, just as the new year dawned.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧔🏻‍♂️ 📜 STICKY @ST0003@ Marriage of Walter Eldridge on SEP 7 1869 — liked quoting poetry by the hearth 🧔🏻‍♂️ 📜 💍** 
+```gedcom
+0 @ST0003@ STICKY             /* SEP 7 1869 Marriage Walter Eldridge */
+1 TYPE PERSON, AN_MARRIAGE
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, GROOM
+1 NAME
+2 FORM Walter Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 MARR
+2 DATE SEP 7 1869
+2 PLAC Eldridge Homestead, Illinois
+1 TDABOVI 1
+1 FLEX ANNOTATION
+2 PHRASE Neatly penned in black ink, likely by a family elder
+2 CONTENTS September 7th, 1869 — Walter and Martha wed beneath the cottonwood tree on the homestead lawn.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👰🏻 🌸 STICKY @ST0004@ Marriage of Martha Green on SEP 7 1869 — cherished pressed flowers and keepsakes 👰🏻 🌸 💍**  
+```gedcom
+0 @ST0004@ STICKY             /* SEP 7 1869 Marriage Martha Green */
+1 TYPE PERSON, AN_MARRIAGE, AN_INHERIT, Gift
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, BRIDE, BENEFICIARY /* She is getting married AND she recieves the Bible */
+1 NAME
+2 FORM Martha Green           /* Further lines omitted to limit example lenght */
+1 SEX F
+1 MARR
+2 DATE SEP 7 1869
+2 PLAC Eldridge Homestead, Illinois
+1 ASSET @ST0660@              /* SEP 7 1869, Martha gets the Eldridge Family Bible. */
+1 TDABOVI 1s
+1 FLEX DESCRIPT
+2 PHRASE Annotation on top of first page.
+2 CONTENTS Annotated first note inside the bible
+1 FLEX ANNOTATION
+2 PHRASE Carefully written in elegant hand, signed by Irene (Green), inside a heart framed by floral doodles
+2 CONTENTS "September 7 1869,
+2 CONT This bible is a gift to my daughter Martha and my son-in-law Walter
+2 CONT on their beautifull sunny  weddingday on the Eldridge Homestead.
+2 CONT With love and kisses, mom"
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👵🏻 🕯️ STICKY @ST0100@ Gift by Irene Green on SEP 7 1869 — wrote candlelit notes full of blessings 👵🏻 🕯️ 🎁** 
+```gedcom
+0 @ST0100@ STICKY             /* Irene Green, Mother of Martha, hands Martha the Bible as a wedding present */
+1 TYPE PERSON, AN_TRANSFER, Gift
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED, INCOMPLETE /* Derived from text in first annotation, probably not complete */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE WITNESS, MOTHER, BRIDE, BENEFICIARY
+1 NAME
+2 FORM Irene Green            /* Further lines omitted to limit example lenght */
+1 SEX F
+1 EVEN AN_TRANSFER, Gift      /* Event is the transfer of the gift, the Bible */
+2 DATE SEP 7 1869
+2 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 FLEX ANNOTATION
+2 PHRASE Personal message by Irene in black ink
+2 CONTENTS  Annotated first note inside the Bible:
+2 CONT September 7 1869
+2 CONT "This bible is a gift to my daughter Martha and my son-in-law Walter
+2 CONT on their beautifull sunny  weddingday on the Eldridge Homestead.
+2 CONT With love and kisses, Mom (Irene)"
+1 FLEX ANNOTATION
+2 PHRASE Decorative remark in delicate hand
+2 CONTENTS The note is signed by Irene and surrounded by a heart and tiny pressed flowers.
+1 NOTE Irene Green, Mother of Martha, original owner of the Bible
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧑🏼 ⚒️ STICKY @ST0005@ Birth of John on JAN 1 1872 — later carved toys from walnut wood 🧑🏼 ⚒️ 🍼** 
+```gedcom
+0 @ST0005@ STICKY             /* JAN 1 1872 Birth John */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM John Eldridge          /* Further lines omitted to limit example lenght */
+1 SEX M
+1 BIRT
+2 DATE JAN 1 1872
+1 TDABOVI 1.1
+1 FLEX ANNOTATION
+2 PHRASE Written faintly in black ink on lined margin
+2 CONTENTS January 1st, 1872 — John was born at home after a long night, arriving just past the winter bells.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👧🏼 🧺 STICKY @ST0006@ Birth of Eleanor on OCT 4 1875 — helped fold linens and carry picnic baskets 👧🏼 🧺 🍼**  
+```gedcom
+0 @ST0006@ STICKY             /* OCT 4 1875 Birth Eleanor */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Eleanor Eldridge       /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE OCT 4 1875
+1 TDABOVI 1.2
+1 FLEX ANNOTATION
+2 PHRASE In the margin, beside the ribbon marker
+2 CONTENTS Eleanor was born October 4 1875. She arrived early in the morning and her cradle stood by the window.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧒🏻 🪀 STICKY @ST0007@ Birth of Alfred on JAN 3 1877 — known for spinning tops and quick laughter 🧒🏻 🪀 🍼**  
+```gedcom
+0 @ST0007@ STICKY             /* JAN 3 1877 Birth Alfred */
+1 TYPE PERSON, AN_BIRTH 
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Alfred Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 BIRT
+2 DATE JAN 3 1877
+1 TDABOVI 1.3
+1 FLEX ANNOTATION
+2 PHRASE Written under John’s entry, in slightly slanted script
+2 CONTENTS Alfred born on January 3rd, 1877 — storm outside, but inside all was warm.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+***🧒🏻 ✝️ STICKY @ST0008@ Baptism of Alfred on JAN 15 1877 — wore lace-trimmed white and was quiet 🧒🏻 ✝️ ✝️**  
+```gedcom
+0 @ST0008@ STICKY             /* JAN 15 1877 Baptism Alfred*/
+1 TYPE PERSON, AN_BAPTISM
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Alfred Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 BAPM
+2 DATE JAN 15 1877
+1 TDABOVI 1.3
+1 FLEX ANNOTATION
+2 PHRASE Squeezed between two lines in brown ink
+2 CONTENTS Baptized Jan 15th 1877. Reverend Morrison performed the rite after the thaw.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👧🏻 🪡 STICKY @ST0009@ Birth of Ruth on MAY 31 1879 — would one day stitch samplers with tulips 👧🏻 🪡 🍼**  
+```gedcom
+0 @ST0009@ STICKY             /* MAY 31 1879 Birth Ruth*/
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Ruth Eldridge          /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE MAY 31 1879
+1 TDABOVI 1.4
+1 FLEX ANNOTATION
+2 PHRASE Faintly penciled beneath a flower doodle
+2 CONTENTS Ruth was born May 31st 1879, in the late afternoon. Her cradle stayed untouched for weeks.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+### 👨‍👩‍👧‍👦 John Eldridge and Clara Watson📖, with their kids: Edward, Mary 🪦, Susan and William. Generation 2
+
+**👩🏼 📖 STICKY @ST0010@ Birth of Clara Watson on FEB 2 1875 — loved writing stories and copying verses 👩🏼 📖 🍼**
+```gedcom
+0 @ST0010@ STICKY             /* FEB 2 1875 Birth Clara Watson */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, BIRTH
+1 NAME
+2 FORM Clara Watson           /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE FEB 2 1875
+1 TDABOVI 1.1s
+1 FLEX ANNOTATION
+2 PHRASE Written below Psalm 121
+2 CONTENTS "Clara was born this 2nd of February, 1875. A calm day with snow upon the porch."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👨🏻‍🦱 🛠️ STICKY @ST0011@ Marriage of John Eldridge on JUN 5 1893 — good with tools and kept a tidy barn 👨🏻‍🦱 🛠️ 💍**
+```gedcom
+0 @ST0011@ STICKY             /* JUN 5 1893 Marriage John Eldridge */
+1 TYPE PERSON, AN_MARRIAGE
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, GROOM
+1 NAME
+2 FORM John Eldridge          /* Further lines omitted to limit example lenght */
+1 SEX M
+1 MARR
+2 DATE JUN 5 1893
+2 PLAC Eldridge Homestead, Illinois
+1 TDABOVI 1.1
+1 FLEX ANNOTATION
+2 PHRASE Note in margin beside Corinthians 13
+2 CONTENTS "June 5th, 1893 — John married today. May his days be steady and his evenings warm."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏻 🎶 STICKY @ST0012@ Marriage of Clara Watson on JUN 5 1893 — sang hymns while sewing by the fire 👩🏻 🎶 💍**
+```gedcom
+0 @ST0012@ STICKY             /* JUN 5 1893 Marriage Clara Watson */
+1 TYPE PERSON, AN_MARRIAGE
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, BRIDE
+1 NAME
+2 FORM Clara Watson           /* Further lines omitted to limit example lenght */
+1 SEX F
+1 MARR
+2 DATE JUN 5 1893
+2 PLAC Eldridge Homestead, Illinois
+1 TDABOVI 1.1s
+1 FLEX ANNOTATION
+2 PHRASE Written in Clara’s careful script
+2 CONTENTS "Clara wed on a clear June day. Her hymn book lay open to ‘Come Thou Fount.’"
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👦🏻 🧃 STICKY @ST0013@ Birth of Edward Eldridge on SEP 12 1899 — always curious, clutching his wooden cup 👦🏻 🧃 🍼** 
+```gedcom
+0 @ST0013@ STICKY             /* SEP 12 1899 Birth Edward */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Edward Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 BIRT
+2 DATE SEP 12 1899
+1 TDABOVI 1.1.1
+1 FLEX ANNOTATION
+2 PHRASE Written in steady hand, upper margin
+2 CONTENTS "Edward came to us September 12th, 1899. Rested well and curious from the start."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👧🏼 🧵 STICKY @ST0014@ Birth of Mary Eldridge on JAN 3 1902 — tiny hands often tangled in her mother’s thread 👧🏼 🧵 🍼**
+```gedcom
+0 @ST0014@ STICKY             /* JAN 3 1902 Birth Mary */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Mary Eldridge          /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE JAN 3 1902
+1 TDABOVI 1.1.2
+1 FLEX ANNOTATION
+2 PHRASE Neatly noted beneath a pressed scrap of muslin
+2 CONTENTS "Mary was born this 3rd of January, 1902. Such tiny hands, always reaching for Clara’s threads."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👼🏻 🕊️ STICKY @ST0015@ Death of Mary Eldridge on JAN 15 1902 — her cradle stayed untouched for weeks 👼🏻 🕊️ ✝️**
+```gedcom
+0 @ST0015@ STICKY             /* JAN 15 1902 Death Mary */
+1 TYPE PERSON, AN_DEATH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, DECEASED
+1 NAME
+2 FORM Mary Eldridge          /* Further lines omitted to limit example lenght */
+1 SEX F
+1 DEAT
+2 DATE JAN 15 1902
+1 TDABOVI 1.1.2
+1 FLEX ANNOTATION
+2 PHRASE Written in faded ink, just below her birth entry
+2 CONTENTS "Our little Mary passed on the 15th of January. Her cradle sits still, the blanket folded."
+2 CONT A lock of her hair is glued here, beside a dried violet.
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏻 🌼 STICKY @ST0016@ Martha hands Clare the Family Bible on Jan 19 1902 — shared in a room that smelled of violets 👩🏻 🌼 🎁** 
+```gedcom
+0 @ST0016@ STICKY             /* Jan 19 1902 Martha hands Clare the Family Bible */
+1 TYPE PERSON, AN_MENTION
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE ASSET, GIFT
+1 NAME "The Eldridge Family Bible"
+1 FLEX ANNOTATION
+1 CONTENTS There is just a dated note here saying "My dearest Clara, find comfort in the Lords words herein.
+2 PHRASE In blue ink
+2 CONT Its yours now." With a signature that looks like Martha's.
+1 EVEN
+2 TYPE ASSET, GIFT
+2 DATE Jan 19 1902
+1 FLEX ANNOTATION
+2 PHRASE Simple inscription, left margin near Psalms
+2 CONTENTS "My dearest Clara, find comfort in the Lord’s words herein.
+2 CONT It’s yours now." Signed by Martha, Jan 19th, 1902
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👧🏻 🍓 STICKY @ST0017@ Birth of Susan on Aug 8 1904 — rosy-cheeked and born during berry season 👧🏻 🍓 🍼** 
+```gedcom
+0 @ST0017@ STICKY             /* Aug 8 1904 Birth Susan */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Susan Eldridge         /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE Aug 8 1904
+1 TDABOVI 1.1.3
+1 FLEX ANNOTATION
+2 PHRASE Noted beside a drawn sprig of clover
+2 CONTENTS "Susan arrived this 8th of August, 1904 — cheeks like berries and a cry that stirred the crows."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧓🏻 🪡 STICKY @ST0975@ Midwife Mrs. Abigail Dorsey assists at Susan's birth — famous for her quilted shawls 🧓🏻 🪡 🍼**
+```gedcom
+0 @ST0975@ STICKY             /* Aug 8 1904 Midwife: Mrs. Abigail Dorsey assisted at birth Susan */
+1 TYPE PERSON, AN_MENTION
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE BIRTH, MIDWIFE
+1 NAME
+2 FORM Mrs. Abigail Dorsey    /* Further lines omitted to limit example lenght */
+1 SEX F
+1 OCCU Midwife
+1 NOTE Assisted with birth of Susan
+1 FLEX ANNOTATION
+2 PHRASE Penned neatly near Susan's name
+2 CONTENTS "Abigail Dorsey came again, her shawl trailing threads as she moved,
+2 CONT and brought Susan into the world with quiet confidence."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👶🏼 🪀 STICKY @ST0018@ Birth of William on Apr 26 1907 — strong lungs, fussed with a spinning top later 👶🏼 🪀 🍼**
+```gedcom
+0 @ST0018@ STICKY             /* Apr 26 1907 Birth William */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM William Eldridge       /* Further lines omitted to limit example lenght */
+1 SEX M
+1 BIRT
+2 DATE Apr 26 1907
+1 TDABOVI 1.1.4
+1 FLEX ANNOTATION
+2 PHRASE Inked plainly with a careful hand
+2 CONTENTS "William came this April day, lungs strong and fists tight — such a boy already."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧓🏻 🪡 STICKY @ST0976@ Midwife Mrs. Abigail Dorsey assists at William's birth — knitted booties for all newborns 🧓🏻 🪡 🍼**
+```gedcom
+0 @ST0976@ STICKY             /*  Aug 8 1904 Midwife: Mrs. Abigail Dorsey assisted at William's birth */
+1 TYPE PERSON, AN_MENTION
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+2 DATE Apr 26 1907
+1 ROLE BIRTH, MIDWIFE
+1 NAME
+2 FORM Mrs. Abigail Dorsey    /* Further lines omitted to limit example lenght */
+1 SEX F
+1 OCCU Midwife
+1 EVEN
+2 TYPE Assisting at birth
+2 DATE Aug 4 1904             /* Date of assisting at birth */
+1 NOTE Assisted with birth of William
+1 FLEX ANNOTATION
+2 PHRASE Written in warm brown ink beside William’s name
+2 CONTENTS "Mrs. Dorsey was again by our side. Her booties, already finished, waited folded in the cradle."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧔🏽 🍷 STICKY @ST0019@ Death of Isaac the Butler on ABT OCT 8 1912 — known for his port wine stories 🧔🏽 🍷 ✝️** 
+```gedcom
+0 @ST0019@ STICKY             /* ABT OCT 8  1912 Death Isaac the Butler and friend of the family */
+1 TYPE PERSON, AN_DEATH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, DECEASED
+1 NAME
+2 FORM Isaac (butler)         /* Further lines omitted to limit example lenght */
+1 SEX M
+1 OCCU Butler
+1 DEAT
+2 DATE ABT OCT 8  1912
+1 NOTE "Isaac our butler and friend died unexpectedly this week."
+1 TDABOVI 0
+1 FLEX ANNOTATION
+2 PHRASE Written with care by Martha, in her soft, slanting script
+2 CONTENTS "Our dear Isaac passed today. More than a butler—he was part of the family.
+2 CONT Always the first to rise, the last to rest, and never short a story.
+2 CONT We shall miss the quiet way he warmed the room with port, kind words and patience."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+### 👨‍👩‍👧 Edward Eldridge, and Rose Jacobs, with their child: Marian📖. Generation 3
+
+**👨🏻 🎩 STICKY @ST0020@ Marriage of Edward Eldridge on MAR 17 1918 — arrived with polished boots and hope 👨🏻 🎩 💍**
+```gedcom
+0 @ST0020@ STICKY             /* MAR 17 1918 Marriage Edward Eldridge */
+1 TYPE PERSON, AN_MARRIAGE
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, GROOM
+1 NAME
+2 FORM Edward Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 MARR
+2 DATE MAR 17 1918
+2 PLAC Eldridge Homestead, Illinois
+1 TDABOVI 1.1.1
+1 FLEX ANNOTATION              /* STICKY @ST0020@ Marriage Edward Eldridge */
+2 PHRASE In Edward’s own neat hand
+2 CONTENTS "Edward Eldridge was wed today, March 17 1918. May his steps be steady and his home warm."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏻 🪞 STICKY @ST0021@ Marriage of Rose Jacobs on MAR 17 1918 — wore a violet ribbon in her dark hair 👩🏻 🪞 💍**
+```gedcom
+0 @ST0021@ STICKY             /* MAR 17 1918 Marriage Rose Jacobs */
+1 TYPE PERSON, AN_MARRIAGE
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, BRIDE
+1 NAME
+2 FORM Rose Jacobs            /* Further lines omitted to limit example lenght */
+1 SEX F
+1 MARR
+2 DATE MAR 17 1918
+2 PLAC Eldridge Homestead, Illinois
+1 TDABOVI 1.1.1s
+1 FLEX ANNOTATION              /* STICKY @ST0021@ Marriage Rose Jacobs */
+2 PHRASE Likely penned by her sister
+2 CONTENTS "Rose looked radiant in her violet ribbon. Married Edward today. A lovely day in early spring."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👧🏼 🎀 STICKY @ST0022@ Birth of Marian Eldridge on DEC 2 1919 — cooed while clutching her mother’s locket 👧🏼 🎀 🍼** 
+```gedcom
+0 @ST0022@ STICKY             /* DEC 2 1919 Birth Marian Eldridge */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, CHILD
+1 NAME
+2 FORM Marian Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE DEC 2 1919
+1 TDABOVI 1.1.1.1
+1 FLEX ANNOTATION              /* STICKY @ST0022@ Birth Marian Eldridge */
+2 PHRASE Delicate script with a faint stain
+2 CONTENTS "A daughter born to Rose and Edward—Marian, on this December 2, 1919. She cries like a songbird."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**🧓🏻 🪡 STICKY @ST0977@ Midwife Mrs. Abigail Dorsey assists at Marian's birth — “gentlest hands in the county” 🧓🏻 🪡 🍼**
+```gedcom
+0 @ST0977@ STICKY             /*  DEC 2 1919 Midwife: Mrs. Abigail Dorsey assisted at Marian's birth */
+1 TYPE PERSON, AN_MENTION
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+2 DATE Apr 26 1907
+1 ROLE BIRTH, MIDWIFE
+1 NAME
+2 FORM Mrs. Abigail Dorsey    /* Further lines omitted to limit example lenght */
+1 SEX F
+1 OCCU Midwife
+1 EVEN
+2 TYPE Assisting at birth
+2 DATE DEC 2 1919             /* Date of assisting at birth */
+1 NOTE Assisted with birth of Marian
+1 FLEX ANNOTATION              /* STICKY @ST0977@ Midwife Mrs. Dorsey */
+2 PHRASE Noted in Clara’s careful script
+2 CONTENTS "Mrs. Abigail Dorsey was present at Marian’s birth. Her hands soothed both mother and child."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏻 🚲 STICKY @ST0023@ Move of Susan to Evanston in 1923 — packed her trunk and rode away smiling 👩🏻 🚲 🧳** 
+```gedcom
+0 @ST0023@ STICKY             /* 1923 move Susan Eldridge moves to Evanston */
+1 TYPE PERSON, AN_MOVE
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, SUBJECT
+1 NAME
+2 FORM Susan Eldridge         /* Further lines omitted to limit example lenght */
+1 SEX F
+1 NOTE "Susan moved to Evanston after her marriage"
+1 DATE 1923
+1 TDABOVI 1.1.3
+1 FLEX ANNOTATION              /* STICKY @ST0023@ Susan moves to Evanston */
+2 PHRASE Slanted handwriting, a small pressed flower nearby
+2 CONTENTS "Susan packed her trunk today, and left for Evanston. A new chapter begins."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏼 🫖 STICKY @ST0024@ Marian’s annotation on Clara’s illness on JAN 29 1936 — penned beside her teacup 👩🏼 🫖 ✏️**
+```gedcom
+0 @ST0024@ STICKY             /* JAN 29 1936 Annotation from Marian about illness of Clara */
+1 TYPE PERSON, AN_OTHER, Annotation by Marian
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE PATIENT
+1 NAME
+2 FORM Clara Eldridge         /* Further lines omitted to limit example lenght */
+1 SEX F
+1 DATE 1870–1936
+1 NOTE "Mom is very ill now, suffering pneumonia, we pray she will get better."
+1 DATE JAN 29 1936
+1 TDABOVI 1.1s
+1 FLEX ANNOTATION              /* STICKY @ST0024@ Illness of Clara */
+2 PHRASE Written hastily with ink smudges
+2 CONTENTS "Mother’s breath is shallow. The doctor fears pneumonia. We keep hope in our hearts."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏼 💎 STICKY @ST0025@ Clare hands Marian her Necklace on JAN 29 1936 — said “It’s yours now, child” 👩🏼 💎 🎁**
+```gedcom
+0 @ST0025@ STICKY             /* JAN 29 1936 Clare hands Marian her Necklace */
+1 TYPE JEWELRY, NECKLACE
+1 TITL "Necklace with pearl pendant"
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE ASSET, GIFT
+1 NOTE Gifted by Clara to Marian
+1 DATE JAN 29 1936
+1 FLEX ANNOTATION              /* STICKY @ST0025@ Necklace gift to Marian */
+2 PHRASE Carefully penned below the illness note
+2 CONTENTS "Today, I gave Marian my pearl necklace. May she wear it in joy and sorrow alike."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏻 🥀 STICKY @ST0026@ Death of Clara Eldridge on FEB 2 1936 — flowers faded in the vase by her bed 👩🏻 🥀 ✝️**
+```gedcom
+0 @ST0026@ STICKY             /* FEB 2 1936 death Clara Eldridge */
+1 TYPE PERSON, AN_DEATH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, DECEASED, GRANTOR
+1 NAME
+2 FORM Clara Eldridge         /* Further lines omitted to limit example lenght */
+1 SEX F
+1 DEAT
+2 DATE FEB 2 1936
+1 TDABOVI 1.1s
+1 FLEX ANNOTATION              /* STICKY @ST0026@ Death of Clara */
+2 PHRASE Gently written with a drawn black border
+2 CONTENTS "Clara passed this morning, February 2, 1936. The lilies by her bed had wilted overnight."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏼 📘 STICKY @ST0027@ Heir Marian Eldridge receives the Bible on FEB 3 1936 — held it tight like a treasure chest 👩🏼 📘 🎁**
+```gedcom
+0 @ST0027@ STICKY             /* FEB 3 1936 heir Marian Eldridge (gets the bible) */
+1 TYPE PERSON, AN_OTHER
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE GRANTEE                /* Marian Eldridge recieves the Bible */
+1 NAME
+2 FORM Marian Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX F
+1 NOTE "As mom died, I Marian, have been granted this beautiful Bible,
+2 CONT which I will keep and extend in her name."
+1 DATE FEB 3 1936
+1 TDABOVI 1.1.1.1
+1 FLEX ANNOTATION              /* STICKY @ST0027@ Marian receives the Bible */
+2 PHRASE A later addition in Marian’s hand
+2 CONTENTS "Clara's Bible is now Marian’s. She holds it close—may it guide her days."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👵🏼 🕯️ STICKY @ST0035@ Death of Martha Eldridge on FEB 15 1922 — whispered something no one caught 👵🏼 🕯️ ✝️** 
+```gedcom
+0 @ST0035@ STICKY             /* JAN 1 1843 Martha Green dies*/
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936              /* Template DATE and SPLAC */
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, DECEASED
+1 NAME
+2 FORM Martha Green           /* Further lines omitted to limit example lenght */
+1 SEX F
+1 DEAT
+2 DATE FEB 15 1922
+2 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 TDABOVI 1s
+1 FLEX ANNOTATION              /* STICKY @ST0035@ Death of Martha Green */
+2 PHRASE Thin ink, fading at the edges
+2 CONTENTS "Martha slipped away today, soft as a breath. No one heard her final words."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👴🏼 📜 STICKY @ST0036@ Death of Walter Eldridge on NOV 18 1922 — died of a broken heart 👴🏼 📜 ✝️** 
+```gedcom
+0 @ST0001@ STICKY             /* MAY 3 1838 Walter Eldridge dies */
+1 TYPE PERSON, AN_BIRTH
+1 TEMPLATE @T00003@
+1 TORIGIN ORIGDOC, TRANSCRIBED /* Derived directly from original bible, entries copied into STICKYs */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 1870–1936
+1 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 ROLE MAIN, DECEASED
+1 NAME
+2 FORM Walter Eldridge        /* Further lines omitted to limit example lenght */
+1 SEX M
+1 DEAT
+2 DATE NOV 18 1922
+2 SPLAC @SP0008@              /* Eldridge Homestead Crystal Lake, Illinois*/
+1 TDABOVI 1
+1 FLEX ANNOTATION              /* STICKY @ST0036@ Death of Walter Eldridge */
+2 PHRASE Same ink and hand as Martha’s note
+2 CONTENTS "Walter followed Martha not long after. His spirit had already left with hers."
+~ ~ ~                         /* Further info left out to shorten example */
+```
+
+### 👥 INDI Structures, not all, just some of them because of the example length.
+
+**👩🏼‍🦱 @I0052@ INDI – Martha Eldridge Green, Matriarch of the family**
+```gedcom
+0 @I0052@ INDI                /* Martha Eldridge Green */
+1 NAME
+2 FORM Martha Green           /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE JAN 1 1843
+2 SPLAC @SP051@               /* Nunda, Illinois */
+1 ROLES                       /* 9 STICKYs as Martha is mentioned 9 times in the TEMPLATE */
+2 STICKY @ST0002@             /* JAN 1 1843 Birth Martha Green */
+2 STICKY @ST0004@             /* SEP 7 1869 Marriage Martha Green and Walter Eldridge */
+2 STICKY @ST0005@             /* JAN 1 1872 Birth John */
+2 STICKY @ST0006@             /* OCT 4 1875 Birth Eleanor */
+2 STICKY @ST0007@             /* JAN 3 1877 Birth Alfred */
+2 STICKY @ST0008@             /* JAN 15 1877 Baptism Alfred*/
+2 STICKY @ST0009@             /* MAY 31 1879 Birth Ruth*/
+2 STICKY @ST0016@             /* Jan 19 1902 Martha hands Clare the Family Bible */
+2 STICKY @ST0035@             /* FEB 15 1922: Martha dies */
+1 ASSETS
+2 STICKY @ST0660@             /* SEP 7 1869, Martha gets the Eldridge Family Bible. */
+2 DATE 12 MAY 1811
+~ ~ ~                         /* Further info left out to shorten example */
+```
+**👩🏼‍🦱 @I0053@ INDI – Clara Eldridge Watson, married to John Eldridge**
+```gedcom
+0 @I0053@ INDI                /* Clara Eldridge Watson */
+1 NAME
+2 FORM Clara Eldridge Watson  /* Further lines omitted to limit example lenght */
+1 SEX F
+1 BIRT
+2 DATE FEB 2 1875
+1 ROLES                       /* 12 STICKYs as Clara is mentioned 12 times in the TEMPLATE */
+2 STICKY @ST0010@             /* FEB 2 1875 Birth Clara Watson */
+2 STICKY @ST0012@             /* JUN 5 1893 Marriage Clara Watson */
+2 STICKY @ST0013@             /* SEP 12 1899 Birth Edward */
+2 STICKY @ST0014@             /* JAN 3 1902 Birth Mary */
+2 STICKY @ST0015@             /* JAN 15 1902 Death Mary */
+2 STICKY @ST0016@             /* Jan 19 1902 Martha hands Clare the Family Bible */
+2 STICKY @ST0017@             /* Aug 8 1904 Birth Susan */
+2 STICKY @ST0018@             /* Apr 26 1907 Birth William */
+2 STICKY @ST0024@             /* JAN 29 1936 Annotation from Marian about illness of Clara */
+2 STICKY @ST0025@             /* JAN 29 1936 Clare hands Marian her Necklace */
+2 STICKY @ST0026@             /* FEB 2 1936 death Clara Eldridge */
+2 STICKY @ST0027@             /* FEB 3 1936 heir Marian Eldridge (gets the bible) */
+1 ASSETS
+2 STICKY @ST0660@             /* Jan 19 1902, Martha hands Clara the Eldridge Family Bible. */
+2 DATE 12 MAY 1811
+~ ~ ~                         /* Further info left out to shorten example */
+```
+
+### 📔 The family ✝️ Bible as an ASSET
+
+#### The Eldridge family bible might have looked a bit like this one:
+
+![Handwritten page from the Turpin Bible (1815)](https://scmuseum.org/sites/default/files/styles/wysiwyg/public/2023-08/Handwritten%20Pages%20from%20the%20Turpin%20Bible%20in%20the%20Collection%20of%20the%20South%20Carolina%20State%20Museum.jpg?itok=oPNr4ZUA)
+
+#### Original: William Turpin Bible (1815) - South Caroline State Museum: https://scmuseum.org/explore/exhibitions/online-exhibitions
+
+```gedcom
+0 @A0001@ ASSET               /* The Eldridge Family Bible, and its owners */
+1 TYPE RELIGIOUS, BIBLE
+1 TITL "Eldridge Family Bible, a gift from Irene Green on the wedding of her daughter Martha "
+1 DATE SEP 7 1869             /* Wedding date of Walter and Martha */
+1 SPLAC @SP0100@              /* Homestead at Crystal Lake, Illinois */
+1 SUBM @B0001@
+1 HISTORY                     /* Shows the owners of the Bible over time */
+2 STICKY @ST0100@             /* Irene Green, Mother of Martha, original owner of the Bible */
+2 STICKY @ST0004@             /* SEP 7 1869 Marriage Martha Green, she gets the bible from her mother Irene */
+2 STICKY @ST0016@             /* Jan 19 1902 Martha hands Clare the Family Bible (after Mary dies) */
+2 STICKY @ST0027@             /* FEB 3 1936 Bible to Marian Eldridge, after her mother Clare dies */
+1 FLEX DESCRIPT
+2 PHRASE "Bible"
+2 CONTENTS "Eldridge Family Bible from around 1850, leather bound. "
+3 LANG en
+1 NOTE Passed through 3 generations of Eldridges. Final entry by Marian Eldridge.
+1 FLEX ANNOTATION
+2 PHRASE In black ink
+2 CONTENTS Annotated first note inside the bible:
+2 CONT September 7 1869
+2 CONT "This bible is a gift to my daughter Martha and my son-in-law Walter
+2 CONT on their beautifull sunny  weddingday on the Eldridge Homestead.
+2 CONT With love and kisses, mom (Irene Green)"
+2 CONT 
+2 CONT It is followed by Irene's signature and a handdrawn heart with flowers around it.
+1 OBJ @O003@                  /* Links to a picture of this bible */
+1 CREA 06 JUL 2025
+1 CHAN 13 AUG 2025
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-11"></a> 
+
+## 🧬 Example 11: DNA Test Results: Match Comparison and Genotype Report
+
+This GEDCOM 8 example demonstrates two distinct but related DNA record types:
+
+- A **DNA match report** comparing two individuals, modeled as a `TEMPLATE` of type `IDENTITY, DNATEST`, with structured `FLEX` fields describing the result details.
+- A **direct genotype report**, modeled as a second `TEMPLATE` of the same type, but focused on recording raw marker data using the new `ARRAY_STRUCTURE`.
+
+Together, these demonstrate the evolving support in GEDCOM 8 for structured genetic evidence, including:
+- Roles like `SUBJECT`, `MATCH`, and `LABORATORY`
+- The use of `FLEX ARRAY` to store tabular genotype values
+- A newly defined data type (`TupleList`) and `ARRAY_STRUCTURE` format for multi-line marker-value pairs
+- The reuse of entities like individuals and organizations across multiple `TEMPLATE`s
+
+Both examples are drawn from plausible real-world test formats (e.g., autosomal comparison and genotype printout). While actual lab formats may vary, this illustrates how GEDCOM 8 can accommodate structured, verifiable genetic records in a consistent way.
+
+---
+**🧬 TEMPLATE @T0088@ – Autosomal DNA Test Match Report – Porridge & Quibble**
+```gedcom
+0 @T0088@ TEMPLATE            /* 06 MAR 2023 Autosomal DNA Comparison Report – Porridge & Quibble */
+1 TYPE IDENTITY, DNATEST, "Autosomal DNA Test Match Report"
+1 TITL Autosomal DNA Comparison Report – Porridge & Quibble
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 MAR 2023            /* Date of the test. */
+1 SPLAC @SP0005@              /* Houston, TX, USA */
+1 EVEN IDENTITY, DNATEST, "Autosomal DNA Test Match Report"
+2 DATE 06 MAR 2023            /* Date of the test. */
+2 SPLAC @SP0005@              /* Houston, TX, USA */
+1 AGNC FamilyTreeDNA – Genealogy & Testing Services
+1 ROLES
+2 STICKY @ST0188@             /* ROLE MAIN, SUBJECT Gretchen Hazel Porridge */
+2 STICKY @ST0288@             /* ROLE MATCH Daniel Quibble */
+2 STICKY @ST0388@             /* ORGANIZATION, LABORATORY Genetic Information Research Institute (GIRI)*/
+2 STICKY @ST0688@             /* ASSET, ITEM Test Report */
+1 CITA
+2 SOUR @S0088@
+2 TITL Autosomal DNA Comparison Report – Porridge & Quibble
+2 PAGE 1                      /* 1 document only */
+~ ~ ~                         /* More lines from the CITA structure */
+1 ADDRPLUS Contact information of: FamilyTreeDNA (FTDNA)
+2 ADDR 1445 North Loop West, Suite 820
+3 CITY Houston
+3 STAE TX
+3 POST 77008
+3 CTRY USA
+2 PHON +1-713-868-1438
+3 TITL Main customer support
+2 EMAIL info@familytreedna.com
+3 TITL General inquiries
+2 WWW https://www.familytreedna.com
+3 TITL Official website
+2 AGNC FamilyTreeDNA – Genealogy & Testing Services
+1 CREA 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**👩‍🔬 STICKY @ST0188@ – Gretchen Hazel Porridge (Subject of DNA test)**
+```gedcom
+0 @ST0188@ STICKY             /* Gretchen's DNA is tested */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@            /* Autosomal DNA Comparison Report */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 MAR 2023            /* Date of the test. */
+1 SPLAC @SP0005@              /* Houston, TX, USA */
+1 ROLE MAIN, SUBJECT
+1 NAME
+2 FORM Gretchen Hazel Porridge
+~ ~ ~
+1 SEX F
+1 BIRT
+2 DATE 12 JAN 1984
+2 SPLAC @SP6543@
+1 EVEN IDENTITY, DNATEST, "Autosomal DNA Test Match Report"
+2 DATE 06 MAR 2023            /* Date of the test. */
+2 SPLAC @SP0005@              /* Houston, TX, USA */
+1 FLEX DESCRIPT
+2 PHRASE DNAType
+2 CONTENTS "Autosomal"
+1 FLEX DESCRIPT
+2 PHRASE "Shared DNA (in cM)"
+2 CONTENTS "142.3 cM"
+1 FLEX INTEGER
+2 PHRASE Number of DNA Segments
+2 CONTENTS 18
+1 FLEX DESCRIPT
+2 PHRASE Longest Segment in cM (centimorgans)
+2 CONTENTS "Longest = 23.1 cM"
+1 FLEX DESCRIPT
+2 PHRASE "Estimated Relationship"
+2 CONTENTS "2nd to 3rd cousin"
+1 CREA 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**👨‍🔬 STICKY @ST0288@ – Daniel Quibble (Match)**
+```gedcom
+0 @ST0288@ STICKY             /* Daniel Quibble's DNA is compared to Gretchen's DNA */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@            /* Autosomal DNA Comparison Report */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 MAR 2023            /* Date of the test. */
+1 SPLAC @SP0005@              /* Houston, TX, USA */
+1 ROLE MATCH
+1 NAME
+2 FORM Daniel Quibble
+~ ~ ~
+1 SEX M
+1 BIRT
+2 DATE 03 MAY 1979
+2 SPLAC @SP0005@              /* Houston, TX, USA */
+1 FLEX DESCRIPT
+2 PHRASE DNAType
+2 CONTENTS "Autosomal"
+1 FLEX DESCRIPT
+2 PHRASE "Shared DNA (in cM)"
+2 CONTENTS "142.3 cM"
+1 FLEX INTEGER
+2 PHRASE Number of DNA Segments
+2 CONTENTS 18
+1 FLEX DESCRIPT
+2 PHRASE Longest Segment in cM (centimorgans)
+2 CONTENTS "Longest = 23.1 cM"
+1 F2 PHRASE "Estimated Relationship"
+2 CONTENTS "2nd to 3rd cousin"
+1 CREA 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**📄 STICKY @ST0688@ – DNA Match Report (Asset-STICKY)**
+```gedcom
+0 @ST0688@ STICKY             /* Document with the testresults. */
+1 TYPE DNA, RESULT, Match report /* DNA testresult (is a Match report) */
+1 TITL DNA Test Report
+2 PHRASE by FamilyTreeDNA – Genealogy & Testing Services
+1 SUBM @B001@
+1 TEMPLATE @T0088@            /* Autosomal DNA Comparison Report */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 MAR 2023            /* Date of the test. */
+1 SPLAC @SP0005@              /* Houston, TX, USA */
+1 ROLE ITEM, CERTIFICATE      /* The document itself */
+1 FLEX DESCRIPT
+2 PHRASE Case Nr 01
+2 CONTENTS 1122442-10
+1 FLEX DESCRIPT
+2 PHRASE Case Nr 02
+2 CONTENTS 1122442-11
+1 FLEX REGNUMBER              /* Report #LG-2023-314  */
+2 PHRASE Test number
+2 CONTENTS #LG-2023-314
+~ ~ ~                         /* More testresults here for STR Locus */
+1 FLEX NOTE
+2 PHRASE Statement of Result
+2 CONTENTS The alleged father cannot be excluded as the biological father of the tested child.
+2 CONT Based on the analysis of STR loci listed above, the probability of paternity
+2 CONT is 99.999999999%
+1 CREA 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**🧪 STICKY @ST0388@ – Laboratory: Genetic Information Research Institute (GIRI)**
+```gedcom
+0 @ST0388@ STICKY             /* Lab where the test was done */
+1 TYPE ORGANIZATION, LABORATORY
+1 TITL Genetic Information Research Institute (GIRI)
+1 SUBM @B001@
+1 TEMPLATE @T0088@            /* Autosomal DNA Comparison Report */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 06 MAR 2023            /* Date of the test. */
+1 SPLAC @SP0005@              /* Houston, TX, USA */
+1 ROLE ISSUER, Laboratory     /* officially issued the testresult */
+~ ~ ~
+1 CREA 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**👩 INDIVIDUAL @I888@ – Gretchen Hazel Porridge**
+```gedcom
+0 @I888@ INDI
+1 NAME Gretchen Hazel Porridge
+1 SEX F
+1 ROLES
+2 STICKY @ST0188@
+3 SUBM @B001@
+3 QUAY 3                      /* Direct and primary evidence */
+1 CHAN 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**👨 INDIVIDUAL @I889@ – Daniel Quibble**
+```gedcom
+0 @I889@ INDI
+1 NAME Daniel Quibble
+1 SEX M
+1 ROLES
+2 STICKY @ST0288@
+3 SUBM @001@
+3 QUAY 3                      /* Direct and primary evidence */
+1 CHAN 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+**📚 SOURCE @S0088@ – Autosomal DNA Comparison Report – Porridge & Quibble**
+```gedcom
+0 @S0088@ SOUR
+1 TITL Autosomal DNA Comparison Report – Porridge & Quibble
+1 AUTH Genetic Information Research Institute (GIRI)
+1 PUBL "Report #LG-2023-314"
+1 DATA
+2 DATE 06 MAR 2023
+2 TEXT "Gretchen Porridge and Daniel Quibble share 142.3 centiMorgans across 18 segments."
+2 LANG eng
+2 MIME text/plain
+~ ~ ~
+1 OBJE @O0054@
+2 TITL Plaintext Summary Report
+~ ~ ~
+```
+**💾 OBJE @O0054@ – Multimedia record with Plaintext Summary Report**
+```gedcom
+0 @O0054@ OBJE                /* Multimedia record with file link  */
+1 FILE https://leafgen.example/reports/lg-2023-314.txt
+1 FORM text/plain
+1 TITL Plaintext Summary Report
+1 CREA 01 MAY 2025
+1 CHAN 07 AUG 2025
+```
+
+**🧬 TEMPLATE @T0931@ – Direct DNA Genotype Report – Gretchen Hazel Porridge**
+```gedcom
+0 @T0931@ TEMPLATE
+1 TYPE IDENTITY, DNATEST
+1 TITL Direct DNA Genotype Report – Gretchen Hazel Porridge
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 04 JUL 2025
+1 SPLAC @SP88332@             /* San Mateo, CA, USA */
+1 EVEN IDENTITY, DNATEST
+2 DATE 04 JUL 2025
+2 SPLAC @SP88332@             /* San Mateo, CA, USA */
+1 CITA
+2 SOUR @S0094@
+2 PAGE 1
+~ ~ ~                         /* More lines from the CITA structure */
+1 ADDRPLUS Contact information of: Genetic Information Research Institute (GIRI)
+2 ADDR 2020 Alameda de las Pulgas
+3 CITY San Mateo
+3 STAE CA
+3 POST 94403
+3 CTRY USA
+2 PHON +1-650-212-2220
+3 TITL Main research line
+2 PHON +1-650-212-2221
+3 TITL Fax line for document intake
+2 EMAIL contact@girinst.org
+3 TITL General correspondence
+2 EMAIL submissions@girinst.org
+3 TITL Sequence data submission desk
+2 WWW https://www.girinst.org
+3 TITL Official research website
+2 AGNC GIRI – Public communications desk
+1 ROLES
+2 STICKY @ST0411@  /* Gretchen Porridge – MAIN, SUBJECT */
+2 STICKY @ST0388@  /* Genetic Information Research Institute – ISSUER */
+1 OBJE @O0094@
+1 CREA 20 JUL 2025
+1 CHAN 07 AUG 2025
+```
+**👤 STICKY – Gretchen Hazel Porridge (Genotype)**
+```gedcom
+0 @ST0411@ STICKY  /* Gretchen Hazel Porridge */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0931@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 EVEN IDENTITY, DNATEST
+2 DATE 04 JUL 2025
+2 SPLAC @SP88332@             /* San Mateo, CA, USA */
+1 ROLE MAIN, SUBJECT
+1 NAME
+2 FORM Gretchen Hazel Porridge
+2 PART Gretchen
+3 TYPE GIVN
+2 PART Hazel
+3 TYPE GIVN
+2 PART Porridge
+3 TYPE SURN
+1 FLEX DNATYPE
+2 PHRASE DNA test type
+2 CONTENTS autosomal
+1 FLEX ARRAY
+2 PHRASE Raw genotype values
+2 CONTENTS ARRAY
+3 CONT (rs123456, A)
+3 CONT (rs234567, T)
+3 CONT (rs345678, G)
+3 CONT (rs456789, C)
+3 CONT (rs567890, T)
+3 CONT (rs678901, A)
+3 CONT (rs789012, G)
+3 (… more rows omitted for clarity …)
+1 CREA 20 JUL 2025
+1 CHAN 07 AUG 2025
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-12"></a>  
+
+## 🛖 Example 12: Norwegian Farm Membership
+###  – "Lien Farm Census, 1832"
+
+This example shows how to represent a **traditional Norwegian farm** as a `GROUP`, linked to individual residents via `STICKY`. The example includes:
+
+- A `TEMPLATE` of type `GROUP, FARM-MEM` describing a 19th-century **farm census**.
+- A `GROUP` record representing the **Lien Farm**, marked with a `DATE` of origin and `SPLAC`.
+- A `STICKY` showing **Ola Thorbjørnsen Lien** as a **farm resident** at that time.
+- Structured `NAME` blocks for semantic clarity.
+- Scandinavian naming customs reflected in surname usage.
+
+It demonstrates how to use a `GROUP` record to represent a traditional Norwegian farm, and how to associate individuals with that group through a `STICKY` record:
+- The `GROUP` representing the **Lien Farm**, is typed as `GROUP, FARM-MEM`, given an `SPLAC`, and marked with a historical `DATE` to suggest the general origin of the group.
+- The `NAME` reflects the name of the farm, with a `PART` of type `LOCATION` to aid semantic clarity.
+- The `INDI` record for Ola Lien shows a name consistent with the local naming tradition, where farm names often became surnames.
+- Ola's `STICKY` record links Ola to the farm group, dated 1832, and uses the role `MAIN, LEADER, RESIDENT`. `MAIN` because he is the main person in this `TEMPLATE`, `LEADER` because he is head of the house, and `RESIDENT` because he lives on that farm.
+- A comment ( /*  */ ) is used for precise clarification of the `STICKY`’s context.
+
+This example reflects the traditional Scandinavian use of farm names. A farm (`GROUP`) represents a naming unit, and individuals link to it via `STICKY`.
+
+| 🧑 Person         | 🧾 STICKY | Roles                     | OCCU           | Notes                   |
+|-------------------|------------|---------------------------|----------------|-------------------------|
+| Ola Thorbjørnsen Lien   | @ST0091@   | `MAIN, LEADER, RESIDENT`    | Farmer         | Head of household       |
+| Ingebjørg Syversdatter Lien | @ST0092@ | `SPOUSE, MEMBER, RESIDENT` | Domestic work  | Wife of Ola             |
+| Marit Olsdatter Lien  | @ST0093@   | `CHILD, MEMBER, RESIDENT`   | —              | Daughter, 6 years old   |
+| Erik Knutsen Lien     | @ST0094@   | `WORKER, RESIDENT`          | Farmhand       | Hired laborer           |
+
+**🛖📄 @T0073@ – TEMPLATE – Lien Farm Census, 1832, containg the household members in that year**
+```gedcom
+0 @T0073@ TEMPLATE            /* Lien Farm Census, 1832 */
+1 TYPE GROUP, FARM-MEM        /* TEMPLATE TYPE from event enumtable */
+1 TITL Lien Farm Census, 1832 /* This TEMPLATE came from a Lien Farm Census, 1832 */
+1 PHRASE Census of farm members in Valdres, Norway
+1 SUBM @B001@                 /* Standard submitter */
+1 TORIGIN ORIGDOC             /* Derived from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 01 JAN 1832
+1 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 EVEN GROUP, FARM-MEM2
+2 DATE 01 JAN 1832
+2 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 ROLES
+2 STICKY @ST0091@             /* Ola Lien – MAIN, LEADER, RESIDENT */
+2 STICKY @ST0092@             /* Ingebjørg Lien – MAIN, SPOUSE, MEMBER, RESIDENT */
+2 STICKY @ST0093@             /* Marit Olsdatter – MAIN, CHILD, MEMBER, RESIDENT */
+2 STICKY @ST0094@             /* Erik Knutsen – MAIN, WORKER, RESIDENT */
+1 CITA
+2 SOUR @S0361@                /* Original document (not present here) */
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 CREA 17 JUL 2025
+1 CHAN 08 AUG 2025
+```
+**🌾 @G0024@ – GROUP – Lien Farm Household. It has 4 members in the HISTORY section**
+```gedcom
+0 @G0024@ GROUP
+1 TYPE FARM                   /* groups all farm members of this farm over time */
+1 TITL Lien Farm Group
+1 PHRASE Historic residence unit in Valdres, Norway
+1 SUBM @B001@
+1 NAME
+2 FORM Lien
+2 PART Lien
+3 TYPE LOCATION
+1 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 DATE 1700
+1 MEMBERS
+2 STICKY @ST0091@             /* Ola Thorbjørnsen Lien */
+2 STICKY @ST0092@             /* Ingebjørg Syversdatter Lien */
+2 STICKY @ST0093@             /* Marit Olsdatter Lien */
+2 STICKY @ST0094@             /* Erik Knutsen Lien */
+1 NOTE Residents of this farm traditionally adopted 'Lien' as a surname.
+1 CREA 17 JUL 2025
+1 CHAN 08 AUG 2025
+```
+**👨‍🦰 @ST0091@ – STICKY – Ola Thorbjørnsen Lien – MAIN, LEADER, RESIDENT**
+```gedcom
+0 @ST0091@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0073@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 01 JAN 1832
+1 ROLE MAIN, LEADER, RESIDENT /* RESIDENT, so he is a member of the GROUP */
+1 GROUP @G0024@               /* Lien Farm, Valdres, Norway */
+1 EVEN GROUP, FARM-MEM2
+2 DATE 01 JAN 1832
+2 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 NAME
+2 FORM Ola Thorbjørnsen Lien
+2 PART Ola
+3 TYPE GIVN
+2 Part Thorbjørnsen           /* Original patronymic lastname */
+3 TYPE SURN
+2 PART Lien
+3 TYPE LOCATION
+1 AGE 39
+1 SEX M
+1 OCCU Farmer
+1 NOTE Head of household residing at Lien Farm.
+1 NOTE Ola Lien appears in farm census of 1832.
+~ ~ ~
+```
+**👩🏼‍🦰 @ST0092@ – STICKY – Ingebjørg Syversdatter Lien – SPOUSE, MEMBER, RESIDENT**
+```gedcom
+0 @ST0092@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0073@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 01 JAN 1832
+1 ROLE MAIN, SPOUSE, RESIDENT /* RESIDENT, so a member of the GROUP */
+1 GROUP @G0024@               /* Lien Farm, Valdres, Norway */
+1 EVEN GROUP, FARM-MEM2
+2 DATE 01 JAN 1832
+2 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 NAME
+2 FORM Ingebjørg Syversdatter Lien /* Syversdatter is patronymic part */
+~ ~ ~
+1 AGE 36
+1 OCCU Domestic work
+1 NOTE Wife of Ola Lien, residing at the farm.
+~ ~ ~
+```
+**👧🏼 @ST0093@ – STICKY – Marit Olsdatter Lien – CHILD, MEMBER, RESIDENT**
+```gedcom
+0 @ST0093@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0073@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 01 JAN 1832
+1 ROLE MAIN, CHILD, RESIDENT  /* RESIDENT, so a member of the GROUP */
+1 GROUP @G0024@               /* Lien Farm, Valdres, Norway */
+1 EVEN GROUP, FARM-MEM2
+2 DATE 01 JAN 1832
+2 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 NAME
+2 FORM Marit Olsdatter Lien   /* Olsdatter is patronymic part, daughter of Ola */
+~ ~ ~
+1 AGE 6
+1 NOTE Daughter of Ola and Ingebjørg, born at the farm.
+~ ~ ~
+```
+**👨🏻 @ST0094@ – STICKY – Erik Knutsen Lien – WORKER, RESIDENT**
+```gedcom
+0 @ST0094@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0073@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 01 JAN 1832
+1 ROLE MAIN, WORKER, RESIDENT /* RESIDENT, so a member of the GROUP */
+1 GROUP @G0024@               /* Lien Farm, Valdres, Norway */
+1 EVEN GROUP, FARM-MEM2
+2 DATE 01 JAN 1832
+2 SPLAC @SP073@               /* Lien Farm, Valdres, Norway */
+1 NAME
+2 FORM Erik Knutsen Lien      /* Knutsen is patronymic part */
+~ ~ ~
+1 AGE 22
+1 OCCU Farmhand
+1 NOTE Hired worker living on the farm at time of census.
+~ ~ ~
+```
+**👨‍🦰 @I0215@ – INDI – Ola Thorbjørnsen Lien**
+```gedcom
+0 @I0215@ INDI
+1 NAME
+2 FORM Ola Thorbjørnsen Lien
+2 PART Ola
+3 TYPE GIVN
+2 Part Thorbjørnsen           /* Original patronymic lastname */
+3 TYPE SURN
+2 PART Lien
+3 TYPE LOCATION
+1 SEX M
+1 ROLES
+2 STICKY @ST0091@             /* Farm Census 1832 */
+2 STICKY @ST0034@             /* Birth of Ola Lien (Template not present) */
+2 STICKY @ST0042@             /* Marriage to Ingebjørg (Template not present) */
+~ ~ ~
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-13"></a>  
+
+## 🏥 Example 13: Hospital Admission and Discharge Record
+
+> **Example 13 – Hospital Admission and Discharge Record**  
+>  
+> This GEDCOM 8 example demonstrates how to document a medical event using two `TEMPLATE`s: one for admission and one for discharge. The example includes:
+>
+> - **Clara Wensley**, admitted to *County General Hospital* in 1933 for acute appendicitis  
+> - The *hospital* modeled as an `ORGANIZATION` with role `SITE` (location where the event occurred)  
+> - The *physician* involved in admission and treatment  
+>  
+> The admission and discharge are captured as two separate `TEMPLATE`s, **as each always has its own set of STICKYs** — even though the people and place are the same. This ensures all `TEMPLATE`s remain self-contained.
+>
+> The example also includes:
+> - Usage of `ROLE` values like `PATIENT`, `PHYSICIAN`, and `SITE`  
+> - Demonstration of `FLEX`, `SPLAC`, and `SOURCE` linking to a scanned register entry  
+> - Touches of humor in `OCCU`, `NOTE`, and `PHRASE` to support clarity and reader engagement.
+
+**👩🏼‍🦱 @T0048@ TEMPLATE – Hospital Admission Record of Edith Clara Wensley**
+```gedcom
+0 @T0048@ TEMPLATE            /* Hospital Admission Record of Edith Clara Wensley */
+1 TYPE MEDICAL, ADMISSION "Hospital Admission Record"
+1 TITL Hospital Admission Record – Edith Clara Wensley, 1933
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 17 FEB 1933
+1 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 EVEN MEDICAL, ADMISSION 
+2 DATE 17 FEB 1933
+2 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 ROLES
+2 STICKY @ST0148@             /* MAIN, PATIENT Edith Clara Wensley */
+2 STICKY @ST0248@             /* PHYSICIAN Dr. Mortimer Hackett */
+2 STICKY @ST0348@             /* ORGANIZATION, MEDICAL, Hospital */
+1 CITA
+2 SOUR @S0048@
+2 TITL Hospital Admission Record – Edith Wensley, 1933
+~ ~ ~
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**👩🏼‍🦱 @ST0148@ STICKY – MAIN, PATIENT Clara Wensley, admission to Hospital**
+```gedcom
+0 @ST0148@ STICKY             /* MAIN, PATIENT Edith Clara Wensley, admission to Hospital */
+1 TYPE PERSON
+1 TITL "Admission to County General Hospital"
+1 SUBM @B001@
+1 TEMPLATE @T0048@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 17 FEB 1933
+1 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 ROLE MAIN, PATIENT
+1 EVEN MEDICAL, ADMISSION 
+2 DATE 17 FEB 1933
+2 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 NAME
+2 FORM Edith Clara Wensley
+2 PART Edith
+3 TYPE GIVN
+2 PART Clara
+3 TYPE GIVN
+2 PART Wensley
+3 TYPE SURN
+1 SEX F
+1 AGE 41
+1 OCCU "Typesetter (known for near-perfect kerning)"
+1 FLEX DESCRIPT
+2 PHRASE "Reason for Admission"
+2 CONTENTS "Acute appendicitis, with mild newspaper withdrawal symptoms"
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**👩🏼‍🦱 @ST0248@ STICKY – PHYSICIAN Dr. Mortimer Hackett 🪓**
+```gedcom
+0 @ST0248@ STICKY             /* PHYSICIAN Dr. Mortimer Hackett */
+1 TYPE PERSON
+1 TITL "Admitting Physician – Dr. Mortimer Hackett"1 SUBM @B001@
+1 TEMPLATE @T0048@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 17 FEB 1933
+1 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 ROLE PHYSICIAN
+1 NAME
+2 FORM Dr. Mortimer Hackett
+2 PART Dr.
+3 TYPE PREFIX
+2 PART Mortimer
+3 TYPE GIVN
+2 PART Hackett
+3 TYPE SURN
+1 SEX M
+1 OCCU "Senior Surgeon, specialist in rapid decisions"
+1 NOTE "Once diagnosed a broken heart as literal. Reputation: uneven."
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**🏥 @ST0348@ STICKY – County General Hospital, Manchester 🏥**
+```gedcom
+0 @ST0348@ STICKY             /* County General Hospital, Manchester */
+1 TYPE ORGANIZATION, MEDICAL, Hospital
+1 TITL "Admission Location – County General Hospital, Manchester"1 SUBM @B001@
+1 TEMPLATE @T0048@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 17 FEB 1933
+1 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 ROLE SITE                   /* Hospital */
+1 NAME
+2 FORM County General Hospital, Manchester
+~ ~ ~
+1 NOTE "Operational since 1891. Tea breaks strictly enforced."
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**👩🏼‍🦱 @I601@ INDI – Edith Clara Wensley**
+```gedcom
+0 @I601@ INDI                 /* INDI of Edith Clara Wensley */
+1 NAME
+2 FORM Edith Clara Wensley
+2 PART Edith
+3 TYPE GIVN
+2 PART Clara
+3 TYPE GIVN
+2 PART Wensley
+3 TYPE SURN
+1 SEX F
+1 AGE 41
+1 ROLES
+2 STICKY @ST0148@             /* MAIN, PATIENT Edith Clara Wensley, admission to Hospital */
+2 STICKY @ST0150@             /* MAIN, PATIENT Edith Clara Wensley, discharge from Hospital */
+1 CHAN 08 AUG 2025
+```
+**💾 @S0048@  SOUR – County General Archives**
+```gedcom
+0 @S0048@ SOUR
+1 TITL Hospital Admission Records, 1933
+1 AUTH County General Archives
+1 PUBL "Volume 3A: Medical Admissions 1930–1935"
+1 ABBR "MedAdm 1933"
+1 DATA
+2 EVEN MEDICAL, ADMISSION
+3 DATE 1933
+3 PLAC Manchester, UK
+2 AGNC County General Hospital
+~ ~ ~
+1 TEXT "Edith Wensley was admitted for appendicitis and treated by Dr. Mortimer Hackett."
+2 MIME application/pdf
+2 LANG eng
+1 OBJE @O025@
+2 TITL Scanned register entry
+~ ~ ~
+```
+**💾 @O025@  OBJE – Multimedia record with file link**
+```gedcom
+0 @O025@ OBJE                 /* Multimedia record with file link  */
+1 FILE https://example.org/hospital/wensley-admission-1933.pdf
+1 FORM application/pdf
+1 TITL Scanned register entry
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**👩🏼‍🦱 @T0048@ TEMPLATE – Hospital Discharge Record of Edith Clara Wensley**
+```gedcom
+0 @T0049@ TEMPLATE            /* Hospital Discharge Record of Edith Clara Wensley */
+1 TYPE MEDICAL, DISCHARGE "Hospital Discharge Record"
+1 TITL "Hospital Discharge Record of Edith Clara Wensley"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 25 FEB 1933
+1 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 EVEN MEDICAL, DISCHARGE 
+2 DATE 25 FEB 1933
+2 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 ROLES
+2 STICKY @ST0150@             /* PERSON, MAIN, PATIENT Edith Clara Wensley */
+2 STICKY @ST0250@             /* PERSON, PHYSICIAN */
+2 STICKY @ST0350@             /* ORGANIZATION, FACILITY */
+1 CITA
+2 SOUR @S0049@                /* Hospital Discharge Record – Edith Wensley, 1933 */
+2 PAGE 5
+2 DATA
+2 TITL "Hospital Discharge Record – Edith Wensley, 1933"
+~ ~ ~
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**👩🏼‍🦱 @ST0150@ STICKY – PATIENT Edith Clara Wensley, discharge from Hospital**
+```gedcom
+0 @ST0150@ STICKY             /* PATIENT Edith Clara Wensley, discharge from Hospital */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0049@            /* Hospital Discharge Record of Edith Clara Wensley */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE MAIN, PATIENT
+1 EVEN MEDICAL, DISCHARGE 
+2 DATE 25 FEB 1933
+2 SPLAC @SP5588@              /* County General Hospital, Manchester, UK */
+1 NAME
+2 FORM Edith Clara Wensley
+2 PART Edith
+3 TYPE GIVN
+2 PART Clara
+3 TYPE GIVN
+2 PART Wensley
+3 TYPE SURN
+1 SEX F
+1 AGE 41
+1 OCCU "Typesetter (known for near-perfect kerning)"
+1 FLEX DESCRIPT
+2 PHRASE "Reason for Admission"
+2 CONTENTS "Acute appendicitis, with mild newspaper withdrawal symptoms"
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**👩🏼‍🦱 @ST0250@ STICKY – PHYSICIAN Dr. Mortimer Hackett 🪓**
+```gedcom
+0 @ST0250@ STICKY             /* PHYSICIAN Dr. Mortimer Hackett */
+1 TYPE PERSON
+1 SUBM @B001@
+1 ROLE PHYSICIAN
+1 NAME
+2 FORM Dr. Mortimer Hackett
+2 PART Dr.
+3 TYPE PREFIX
+2 PART Mortimer
+3 TYPE GIVN
+2 PART Hackett
+3 TYPE SURN
+1 SEX M
+1 OCCU "Senior Surgeon, specialist in rapid decisions"
+1 NOTE "Once diagnosed a broken heart as literal. Reputation: uneven."
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**🏥 @ST0350@ STICKY – County General Hospital, Manchester 🏥**
+```gedcom
+0 @ST0350@ STICKY             /* County General Hospital, Manchester */
+1 TYPE ORGANIZATION, MEDICAL, Hospital
+1 SUBM @B001@
+1 ROLE SITE
+1 NAME
+2 FORM County General Hospital, Manchester
+1 NOTE "Operational since 1891. Tea breaks strictly enforced."
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+**💾 @S0049@  SOUR – Hospital Discharge Record**
+```gedcom
+0 @S0049@ SOUR
+1 TITL "Hospital Discharge Record – Edith Wensley, 1933"
+1 AUTH County General Archives
+1 PUBL "Volume 3A: Medical Discharges 1930–1935"
+1 ABBR "Wensley Discharge 1933"
+1 DATA
+2 EVEN MEDICAL, DISCHARGE
+3 DATE 25 FEB 1933
+4 PHRASE "Successful recovery from appendectomy"
+3 PLAC Manchester, UK
+2 AGNC County General Hospital
+~ ~ ~
+1 NOTE "Edith Wensley discharged after full recovery and minor complaints about the tea."
+1 OBJE @O062@
+2 TITL Scanned discharge entry
+~ ~ ~
+```
+**💾 @O062@  OBJE – Multimedia record with file link**
+```gedcom
+0 @O062@ OBJE                 /* Multimedia record with file link  */
+1 FILE https://example.org/hospital/wensley-discharge-1933.pdf
+1 FORM application/pdf
+1 TITL Scanned discharge entry
+1 CREA 30 APR 2025
+1 CHAN 08 AUG 2025
+```
+
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-14"></a> 
+
+## 🛠️ Example 14: Mid Century Employment Transfer Order
+
+This GEDCOM 8 example documents the official transfer of Gertrude Elmsbottom, a long-serving employee of Western Office Supplies Co., from the Leiden branch to the Rotterdam headquarters in June 1954. It showcases how occupational changes can be modeled with detailed `STICKY` roles for both the employee and the organizations involved, including an issuer of the transfer. The record draws directly from an original corporate memo and includes:
+- Clear `EMPLOYER` roles for both origin and destination workplaces
+- Date-specific `OCCU` entries for old and new positions
+- Use of `FLEX DESCRIPT` for job title details
+- Address information for the destination workplace
+- A source record referencing a scanned internal memo
+
+It demonstrates how employment events can be precisely recorded with origin/destination tracking, organizational metadata, and asset linkage for documentary evidence.
+
+**🏢 @T0050@ TEMPLATE – Employment Transfer Order for Gertrude Elmsbottom, 1954 🏢**
+```gedcom
+0 @T0050@ TEMPLATE
+1 TYPE OCCUPATIONAL, EMPLOYMENT, "Employment Transfer Order"
+1 TITL Employment Transfer – Gertrude Elmsbottom, 1954
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954
+1 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 EVEN OCCUPATIONAL, EMPLOYMENT, "Employment Transfer Order"
+2 DATE 18 JUN 1954
+2 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 ROLES
+2 STICKY @ST0150@             /* Gertrude Elmsbottom MAIN, EMPLOYEE */
+2 STICKY @ST0250@             /* Western Office Supplies Co., Leiden Branch EMPLOYER */
+2 STICKY @ST0251@             /* Western Office Supplies Co., Rotterdam HQ EMPLOYER */
+2 STICKY @ST0350@             /* Mr. Cornelis P. Wriggle ISSUER */
+1 CITA
+2 SOUR @S0050@
+2 TITL Employment Transfer – Gertrude Elmsbottom, 1954
+~ ~ ~
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**👩🏼‍🦰 @ST0150@ – STICKY – Gertrude Elmsbottom MAIN, EMPLOYEE**
+```gedcom
+0 @ST0150@ STICKY             /* Gertrude Elmsbottom MAIN, EMPLOYEE */
+1 TYPE PERSON
+1 TITL Employment Transfer – Gertrude Elmsbottom, 1954
+1 SUBM @B001@
+1 TEMPLATE @T0050@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954
+1 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 EVEN OCCUPATIONAL, EMPLOYMENT, "Employment Transfer Order"
+2 DATE 18 JUN 1954
+2 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 ROLE MAIN, EMPLOYEE
+1 NAME
+2 TYPE BIRTH
+2 FORM Gertrude Elmsbottom
+2 PART Gertrude
+3 TYPE GIVN
+2 PART Elmsbottom
+3 TYPE SURN
+1 SEX F
+1 AGE 42
+1 OCCU "Team lead, mailroom automation (1950–1954)" /* Current job */
+2 SPLAC @SP0042@              /* Western Office Supplies Co., Leiden Branch (place from) */
+2 DATE 17 JUN 1954            /* Last working day in old job in Leiden */
+1 OCCU "Senior clerk, whisperer of paper clips" /* New job */
+2 SPLAC @SP0043@              /* Western Office Supplies Co., Rotterdam HQ (place to) */
+2 DATE 18 JUN 1954            /* Starting date for new job in Rotterdam */
+1 FLEX DESCRIPT
+2 PHRASE "New position"
+2 CONTENTS "Departmental Correspondence Overlord, Level II"
+1 NOTE "Gertrude Elmsbottom was officially reassigned to HQ effective immediately."
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**🏢 🧑‍🎓 @ST0250@ – STICKY – Western Office Supplies Co., Leiden Branch - ORGANIZATION, COMPANY 🏢 🧑‍🎓**
+```gedcom
+0 @ST0250@ STICKY             /* Western Office Supplies Co., Leiden Branch */
+1 TYPE ORGANIZATION, COMPANY, WORKPLACE
+1 TITL Western Office Supplies Co., Leiden Branch
+1 SUBM @B001@
+1 TEMPLATE @T0050@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954
+1 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 ROLE EMPLOYER
+1 NAME
+2 FORM Western Office Supplies Co., Leiden Branch
+~ ~ ~                         /* Rest of the NAME structure */
+1 NOTE "Originating office. Known for lukewarm coffee and aggressive filing."
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**🏢 🚢 @ST0251@ – STICKY – Western Office Supplies Co., Rotterdam HQ (Destination) - ORGANIZATION, COMPANY 🏢 🚢**
+```gedcom
+0 @ST0251@ STICKY             /* Western Office Supplies Co., Rotterdam HQ (Destination) */
+1 TYPE ORGANIZATION, COMPANY, WORKPLACE
+1 TITL Western Office Supplies Co., Rotterdam HQ (Destination)
+1 SUBM @B001@
+1 TEMPLATE @T0050@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954
+1 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 ROLE EMPLOYER
+1 NAME
+2 FORM Western Office Supplies Co., Rotterdam HQ
+1 ADDR
+2 STREET Clipfileplein 14
+2 CITY Rotterdam
+2 POST 3012 CD
+2 CTRY Netherlands
+1 NOTE "Receives employee. Boasts a third-floor nap corridor."
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**👨🏻‍🦱 @ST0350@ – STICKY – Mr. Cornelis P. Wriggle ISSUER**
+```gedcom
+0 @ST0350@ STICKY             /* Mr. Cornelis P. Wriggle ISSUER */
+1 TYPE PERSON
+1 TITL Mr. Cornelis P. Wriggle ISSUE
+1 SUBM @B001@
+1 TEMPLATE @T0050@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 18 JUN 1954
+1 SPLAC @SP0046@              /* Rotterdam, Netherlands */
+1 ROLE ISSUER
+1 NAME
+2 FORM Mr. Cornelis P. Wriggle
+2 PART Cornelis
+3 TYPE GIVN
+2 PART P.
+3 TYPE GIVN
+2 PART Wriggle
+3 TYPE SURN
+1 SEX M
+1 OCCU "HR Officer and certified form-stamp enthusiast"
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**👩🏼‍🦰 @I701@ – INDI – Gertrude Elmsbottom**
+```gedcom
+0 @I701@ INDI                 /* Gertrude Elmsbottom MAIN, EMPLOYEE */
+1 NAME
+2 TYPE BIRTH
+2 FORM Gertrude Elmsbottom
+2 PART Gertrude
+3 TYPE GIVN
+2 PART Elmsbottom
+3 TYPE SURN
+1 SEX F
+1 ROLES
+1 STICKY @ST0151@             /* OCCU: Junior typist (1938–1945) not in this example */
+1 STICKY @ST0152@             /* OCCU: Wartime administrator (1945–1948) not in this example */
+1 STICKY @ST0153@             /* OCCU: Team lead, mailroom automation (1950–1954) */
+1 STICKY @ST0150@             /* OCCU: Senior clerk (1954 transfer to Rotterdam HQ) */
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**💾 @S0050@  SOUR – Employment Transfer – Gertrude Elmsbottom, 1954**
+```gedcom
+0 @S0050@ SOUR                /* Employment Transfer – Gertrude Elmsbottom, 1954 */
+1 TITL Employment Transfer – Gertrude Elmsbottom, 1954
+1 AUTH Western Office Supplies Co.
+1 PUBL "Internal Memo Archive, Binder F-12"
+1 ABBR "Transfer Order 1954"
+1 DATA
+2 EVEN OCCUPATIONAL, EMPLOYMENT, "Employment Transfer Order"
+3 DATE 18 JUN 1954
+4 PHRASE "Official transfer from Leiden to Rotterdam"
+3 PLAC Rotterdam, Netherlands
+2 AGNC Western Office Supplies Co.
+~ ~ ~                         /* More from the SOUR */
+1 OBJE @O0011@
+2 TITL Scanned internal memo
+~ ~ ~
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+**💾 @O0011@  OBJE – Multimedia record with file link**
+```gedcom
+0 @O0011@ OBJE                /* Multimedia record with file link  */
+1 FILE https://example.org/employment/elmsbottom-transfer-1954.pdf
+1 TITL Scanned internal memo
+1 FORM application/pdf
+1 CREA 30 APR 2025
+1 CHAN 12 AUG 2025
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-15"></a>  
+
+## 🧾 Example 15: Legal Will Creation and Execution with Estate Transfers
+
+This GEDCOM 8 example models a **two-stage legal will process** using dual `TEMPLATE` records:
+
+1. **Will Creation** (`TYPE DEATH, WILL, "Creation of the Will"`) — where the testator (Emil Rothenbühler) formally records their intentions.
+2. **Will Execution** (`TYPE DEATH, WILL, "Execution of the Will"`) — following the testator's death, where the estate is distributed to named heirs.
+
+The example includes:
+
+- A **decedent**, whose two `STICKY` roles span both creation and execution phases.
+- A **legal executor**, present in both `TEMPLATE`S with professional credentials and `STICKY` structure for reuse across stages.
+- A **notary office**, modeled as an organization (`ORGANIZATION, NOTAR`) with official certification duties.
+- Multiple **heirs**, each receiving a specific asset and a tailored percentage of the liquid estate to ensure equal inheritance value.
+- Multiple **ASSET** `STICKY`s, each transferred via a `TRANSFER` structure with witty `NOTE`s included for flair and realism.
+- A realistic **bank division** where the remaining money after asset assignment is split in calculated percentages to equalize the total value inherited by each heir.
+- Use of `FLEX VALUE` for asset appraisal, and `SHARE` for partial distribution.
+- Proper linkage to an `INDI` record for Emil Rothenbühler connecting both `STICKY`s.
+
+This example demonstrates how GEDCOM 8 enables structured inheritance scenarios using linked `STICKY`, `TRANSFER`, and `TEMPLATE` blocks — reflecting complex legal and familial dynamics while remaining strictly spec-compliant.
+
+
+**📜 @T016@ TEMPLATE – Creation of the Will of Emil Rothenbühler**
+```gedcom
+0 @T015@ TEMPLATE
+1 TYPE DEATH, WILL, "Creation of the Will"
+1 TITL Last Will and Testament of Emil Rothenbühler
+2 PHRASE "Creation of the Will of Emil Rothenbühler"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 8 SEP 1998
+1 SPLAC @SP001@               /* Bern, Switzerland */
+1 EVEN DEATH, WILL, "Creation of the Will"
+2 DATE 8 SEP 1998
+2 SPLAC @SP001@               /* Bern, Switzerland */
+1 ROLES
+2 STICKY @ST0151@             /* Emil Rothenbühler     - MAIN, GRANTOR - Will Creation */
+2 STICKY @ST0251@             /* Franz Müller          - NOTARY - Will Creation */
+2 STICKY @ST0252@             /* Notariat Bern Zentrum - ORGANIZATION, NOTARY - Will Creation */
+1 CITA
+2 SOUR @S0341@                /* Not present in this example */
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 CREA 30 APR 2025
+1 CHAN 20 JUL 2025
+```
+**🧔‍♂️ @ST0151@ STICKY – Emil Rothenbühler**
+```gedcom
+0 @ST0151@ STICKY             /* Emil Rothenbühler, GRANTOR, DECEDENT */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T015@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE MAIN, GRANTOR          /* NOT role DECEDENT as at this time he is still alive */
+1 NAME
+2 FORM Emil Rothenbühler
+2 PART Emil
+3 TYPE GIVN
+2 PART Rothenbühler
+3 TYPE SURN
+1 SEX M
+1 BIRT
+2 DATE 1952
+2 SPLAC @SP002@               /* Zürich, Switzerland */
+1 OCCU Chocolatier
+1 CREA 30 APR 2025
+1 CHAN 20 JUL 2025
+```
+**🧑‍⚖️ @ST0251@ STICKY – Franz Müller**
+```gedcom
+0 @ST0251@ STICKY             /* Franz Müller NOTARY */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T015@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE NOTARY                 /* Helped writing the will, ensures proper legal formalities */
+1 NAME
+2 FORM Franz Müller
+2 PART Franz
+3 TYPE GIVN
+2 PART Müller
+3 TYPE SURN
+1 OCCU Lawyer
+1 CREA 30 APR 2025
+1 CHAN 20 JUL 2025
+```
+**🏛️ @ST0252@ STICKY – Notariat Bern Zentrum**
+```gedcom
+0 @ST0252@ STICKY             /* Notariat Bern Zentrum */
+1 TYPE ORGANIZATION, NOTARY
+1 SUBM @B001@
+1 TEMPLATE @T015@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE NOTARY
+1 NAME
+2 FORM Notariat Bern Zentrum
+2 PART Notariat Bern Zentrum
+3 TYPE ORGL
+1 CREA 30 APR 2025
+1 CHAN 20 JUL 2025
+```
+**📜 @T016@ TEMPLATE – Execution of the Will of Emil Rothenbühler**
+```gedcom
+0 @T016@ TEMPLATE             /* Execution of Will (Emil Rothenbühler) */
+1 TYPE DEATH, WILL, "Execution of Will and Estate Transfer"
+1 TITL "Execution of Will and Estate Transfer of Emil Rothenbühler"
+2 PHRASE "Execution of the Will of Emil Rothenbühler"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 01 JUN 2020
+1 SPLAC @SP8585@              /* Bern, Switzerland */
+1 EVEN DEATH, WILL
+2 DATE 01 JUN 2020
+2 SPLAC @SP8585@              /* Bern, Switzerland */
+1 ROLES
+2 STICKY @ST0152@             /* 👴 Emil Rothenbühler - MAIN, GRANTOR, DECEDENT */
+2 STICKY @ST0253@             /* Franz Müller - EXECUTOR */
+2 STICKY @ST0254@             /* Notariat Bern Zentrum - NOTARY */
+2 STICKY @ST0351@             /* 🧔🏻‍♂️ Markus Rothenbühler - HEIR1, SON */
+2 STICKY @ST0352@             /* 👱🏻‍♀️ Sophie Rothenbühler - HEIR2, DAUGHTER */
+2 STICKY @ST0353@             /* 👩🏻‍🦰 Eliane Keller - HEIR3 */
+2 STICKY @ST0451@             /* Alpine Chalet - ASSET ESTATE, COUNTRYHOUSE */
+2 STICKY @ST0452@             /* ⌚Vintage Watch - ASSET BELONGINGS, CLOTHING, "Watch" */
+2 STICKY @ST0453@             /* 📚Book Collection - ASSET BOOK, LITERATURE, "Book collection" */
+2 STICKY @ST0454@             /* 💰Bank Account - ASSET FINANCE, ACCOUNTS */
+
+1 TRANSFER @ST0451@           /* 🏡Alpine Chalet at Lake Oeschinen */
+2 GRANTOR @ST0152@            /* 👴 Emil Rothenbühler - MAIN, GRANTOR, DECEDENT */
+2 GRANTEE @ST0351@            /* 🧔🏻‍♂️ Markus Rothenbühler - HEIR1, SON */
+1 NOTE "🏡 The house near Lake Oeschinen goes to Markus."
+
+1 TRANSFER @ST0452@           /* ⌚Vintage Watch: Patek Philippe 1952 Ref. 2499 */
+2 GRANTOR @ST0152@            /* 👴 Emil Rothenbühler - MAIN, GRANTOR, DECEDENT */
+2 GRANTEE @ST0352@            /* 👱🏻‍♀️ Sophie Rothenbühler - HEIR2, DAUGHTER */
+1 NOTE "⌚ Sophie gets the Patek Philippe — it's about time."
+
+1 TRANSFER @ST0453@           /* 📚Book Collection */
+2 GRANTOR @ST0152@            /* 👴 Emil Rothenbühler - MAIN, GRANTOR, DECEDENT */
+2 GRANTEE @ST0353@            /* 👩🏻‍🦰 Eliane Keller - HEIR3 */
+1 NOTE "📚 Eliane inherits the rare book collection — with no overdue fines."
+
+1 TRANSFER @ST0454@           /* 💰Bank Account: # 718-348-B, Zürcher Kantonalbank */
+2 GRANTOR @ST0152@            /* 👴 Emil Rothenbühler - MAIN, GRANTOR, DECEDENT */
+2 GRANTEE @ST0351@            /* 🧔🏻‍♂️ Markus Rothenbühler - HEIR1, SON */
+3 SHARE 5.13%
+2 GRANTEE @ST0352@            /* 👱🏻‍♀️ Sophie Rothenbühler - HEIR2, DAUGHTER */
+3 SHARE 46.15%
+2 GRANTEE @ST0353@            /* 👩🏻‍🦰 Eliane Keller - HEIR3 */
+3 SHARE 46.15%
+1 NOTE "💸 Account funds divided to equalize asset value."
+1 FLEX DESCRIPT
+2 PHRASE "Bank Account"
+2 CONTENTS NOTE
+3 CONT The bankaccount with number # 718-348-B, Zürcher Kantonalbank,
+3 CONT is reserved for estate tax and final obligations.
+~ ~ ~
+1 CITA
+2 SOUR @S0331@                /* Not present in this example */
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🧔‍♂️ @ST0152@ STICKY – Main Deceased Emil Rothenbühler**
+```gedcom
+0 @ST0152@ STICKY             /* Main Deceased Emil Rothenbühler */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 EVEN DEATH, WILL
+2 DATE 01 JUN 2020
+2 SPLAC @SP8585@              /* Bern, Switzerland */
+1 ROLE MAIN, GRANTOR, DECEDENT
+1 NAME
+2 FORM Emil Rothenbühler
+2 PART Emil
+3 TYPE GIVN
+2 PART Rothenbühler
+3 TYPE SURN
+1 DEAT
+2 DATE 17 FEB 2020
+1 SPLAC @SP001@               /* Bern, Switzerland */
+1 NOTE "Long-time alpine chocolatier and hoarder of mechanical things."
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🧑‍⚖️ @ST0253@ STICKY – Franz Müller EXECUTOR**
+```gedcom
+0 @ST0253@ STICKY             /* Franz Müller EXECUTOR */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE EXECUTOR
+1 NAME
+2 FORM Franz Müller
+2 PART Franz
+3 TYPE GIVN
+2 PART Müller
+3 TYPE SURN
+1 SEX M
+1 AGE 61
+1 ADDR
+2 STREET Bundesgasse 12
+2 CITY Bern
+2 POST 3011
+2 CTRY Switzerland
+1 AGNC "Estate Administration Group – Canton Bern"
+1 OCCU "Licensed Executor & Paper Inspector"
+1 NOTE "Personally handled the chocolate vault inventory with surgical precision."
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🏛️ @ST0254@ STICKY – Notary: "Notariat Bern Zentrum"**
+```gedcom
+0 @ST0254@ STICKY             /* Notariat Bern Zentrum */
+1 TYPE ORGANIZATION
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE NOTARY
+1 NAME
+2 FORM Notariat Bern Zentrum
+~ ~ ~
+1 ADDR
+2 STREET Marktgasse 3
+2 CITY Bern
+2 POST 3011
+2 CTRY Switzerland
+1 AGNC "Canton Bern, Legal Division"
+1 NOTE "Document sealed and verified by municipal authority"
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🧑‍🔧 @ST0351@ STICKY – Heir1 and Grantee: Son Markus Rothenbühler**
+```gedcom
+0 @ST0351@ STICKY             /* Heir1, Son, Grantee: Markus Rothenbühler */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR1, SON, GRANTEE
+1 NAME
+2 FORM Markus Rothenbühler
+2 PART Markus
+3 TYPE GIVN
+2 PART Rothenbühler
+3 TYPE SURN
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**👩‍💼 @ST0352@ STICKY – heir2, Daughter, Grantee: Sophie Rothenbühler**
+```gedcom
+0 @ST0352@ STICKY             /* heir2, Daughter, Grantee: Sophie Rothenbühler */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR2, DAUGHTER, GRANTEE
+1 NAME
+2 FORM Sophie Rothenbühler
+2 PART Sophie
+3 TYPE GIVN
+2 PART Rothenbühler
+3 TYPE SURN
+1 SEX F
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🎓 @ST0353@ STICKY – Heir3 - Eliane Keller**
+```gedcom
+0 @ST0353@ STICKY             /* Heir3 - Eliane Keller */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR3
+1 NAME
+2 FORM Eliane Keller
+2 PART Eliane
+3 TYPE GIVN
+2 PART Keller
+3 TYPE SURN
+1 SEX F
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🏡 @ST0451@ – STICKY – Alpine Chalet at Lake Oeschinen**
+```gedcom
+0 @ST0451@ STICKY             /* Alpine Chalet at Lake Oeschinen */
+1 TYPE PROPERTY, HOUSE, "Alpine Chalet at Lake Oeschinen"
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE PROPERTY
+1 FLEX DECIMAL, CURR, CHF
+2 PHRASE "House Value"
+2 CONTENTS 270000.00
+1 NOTE "Transferred to Markus Rothenbühler"
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**⌚ @ST0452@ – STICKY – Vintage Watch: "Patek Philippe 1952 Ref. 2499"**
+```gedcom
+0 @ST0452@ STICKY             /* Patek Philippe 1952 Ref. 2499 */
+1 TYPE BELONGINGS, KEEPSAKE, Watch: "Patek Philippe 1952 Ref. 2499"
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIRLOOM
+1 FLEX DECIMAL, CURR, CHF
+2 PHRASE "Appraised Watch Value"
+2 CONTENTS 30000.00
+1 NOTE "Bequeathed to Sophie Rothenbühler"
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**📚 @ST0453@ STICKY – Book Collection**
+```gedcom
+0 @ST0453@ STICKY             /* Book Collection */
+1 TYPE BOOK, LITERATURE, "Book collection"
+1 TITL Swiss Literature Collection
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE ITEM
+1 FLEX DECIMAL, CURR, CHF
+2 PHRASE Appraised Value
+2 CONTENTS 30000.00
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🏦 @ST0454@ STICKY – Bank account: "# 718-348-B, Zürcher Kantonalbank**
+```gedcom
+0 @ST0454@ STICKY             /* Account # 718-348-B, Zürcher Kantonalbank */
+1 TYPE FINANCE, ACCOUNTS, "Account # 718-348-B, Zürcher Kantonalbank"
+1 SUBM @B001@
+1 TEMPLATE @T016@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE ITEM
+1 NAME
+~ ~ ~
+1 FLEX DECIMAL, CURR, CHF
+2 PHRASE Bank Balance
+2 CONTENTS CHF 585000.00
+1 FLEX ACCOUNTNR
+2 PHRASE "Account-number"
+2 CONTENTS 985FT650003AB009
+1 FLEX DESCRIPT
+2 PHRASE "Bank Account"
+2 CONTENTS NOTE
+3 CONT The bankaccount with number # 718-348-B, Zürcher Kantonalbank,
+3 CONT is reserved for estate tax and final obligations.
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🧾 @I015@ INDI – Emil Rothenbühler**
+```gedcom
+0 @I015@ INDI                 /* Emil Rothenbühler */
+1 NAME
+2 FORM Emil Rothenbühler
+2 PART Emil
+3 TYPE GIVN
+2 PART Rothenbühle
+3 TYPE SURN
+1 ROLES
+2 STICKY @ST0151@             /* Emil Rothenbühler - Will Creation DATE 8 SEP 1978 */
+2 STICKY @ST0152@             /* Emil Rothenbühler - GRANTOR Will Executed DATE 01 JUN 2020 */
+1 ASSETS
+2 STICKY @ST0451@             /* 🏠Alpine Chalet - PROPERTY, HOUSE, "Alpine Chalet at Lake Oeschinen" */
+2 STICKY @ST0452@             /* ⌚Vintage Watch - BELONGINGS, KEEPSAKE, Watch: "Patek Philippe 1952 Ref. 2499" */
+2 STICKY @ST0453@             /* 📚Book Collection - BOOK, LITERATURE, "Book collection" */
+2 STICKY @ST0454@             /* 💰Bank Account - FINANCE, ACCOUNTS, "Account # 718-348-B, Zürcher Kantonalbank" */
+1 NOTE The ASSETS struture here, only shows the STICKYs at the time of granting.
+2 CONT In fact there should also be 4 STICKYs in the ASSETS section for the same entities
+2 CONT at time of acquisition ! But they are not mentioned here.
+~ ~ ~
+1 CREA 30 APR 2025
+1 CHAN 10 AUG 2025
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-16"></a>  
+
+## ⚔️ Example 16: Historical Title and Nobility Inheritance
+
+
+This GEDCOM 8 example models the transfer of a noble title and ancestral property upon the death of a titled individual.
+The record includes:
+- • A deceased baron who had the title (`MAIN, DECEASED, TITLED`)
+- • An heir receiving both a title and an estate
+- • A symbolic heraldic medallion as an object with ROLE HEIRLOOM
+- • A monarch or state official confirming the transition
+- • A `STICKY` with extended attributes (`ADDR, OCCU, AGNC, NOTE`)
+- • Example of a noble title via `TITLE, Baron`, with `ROLE DIGNITY`
+- • A simple land asset using `FLEX DECIMAL, LAND`  
+- • A dedicated `STICKY` and `TRANSFER` to reflect the noble title passing
+- • An `ASSET` with `HISTORY` showing previous barons by `STICKY` reference only
+
+This showcases how nobility, symbolic inheritance, and property can be represented using enhanced GEDCOM 8 structures.  
+
+***
+**IMPORTANT**  
+
+>- The first 4 barons show a `STICKY` here, but the `TEMPLATE`s they belong to are not presented, to keep the example short.
+***
+
+**⚔️ @T0052@ TEMPLATE - Historical Title and Nobility Inheritance**
+```gedcom
+0 @T0052@ TEMPLATE            /* Inheritance of Noble Title and Estate */
+1 TYPE DEATH, WILL, Title
+1 TITL Inheritance of Noble Title and Estate
+1 SUBM @B001@
+1 DATE 14 NOV 1812
+1 SPLAC @SP0052@              /* County of Northumberland, United Kingdom */
+1 ROLES
+2 STICKY @ST0152@     /* MAIN, DECEASED, TITLED: Alaric Montmorency 5th baron of Ashcroft died November 2 1812 👑 */
+2 STICKY @ST0252@             /* HEIR, SON: Percival Montmorency 6th baron of Ashcroft 👑 */
+2 STICKY @ST0352@             /* George III – Monarch */
+2 STICKY @ST0451@             /* Baronial Title – ROLE DIGNITY 🫅 */
+2 STICKY @ST0452@             /* Ashcroft Hall – ESTATE MANOR "Ashcroft Hall and grounds" 🏡*/
+2 STICKY @ST0453@             /* Heraldic Medallion – JEWELRY CHAIN with ROLE HEIRLOOM ⭐*/
+2 STICKY @ST0551@             /* Baronial Lineage Asset */
+1 TRANSFER @ST0451@           /* Baronial Title – DIGNITY 🫅*/
+2 GRANTOR @ST0152@    /* MAIN, DECEASED, TITLED: Alaric Montmorency 5th baron of Ashcroft died November 2 1812 👑 */
+2 GRANTEE @ST0252@            /* HEIR, SON: Percival Montmorency becomes 6th baron of Ashcroft 👑 */
+1 TRANSFER @ST0452@           /* Ashcroft Hall – ASSET */
+2 GRANTOR @ST0152@    /* MAIN, DECEASED, TITLED: Alaric Montmorency 5th baron of Ashcroft died November 2 1812 👑 */
+2 GRANTEE @ST0252@            /* HEIR, SON: Percival Montmorency as 6th baron of Ashcroft 👑 */
+1 FLEX ANNOTATION
+2 PHRASE "Handwritten annotation on the will"
+2 CONTENTS "A title weighs nothing but carries centuries."
+1 CITA
+2 SOUR @S0321@
+2 PAGE 5
+2 DATA
+~  ~ ~
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🪦 @ST0152@ STICKY – Alaric Montmorency 5th baron of Ashcroft died November 2 1812 👑**
+```gedcom
+0 @ST0152@ STICKY             /* Alaric Montmorency MAIN, DECEASED, TITLE */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0052@            /* Inheritance of Noble Title and Estate */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE MAIN, DECEASED, TITLED /* Role TITLED, because he had the title */
+1 ASSET @A032@                /* Connects STICKY to the ASSET of the title */
+1 NAME
+2 FORM Alaric James Montmorency
+2 PART Alaric
+3 TYPE GIVN
+2 PART James
+3 TYPE GIVN
+2 PART Montmorency
+3 TYPE SURN
+1 SEX M
+1 DEAT
+2 DATE 3 NOV 1812
+2 SPLAC @SP0451@              /* Ashcroft Hall, Northumberland */
+1 TITL                        /* Official GEDCOM tag */
+2 TYPE Baron
+1 FLEX ANNOTATION             /* More flexible way of representing the TITLE */
+2 PHRASE "Title held"
+2 CONTENTS NOTE
+3 CONT "5th Baron of Ashcroft"
+1 OCCU "Landowner, foxhunting enthusiast, parliamentary absentee"
+1 NOTE "Known for impromptu speeches and thorough moustache twirling"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🧔‍♂️ @ST0252@ STICKY – Percival Montmorency 6th baron of Ashcroft 👑**
+```gedcom
+0 @ST0252@ STICKY             /* Percival Montmorency – HEIR, SON, TITLE */
+1 TYPE HEIR, SON
+1 SUBM @B001@
+1 TEMPLATE @T0052@            /* Inheritance of Noble Title and Estate */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR, SON, TITLED
+1 ASSET @A032@                /* Connects STICKY to the ASSET of the title */
+1 NAME
+2 FORM Percival Alaric Montmorency
+2 PART Percival
+3 TYPE GIVN
+2 PART Alaric
+3 TYPE GIVN
+2 PART Montmorency
+3 TYPE SURN
+1 SEX M
+1 AGE 26
+1 ADDR
+2 STREET Ashcroft Hall
+2 CITY Northumberland
+2 POST --
+2 CTRY United Kingdom
+1 SPLAC @SP0451@              /* Ashcroft Hall, Northumberland */
+1 TITL                        /* Official GEDCOM tag */
+2 TYPE Baron
+1 FLEX ANNOTATION
+2 PHRASE "New title granted"
+2 CONTENTS NOTE
+3 CONT "6th Baron of Ashcroft"
+1 NOTE "Inherited title and responsibilities; inherited eyebrows uncertain"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**👑 @ST0352@ STICKY – George III**
+```gedcom
+0 @ST0352@ STICKY             /* George III */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0052@            /* Inheritance of Noble Title and Estate */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE LEGAL, RULER, "Monarch" /* Ruling Monarch George III */
+1 NAME
+2 FORM George III
+2 PART George
+3 TYPE GIVN
+2 PART III
+3 TYPE SUFFIX
+1 OCCU "King of the United Kingdom"
+1 AGNC "Royal Crown, by Grace of God"
+1 FLEX ANNOTATION
+2 PHRASE Authorise Reason
+2 CONTENTS "Authorized hereditary transition as per letters patent"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🫅 @ST0451@ STICKY – Baronial Title DIGNITY 🫅**
+```gedcom
+0 @ST0451@ STICKY             /* Baronial Title */
+1 TYPE TITLE, Baron 
+1 TITLE "Baron of Ashcroft"
+1 SUBM @B001@
+1 TEMPLATE @T0052@            /* Inheritance of Noble Title and Estate */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE DIGNITY
+1 NOTE "A hereditary honor with ceremonial duties and inherited prestige"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🏰 @ST0452@ STICKY – Ashcroft Hall**
+```gedcom
+0 @ST0452@ STICKY             /* Ashcroft Hall */
+1 TYPE ESTATE MANOR "Ashcroft Hall and grounds"
+1 SUBM @B001@
+1 TEMPLATE @T0052@            /* Inheritance of Noble Title and Estate */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE ASSET
+1 FLEX DECIMAL, LANDSIZE, Acres
+2 PHRASE "Size of the land"
+2 CONTENTS 512
+1 FLEX ANNOTATION
+2 PHRASE Written by clerck
+2 CONTENTS "Acres of rolling hills, 3 gables, 2 peacocks, 1 confusing attic"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🪙 @ST0453@ STICKY – Heraldic Medallion**
+```gedcom
+0 @ST0453@ STICKY             /* Heraldic Medallion */
+1 TYPE JEWELRY CHAIN "Baronial Heraldic Medallion"
+1 SUBM @B001@
+1 TEMPLATE @T0052@            /* Inheritance of Noble Title and Estate */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIRLOOM
+1 FLEX DECIMAL, GBP
+2 PHRASE "Value of the Medallion"
+2 CONTENTS 1400
+1 FLEX MATERIAL
+2 PHRASE "Material"
+2 CONTENTS "Silver"
+1 NOTE "Silver medallion engraved with stag and crown; symbolic, not negotiable"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🫅 @A032@ ASSET – Title: "Baron of Ashcroft"**
+```gedcom
+0 @A032@ ASSET                /* ASSET for Title: "Baron of Ashcroft" */
+1 TYPE TITLE, Baron           /* Same as for Title STICKY */
+1 TITL Baron of Ashcroft      /* Same as for Title STICKY */
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* ORIGDOC, as this ASSET is created from info on the @T0052@ TEMPLATE */
+1 QUAY 3
+1 DATE 21 JUL 2025
+1 SPLAC @SP0451@              /* Ashcroft Hall, Northumberland */
+1 HISTORY
+2 STICKY @ST0651@             /* Aloysius Montmorency 1th baron of Ashcroft died March 1 1712👑 */
+2 STICKY @ST0652@             /* Bartholomew Montmorency 2nd baron of Ashcroft died February 5 1742👑 */
+2 STICKY @ST0653@             /* Wilberforce Montmorency 3rd baron of Ashcroft died June 19 1776👑 */
+2 STICKY @ST0654@             /* Thaddeus Montmorency 4th baron of Ashcroft died October 29 1794👑 */
+2 STICKY @ST0152@             /* Alaric Montmorency 5th baron of Ashcroft died November 2 1812 👑 */
+2 STICKY @ST0252@             /* Percival Montmorency 6th baron of Ashcroft 👑 */
+1 CREA 21 JUL 2025
+1 CHAN 11 AUG 2025
+```
+**👑 👑 👑 👑 4 STICKY's – "Barons of Ashcroft" THEY DONT HAVE A TEMPLATE IN THIS EXAMPLE  !!!**  
+
+**🧔‍♂️ @ST0252@ STICKY – Aloysius Montmorency 1th baron of Ashcroft died March 1 1712👑**
+```gedcom
+0 @ST0651@ STICKY             /* Aloysius Montmorency – 1st Baron */
+1 TYPE HEIR, SON
+1 SUBM @B001@
+1 TEMPLATE @T01001@           /* Inh. of Noble Title and Estate MAR 1 1712 */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR, SON, TITLED
+1 ASSET @A032@                /* Connects STICKY to the ASSET of the title */
+1 NAME
+2 FORM Aloysius Montmorency
+2 PART Aloysius
+3 TYPE GIVN
+2 PART Montmorency
+3 TYPE SURN
+1 SEX M
+1 AGE 34
+1 DEAT
+2 DATE 01 MAR 1712
+2 SPLAC @SP0451@              /* Ashcroft Hall, Northumberland */
+1 SPLAC @SP0451@              /* Ashcroft Hall, Northumberland */
+1 TITL
+2 TYPE Baron
+1 FLEX TITLE
+2 PHRASE "New title granted"
+2 CONTENTS "1st Baron of Ashcroft"
+1 NOTE "Kept a pet mole named Bertrand. Claimed it once outdebated a bishop."
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**👴🏻 @ST0252@ STICKY – Bartholomew Montmorency 2nd baron of Ashcroft died February 5 1742👑**
+```gedcom
+0 @ST0652@ STICKY             /* Bartholomew Montmorency – 2nd Baron */
+1 TYPE HEIR, SON
+1 SUBM @B001@
+1 TEMPLATE @T01002@           /* Inh of Noble Title and Estate FEB 5 1742 */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR, SON, TITLED
+1 ASSET @A032@
+1 NAME
+2 FORM Bartholomew Montmorency
+2 PART Bartholomew
+3 TYPE GIVN
+2 PART Montmorency
+3 TYPE SURN
+1 SEX M
+1 AGE 37
+1 DEAT
+2 DATE 05 FEB 1742
+2 SPLAC @SP0451@
+1 SPLAC @SP0451@
+1 TITL
+2 TYPE Baron
+1 FLEX TITLE
+2 PHRASE "New title granted"
+2 CONTENTS "2nd Baron of Ashcroft"
+1 NOTE "Wore two monocles, one per eye. Declared forks ‘an ungodly invention.’"
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**👴🏼 @ST0252@ STICKY – Wilberforce Montmorency 3rd baron of Ashcroft died June 19 1776👑**
+```gedcom
+0 @ST0653@ STICKY             /* Wilberforce Montmorency – 3rd Baron */
+1 TYPE HEIR, SON
+1 SUBM @B001@
+1 TEMPLATE @T01003@           /* Inh of Noble Title and Estate JUN 19 1776 */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR, SON, TITLED
+1 ASSET @A032@
+1 NAME
+2 FORM Wilberforce Montmorency
+2 PART Wilberforce
+3 TYPE GIVN
+2 PART Montmorency
+3 TYPE SURN
+1 SEX M
+1 AGE 41
+1 DEAT
+2 DATE 19 JUN 1776
+2 SPLAC @SP0451@
+1 SPLAC @SP0451@
+1 TITL
+2 TYPE Baron
+1 FLEX TITLE
+2 PHRASE "New title granted"
+2 CONTENTS "3rd Baron of Ashcroft"
+1 NOTE "Chronically late; insisted time was a rumor. Once missed his own knighthood."
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🧔‍♂️ @ST0252@ STICKY – Thaddeus Montmorency 4th baron of Ashcroft died October 29 1794👑**
+```gedcom
+0 @ST0654@ STICKY             /* Thaddeus Montmorency – 4th Baron */
+1 TYPE HEIR, SON
+1 SUBM @B001@
+1 TEMPLATE @T01004@           /* Inh of Noble Title and Estate OCT 29 1794 */
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE HEIR, SON, TITLED
+1 ASSET @A032@
+1 NAME
+2 FORM Thaddeus Montmorency
+2 PART Thaddeus
+3 TYPE GIVN
+2 PART Montmorency
+3 TYPE SURN
+1 SEX M
+1 AGE 48
+1 DEAT
+2 DATE 29 OCT 1794
+2 SPLAC @SP0451@
+1 SPLAC @SP0451@
+1 TITL
+2 TYPE Baron
+1 FLEX TITLE
+2 PHRASE "New title granted"
+2 CONTENTS "4th Baron of Ashcroft"
+1 NOTE "Grew sideburns so vast they required seasonal pruning."
+1 CREA 30 APR 2025
+1 CHAN 11 AUG 2025
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-17"></a>  
+## 🛡️ Example 17: Guild Membership Certificate 
+
+This GEDCOM 8 example models a **Guild Membership Certificate** issued on 15 March 1702 in London to John Smith by the Worshipful Company of Blacksmiths. It demonstrates:
+
+- Representing a historical membership record as both an **event** (`GROUP, GUILD-MEM`) and an **asset** `STICKY`
+- Linking multiple roles (`MEMBER`, `MASTER`, `WITNESS`, `ITEM, CERTIFICATE`) to the same `TEMPLATE`
+- Incorporating a **period-style transcription** (“Be it knowne unto all men by these presentes…”) within a `FLEX ANNOTATION` to preserve historical context and style
+- Using `FLEX` fields for structured details like membership number, fee, duration, status, and seal description
+- Associating a scanned copy of the certificate as an `OBJE`
+
+The example captures not only the facts of membership but also the ceremonial and legal style of the time. It shows how GEDCOM 8 can integrate factual, structured metadata with verbatim historical language to create a rich, verifiable record.
+
+**⚒️ @T0070@ TEMPLATE – Guild Membership Certificate of John Smit in London ⚒️**
+```gedcom
+0 @T0070@ TEMPLATE            /* Guild Membership Certificate of John Smith */
+1 TYPE GROUP, GUILD-MEM
+1 TITL "Guild Membership Certificate – Worshipful Company of Blacksmiths"
+1 SUBM @B001@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 DATE 15 MAR 1702            /* Date of issue on document */
+1 SPLAC @SP0070@              /* London, Middlesex, England */
+1 FLEX REGNUMBER
+2 PHRASE Guild Membership Number
+2 CONTENTS 12345-BS
+1 FLEX DECIMAL, CURR, GBP
+2 PHRASE Fee paid
+2 CONTENTS 2.0
+1 FLEX Descript
+2 PHRASE Membership duration
+2 CONTENTS Lifetime
+1 FLEX DESCRIPT
+2 PHRASE Member status
+2 CONTENTS Active
+1 FLEX DESCRIPT
+2 PHRASE Official Seal or Stamp
+2 CONTENTS Red wax with hammer and anvil emblem
+1 FLEX ANNOTATION
+2 PHRASE Document description
+2 CONTENT NOTE
+3 CONT Document includes official wax seal, handwritten signatures, details of training,
+3 CONT journeyman certification, and record of a skills examination required for guild entry.
+3 CONT Document issued by the Worshipful Company of Blacksmiths.
+1 FLEX ANNOTATION
+2 PHRASE Full period-style text of membership certificate, summarizing training, qualification, method of entry, rights, oath, and signatories
+2 CONTENTS NOTE
+3 CONT Be it knowne unto all men by these presentes, that I, John Smith, having faithfully served a full seaven
+3 CONT years’ apprenticeship under Master Robert Turner in the noble craft of blacksmithing — forging of tools,
+3 CONT horseshoeing, welding of iron, and sundry works — am hereby admitted as a free journeyman of the Worshipful
+3 CONT Company of Blacksmiths.
+3 CONT By virtue of mine completed service and the passing of the masters’ examination, I am granted liberty
+3 CONT to keep my own forge, take apprentices, and sell wares within the city bounds.
+3 CONT I doe solemnly sweare to uphold the statutes of this Company, to set forth honest measure, true workmanship,
+3 CONT and just price, according to the ancient custom.
+3 CONT In witnesse hereof, this charter is sealed and subscribed by our hands:
+3 CONT
+3 CONT John Smith, Edward Clarke, and the said Master Robert Turner,
+3 CONT 
+3 CONT in the Year of Our Lord 1702.
+1 EVEN GROUP, GUILD-MEM
+2 DATE 15 MAR 1702            /* Date of issue on document */
+2 SPLAC @SP0070@              /* London, Middlesex, England */
+1 ROLES
+2 STICKY @ST0100@             /* Journeyman John Smith – Becomes official certified member */
+2 STICKY @ST0101@             /* Robert Turner – Guild Master */
+2 STICKY @ST0102@             /* Edward Clarke – Witness */
+2 STICKY @ST0103@             /* Guild Membership Certificate */
+1 CITA
+2 SOUR @S0045@
+2 TITL Scan of Guild Membership Certificate - 
+2 PAGE 1
+1 DATA
+~ ~ ~
+1 CREA 26 APR 2025
+1 CHAN 11 AUG 2025
+```
+**📜 @ST0103@ STICKY – Guild Membership Certificate as physical asset**
+```gedcom
+0 @ST0103@ STICKY             /* Guild Membership Certificate as physical asset */
+1 TYPE DOCUMENT, CERTIFICATE, "Guild Membership Certificate"
+1 TITL Guild Membership Certificate of John Smith
+2 PHRASE "Issued by Worshipful Company of Blacksmiths in London"
+1 SUBM @B001@
+1 TEMPLATE @T0070@            /* Guild Membership Certificate of John Smit in London */
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 15 MAR 1702            /* Date of issue on document */
+1 SPLAC @SP0070@              /* London, Middlesex, England */
+1 FLEX DESCRIPT
+2 PHRASE Material of certificate
+2 CONTENTS Parchment with handwritten calligraphy and embossed guild seal
+1 OBJ @O0031@                 /* Scan of Guild Membership Certificate of John Smith */
+1 CREA 01 JUL 2025
+1 CHAN 31 JUL 2025
+```
+**🧔🏻‍♂️ @ST0100@ STICKY – John Smith - admitted into the guild 🧔🏻‍♂️**
+```gedcom
+0 @ST0100@ STICKY             /* John Smith */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0070@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 EVEN GROUP, GUILD-MEM
+2 DATE 15 MAR 1702            /* Date of issue on document */
+2 SPLAC @SP0070@              /* London, Middlesex, England */
+1 ROLE MEMBER
+1 FLEX ANNOTATION
+2 PHRASE Details of professional training
+2 CONTENTS NOTE
+3 CONT Seven-year apprenticeship under Master William Carter, specializing in forging tools and horseshoeing
+1 FLEX ANNOTATION
+2 PHRASE Level of trade qualification
+2 CONTENTS NOTE
+3 CONT Certified journeyman status awarded by the Worshipful Company of Blacksmiths
+1 FLEX ANNOTATION
+2 PHRASE Membership obtained by:
+2 CONTENTS NOTE
+3 CONT Apprenticeship completion and successful skills examination, including demonstration of forging, welding, and tool-making
+1 FLEX ANNOTATION
+2 PHRASE Membership rights granted
+2 CONTENTS NOTE
+3 CONT Right to operate a forge, employ apprentices, and sell iron goods in the city market
+1 FLEX ANNOTATION
+2 PHRASE Membership oath text
+2 CONTENTS NOTE
+3 CONT Sworn oath to uphold guild rules, fair pricing, and quality standards
+1 FLEX ANNOTATION
+2 PHRASE Signatories on certificate
+2 CONTENTS NOTE
+3 CONT John Smith, Robert Turner, Edward Clarke
+1 NOTE Person admitted into the guild.
+1 NAME
+2 FORM John Smith
+2 PART John
+3 TYPE GIVN
+2 PART Smith
+3 TYPE SURN
+1 SEX M
+1 AGE 35
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**👨🏻‍🦱 @ST0101@ STICKY – Robert Turner - Guild master approving the membership 👨🏻‍🦱**
+```gedcom
+0 @ST0101@ STICKY             /* Robert Turner */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0070@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE MASTER
+1 NOTE Guild master approving the membership.
+1 NAME
+2 FORM Robert Turner
+2 PART Robert
+3 TYPE GIVN
+2 PART Turner
+3 TYPE SURN
+1 SEX M
+1 AGE 50
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**👨‍🦲 @ST0102@ STICKY – Edward Clarke - witnessing the admission 👨‍🦲**
+```gedcom
+0 @ST0102@ STICKY             /* Edward Clarke */
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0070@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE WITNESS
+2 PHRASE Person witnessing the admission.
+1 NAME
+2 FORM Edward Clarke
+2 PART Edward
+3 TYPE GIVN
+2 PART Clarke
+3 TYPE SURN
+1 SEX M
+1 AGE 42
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**📜 @ST0103@ STICKY – Scan of Guild Membership Certificate of John Smit in London - STICKY 📜**
+```gedcom
+0 @ST0103@ STICKY             /* Certificate */
+1 TYPE CERTIFICATE
+2 PHRASE "Guild Membership Certificate of John Smit in London"
+1 SUBM @B001@
+1 TEMPLATE @T0070@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 FLEX MATERIAL
+2 PHRASE Material of certificate
+2 CONTENTS Parchment with handwritten calligraphy and embossed guild seal
+1 ROLE ITEM, CERTIFICATE      /* The certificate itself. */
+1 OBJ @O003@                  /* Scan of The certificate itself. (not present in example)*/
+2 TITLE "Scan of Guild Membership Certificate of John Smit 15 MAR 1702"
+1 CREA 26 APR 2025
+1 CHAN 11 AUG 2025
+```
+**🧔🏻‍♂️ @I0500@ INDI – John Smith - admitted into the guild 🧔🏻‍♂️**
+```gedcom
+0 @I0500@ INDI
+1 NAME
+2 FORM John Smith
+2 PART John
+3 TYPE GIVN
+2 PART Smith
+3 TYPE SURN
+1 SEX M
+1 AGE 35
+1 ROLES
+2 STICKY @ST0100@             /* John Smith – Member */
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**👨🏻‍🦱 @I0501@ INDI – Robert Turner - Guild master approving the membership 👨🏻‍🦱**
+```gedcom
+0 @I0501@ INDI
+1 NAME
+2 FORM Robert Turner
+2 PART Robert
+3 TYPE GIVN
+2 PART Turner
+3 TYPE SURN
+1 SEX M
+1 AGE 50
+1 ROLES
+2 STICKY @ST0101@             /* Robert Turner – Guild Master */
+2 STICKY @ST0201@             /* Robert Turner – Member */
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**👨‍🦲 @I0502@ INDI – Edward Clarke - witnessing the admission 👨‍🦲**
+```gedcom
+0 @I0502@ INDI
+1 NAME
+2 FORM Edward Clarke
+2 PART Edward
+3 TYPE GIVN
+2 PART Clarke
+3 TYPE SURN
+1 SEX M
+1 AGE 42
+1 ROLES
+2 STICKY @ST0102@             /* Edward Clarke – Witness */
+2 STICKY @ST0202@             /* Edward Clarke – Member */
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**🏘️ @SP0070@ SPLAC – London, Middlesex, England 🏘️**
+```gedcom
+0 @SP0070@ SPLAC              /* London, Middlesex, England */
+1 TYPE CITY, POLI, 51, City   /* Gov type 51 is City*/ 
+~ ~ ~
+```
+**🛡️ @SP0070@ GROUP – Worshipful Company of Blacksmiths, London, Middlesex, England 🛡️**
+```gedcom
+0 @T0071@ GROUP
+1 TYPE ORGANIZATION, TRADEUNION, Guild
+1 TITL "Worshipful Company of Blacksmiths, London"
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 SUBM @B001@
+1 SPLAC @SP0070@              /* London, Middlesex, England */
+1 DATE 15 MAR 1702
+1 SPLAC @SP0070@              /* London, Middlesex, England */
+1 MEMBERS
+2 STICKY @ST0100@             /* John Smith – Member */
+2 STICKY @ST0201@             /* Robert Turner – Member */
+2 STICKY @ST0202@             /* Edward Clarke – Member */
+1 FLEX NOTE
+2 PHRASE Official Seal or Stamp
+2 CONTENTS NOTE
+3 CONT Official Seal or Stamp:
+3 CONT Red wax with hammer and anvil emblem
+1 CREA 26 APR 2025
+1 CHAN 09 AUG 2025
+```
+**💾 @S0045@ SOURCE for Guild Membership Certificate**
+```gedcom
+0 @S0045@ SOUR
+1 TITL Guild Membership Certificate of John Smit in London
+1 AUTH Worshipful Company of Blacksmiths in London
+1 PUBL "Filed in London National Archives, case #1905-328C"
+1 ABBR "John Smith 1702"
+1 DATA
+2 EVEN GROUP, GUILD-MEM
+3 DATE 15 MAR 1702            /* Date of issue on document */
+4 PHRASE "Guild Membership Certificate of John Smit in London"
+3 SPLAC @SP0070@              /* London, Middlesex, England */
+2 AGNC Worshipful Company of Blacksmiths in London
+2 NOTE "Preserved in London National Archives, box 12, folder 3"
+~ ~ ~
+1 OBJ @O0031@                 /* Scan of Guild Membership Certificate of John Smith */
+2 TITL Scanned Guild Membership Certificate of John Smit in London
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+**🖼️ @O0031@ OBJE – Scan of Guild Membership Certificate of John Smith - OBJE 🖼️**
+```gedcom
+0 OBJE @O0031@                /* Multimedia record with file link  */
+1 FILE https://example.org/guildcertifs/John Smith-1702-cert.pdf
+2 FORM application/pdf
+3 MIME application/pdf
+2 TITL Scanned Guild Membership certificate
+1 CREA 29 APR 2025
+1 CHAN 31 JUL 2025
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+
+<a name="example-18"></a>  
+
+## ⚖️ Example 18: Court Trial Record, Humorous Fictional Case
+
+This example shows how a GEDCOM 8 structure can model a court trial involving many roles, using only `STICKY` blocks with `ROLE` info.  
+The case? A dramatic but highly fictional courtroom battle involving various characters — each linked to a single `TEMPLATE` using a properly structured `STICKY`.  
+This is a **fun** and slightly absurd illustration designed to help users understand the many `ROLE` types usable in legal records.
+
+**⚖️ @T0088@ – TEMPLATE – Verdict of Guilty, Custodial Sentence**
+```gedcom
+0 @T0088@ TEMPLATE
+1 TYPE LEGAL, JUDGMENT
+1 TITL Verdict of Guilty - Custodial Sentence
+2 PHRASE Verdict of Guilty for Jack Hammer
+1 SUBM @B001@
+1 TORIGIN ORIGDOC             /* Derived directly from original document */
+1 QUAY 3                      /* Direct and primary evidence */
+1 DATE 01 APR 2024
+1 SPLAC @SP0999@              /* Fictional Courthouse, Funtown */
+1 EVEN
+2 DATE 01 APR 2024
+2 SPLAC @SP0999@              /* Fictional Courthouse, Funtown */
+1 ROLES
+2 STICKY @ST0090@             /* Defendant: Jack Hammer MAIN, DEFENDANT */
+2 STICKY @ST0091@             /* Defense Lawyer: Habeas Jokers LAWYER, DEFENSE*/
+2 STICKY @ST0092@             /* Prosecutor: Blaise Hearsay PROSECUTOR */
+2 STICKY @ST0093@             /* Judge: Bench Warmers JUDGE */
+2 STICKY @ST0094@             /* Jury Foreman: Luke Atmey JURY, FOREMAN */
+2 STICKY @ST0095@             /* Defense Witness: William Havamug WITNESS, DEFENSE */
+2 STICKY @ST0096@             /* Prosecution Witness: Joe Starbuck WITNESS, PROSECUTION */
+2 STICKY @ST0097@             /* Victim: Delicia Scones VICTIM */
+1 CITA
+2 SOUR @S0071@
+2 PAGE 5
+2 DATA
+~ ~ ~
+1 CREA 16 APR 2025
+1 CHAN 10 AUG 2025
+```
+**🔨 @ST0090@ STICKY – Defendant: Jack Hammer**
+```gedcom
+0 @ST0090@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 EVEN
+2 DATE 01 APR 2024
+2 SPLAC @SP0999@              /* Fictional Courthouse, Funtown */
+1 ROLE MAIN, DEFENDANT
+1 NAME
+2 FORM Jack Hammer
+~ ~ ~
+1 SEX M
+1 AGE 37
+1 OCCU Freelance Demolitionist
+1 NOTE Known to carry a literal hammer everywhere.
+~ ~ ~
+```
+**🕶️ @ST0091@ STICKY – Defense Lawyer: Habeas Jokers**
+```gedcom
+0 @ST0091@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE LAWYER, DEFENSE
+1 NAME
+2 FORM Habeas Jokers
+~ ~ ~
+1 SEX M
+1 AGE 63
+1 NOTE Claimed 327 years of combined courtroom experience.
+~ ~ ~
+```
+**📢 @ST0092@ STICKY – Prosecutor: Blaise Hearsay**
+```gedcom
+0 @ST0092@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE PROSECUTOR
+1 NAME
+2 FORM Blaise Hearsay
+~ ~ ~
+1 SEX F
+1 AGE 42
+1 OCCU State Attorney
+1 NOTE Famous for never saying "Objection!"
+~ ~ ~
+```
+*👩‍⚖️ @ST0093@ STICKY – Judge: Bench Warmers**
+```gedcom
+0 @ST0093@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE JUDGE
+1 NAME
+2 FORM Bench Warmers
+~ ~ ~
+1 SEX M
+1 AGE 78
+1 NOTE Known to nap during opening statements.
+~ ~ ~
+```
+**🎯 @ST0094@ STICKY – Jury Foreman: Luke Atmey**
+```gedcom
+0 @ST0094@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE JURY, FOREMAN
+1 NAME
+2 FORM Luke Atmey
+~ ~ ~
+1 SEX M
+1 AGE 51
+1 NOTE Jury voted 11-1 until Luke convinced them over pizza.
+~ ~ ~
+```
+**☕ @ST0095@ STICKY – Defense Witness: William Havamug**
+```gedcom
+0 @ST0095@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE WITNESS, DEFENSE
+1 NAME
+2 FORM William Havamug
+~ ~ ~
+1 SEX M
+1 AGE 89
+1 NOTE “I saw everything through my monocle,” he claimed.
+~ ~ ~
+```
+**🔍 @ST0096@ STICKY – Prosecution Witness: Joe Starbuck**  
+```gedcom
+0 @ST0096@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE WITNESS, PROSECUTION
+1 NAME
+2 FORM Joe Starbuck
+~ ~ ~
+1 SEX M
+1 AGE 29
+1 OCCU Barista
+1 NOTE Eyewitness because trial took place next to his café.
+~ ~ ~
+```
+**💔 @ST0097@ STICKY – Victim: Delicia Scones**
+```gedcom
+0 @ST0097@ STICKY
+1 TYPE PERSON
+1 SUBM @B001@
+1 TEMPLATE @T0088@
+1 TORIGIN ORIGDOC
+1 QUAY 3
+1 ROLE VICTIM
+1 NAME
+2 FORM Delicia Scones
+~ ~ ~
+1 SEX F
+1 AGE 34
+1 NOTE Lost a bakery window in the altercation.
+~ ~ ~
+```
+
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+
+---
+
+<a name="example-19"></a>  
+## 🪦 Example 19: Gravestone with Named and Implied Persons
+
+This example demonstrates a `MEMORIAL, GRAVESTONE` `TEMPLATE` built from a single photographed tombstone — but reveals much more. It shows how careful attention to inscriptions can yield named individuals, inferred family relationships, roles, dates, and annotations.
+
+**Highlights:**
+
+- **Deep analysis of inscriptions**: Each name, role, and date was derived from text on the gravestone (e.g., "beloved father" implies a child; "gran" implies a grandchild born later).
+- **Rich CITA structure**: The `TEMPLATE` includes a fully developed `CITA` with `DATA`, `TRANSCRIPT`, `TEXTDISPLAY`, `URL`, `RECORDID`, and more — useful for rigorous source linking.
+- **STICKY roles**:
+  - Thaddeus (`ROLE MAIN, DECEASED`, `AN_DEATH`)
+  - Euphemia (`ROLE WIDOW, DECEASED`, `AN_DEATH`)
+  - One `CHILD` and one `GRANDCHILD` implied (`AN_MENTION`)
+- **Estimated data**: `MARR` date ranges are included for the couple, along with a `BIRT` date for the grandchild (after Thaddeus’s death).
+- **FLEX ANNOTATION** captures:
+  - Epitaphs with emojis and musical symbols (e.g., 🎵 “Forever in His arms”)
+  - Religious quotes and Bible verses (`John 14:1`)
+- **Occupation** ("Pastor") is justified by context and reinforced by the gravestone’s biblical tone.
+- **Document chain**:
+  - The `TEMPLATE` links to a `SOURCE` (cemetery register)
+  - The `SOURCE` links to a `REPO` (cemetery records office) using a full `<<SOURCE_REPOSITORY_CITATION>>` with `CALN`, `MEDI`, and `NOTE`
+  - A linked `OBJE` contains a fictional photo of the stone
+- `TORIGIN ORIGDOC, INCOMPLETE` signals that some persons are only partially documented.
+- `TORIGIN ORIGDOC, GUESSED` signals that some persons (the children) were only "guessed" to exist. as all other info about them is missing.
+- `QUAY` values are used to reflect varying certainty per person.
+
+*🪦 This example shows how even minimal physical evidence can be maximally encoded using GEDCOM 8 structures — when parsed with care.*
+
+
+
+**🪦 @T019@ - Gravestone for Thaddeus and Euphemia Stoneworthy**
+```gedcom
+0 @T019@ TEMPLATE
+1 TYPE MEMORIAL, GRAVESTONE
+1 TITL Gravestone for Thaddeus and Euphemia Stoneworthy
+1 SUBM @B001@
+1 TORIGIN ORIGDOC, INCOMPLETE
+1 QUAY 2
+1 DATE 15 APR 1924
+1 SPLAC @SP019@               /* Roseview Cemetery, Northmoor */
+1 FLEX ANNOTATION
+2 PHRASE Tombstone inscription
+2 CONTENTS "In loving memory of Thaddeus Stoneworthy — beloved husband and father."
+1 FLEX ANNOTATION
+2 PHRASE Tombstone inscription
+2 CONTENTS "Euphemia Stoneworthy — dearly loved mother and gran. 🎵 Forever in His arms."
+1 FLEX ANNOTATION
+2 PHRASE Bible verse from tombstone
+2 CONTENTS "Let not your heart be troubled." (John 14:1)
+1 CITA
+2 SOUR @S019@                 /* Roseview Cemetery Tombstone Register */
+2 PAGE Section 5, Row B, Plot 12
+2 DATA
+3 DATE 18 MAR 1932
+3 TEXT “Gravestone of Thaddeus and Euphemia Stoneworthy, Section 5, Row B, Plot 12”
+4 MIME text/plain
+4 LANG en
+2 AUTHOR Northmoor Cemetery Administration
+2 TITL Tombstone Register of Roseview Cemetery, 1890–1950
+2 DATES
+3 RECORDED 18 MAR 1932
+2 TEXTDISPLAY “Roseview Cemetery Register: Section 5, Row B, Plot 12”
+2 TRANSCRIPT “Gravestone of Thaddeus and Euphemia Stoneworthy, Section 5, Row B, Plot 12”
+2 FORMAT
+3 TYPE image/jpeg
+2 URL https://roseviewcemetery.example.org/stoneworthy-gravestone.jpg
+2 LANGUAGE en
+2 RECORDID RCV-STN-5B12
+2 CONTAINER Roseview Cemetery Archives
+2 ITEMTYPE Memorial Gravestone Record
+2 SHORTTITLE Roseview Tombstones
+2 WWWLINK
+3 VALUE https://roseviewcemetery.org/register
+2 QUAY 3
+2 OBJE @O019@                 /* Gravestone photograph */
+1 ROLES
+2 STICKY @ST1901@             /* Thaddeus Stoneworthy, main */
+2 STICKY @ST1902@             /* Euphemia Stoneworthy, widow */
+2 STICKY @ST1903@             /* child (implied) */
+2 STICKY @ST1904@             /* grandchild (implied) */
+1 CREA 27 JUL 2025
+1 CHAN 27 JUL 2025
+```
+**🪦 @ST1901@ STICKY – Main (Thaddeus Stoneworthy)**
+```gedcom
+0 @ST1901@ STICKY             /* Thaddeus Stoneworthy */
+1 TYPE PERSON, AN_DEATH
+1 SUBM @B001@
+1 TEMPLATE @T019@
+1 TORIGIN ORIGDOC
+1 QUAY 2
+1 ROLE MAIN, DECEASED
+1 NAME
+2 FORM Thaddeus Stoneworthy
+2 PART Thaddeus
+3 TYPE GIVN
+2 PART Stoneworthy
+3 TYPE SURN
+1 BIRT
+2 DATE 21 NOV 1858
+1 DEAT
+2 DATE 07 APR 1924
+1 BURI
+2 DATE 09 APR 1924
+1 MARR
+2 DATE BET 1880 AND 1890
+1 OCCU Pastor
+1 CREA 27 JUL 2025
+1 CHAN 27 JUL 2025
+```
+**🕊️ @ST1902@ STICKY – Widow (Euphemia Stoneworthy)**
+```gedcom
+0 @ST1902@ STICKY             /* Euphemia Stoneworthy */
+1 TYPE PERSON, AN_DEATH
+1 SUBM @B001@
+1 TEMPLATE @T019@
+1 TORIGIN ORIGDOC
+1 QUAY 2
+1 ROLE WIDOW, DECEASED
+1 NAME
+2 FORM Euphemia Stoneworthy
+2 PART Euphemia
+3 TYPE GIVN
+2 PART Stoneworthy
+3 TYPE SURN
+1 BIRT
+2 DATE 04 FEB 1862
+1 DEAT
+2 DATE 12 MAR 1932
+1 BURI
+2 DATE 14 MAR 1932
+1 MARR
+2 DATE BET 1880 AND 1890
+1 CREA 27 JUL 2025
+1 CHAN 27 JUL 2025
+```
+**👶 @ST1903@ STICKY – Child (implied)**
+```gedcom
+0 @ST1903@ STICKY             /* child of Thaddeus and Euphemia */
+1 TYPE PERSON, AN_MENTION
+1 SUBM @B001@
+1 TEMPLATE @T019@
+1 TORIGIN ORIGDOC, GUESSED
+1 QUAY 1
+1 ROLE CHILD
+1 CREA 27 JUL 2025
+1 CHAN 27 JUL 2025
+```
+**👼 @ST1904@ STICKY – Grandchild (implied)**
+```gedcom
+0 @ST1904@ STICKY             /* grandchild of Euphemia */
+1 TYPE PERSON, AN_MENTION
+1 SUBM @B001@
+1 TEMPLATE @T019@
+1 TORIGIN ORIGDOC, GUESSED
+1 QUAY 1
+1 ROLE GRANDCHILD
+1 BIRT
+2 DATE AFT 07 APR 1924        /* Date unknown, but the birth probably came after Thaddeus death */
+1 CREA 27 JUL 2025
+1 CHAN 27 JUL 2025
+```
+**📚 @S019@ SOURCE – Northmoor Cemetery Tombstone Registry**
+```gedcom
+0 @S019@ SOUR
+1 TITL Tombstone Register of Roseview Cemetery, Northmoor (1890–1950)
+1 AUTH Northmoor Cemetery Administration
+1 PUBL Office of Records, Roseview Cemetery
+1 ABBR Roseview Tombstone Register
+1 TEXT Registry index with engraved inscriptions and burial details. Covers headstones, memorials, and niche plates for interments from 1890–1950
+1 DATA
+~ ~ ~
+1 REPO @R019@
+2 CALN Section 5B, Registry Volume 3
+3 MEDI BOOK
+3 PHRASE Roseview Cemetery Burial Records
+2 NOTE Original burial register used for verifying inscriptions and burial locations
+```
+**🖼️ @O019@ OBJE – Photo of the Stoneworthy Gravestone**
+```gedcom
+0 @O019@ OBJE
+1 FILE https://roseviewcemetery.example.org/stoneworthy-gravestone.jpg
+2 FORM image/jpeg
+3 MEDI Image
+2 TITL Gravestone of Thaddeus and Euphemia Stoneworthy 18 MAR 1932
+1 NOTE Digitized photo of gravestone in Section 5, Row B, Plot 12 of Roseview Cemetery
+```
+**🏛️ @R019@ REPO – Roseview Cemetery Records Office**
+```gedcom
+0 @R019@ REPO
+1 NAME Roseview Cemetery Records Office
+1 ADDR 777 Memorial Lane
+2 CITY Northmoor
+2 POST NM44 2TG
+2 CTRY United Kingdom
+1 EMAIL records@roseviewcemetery.org
+1 WWW https://roseviewcemetery.org/records
+```
+
+[🔝 Back to top](#appendix-b-gedcom-examples)
+

From 2abdecb306c25abf2f8c979dec1a66d38eea6a41 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 10:21:11 +0200
Subject: [PATCH 02/11] Update specification/gedcom-3-structures-3-meaning.md

Sorry for the typo

Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
---
 specification/gedcom-3-structures-3-meaning.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-3-structures-3-meaning.md b/specification/gedcom-3-structures-3-meaning.md
index 9b3bf496..76dccb70 100644
--- a/specification/gedcom-3-structures-3-meaning.md
+++ b/specification/gedcom-3-structures-3-meaning.md
@@ -1386,7 +1386,7 @@ The d’Aboville-like numbering system expresses position using dot-separated in
 - Each person’s number reflects their birth order among siblings.
 - Example values: 1, 1.2, 1.2.3, 2.1.2, etc.
 - The s suffix (e.g., 1s, 1.2s) may be added to indicate a spouse of the person bearing the primary number.
-- The system is **local to the `TEMPLATE`** only; numbers are not reused outside. (Thats why its called `TDABOVI` and not `DABOVI`)
+- The system is **local to the `TEMPLATE`** only; numbers are not reused outside. (That's why it's called `TDABOVI` and not `DABOVI`)
 
 **Official Format Rules:**
 - **Pattern:** must match regex `^(\d+(\.\d+)*)(s?)$`

From 4ecbd1dfb77f10c00fdaf6a205a9e2c3dd22bbbc Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 10:29:14 +0200
Subject: [PATCH 03/11] Update
 specification/gedcom-3-structures-4-enumerations-roles.md

Agreed!

Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
---
 specification/gedcom-3-structures-4-enumerations-roles.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-3-structures-4-enumerations-roles.md b/specification/gedcom-3-structures-4-enumerations-roles.md
index 4f5b18ec..8039e01a 100644
--- a/specification/gedcom-3-structures-4-enumerations-roles.md
+++ b/specification/gedcom-3-structures-4-enumerations-roles.md
@@ -266,7 +266,7 @@ for detail: [property name, heir, date] |
 | 📜 | `INHERITANCE` | `ESTATE`          | The entire collection of assets and liabilities owned by the deceased person at the time of death. Use PHRASE for detail: [property name, heir, date] |
 | 📜 | `INHERITANCE` | `EXECUTOR`        | The person executing the will (may or may not be heir). Responsible for executing a will |
 | 📜 | `INHERITANCE` | `EXITINGH`        | Exiting heir: The person who is next in line to inherit a title or property, and whose right of inheritance is not subject to being defeated by the birth of a closer relative. 
-| 📜 | `INHERITANCE` | `GARDIAN`         | Appointed for minor heirs |
+| 📜 | `INHERITANCE` | `GUARDIAN`         | Appointed for minor heirs |
 | 📜 | `INHERITANCE` | `GRANTEE`         | One who receives a right or property |
 | 📜 | `INHERITANCE` | `GRANTOR`         | Establishes trust or grants asset One who grants a right or property|
 | 📜 | `INHERITANCE` | `HEIR`            | Designated recipient of legacy or estate. Inheritor, may have legal or familial tie |

From 47a05f66010bf0d2f569bfcc1ce9544a3d194540 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 10:47:40 +0200
Subject: [PATCH 04/11] Update
 specification/gedcom-3-structures-4-enumerations-roles.md

Ok i'll do the others too.

Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
---
 specification/gedcom-3-structures-4-enumerations-roles.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-3-structures-4-enumerations-roles.md b/specification/gedcom-3-structures-4-enumerations-roles.md
index 8039e01a..686e3905 100644
--- a/specification/gedcom-3-structures-4-enumerations-roles.md
+++ b/specification/gedcom-3-structures-4-enumerations-roles.md
@@ -10,7 +10,7 @@ This table describes the high-level category of function or relationship this `S
 
 | ICO | MAINROLE     | Description                                                                |
 |-----| ------------ | ----------------------------------------------------------------------- |
-| 🗂️ | `ADMIN`      | Person acted in an administrative or bureaucratic role (e.g. official, clerk, registrar, census). |
+| 🗂️ | `ADMIN`      | Person acted in an administrative or bureaucratic role (e.g., official, clerk, registrar, census). |
 | 🧱 | `ASSET`      | Person or Asset who/that was connected to the possession, transfer, or status of a non-human entity (e.g., land, object). |
 | 👶 | `BIRTH`      | Person was born or played a key role in a birth event. (child, parent, midwife)|
 | 🏢 | `CORPORATION`| Person was involved in an institution (e.g. school, guild, company). |

From c1a29dbea67391db2ff9b9f14d5f9a11867a1d63 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 11:05:31 +0200
Subject: [PATCH 05/11] Update gedcom-3-structures-4-enumerations-roles.md

Added comma where needed.
---
 ...edcom-3-structures-4-enumerations-roles.md | 60 +++++++++----------
 1 file changed, 30 insertions(+), 30 deletions(-)

diff --git a/specification/gedcom-3-structures-4-enumerations-roles.md b/specification/gedcom-3-structures-4-enumerations-roles.md
index 686e3905..2b4fdbe6 100644
--- a/specification/gedcom-3-structures-4-enumerations-roles.md
+++ b/specification/gedcom-3-structures-4-enumerations-roles.md
@@ -13,15 +13,15 @@ This table describes the high-level category of function or relationship this `S
 | 🗂️ | `ADMIN`      | Person acted in an administrative or bureaucratic role (e.g., official, clerk, registrar, census). |
 | 🧱 | `ASSET`      | Person or Asset who/that was connected to the possession, transfer, or status of a non-human entity (e.g., land, object). |
 | 👶 | `BIRTH`      | Person was born or played a key role in a birth event. (child, parent, midwife)|
-| 🏢 | `CORPORATION`| Person was involved in an institution (e.g. school, guild, company). |
+| 🏢 | `CORPORATION`| Person was involved in an institution (e.g., school, guild, company). |
 | 🔁 | `CROSSROLE`  | Role applicable in multiple contexts (e.g., witness, guardian). |
-| ⚰️ | `DEATH`      | Person died or had a role in the context of death (e.g. deceased, undertaker, mourner). |
+| ⚰️ | `DEATH`      | Person died or had a role in the context of death (e.g., deceased, undertaker, mourner). |
 | 🧬 | `DNA`        | Roles related to genetic testing in analysis labs or research programs, genealogical matching, lab processing, and interpretation of DNA test results. Includes both professional and familial participation  — with focus on identity, inheritance, and kinship confirmation. |
-| 📚 | `EDUCATIONAL`| Person acted in an educational setting (e.g. teacher, student, examiner). |
-| 🗓️ | `EVENT`      | Person participated in a general event (e.g. spectator, officiant). |
+| 📚 | `EDUCATIONAL`| Person acted in an educational setting (e.g., teacher, student, examiner). |
+| 🗓️ | `EVENT`      | Person participated in a general event (e.g., spectator, officiant). |
 | 👨‍👩‍👧 | `FAMILY`     | Role defines kinship or household relationship. (parent, child, spouse) |
-| 🛡️ | `GROUP`      | Role in a collective or institutional context (e.g. tribe, church, farm, guild). |
-| 🪪 | `IDENTITY`   | Roles associated with formal or legal identification (e.g. renamed, declared), such as declared identity, proven relationships, or official recognitions. Includes DNA-based identity roles such as matched individual or inferred parent. |
+| 🛡️ | `GROUP`      | Role in a collective or institutional context (e.g., tribe, church, farm, guild). |
+| 🪪 | `IDENTITY`   | Roles associated with formal or legal identification (e.g., renamed, declared), such as declared identity, proven relationships, or official recognitions. Includes DNA-based identity roles such as matched individual or inferred parent. |
 | 📜 | `INHERITANCE`| Person was involved in inheritance or estate transfer. |
 | ⚖️ | `JUDICIAL`   | Role in legal or courtroom setting. (judge, magistrate, court officer, plaintiff) |
 | 🖋️ | `LEGAL`      | Role in legal matters outside court (e.g., agent, claimant, notary, lawyer). |
@@ -59,22 +59,22 @@ This table defines all standardized combinations of `MAINROLE` and `ROLE` used i
 | 🗂️ | `ADMIN`       | `TRANSCRIBER`     | Enters information  |
 | 🗂️ | `ADMIN`       | `VERIFIER`        | Verifies document authenticity  |
 | 🧱 | `ASSET`       | `ASSIGNEE`        | Assigned asset  |
-| 🧱 | `ASSET`       | `AUCTION`         | Asset offered for sale via auction (e.g. toolset or furniture in probate)  |
+| 🧱 | `ASSET`       | `AUCTION`         | Asset offered for sale via auction (e.g., toolset or furniture in probate)  |
 | 🧱 | `ASSET`       | `AWARD`           | Prize or honor, given in recognition or as a prize. Use PHRASE for detail: [medal, certificate, award name, event, date]  |
 | 🧱 | `ASSET`       | `BENEFICIARY`     | Legal or named recipient of an object, particularly in the context of a will or deed. |
 | 🧱 | `ASSET`       | `BEQUEST`         | Asset being inherited through a will or succession document   |
 | 🧱 | `ASSET`       | `CERTIFICATE`     | Asset representing the document itself.  |
-| 🧱 | `ASSET`       | `COLLATERAL`      | Asset pledged as security for a loan or legal agreement (e.g. land in a bond)  |
+| 🧱 | `ASSET`       | `COLLATERAL`      | Asset pledged as security for a loan or legal agreement (e.g., land in a bond)  |
 | 🧱 | `ASSET`       | `CREATOR`         | Original maker or fabricator of the item (e.g., artisan who crafted the medal). |
 | 🧱 | `ASSET`       | `DONOR`           | Person who gives or gifts the item voluntarily. |
-| 🧱 | `ASSET`       | `GIFT`            | Asset being donated or given or ceremonially transferred(e.g. a cow given to a daughter on marriage) |
+| 🧱 | `ASSET`       | `GIFT`            | Asset being donated or given or ceremonially transferred(e.g., a cow given to a daughter on marriage) |
 | 🧱 | `ASSET`       | `HOLDER`          | Person who was the **recipient**, **bearer**, or **user** of an item such as a passport, license, or medal. Includes **legal**, **formal**, or **official** document reception. Posession can be pemanent or temporarely. |
 | 🧱 | `ASSET`       | `ISSUER`          | Person (or organization) who created, issued, awarded, or granted the item. Often official or institutional. (e.g., organization issuing a medal, license, passport, testresult)|
-| 🧱 | `ASSET`       | `ITEM`            | Catch-all for miscellaneous movable assets (e.g. book, cart, sword) |
-| 🧱 | `ASSET`       | `LISTED`          | Mentioned in a record but not transferred, often for valuation or record (e.g. farm in a will) |
-| 🧱 | `ASSET`       | `LOT`             | Grouped or undivided set of items treated as a unit (e.g. “lot of 6 chairs”) |
+| 🧱 | `ASSET`       | `ITEM`            | Catch-all for miscellaneous movable assets (e.g., book, cart, sword) |
+| 🧱 | `ASSET`       | `LISTED`          | Mentioned in a record but not transferred, often for valuation or record (e.g., farm in a will) |
+| 🧱 | `ASSET`       | `LOT`             | Grouped or undivided set of items treated as a unit (e.g., “lot of 6 chairs”) |
 | 🧱 | `ASSET`       | `OTHER`           | Catch-all; must clarify with `PHRASE`  |
-| 🧱 | `ASSET`       | `PROPERTY`        | General asset (real estate or fixed structure) being transferred between parties (e.g. house, land parcel) |
+| 🧱 | `ASSET`       | `PROPERTY`        | General asset (real estate or fixed structure) being transferred between parties (e.g., house, land parcel) |
 | 🧱 | `ASSET`       | `RECIPIENT`       | Person receiving the asset.   |
 | 🧱 | `ASSET`       | `REPAIRER`        | Person tasked with maintaining or restoring the object. |
 | 🧱 | `ASSET`       | `STOCKRENTAL`     | Asset temporarily assigned or rented (e.g. oxen or horse or cart lent for a season) |
@@ -147,23 +147,23 @@ This table defines all standardized combinations of `MAINROLE` and `ROLE` used i
 | 🧬 | `DNA`         | `GENETICIST`  | Certified specialist who reviewed, confirmed, or interpreted the DNA results. |
 | 🧬 | `DNA`         | `KITOWNER`    | Registered owner or account holder of the DNA test kit, possibly different from the test subject. |
 | 🧬 | `DNA`         | `LABTECH`  | Laboratory or technical worker responsible for processing or validating the DNA sample. |
-| 🧬 | `DNA`         | `MATCH`       | Individual whose genetic material matched the subject’s, either fully or partially. (e.g. relative match, segment overlap) |
-| 🧬 | `DNA`         | `PARENTAL`    | Biological parent, ancestor or presumed biological contributor, confirmed through DNA evidence (e.g. paternity test). |
+| 🧬 | `DNA`         | `MATCH`       | Individual whose genetic material matched the subject’s, either fully or partially. (e.g., relative match, segment overlap) |
+| 🧬 | `DNA`         | `PARENTAL`    | Biological parent, ancestor or presumed biological contributor, confirmed through DNA evidence (e.g., paternity test). |
 | 🧬 | `DNA`         | `SITE`| Location connected to testing, analysis, or reporting of DNA.<br>Use PHRASE for detail: [lab, laboratory, testing center, facility, analysis center, clinic] |
-| 🧬 | `DNA`         | `SPONSOR`     | Person or organization that funded or facilitated the DNA test. (e.g. gift, project, third-party study) |
+| 🧬 | `DNA`         | `SPONSOR`     | Person or organization that funded or facilitated the DNA test. (e.g., gift, project, third-party study) |
 | 🧬 | `DNA`         | `SUBJECT`     | Person whose DNA was tested, submitted, or reported. May include self-testers or individuals analyzed by third parties; may also appear as "testee" or "donor". |
 | 📚 | `EDUCATIONAL` | `EXAMINER`        | Official evaluating exams (inspecting, certifying, examining)  |
 | 📚 | `EDUCATIONAL` | `SITE`| Site where instruction or academic activity took place.<br>Use PHRASE for detail: [school, university, boarding school, classroom, academy] |
 | 📚 | `EDUCATIONAL` | `STUDENT`         | Person recieving instruction. Enrolled or studying ; pupil, student, apprentice |
 | 📚 | `EDUCATIONAL` | `TEACHER`         | Delivered lessons or instruction; includes instructors, tutors |
-| 🗓️ | `EVENT`       | `OFFICIANT`       | Conducts ceremony or signs something, e.g. priest, registrar    |
+| 🗓️ | `EVENT`       | `OFFICIANT`       | Conducts ceremony or signs something, e.g., priest, registrar    |
 | 🗓️ | `EVENT`       | `ORGANIZER`       | Person coordinating or arranging the event                                      |
 | 🗓️ | `EVENT`       | `PARTICIPANT`     | General event role, not further specified           |
 | 🗓️ | `EVENT`       | `PARTYMEMBER`     | Someone who is part of a group celebrating a specific even |
 | 🗓️ | `EVENT`       | `RECORDER`        | Person who documented or recorded details of the event.     |
 | 🗓️ | `EVENT`       | `SPECTATOR`       | Passive observer                                           |
-| 🗓️ | `EVENT`       | `TARGET`          | Person affected by the event, e.g. victim or beneficiary               |
-| 🗓️ | `EVENT`       | `WITNESS`         | Person who saw the event (e.g. accident, birth, signing)             |
+| 🗓️ | `EVENT`       | `TARGET`          | Person affected by the event, e.g., victim or beneficiary               |
+| 🗓️ | `EVENT`       | `WITNESS`         | Person who saw the event (e.g., accident, birth, signing)             |
 | 👨‍👩‍👧 | `FAMILY`      | `ADOPTEE`         | The child being adopted  |
 | 👨‍👩‍👧 | `FAMILY`      | `ADOPTER`         | Legal adoptive parent  |
 | 👨‍👩‍👧 | `FAMILY`      | `AUNT`            | Aunt  |
@@ -242,13 +242,13 @@ This table defines all standardized combinations of `MAINROLE` and `ROLE` used i
 | 🛡️ | `GROUP`       | `TRANSFERRED`     | Moved from one group to another |
 | 🛡️ | `GROUP`       | `WORKER`          | General laborer or active contributor|
 | 🪪 | `IDENTITY`    | `APPLICANT`       | Person who filed or initiated an application for identity-related documents (e.g., passport, visa, name change). |
-| 🪪 | `IDENTITY`    | `ASSIGNED`        | Someone else gives the identity, e.g. "He is John Smith"        |
-| 🪪 | `IDENTITY`    | `DECLARED`        | Person says who they are, e.g. "I am John Smith"   |
+| 🪪 | `IDENTITY`    | `ASSIGNED`        | Someone else gives the identity, e.g., "He is John Smith"        |
+| 🪪 | `IDENTITY`    | `DECLARED`        | Person says who they are, e.g., "I am John Smith"   |
 | 🪪 | `IDENTITY`    | `EXAMINER`        | Person responsible for inspecting or verifying submitted identity documents or biometric records. |
 | 🪪 | `IDENTITY`    | `INTERPRETER`     | Present to assist in cases where language barriers existed during identity proceedings (common in immigration or legal name change). |
 | 🪪 | `IDENTITY`    | `NAMED`           | A name is stated without a formal declaration              |
 | 🪪 | `IDENTITY`    | `RECORDER`        | Person who entered or copied the identity data into a formal register (e.g., civil clerk, church scribe). |
-| 🪪 | `IDENTITY`    | `RENAMED`         | Explicit change of name, e.g. adoption, alias, name change    |
+| 🪪 | `IDENTITY`    | `RENAMED`         | Explicit change of name, e.g., adoption, alias, name change    |
 | 🪪 | `IDENTITY`    | `SPONSOR`         | Person vouching for or supporting the identity/residency claim of another, especially in immigration or residency permission cases. |
 | 🪪 | `IDENTITY`    | `WITNESS`         | Individual attesting to someone’s identity (e.g., in affidavit, oath, or testimony). Often required for birth, alias, or passport paperwork. |
 | 📜 | `INHERITANCE` | `ATTORNEY`        | Attorny, also called Solicitor. The legal professional who provides legal advice during will creation and ensures it meets all legal requirements. |
@@ -331,7 +331,7 @@ for detail: [property name, heir, date] |
 | 💍 | `MARRIAGE`    | `FIANCÉ(E)`       | Engaged to be married; may not result in marriage |
 | 💍 | `MARRIAGE`    | `GROOM`           | Male partner in marriage-type event   |
 | 💍 | `MARRIAGE`    | `MAIDOFHONOR`     | Witness or supporter for bride   |
-| 💍 | `MARRIAGE`    | `MARRIAGE-WITNESS`| Someone witnessing the marriage, e.g. best man       |
+| 💍 | `MARRIAGE`    | `MARRIAGE-WITNESS`| Someone witnessing the marriage, e.g., best man       |
 | 💍 | `MARRIAGE`    | `OFFICIANT`       | Person leading the ceremony                         |
 | 💍 | `MARRIAGE`    | `PARTNER`         | Unmarried long-term partner, registered or informal. Or one of the marrying persons                                          |
 | 💍 | `MARRIAGE`    | `SPOUSE`          | Married partner, legally recognized. Used where sex or role is unspecified or later in life |
@@ -341,7 +341,7 @@ for detail: [property name, heir, date] |
 | 🎞️ | `MEDIA`       | `COPYRIGHT`       | Media holding copyright status. Use PHRASE for detail: [copyright holder, jurisdiction, term] |
 | 🎞️ | `MEDIA`       | `CURATOR`         | Organized or selected items for publication/exhibit |
 | 🎞️ | `MEDIA`       | `EDITOR`          | Reviewed or prepared content for publication or release |
-| 🎞️ | `MEDIA`       | `ILLUSTRATOR`     | Visual artist or designer of the media object (e.g. sketch, diagram, enhancement) |
+| 🎞️ | `MEDIA`       | `ILLUSTRATOR`     | Visual artist or designer of the media object (e.g., sketch, diagram, enhancement) |
 | 🎞️ | `MEDIA`       | `INTERVIEWEE`     | Provided personal answers or narrative used in the media content |
 | 🎞️ | `MEDIA`       | `MENTIONED`       | Referenced inside the media                          |
 | 🎞️ | `MEDIA`       | `PHOTOGRAPHER`    | Took or captured the photo or visual image |
@@ -363,7 +363,7 @@ for detail: [property name, heir, date] |
 | 🪖 | `MILITARY`    | `CASUALTY`       | Person who is wounded, missing, killed  |
 | 🪖 | `MILITARY`    | `COMMANDER`      | Leader (Officer) of group or unit; may be temporary |
 | 🪖 | `MILITARY`    | `CONSCRIPT`      | Drafted into service; may include limited service duration |
-| 🪖 | `MILITARY`    | `ENLISTED`       | Non-officer member of military (e.g. private, corporal) Signed up for military service |
+| 🪖 | `MILITARY`    | `ENLISTED`       | Non-officer member of military (e.g., private, corporal) Signed up for military service |
 | 🪖 | `MILITARY`    | `OFFICER`        | Held formal military role; rank may be known |
 | 🪖 | `MILITARY`    | `RECIPIENT`      | Person awarded a medal, rank insignia, commendation, or military honor. |
 | 🪖 | `MILITARY`    | `RECRUITOR`      | Recruits others |
@@ -392,7 +392,7 @@ for detail: [property name, heir, date] |
 | 🏘️ | `PROPERTY`    | `OWNER`          | Person or group who owns the property (Landowner or leaseholder) (legal or practical owner) |
 | 🏘️ | `PROPERTY`    | `OCCUPANT`       | Current inhabitant of a property  |
 | 🏘️ | `PROPERTY`    | `ORIGIN`         | Location where an event or journey begins. Use PHRASE for detail: [event, location, date] |
-| 🏘️ | `PROPERTY`    | `RECORDED-BY`    | Someone listing or describing the property/asset (e.g. inventoried it)        |
+| 🏘️ | `PROPERTY`    | `RECORDED-BY`    | Someone listing or describing the property/asset (e.g., inventoried it)        |
 | 🏘️ | `PROPERTY`    | `RESIDENT`       | Lives on the property (house, farm, etc.)           |
 | 🏘️ | `PROPERTY`    | `SCENE`          | Location where a notable event occurred. Use PHRASE for detail: [event type, location, date] |
 | 🏘️ | `PROPERTY`    | `SELLER`         | Sold the property. (Seller in a transaction) Party selling or transferring ownership |
@@ -418,7 +418,7 @@ for detail: [property name, heir, date] |
 | ✝️ | `RELIGIOUS`   | `MONK`           | Monastic religious figure. <br>Use PHRASE for detail: [abbey, cloister, vows, friar, monastic] |
 | ✝️ | `RELIGIOUS`   | `NOVICE`         | Person in early stage of religious life, not yet fully vowed or ordained. <br>Use PHRASE for detail: [initiate, training, probation, monastery] |
 | ✝️ | `RELIGIOUS`   | `NUN`            | Female monastic. <br>Use PHRASE for detail: [convent, sister, habit, cloister, vows] |
-| ✝️ | `RELIGIOUS`   | `OFFICIANT`      | Performed a religious function (e.g. marriage, baptism). <br>Use PHRASE for detail: [marriage, baptism, religious duty, clergy] |
+| ✝️ | `RELIGIOUS`   | `OFFICIANT`      | Performed a religious function (e.g., marriage, baptism). <br>Use PHRASE for detail: [marriage, baptism, religious duty, clergy] |
 | ✝️ | `RELIGIOUS`   | `ORDAINER`       | Someone who has the right to ordain deacons and others. <br>Use PHRASE for detail: [ordination, bishop, authority, consecrate] |
 | ✝️ | `RELIGIOUS`   | `PASTOR`         | Pastor or church leader. <br>Use PHRASE for detail: [preacher, leader, service, congregation] |
 | ✝️ | `RELIGIOUS`   | `PRIEST`         | Religious officiant or cleric. <br>Use PHRASE for detail: [mass, church, clergy, ordination] |
@@ -434,11 +434,11 @@ for detail: [property name, heir, date] |
 | 🌐 | `SOCIAL`      | `DEDICATOR`     | Person who organized or dedicated the memorial    |
 | 🌐 | `SOCIAL`      | `ENSLAVER`      | Person who held others in involuntary servitude or bondage. |
 | 🌐 | `SOCIAL`      | `GUEST`         | Attended or featured at the event |
-| 🌐 | `SOCIAL`      | `HONOREE`       | [The person being commemorated (e.g. on a gravestone or memorial)]  [Person being honored in a tribute event]|
+| 🌐 | `SOCIAL`      | `HONOREE`       | [The person being commemorated (e.g., on a gravestone or memorial)]  [Person being honored in a tribute event]|
 | 🌐 | `SOCIAL`      | `HOST`          | Gave the party, reception, or event |
-| 🌐 | `SOCIAL`      | `INSCRIBED`     | Person named in writing, e.g. on a war memorial      |
+| 🌐 | `SOCIAL`      | `INSCRIBED`     | Person named in writing, e.g., on a war memorial      |
 | 🌐 | `SOCIAL`      | `MENTOR`        | Guided or advised another; includes apprenticeships |
-| 🌐 | `SOCIAL`      | `PARTICIPANT`   | Present in public or semi-public event marking something, e.g. parade, unveiling |
+| 🌐 | `SOCIAL`      | `PARTICIPANT`   | Present in public or semi-public event marking something, e.g., parade, unveiling |
 | 🌐 | `SOCIAL`      | `REPRESENTATIVE`| Portrayed or represented another person, usually in a theatrical or ceremonial setting. |
 | 🌐 | `SOCIAL`      | `SITE`| Setting of public or private gatherings and social events.<br>Use PHRASE for detail: [ballroom, village square, party tent, pub, dining hall, cinema] |
 | 🌐 | `SOCIAL`      | `SLAVE`         | Person held in bondage or forced labor; property of another. |

From 43f3351958523299439f9704031533d3595718fe Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 12:23:50 +0200
Subject: [PATCH 06/11] Update gedcom-6-appendix-examples-sticky.md

Trying to get the linktable working.
---
 specification/gedcom-6-appendix-examples-sticky.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
index 050049ab..e375dd04 100644
--- a/specification/gedcom-6-appendix-examples-sticky.md
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -26,7 +26,7 @@ Click 🔝 to return here from any example.
 
 | 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
 |-----------|------------------|-------------------------------------------------------------------|
-| [💍 Example 01](#💍-example-01-wedding-certificate-with-family-necklace-transfer) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
+| [💍 Example 01](#example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
 | [👧🏻 Example 02](#👧🏻-example-02-international-adoption-certificate) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
 | [🍼 Example 03](#🍼-example-03-medical-birth-certificate) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
 | [💍🧒 Example 04](#💍🧒-example-04-wedding-with-step-children-from-both-sides) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |

From 41ddcde5ed1a0b1da26fd96267a7099e0e868ad5 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 12:41:18 +0200
Subject: [PATCH 07/11] Update gedcom-6-appendix-examples-sticky.md

Linktable corrected and some errors in example
---
 .../gedcom-6-appendix-examples-sticky.md      | 41 ++++++++++---------
 1 file changed, 21 insertions(+), 20 deletions(-)

diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
index e375dd04..fc138d69 100644
--- a/specification/gedcom-6-appendix-examples-sticky.md
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -27,24 +27,24 @@ Click 🔝 to return here from any example.
 | 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
 |-----------|------------------|-------------------------------------------------------------------|
 | [💍 Example 01](#example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
-| [👧🏻 Example 02](#👧🏻-example-02-international-adoption-certificate) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
-| [🍼 Example 03](#🍼-example-03-medical-birth-certificate) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
-| [💍🧒 Example 04](#💍🧒-example-04-wedding-with-step-children-from-both-sides) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |
-| [🧮 Example 05](#🧮-example-05-census-with-annotated-events) | FAMILY, CENSUS |  **🧮 Example 05: Census with Annotated Events**<br>Census of a family: Father, Mother, Son, Daughter, Enumerator, Boarder. Includes **annotated "events"** (`AN_BIRTH`, and `AN_MOVE`) |
-| [🎖️ Example 06](#🎖️-example-06-medal-awarded-to-individual) | ASSET, MEDAL        | **🎖️ Example 06: Medal awarded to individual**<br>A medal (`ASSET`) given to a soldier, using `STICKY` links and `FLEX` fields. The `TEMPLATE` is of type `MILITARY, AWARD` and connects a tangible object (the medal itself) with the recipient using `STICKY` roles. |
-| [🌿 Example 07](#🌿-example-07-land-grant-record) | PROPERTY, GRANT | **🌿 Example 07: Land Grant Record**<br>This example models a royal land grant issued in 1811 to a private citizen as a reward for military service. It includes a structured `TRANSFER` with a defined `GRANTOR`, `GRANTEE`, and land parcel `ASSET`, as well as a properly detailed `CITA` section with archival metadata.|
-| [🪪 Example 08](#🪪-example-08-naturalization-and-passport) | ORGANIZATION, COURT and<br>IDENTITY, PASSPORT | **🪪 Example 08: Naturalization and Passport**<br>**A `TEMPLATE` pair** modeling naturalization and passport issuance for Leopold Federwitz in early 1900s USA. Includes legal authority roles, asset `STICKY`s (Naturalization certificate and passport), and showcases how to store both under the `ASSETS` section of the `INDI`. The `TEMPLATE`s events are: `NATU` (official GEDCOM) and `EVEN IDENTITY, PASSPORT` (no official GEDCOM event present)|
-| [⛪ Example 09](#⛪-example-09-adult-baptism-and-religious-roles) | RELIGIOUS and BAPTISM | **⛪ Example 09: Adult baptism and Religious roles**<br>A combination of multi-role religious events: includes adult convert, clergy, ordination backstory, and baptism with an `ASSET` (baptism gown) use. It has: Adult conversion (Hans and Johannes); Infant baptism (Johannes); Ordination (Einar Voss); Clergy participation (Henrik Brodahl); Godparent and family witness roles (Marta, Karl); Religious assets (Baptism gown) |
-| [📙 Example 10](#📙-example-10-family-bible) | SECONDARY, FAMILYBIBLE | **📙 Example 10: Family Bible**<br>A richly annotated family Bible (TYPE SECONDARY, FAMILYBIBLE) spanning 3 generations of the Eldridge family (1869–1936). Uses `AN_xxx` `STICKY` types to model secondary handwritten events (with `FLEX ANNOTATION`) like births, deaths, illnesses, and gifts. Includes the Bible's `ASSET`-record, a beloved butler and a midwife, and shows `TDABOVI` lineage, and emotional historical record-keeping in `FLEX`. Includes period photos. |
-| [🧬 Example 11](#🧬-example-11-dna-test-results-match-comparison-and-genotype-report) | IDENTITY, DNATEST | **🧬 Example 11: DNA Test Results – Match Comparison & Genotype Report**<br>A pair of `TEMPLATE`s modeling both a DNA match comparison report, using `FLEX` entries for shared segments and relationship estimates. And a direct genotype report. Includes `STICKY` for the match report (`ASSET`), uses `ADDRPLUS` for lab and test center contacts, and demonstrates `FLEX ARRAY` for tabular genotype values. Shared entities like individuals are reused across both reports. |
-| [🛖 Example 12](#🛖-example-12-norwegian-farm-membership) | RESIDENCE, FARM-OCCU | **🛖 Example 12: Norwegian Farm Membership**<br>This example demonstrates how to use a `GROUP` record to represent **a traditional Norwegian farm** in a historical context (Lien Farm Census, 1832, Valdres, Norway), and how to associate both family and non-family individuals with that group using `STICKY` roles like `LEADER`, `MEMBER`, `WORKER`, and `RESIDENT`. |
-| [🏥 Example 13](#🏥-example-13-hospital-admission-and-discharge-record) | MEDICAL, ADMISSION and DISCHARGE | **🏥 Example 13: Hospital Admission and Discharge Record**<br>Two `TEMPLATE`s modeling a patient's hospital stay in 1933 for acute appendicitis. An admission and a discharge `TEMPLATE`. Shows the hospital as an organization and roles like `PATIENT`, `PHYSICIAN`, and `SITE` (for the hospital itself), with `FLEX`, `SPLAC`, and a scanned source register. |
-| [🛠️ Example 14](#🛠️-example-14-mid-century-employment-transfer-order) | OCCUPATIONAL, EMPLOYMENT | **🛠️ Example 14: Mid Century Employment Transfer Order**<br>This `TEMPLATE` records the formal transfer of employee Gertrude Elmsbottom from the Leiden Branch to the Rotterdam HQ of Western Office Supplies Co. in 1954. Includes `STICKY` records for the employee, both originating and receiving workplaces, and the issuing officer. Demonstrates `EMPLOYER` roles for organizations, sequential `OCCU` facts for old and new positions, structured `FLEX DESCRIPT` for the new job title, and integration of `SOURCE` with scanned memo evidence. |
-| [🧾 Example 15](#🧾-example-15-legal-will-creation-and-execution-with-estate-transfers) | DEATH, WILL | **🧾 Example 15: Legal Will Creation and Execution with Estate Transfers**<br>This dual-`TEMPLATE` example models the two-stage legal will process for Emil Rothenbühler: will creation (while alive) and will execution (after death). It includes `STICKY`s for the decedent across both stages, a notary, legal executor, multiple heirs, and detailed `TRANSFER` structures for assets. Also demonstrates `FLEX VALUE` for appraisal, `SHARE` for proportional distribution, and a realistic asset division process. Includes dedicated `STICKY` and `TRANSFER` for each asset to track inheritance lineage and value allocation. |
-| [⚔️ Example 16](#⚔️-example-16-historical-title-and-nobility-inheritance) | DEATH, WILL, Title | **⚔️ Example 16:  Historical Title and Nobility Inheritance**<br>This `TEMPLATE` models the inheritance of a noble title and estate following the death of a titled individual. Features include a `STICKY` for the title holder, an heir receiving both property and title, symbolic artifacts, and a ruling monarch confirming the transfer. Demonstrates `TITLE, Baron`, land size, annotations, and an `ASSET` history of previous holders. Includes a dedicated `STICKY` and `TRANSFER` for the title itself (`ROLE DIGNITY`), showing how titles can be modeled as independent assets with full lineage tracking.
-| [🛡️ Example 17](#🛡️-example-17-guild-membership-certificate) | GROUP, GUILD-MEM | **🛡️ Example 17: Guild Membership Certificate**<br>Guild admission certificate for John Smith in 1702 London, issued by the Worshipful Company of Blacksmiths in London, including the original oath and rights text<br>(“Be it knowne unto all men by these presentes…”),<br>modeled as both `TEMPLATE` event and asset `STICKY`. Includes structured membership details. |
-[⚖️ Example 18](#⚖️-example-18-court-trial-record-humorous-fictional-case) | LEGAL, JUDGMENT | **⚖️ Example 18: Court Trial Record – Humorous Fictional Case**<br>Illustrates a fictional court trial modeled in GEDCOM 8, focusing on the use of `STICKY` roles in legal records. Includes `ROLE` types like `DEFENDANT`, `JUDGE`, `JURY FOREMAN`, and `WITNESS`, showing how to link individuals to a single `TEMPLATE`. Playfully absurd, but structurally correct. |
-| [🪦 Example 19](#🪦-example-19-gravestone-with-named-and-implied-persons) | MEMORIAL, GRAVESTONE | **🪦 Example 19: Gravestone with Named and Implied Persons**<br>Shows multiple individuals on a shared tombstone: two named (with roles `MAIN` and `WIDOW`) and two implied (`CHILD`, `GRANDCHILD`). Includes annotations, a Bible verse, estimated marriage date, and `QUAY` levels. `TEMPLATE` has `1 TORIGIN ORIGDOC, INCOMPLETE` |
+| [👧🏻 Example 02](#example-02) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
+| [🍼 Example 03](#example-03) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
+| [💍🧒 Example 04](#example-04) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |
+| [🧮 Example 05](#example-05) | FAMILY, CENSUS |  **🧮 Example 05: Census with Annotated Events**<br>Census of a family: Father, Mother, Son, Daughter, Enumerator, Boarder. Includes **annotated "events"** (`AN_BIRTH`, and `AN_MOVE`) |
+| [🎖️ Example 06](#example-06) | ASSET, MEDAL        | **🎖️ Example 06: Medal awarded to individual**<br>A medal (`ASSET`) given to a soldier, using `STICKY` links and `FLEX` fields. The `TEMPLATE` is of type `MILITARY, AWARD` and connects a tangible object (the medal itself) with the recipient using `STICKY` roles. |
+| [🌿 Example 07](#example-07) | PROPERTY, GRANT | **🌿 Example 07: Land Grant Record**<br>This example models a royal land grant issued in 1811 to a private citizen as a reward for military service. It includes a structured `TRANSFER` with a defined `GRANTOR`, `GRANTEE`, and land parcel `ASSET`, as well as a properly detailed `CITA` section with archival metadata.|
+| [🪪 Example 08](#example-08) | ORGANIZATION, COURT and<br>IDENTITY, PASSPORT | **🪪 Example 08: Naturalization and Passport**<br>**A `TEMPLATE` pair** modeling naturalization and passport issuance for Leopold Federwitz in early 1900s USA. Includes legal authority roles, asset `STICKY`s (Naturalization certificate and passport), and showcases how to store both under the `ASSETS` section of the `INDI`. The `TEMPLATE`s events are: `NATU` (official GEDCOM) and `EVEN IDENTITY, PASSPORT` (no official GEDCOM event present)|
+| [⛪ Example 09](#example-09) | RELIGIOUS and BAPTISM | **⛪ Example 09: Adult baptism and Religious roles**<br>A combination of multi-role religious events: includes adult convert, clergy, ordination backstory, and baptism with an `ASSET` (baptism gown) use. It has: Adult conversion (Hans and Johannes); Infant baptism (Johannes); Ordination (Einar Voss); Clergy participation (Henrik Brodahl); Godparent and family witness roles (Marta, Karl); Religious assets (Baptism gown) |
+| [📙 Example 10](#example-10) | SECONDARY, FAMILYBIBLE | **📙 Example 10: Family Bible**<br>A richly annotated family Bible (TYPE SECONDARY, FAMILYBIBLE) spanning 3 generations of the Eldridge family (1869–1936). Uses `AN_xxx` `STICKY` types to model secondary handwritten events (with `FLEX ANNOTATION`) like births, deaths, illnesses, and gifts. Includes the Bible's `ASSET`-record, a beloved butler and a midwife, and shows `TDABOVI` lineage, and emotional historical record-keeping in `FLEX`. Includes period photos. |
+| [🧬 Example 11](#example-11) | IDENTITY, DNATEST | **🧬 Example 11: DNA Test Results – Match Comparison & Genotype Report**<br>A pair of `TEMPLATE`s modeling both a DNA match comparison report, using `FLEX` entries for shared segments and relationship estimates. And a direct genotype report. Includes `STICKY` for the match report (`ASSET`), uses `ADDRPLUS` for lab and test center contacts, and demonstrates `FLEX ARRAY` for tabular genotype values. Shared entities like individuals are reused across both reports. |
+| [🛖 Example 12](#example-12) | RESIDENCE, FARM-OCCU | **🛖 Example 12: Norwegian Farm Membership**<br>This example demonstrates how to use a `GROUP` record to represent **a traditional Norwegian farm** in a historical context (Lien Farm Census, 1832, Valdres, Norway), and how to associate both family and non-family individuals with that group using `STICKY` roles like `LEADER`, `MEMBER`, `WORKER`, and `RESIDENT`. |
+| [🏥 Example 13](#example-13) | MEDICAL, ADMISSION and DISCHARGE | **🏥 Example 13: Hospital Admission and Discharge Record**<br>Two `TEMPLATE`s modeling a patient's hospital stay in 1933 for acute appendicitis. An admission and a discharge `TEMPLATE`. Shows the hospital as an organization and roles like `PATIENT`, `PHYSICIAN`, and `SITE` (for the hospital itself), with `FLEX`, `SPLAC`, and a scanned source register. |
+| [🛠️ Example 14](#example-14) | OCCUPATIONAL, EMPLOYMENT | **🛠️ Example 14: Mid Century Employment Transfer Order**<br>This `TEMPLATE` records the formal transfer of employee Gertrude Elmsbottom from the Leiden Branch to the Rotterdam HQ of Western Office Supplies Co. in 1954. Includes `STICKY` records for the employee, both originating and receiving workplaces, and the issuing officer. Demonstrates `EMPLOYER` roles for organizations, sequential `OCCU` facts for old and new positions, structured `FLEX DESCRIPT` for the new job title, and integration of `SOURCE` with scanned memo evidence. |
+| [🧾 Example 15](#example-15) | DEATH, WILL | **🧾 Example 15: Legal Will Creation and Execution with Estate Transfers**<br>This dual-`TEMPLATE` example models the two-stage legal will process for Emil Rothenbühler: will creation (while alive) and will execution (after death). It includes `STICKY`s for the decedent across both stages, a notary, legal executor, multiple heirs, and detailed `TRANSFER` structures for assets. Also demonstrates `FLEX VALUE` for appraisal, `SHARE` for proportional distribution, and a realistic asset division process. Includes dedicated `STICKY` and `TRANSFER` for each asset to track inheritance lineage and value allocation. |
+| [⚔️ Example 16](#example-16) | DEATH, WILL, Title | **⚔️ Example 16:  Historical Title and Nobility Inheritance**<br>This `TEMPLATE` models the inheritance of a noble title and estate following the death of a titled individual. Features include a `STICKY` for the title holder, an heir receiving both property and title, symbolic artifacts, and a ruling monarch confirming the transfer. Demonstrates `TITLE, Baron`, land size, annotations, and an `ASSET` history of previous holders. Includes a dedicated `STICKY` and `TRANSFER` for the title itself (`ROLE DIGNITY`), showing how titles can be modeled as independent assets with full lineage tracking.
+| [🛡️ Example 17](#example-17) | GROUP, GUILD-MEM | **🛡️ Example 17: Guild Membership Certificate**<br>Guild admission certificate for John Smith in 1702 London, issued by the Worshipful Company of Blacksmiths in London, including the original oath and rights text<br>(“Be it knowne unto all men by these presentes…”),<br>modeled as both `TEMPLATE` event and asset `STICKY`. Includes structured membership details. |
+[⚖️ Example 18](#example-18) | LEGAL, JUDGMENT | **⚖️ Example 18: Court Trial Record – Humorous Fictional Case**<br>Illustrates a fictional court trial modeled in GEDCOM 8, focusing on the use of `STICKY` roles in legal records. Includes `ROLE` types like `DEFENDANT`, `JUDGE`, `JURY FOREMAN`, and `WITNESS`, showing how to link individuals to a single `TEMPLATE`. Playfully absurd, but structurally correct. |
+| [🪦 Example 19](#example-19) | MEMORIAL, GRAVESTONE | **🪦 Example 19: Gravestone with Named and Implied Persons**<br>Shows multiple individuals on a shared tombstone: two named (with roles `MAIN` and `WIDOW`) and two implied (`CHILD`, `GRANDCHILD`). Includes annotations, a Bible verse, estimated marriage date, and `QUAY` levels. `TEMPLATE` has `1 TORIGIN ORIGDOC, INCOMPLETE` |
 
 
 
@@ -291,7 +291,7 @@ This example demonstrates a marriage certificate that includes a non-monetary pr
 2 PHRASE "Value of the item"
 2 CONTENTS 185.00
 1 FLEX DESCRIPT
- PHRASE "Description:"
+2 PHRASE "Description:"
 2 CONTENTS Victorian Silver Necklace with blue topaz
 1 FLEX MATERIAL
 2 PHRASE "Material it is made of"
@@ -482,7 +482,8 @@ The adoption certificate is stored in the @S0047@ source record with a digital s
 2 PART Petrova
 3 TYPE SURN
 1 ROLES
-2 STICKY @ST0147@             /* ALL info is in the STICKY, No Longer in the INDI */
+2 STICKY @ST0146@             /* Sofiya, real name at birth (ALL info in the STICKY, No Longer in the INDI) */
+2 STICKY @ST0147@             /* Sofia, adopted name (ALL info in the STICKY, No Longer in the INDI) */
 1 CHAN 29 APR 2025
 1 CHAN 29 APR 2025
 ```

From 2b852a682b487a3f84c8fec0fba1019289409634 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 12:52:48 +0200
Subject: [PATCH 08/11] Update gedcom-6-appendix-examples-sticky.md

Links still not working
---
 specification/gedcom-6-appendix-examples-sticky.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
index fc138d69..a845daa1 100644
--- a/specification/gedcom-6-appendix-examples-sticky.md
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -26,7 +26,7 @@ Click 🔝 to return here from any example.
 
 | 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
 |-----------|------------------|-------------------------------------------------------------------|
-| [💍 Example 01](#example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
+| [💍 Example 01](example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
 | [👧🏻 Example 02](#example-02) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
 | [🍼 Example 03](#example-03) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
 | [💍🧒 Example 04](#example-04) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |

From d06ec1110f75f248935a71bd36acb1606c451867 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 12:57:52 +0200
Subject: [PATCH 09/11] Update gedcom-6-appendix-examples-sticky.md

Another try on the links
---
 specification/gedcom-6-appendix-examples-sticky.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
index a845daa1..00daa7c4 100644
--- a/specification/gedcom-6-appendix-examples-sticky.md
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -26,7 +26,7 @@ Click 🔝 to return here from any example.
 
 | 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
 |-----------|------------------|-------------------------------------------------------------------|
-| [💍 Example 01](example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
+| [💍 Example 01](user-content-example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
 | [👧🏻 Example 02](#example-02) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
 | [🍼 Example 03](#example-03) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
 | [💍🧒 Example 04](#example-04) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |

From def70f0db792372fe7225a80253f3c14afa22345 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Sat, 16 Aug 2025 13:14:19 +0200
Subject: [PATCH 10/11] Update gedcom-6-appendix-examples-sticky.md

next try on 13:14
---
 specification/gedcom-6-appendix-examples-sticky.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
index 00daa7c4..ea154c9e 100644
--- a/specification/gedcom-6-appendix-examples-sticky.md
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -26,7 +26,7 @@ Click 🔝 to return here from any example.
 
 | 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
 |-----------|------------------|-------------------------------------------------------------------|
-| [💍 Example 01](user-content-example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
+| [💍 Example 01](gedcom-6-appendix-examples-sticky.md/example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
 | [👧🏻 Example 02](#example-02) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
 | [🍼 Example 03](#example-03) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
 | [💍🧒 Example 04](#example-04) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |

From b65016b027b34ec7c21b16eac267817612fb8367 Mon Sep 17 00:00:00 2001
From: "Tineke Kosmis (Granny10)" <33637841+mother10@users.noreply.github.com>
Date: Mon, 8 Sep 2025 11:24:23 +0200
Subject: [PATCH 11/11] Update gedcom-6-appendix-examples-sticky.md

Correct table link
---
 specification/gedcom-6-appendix-examples-sticky.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/gedcom-6-appendix-examples-sticky.md b/specification/gedcom-6-appendix-examples-sticky.md
index ea154c9e..a845daa1 100644
--- a/specification/gedcom-6-appendix-examples-sticky.md
+++ b/specification/gedcom-6-appendix-examples-sticky.md
@@ -26,7 +26,7 @@ Click 🔝 to return here from any example.
 
 | 🧾 Example | 📂 TEMPLATE Type | 📌 What it Shows                                                  |
 |-----------|------------------|-------------------------------------------------------------------|
-| [💍 Example 01](gedcom-6-appendix-examples-sticky.md/example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
+| [💍 Example 01](example-01) | MARRIAGE, CIVIL |  **💍 Example 01: Wedding Certificate with Family Necklace Transfer**<br>A marriage certificate that includes a non-monetary property transfer — in this case, a piece of jewelry given by the groom to the bride by a `TRANSFER`. (With `ASSET` and `FLEX`.)<br>Further, its `STICKY`s, hold **all information** that can be derived from a certain event, or `TEMPLATE`, so it shows the function of a `STICKY`is to replace part of the info of an `INDI`.<br>`MARR` tag now is in the couples `STICKY` records.   |
 | [👧🏻 Example 02](#example-02) | CHILD, ADOPTION |  **👧🏻 Example 02: International Adoption Certificate**<br>International adoption certificate, issued in 1992, including adoptive parents (`ROLE ADOPTER`), adopted child (born elsewhere, `ROLE MAIN, CHILD, ADOPTEE`), and issuing authority.<br>`ADOP` and `PEDI` now in the `TEMPLATE` and in the childs `STICKY`. With BIRTH name and ADOPTED name. The adopted child is added to the `ROLES` section of **BOTH parents**.  |
 | [🍼 Example 03](#example-03) | CHILD, BIRTH, Medical |  **🍼 Example 03: Medical Birth Certificate**<br>A birth certificate of a child born in a hospital. With father, mother, doctor and nurse `STICKY`'s. The child's `STICKY` has Weight, Length, and APGAR-score in `FLEX`. **The childs `STICKY` is also added to the `INDI` of both his parents !!** |
 | [💍🧒 Example 04](#example-04) | MARRIAGE, CIVIL |  **💍🧒 Example 04: Wedding with step children from both sides**<br>A marriage where both partners each already have children who become each others step children after that marriage. Including connections to there `INDI`'s. **All children, their biological and stepchildren** are mentioned in the `ROLES`section of their parents.  |