@atmosx/event-product-parser 3.0.4 → 3.0.6

package/.github/docs/docs-general-configurations.md

@@ -0,0 +1,209 @@
+<div align="center">
+	<a href="https://atmosphericx.scriptkitty.cafe">
+		<img src="../logo.png" alt="@atmosx/event-product-parser" width="800"/>
+	</a>
+	<br>
+	<p>A TypeScript/JavaScript library for parsing and ingesting NOAA and NWS Weather Text Products</p>
+	<small>A project built and maintained with ❤️ by the AtmosphericX team</small>
+	<p align="center">
+		<a href="https://atmosphericx.scriptkitty.cafe"><b>Documentation</b></a> |
+		<a href="https://github.com/AtmosphericX"><b>Repositories</b></a> |
+		<a href="https://www.npmjs.com/search?q=%40atmosx"><b>NPM Packages</b></a> |
+		<a href="https://atmosphericx-discord.scriptkitty.cafe"><b>Community Discord</b></a>
+	</p>
+</div>
+<br><br>
+
+
+# 4.0 - General Configurations
+
+`@atmosx/event-product-parser` provides a wide range of configuration options, from basic event handling and management to advanced filtering capabilities and customizable event properties. This section provides a comprehensive overview of every available configuration, including event settings, filtering options, and parser behavior, along with detailed explanations and practical examples to help you configure the parser for your specific use case.
+
+# 4.1 - Event Management & History
+
+**EventManagement** is a core configuration that controls how parsed events are managed throughout their lifecycle. When enabled, the parser automatically stores events in an internal, memory-safe cache, allowing it to efficiently track event issuance, updates, cancellations, upgrades, and expiration. This eliminates the need to implement and maintain your own event caching solution while ensuring event state remains consistent and up to date.
+
+Enabling **EventManagement** also unlocks the [ActionSettings](TODO) configuration, which allows you to define actions that are automatically executed after events have been parsed.
+
+```ts
+import { Manager } from '@atmosx/event-product-parser';
+
+const client = new Manager({
+	GlobalSettings: {
+		EventManagement: true, // Enable event management
+	},
+});
+```
+
+* Disabling **EventManagement** prevents the parser from tracking previously seen events. As a result, event expiration, cancellation, and update notifications will no longer be emitted. It is **strongly recommended** to leave this option enabled unless you have a specific reason to disable it.
+
+
+# 4.2 - Geometry Configurations
+
+`@atmosx/event-product-parser` provides configuration options for managing geometry properties associated with each event. These settings allow you to control how event geometries are handled during the receiving, parsing, and memory management stages of the event lifecycle.
+
+```ts
+GlobalSettings: {
+	DisableGeometryParsing: false, // Disables geometry parsing
+	UseShapefileCoordinates: true, // Uses UGC shapefile coordinate database
+	ShapefileSkipPoints: 0, // Skips points while building geometry for shapefiles
+},
+```
+
+## 4.2.1 - Disable Geometry Parsing
+
+The **DisableGeometryParsing** configuration is used to disable event geometry parsing. It was originally introduced as a way to reduce memory usage and improve parsing performance. However, with the introduction of memory-safe event caching, this configuration is now considered redundant and provides limited benefits in most use cases.
+
+It is recommended to keep geometry parsing enabled unless you have a specific requirement to exclude geometry data from processed events.
+
+```ts
+GlobalSettings: {
+	DisableGeometryParsing: true,
+},
+```
+
+## 4.2.2 – Force Shapefile Coordinates
+
+The **UseShapefileCoordinates** configuration allows you to obtain geographic coordinates and location information for spatial features. Shapefiles store geometry data such as points, lines, and polygons, which can be used to identify the exact position of features on a map.
+
+When this feature is enabled, coordinate data is retrieved from the shapefile database instead of relying on raw polygon coordinate values. Disabling this feature will use the polygon coordinates provided directly in the raw text data.
+
+```ts
+GlobalSettings: {
+	UseShapefileCoordinates: true
+}
+```
+
+Example raw polygon coordinates:
+
+```text
+LAT...LON 4587 6965 4585 6968 4588 6971 4587 6972
+          4584 6970 4576 6972 4576 6976 4577 6978
+          4574 6981 4566 6974 4565 6970 4558 6971
+          4553 6978 4530 6970 4567 7054 4573 7038
+          4580 7042 4589 7026 4596 7026 4598 6968
+```
+
+## 4.2.3 - Shapefile Skip Points
+
+The **ShapefileSkipPoints** configuration allows you to skip a specified number of points when building geometry for shapefiles. This can be useful for reducing the complexity of the resulting geometry or for performance reasons. This uses the [polygon-clipping](https://www.npmjs.com/package/polygon-clipping) library.
+
+```ts
+GlobalSettings: {
+	ShapefileSkipPoints: 2, // Skip every 2nd point
+},
+```
+
+# 4.3 – Tracking Node Settings
+
+Tracking nodes are GPS-based longitude/latitude filters used to monitor and manage geographic locations. They allow the system to match, filter, and process data based on specified coordinate positions.
+
+Each tracking node is defined by a longitude and latitude location, which is used to determine whether incoming geographic data falls within the configured tracking criteria. This enables location-based filtering and tracking of relevant points or areas. For more information, see [Creating & Configuring Tracking Nodes](TODO).
+
+
+```ts
+GlobalSettings: {
+	NodeTTL: 60 // Time-To-Live (Event Updating)
+	NodeMaxDistance: 125 // Miles (Radius)
+}
+```
+
+## 4.3.1 - NodeTTL
+
+**NodeTTL** defines how frequently events are updated against your configured tracking node filters.
+During each update cycle, the system evaluates:
+
+* Whether the event is inside the tracking node area.
+* The distance from the tracking node (in miles and kilometers).
+* The nearest point distance from the associated polygon boundary.
+
+## 4.3.2 - Max Distance
+
+**NodeMaxDistance**, defined in *miles*, specifies the maximum distance an event can be from a tracking node before it is filtered out. Events within this distance threshold will continue to be processed by the tracking node filters, while events beyond the configured distance will be ignored.
+
+## 4.3.3 - Tracking Node Properties
+```json
+{
+	"type": "Feature",
+	"geometry": {
+		"type": "Polygon",
+		"coordinates": [[]]
+	},
+	"properties": {
+		"metadata": {
+			"nodes": [
+				{
+					"id": "Tracking Node Test",
+					"coordinates": [[]],
+					"nearest": [0, 0],
+					"miles": 52.1,
+					"kilometers": 83.8,
+					"proximity": false
+				}
+			],
+			"filtered_proximity": false,
+			"updated": 000000000000
+		}
+	}
+}
+```
+
+# 4.4 - Advanced Event Filters
+Filtering is a critical component of `@atmosx/event-product-parser`, allowing your service to selectively process or ignore incoming data. Advanced event filters provide control over events, ICAO identifiers, [UGC (Universal Geographic Code)](https://www.weather.gov/media/documentation/docs/NWS_Geolocation.pdf) areas, states, and geographic locations.
+
+These settings allow you to define which data should be processed, as well as exclude unwanted events, locations, or test products.
+
+
+```ts
+GlobalSettings: {
+	EventFiltering: {
+		ListeningEvents: [],
+		ListeningICAO: [],
+		ListeningUGC: [],
+		ListeningStates: [],
+		IgnoredICAO: [],
+		IgnoredEvents: [],
+		NodeLocationFiltering: false,
+		IgnoreTestProducts: true,
+	}
+}
+```
+
+## 4.4.1 – Events & Wildcards
+
+Events can be filtered by using either the **wildcard** syntax or by providing the complete event name.
+
+Using wildcards allows you to match multiple related events without needing to define each event individually. For more precise filtering, the full event name can be provided to match only a specific event type.
+
+```ts
+GlobalSettings: {
+	EventFiltering: {
+		ListeningEvents: [
+			`*Tornado Warning*`, 
+			`Tornado Emergency`,
+			`*Thunderstorm Warning*`,
+			`Fire Weather Warning`
+		]
+	}
+}
+```
+In the configuration above, the `*` character is used as a wildcard to match any text before or after the specified value.
+
+* `*Tornado Warning*` matches any event containing **"Tornado Warning"** anywhere in the name.
+* `Tornado Emergency` matches only the exact name **"Tornado Emergency"**.
+* `*Thunderstorm Warning*` matches any event containing **"Thunderstorm Warning"** anywhere in the name.
+* `Fire Weather Warning` matches only the exact name **"Fire Weather Warning"**.
+
+Additionally, all events can be processed by setting **ListeningEvents** to an empty array (`[]`). This disables event name filtering and allows all available events to be accepted.
+
+
+
+## 4.4.2 - ICAOs
+## 4.4.3 - UGC
+## 4.4.4 - States
+## 4.4.5 - Ignoring Filters
+## 4.4.6 - Node Location Filtering
+## 4.4.7 - Test Products
+# 4.5 - Archive Configurations
+## 4.5.1 - TTL (Time-To-Live)
+## 4.5.2 - EAS Toneout

package/.github/docs/docs-integrations.md

@@ -0,0 +1,37 @@
+<div align="center">
+	<a href="https://atmosphericx.scriptkitty.cafe">
+		<img src="../logo.png" alt="@atmosx/event-product-parser" width="800"/>
+	</a>
+	<br>
+	<p>A TypeScript/JavaScript library for parsing and ingesting NOAA and NWS Weather Text Products</p>
+	<small>A project built and maintained with ❤️ by the AtmosphericX team</small>
+	<p align="center">
+		<a href="https://atmosphericx.scriptkitty.cafe"><b>Documentation</b></a> |
+		<a href="https://github.com/AtmosphericX"><b>Repositories</b></a> |
+		<a href="https://www.npmjs.com/search?q=%40atmosx"><b>NPM Packages</b></a> |
+		<a href="https://atmosphericx-discord.scriptkitty.cafe"><b>Community Discord</b></a>
+	</p>
+</div>
+<br><br>
+
+# 5.0 - Actions / Integrations 
+
+# 5.1 - Action Events & Wildcards
+
+# 5.2 - Discord Webhooks
+## 5.2.1 - Ratelimiting
+
+# 5.3 - NTFY Push Notifications
+## 5.3.1 - Server Configuration
+## 5.3.2 - Action Configuration
+
+# 5.4 - Broadcastify Feed Attachments
+## 5.4.1 - Tag Filtering
+
+# 5.5 - Mock EAS Generator
+## 5.5.1 - Linux Prerequisites
+## 5.5.2 - Limitations
+
+# 5.6 - Event Archiving
+## 5.6.1 - Raw Text Product Archiving
+## 5.6.2 - GeoJSON Archiving

package/.github/docs/docs-listeners.md

@@ -0,0 +1,28 @@
+<div align="center">
+	<a href="https://atmosphericx.scriptkitty.cafe">
+		<img src="../logo.png" alt="@atmosx/event-product-parser" width="800"/>
+	</a>
+	<br>
+	<p>A TypeScript/JavaScript library for parsing and ingesting NOAA and NWS Weather Text Products</p>
+	<small>A project built and maintained with ❤️ by the AtmosphericX team</small>
+	<p align="center">
+		<a href="https://atmosphericx.scriptkitty.cafe"><b>Documentation</b></a> |
+		<a href="https://github.com/AtmosphericX"><b>Repositories</b></a> |
+		<a href="https://www.npmjs.com/search?q=%40atmosx"><b>NPM Packages</b></a> |
+		<a href="https://atmosphericx-discord.scriptkitty.cafe"><b>Community Discord</b></a>
+	</p>
+</div>
+<br><br>
+
+# 6.0 - Listeners 
+# 6.1 - XMPP / NWS Status
+# 6.2 - Test Products
+# 6.3 - Expired Products
+# 6.4 - Specific Product Types
+# 6.5 - Filtered Products
+# 6.6 - Cache Updates
+# 6.7 - Tracking Node Updates
+# 6.8 - Storm Prediction Center Products
+# 6.9 - Debugging
+# 6.10 - Logs / Journal
+# 6.11 - Wildcard

package/.github/docs/docs-source-configuration.md

@@ -0,0 +1,218 @@
+<div align="center">
+	<a href="https://atmosphericx.scriptkitty.cafe">
+		<img src="../logo.png" alt="@atmosx/event-product-parser" width="800"/>
+	</a>
+	<br>
+	<p>A TypeScript/JavaScript library for parsing and ingesting NOAA and NWS Weather Text Products</p>
+	<small>A project built and maintained with ❤️ by the AtmosphericX team</small>
+	<p align="center">
+		<a href="https://atmosphericx.scriptkitty.cafe"><b>Documentation</b></a> |
+		<a href="https://github.com/AtmosphericX"><b>Repositories</b></a> |
+		<a href="https://www.npmjs.com/search?q=%40atmosx"><b>NPM Packages</b></a> |
+		<a href="https://atmosphericx-discord.scriptkitty.cafe"><b>Community Discord</b></a>
+	</p>
+</div>
+<br><br>
+
+
+# 3.0 - Source Configurations
+
+
+`@atmosx/event-product-parser` supports multiple source configurations that allow you to customize how weather data is ingested and processed. These configurations define the external services, connection methods, and parsing used by the parser to receive weather products. The available source configurations provide flexibility for different data ingestion requirements, allowing you to choose the appropriate source based on your application's needs while maintaining a consistent parsing experience.
+
+# 3.1 - NOAA Weather Wire Service
+[NOAA Weather Wire Service](https://www.weather.gov/nwws) is a real-time dissemination service that delivers official weather information, alerts, forecasts, products, and warnings in text format from NWS Weather Forecast Offices and National Centers.
+
+This service is designed for television and radio broadcasters, emergency managers, commercial alerting providers, private weather services, and other organizations that require rapid access to weather products.
+
+
+Each alert, forecast, and observation is delivered over [XMPP](https://xmpp.org/) using the standardized [WMO Header Format](#34---geojson--wmo-formatting). This provides a consistent structure for automated processing.
+
+Accessing the NOAA Weather Wire Service requires credentials, which can be obtained by sending an email to [NWWS.Issue@noaa.gov](mailto:NWWS.Issue@noaa.gov).
+
+When requesting access, provide the following information:
+
+* Name (First and Last)
+* Company
+* Address
+* State, City, and ZIP Code
+* Telephone Number
+* Account Information: Single or Multiple Accounts
+
+NWS processing of your request may take as long as 10 days or more depending on critical weather days and NWS priority requirements.
+
+
+# 3.2 - National Weather Service API
+The [National Weather Service](https://www.weather.gov/) provides a [RESTful API](https://www.weather.gov/documentation/services-web-api) for programmatically accessing weather data and products.
+
+Compared to the [NOAA Weather Wire Service](#31---noaa-weather-wire-service), the API introduces additional latency, with data typically delayed by 1 to 2 minutes on average. This delay is one of the primary tradeoffs when using the API instead of NOAA Weather Wire Service for real-time weather product ingestion.
+
+The NWS API is best suited for applications that require on demand access to weather data rather than the lowest possible latency delivery of operational weather products. All responses are provided in [GeoJSON](https://geojson.org/) format, making the data straightforward to parse and integrate into applications.
+
+
+# 3.3 - NOAA Weather Wire Service vs NWS RESTful API
+There are significant differences between these two sources. [NOAA Weather Wire Service](#31---noaa-weather-wire-service) requires authenticated access and is optimized for real-time product delivery, while the [NWS RESTful API](#32---national-weather-service-api) is publicly accessible and designed for on demand data retrieval.
+
+| Feature | NOAA Weather Wire Service | NWS RESTful API |
+| --- | --- | --- |
+| Authentication | ✅ | ❌ |
+| Real-time Delivery | ✅ | ❌ |
+| WMO Formatting | ✅ | ❌ |
+| Persistent Connection | ✅ | ❌ |
+| Low Latency Products | ✅ | ❌ |
+| Easy to Use | ❌ | ✅ |
+| Publicly Accessible | ❌ | ✅ |
+
+
+# 3.4 - GeoJSON & WMO Formatting
+
+`@atmosx/event-product-parser` supports two primary data formats when ingesting weather products. The [NOAA Weather Wire Service](#31---noaa-weather-wire-service) uses [WMO Format](#342---wmo-format), while the [National Weather Service API](#32---national-weather-service-api) uses [GeoJSON](#341---geojson).
+
+## 3.4.1 - GeoJSON
+[GeoJSON](https://geojson.org/) is a format for encoding a variety of geographic data structures. It is based on the JavaScript Object Notation (JSON) standard and is widely used for representing geographic features in web applications.
+
+You can view a real-world sample [here](/.github/samples/SAMPLE_GEOJSON.json).
+
+```json
+{
+	"type": "Feature",
+	"geometry": {
+		"type": "Polygon",
+		"coordinates": [[]]
+	},
+	"properties": {}
+}
+```
+
+## 3.4.2 - WMO Format
+**WMO Format** (World Meteorological Organization Format) is a standardized structure used for exchanging meteorological data, including observations, forecasts, and warnings. It provides a consistent format for weather products, allowing meteorological organizations and systems around the world to reliably share and process weather information.
+
+A real-world example of a WMO-formatted product can be found [here](/.github/samples/SAMPLE_TEXT_PRODUCT.txt).
+```text
+000
+WUUS51 KLOT 000000
+SVRGYX
+ILC001-ILC002-
+/O.NEW.XXXX.XX.X.0000.000000T0000Z-000000T0000Z/
+
+BULLETIN - IMMEDIATE BROADCAST REQUESTED
+
+Severe Thunderstorm Warning
+
+National Weather Service
+
+XXXX PM Timezone Weekday Month DD 2026
+
+TEST EXAMPLE - TEXT EXAMPLE - TEST EXAMPLE
+
+&&
+
+
+
+LAT...LON 4587 6965 4585 6968 4588 6971 4587 6972
+
+      4584 6970 4576 6972 4576 6976 4577 6978
+
+      4574 6981 4566 6974 4565 6970 4558 6971
+
+      4553 6978 4530 6970 4567 7054 4573 7038
+
+      4580 7042 4589 7026 4596 7026 4598 6968
+
+TIME...MOT...LOC 1650Z 313DEG 52KT 4600 7042
+```
+
+
+# 3.5 - Configuring NOAA Weather Wire Service
+
+Configuring `@atmosx/event-product-parser` to use the [NOAA Weather Wire Service](#31---noaa-weather-wire-service) requires setting up the necessary credentials and connection parameters to establish a persistent connection to the service. This can be configured through the **Manager** class within your application.
+
+* Keep in mind that settings configured within `NOAAWeatherWireServiceSettings` only apply to the [NOAA Weather Wire Service](#31---noaa-weather-wire-service) source and do not affect the [National Weather Service API](#32---national-weather-service-api) source.
+
+```ts
+import { Manager } from '@atmosx/event-product-parser';
+
+const client = new Manager({
+	EnableWireService: true, // Enable NOAA Weather Wire Service (NWWS)
+	NOAAWeatherWireServiceSettings: {
+		CredentialSettings: {
+			Username: `USERNAME`, // Case sensitive
+			Password: `PASSWORD`, // Case sensitive
+			Nickname: `NICKNAME`, // Visible to other connected users
+		},
+	},
+});
+```
+
+* Only **one** source can be enabled at a time. (*This project does not use fallback sources*)
+
+## 3.5.1 - Auto Reconnecting
+
+With [XMPP](https://xmpp.org/) connections, `@atmosx/event-product-parser` can automatically reconnect to the [NOAA Weather Wire Service](#31---noaa-weather-wire-service) if the connection is interrupted.
+
+This ensures your application can maintain a persistent connection and continue receiving weather products without requiring manual intervention after temporary network failures or service disruptions.
+
+* This configuration only applies to the [NOAA Weather Wire Service](#31---noaa-weather-wire-service) using [XMPP](https://xmpp.org/). The [National Weather Service API](#32---national-weather-service-api) source does not require auto reconnect configuration.
+
+```ts
+NOAAWeatherWireServiceSettings: {
+	ReconnectionSettings: {
+		Enabled: true, // Enable auto reconnect
+		ReconnectionInterval: 60, // Time since last stanza before reconnecting (seconds)
+	},
+},
+```
+
+## 3.5.2 - Stanza Caching
+
+Optionally, you can enable stanza caching to retain previously processed [XMPP](https://xmpp.org/) stanzas. This can help prevent data loss in the event that your application requires a fresh restart.
+
+* Keep in mind that increasing **MaxRetentionHistory** will increase the amount of time required for `@atmosx/event-product-parser` to initialize, as more cached stanzas must be loaded and processed during startup.
+
+```ts
+NOAAWeatherWireServiceSettings: {
+	CacheSettings: {
+		Enabled: true, // Enable stanza caching
+		MaxDatabaseHistory: 50000, // Maximum stanzas to store in the database
+		MaxRetentionHistory: 1200, // Maximum stanzas to load during startup
+	},
+},
+```
+
+## 3.5.3 - Stanza Processing Settings
+
+While processing stanzas, each one is categorized based on its contents and characteristics. This includes formats such as [CAP (Common Alerting Protocol) v1.2](https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html), [VTEC](https://www.weather.gov/vtec/), [UGC](https://www.weather.gov/gis/AWIPSShapefiles), and **Raw Text** products. By default, all product categories are enabled by default which includes: 
+
+* UGC Only Products
+* VTEC/HVTEC Only Products
+* Raw Text (No UGC/VTEC Present)
+
+Please keep in mind that the **Common Alerting Protocol** text products will always be skipped as they tend to be slower for ingestion and require extra steps which include parsing [XML](https://www.w3.org/TR/REC-xml/). There is **NO** longer support for this category.
+
+
+```ts
+NOAAWeatherWireServiceSettings: {
+	StanzaSettings: {
+		DisableUGC: false, // Disables all UGC Categories
+		DisableVTEC: false, // Disables all VTEC/HVTEC Categories
+		DisableText: false, // Disables all RawText Categories
+	}
+},
+```
+
+
+# 3.6 - Configuring National Weather Service API
+
+The [National Weather Service API](#32---national-weather-service-api) requires minimal configuration compared to the [NOAA Weather Wire Service](#31---noaa-weather-wire-service). While there are fewer available settings, the API source is designed to provide simple access to weather data through RESTful requests without requiring authentication or persistent connections.
+
+```ts
+import { Manager } from '@atmosx/event-product-parser';
+
+const client = new Manager({
+	EnableWireService: false, // Disable NOAA Weather Wire Service (NWWS)
+	NationalWeatherServiceSettings: {
+        CallbackInterval: 30, // How often it retrieves new products (Minimum: 15 seconds)
+        EventsEndpoint: `https://api.weather.gov/alerts/active`, // RESTful API
+    },
+});
+```

package/.github/docs/docs-technical.md

@@ -0,0 +1,50 @@
+<div align="center">
+	<a href="https://atmosphericx.scriptkitty.cafe">
+		<img src="../logo.png" alt="@atmosx/event-product-parser" width="800"/>
+	</a>
+	<br>
+	<p>A TypeScript/JavaScript library for parsing and ingesting NOAA and NWS Weather Text Products</p>
+	<small>A project built and maintained with ❤️ by the AtmosphericX team</small>
+	<p align="center">
+		<a href="https://atmosphericx.scriptkitty.cafe"><b>Documentation</b></a> |
+		<a href="https://github.com/AtmosphericX"><b>Repositories</b></a> |
+		<a href="https://www.npmjs.com/search?q=%40atmosx"><b>NPM Packages</b></a> |
+		<a href="https://atmosphericx-discord.scriptkitty.cafe"><b>Community Discord</b></a>
+	</p>
+</div>
+<br><br>
+
+# 8.0 - Technical Parser Documentation
+# 8.1 - Workflow & Pipeline
+# 8.2 - Core Parsing Logic
+## 8.2.1 - VTEC
+### 8.2.1.1 - Product Dictionary
+### 8.2.1.2 - Tracking
+### 8.2.1.3 - Event Dictionary
+### 8.2.1.4 - Status Dictionary
+### 8.2.1.5 - Organization Sender
+### 8.2.1.6 - Expiry Parsing
+### 8.2.1.7 - Watch Parsing
+### 8.2.1.8 - KWNS / SPC
+## 8.2.2 - UGC
+### 8.2.2.1 - Extracting Headers
+### 8.2.2.2 - Getting Zones
+### 8.2.2.3 - Extracting Expiry
+### 8.2.2.4 - UGC to Zones
+## 8.2.3 - HVTEC
+### 8.2.3.1 - Flood Severity
+### 8.2.3.2 - Flood Causes
+### 8.2.3.3 - Flood Records
+## 8.2.4 - Raw Text
+### 8.2.4.1 - Extracting Descriptions
+### 8.2.4.2 - Extracting Coordinates
+### 8.2.4.3 - Extracting String Specifics
+### 8.2.4.4 - Extracting XML
+## 8.2.5 - Building Properties
+## 8.2.6 - Building Geometry
+# 8.3 - Event Validation & Filtering
+## 8.3.1 - Enhanced Event Naming
+## 8.3.2 - Appending Attachments
+## 8.3.3 - Generation Hashes
+# 8.4 - Event & History Management
+# 8.5 - Action Workflow