diff --git a/chapters/1045479741.json b/chapters/1045479741.json
new file mode 100644
index 0000000..5f7ef69
--- /dev/null
+++ b/chapters/1045479741.json
@@ -0,0 +1,87 @@
+[
+  {
+    "timestamp": "0:02",
+    "title": "Opening and webinar logistics",
+    "summary": "Recording will be sent post-session. Questions may be asked in chat or unmuted during the call."
+  },
+  {
+    "timestamp": "0:59",
+    "title": "Axway Summits 2025 announcements",
+    "summary": "North America summit in Austin March 25-26, Barcelona June. Peer-to-peer networking program available for customer connections in shared time zones."
+  },
+  {
+    "timestamp": "2:18",
+    "title": "Customer-hosted user group sessions",
+    "summary": "On-site sessions available at customer locations (9am-4pm format). Axway provides continental breakfast and lunch; customers provide meeting room only."
+  },
+  {
+    "timestamp": "6:07",
+    "title": "OS migration from RHEL8 to RHEL9",
+    "summary": "Tarballing and moving ST servers across OS versions is not officially supported despite potentially working technically. Unsupported approaches risk hidden issues downstream during future updates. Recommends disaster recovery model with separate database for testing new cluster, then switching to live database to minimize downtime."
+  },
+  {
+    "timestamp": "10:41",
+    "title": "Backup and installer requirements",
+    "summary": "Installer folder must be backed up separately as it is required for updates. For edges, reinstalling new ones with certificates is faster than recovering backups when recovery takes >15 minutes."
+  },
+  {
+    "timestamp": "11:33",
+    "title": "Disaster recovery mechanism implementation",
+    "summary": "DR uses same-server backups only. New cluster configured on separate database, then repoints to live database. Requires replacing server IDs to match originals. Log files must be moved manually if desired."
+  },
+  {
+    "timestamp": "16:01",
+    "title": "IP address changes during migration",
+    "summary": "Reusing same IPs simplifies configuration. New IPs require reconfiguring edge allowed-servers list for SOCKS proxy enablement. PostGres database (Sept 2024+) stores edge IP in configuration, unlike MySQL. Update IP in zones before edges go live."
+  },
+  {
+    "timestamp": "18:44",
+    "title": "Disaster recovery model and orchestration",
+    "summary": "DR model with override files simplifies IP updates at startup. Zones updated via API or after admin startup. New Docker documentation rewrites clarify disaster recovery process. Same guidance applies to pre-September versions."
+  },
+  {
+    "timestamp": "24:20",
+    "title": "Archive and resubmit configuration basics",
+    "summary": "Send-to-partner step defaults cannot be changed individually. Retry defaults (5x in ~1 min) require manual adjustment. Template routes solve default inconsistency across multiple routes by centralizing configuration."
+  },
+  {
+    "timestamp": "28:18",
+    "title": "Archive folder storage strategy",
+    "summary": "Archive folder must not be on home folder drive. Separate drive prevents simultaneous write IO overload during file receipt and archival. Even low-performance storage acceptable due to single write, read-on-resubmit pattern."
+  },
+  {
+    "timestamp": "30:47",
+    "title": "Delete-on-success vs archive retention policy",
+    "summary": "Delete-files-older-than parameter applies to archive folder only. Archive maintenance application uses nightly scheduler. File maintenance application separately manages subscription folder cleanup by date, independent of failure reason."
+  },
+  {
+    "timestamp": "36:36",
+    "title": "Archive folder structure and file naming",
+    "summary": "Archive creates subdirectories by account, login, then folder hierarchy. Files renamed to prevent collision of same filename. Tracking table entry provides archive file path for resubmit; falls back to subscription folder if archive missing."
+  },
+  {
+    "timestamp": "41:10",
+    "title": "Rotate-folder for high-volume archive",
+    "summary": "Rotate creates daily/hourly timestamp subfolders to prevent thousands of files in single directory. Manages filesystem performance at scale. ST auto-intelligently uses when needed; safe to always enable."
+  },
+  {
+    "timestamp": "45:06",
+    "title": "Configuration hierarchy for archiving",
+    "summary": "Setting precedence: account > business unit > global for archiving parameters. Allows granular control while inheriting sensible defaults."
+  },
+  {
+    "timestamp": "47:41",
+    "title": "Domain-model API organization",
+    "summary": "ST does not organize by domain; API manager or gateway in front of ST handles domain grouping if needed. ST remains application-level cluster agnostic."
+  },
+  {
+    "timestamp": "49:28",
+    "title": "Standard cluster scaling with new database",
+    "summary": "Three nodes maximum officially supported for standard cluster; third node has performance considerations. New database moves all load to primary database rather than distributed dispatch, worsening bottleneck risk if cluster overloaded."
+  },
+  {
+    "timestamp": "51:51",
+    "title": "Enterprise cluster resource separation",
+    "summary": "Enterprise cluster splits database separately, enabling scaling. Combining application and database on same node in standard cluster creates resource contention and failure risk under high load."
+  }
+]