# Static Analysis of the Copied ATHENSA 7 Installation

**Source copy:** `Z:/AW Team/Manish/Telecasting/Software - Program Files`  
**Analysis mode:** read-only static inspection; no vendor executable, batch file, command file, or VBScript was run.  
**Purpose:** identify the exact build, bundled documentation, automation surfaces, operational risks, and what remains unknown before integrating Hermes with a production 24/7 channel.

## 1. Exact product builds

The executable version resources and bundled ReadMe files agree:

| Component | Copied executable | File version | Product identity | Bundled date |
|---|---|---:|---|---|
| ATHENSA List | `Athensa LLC/Athensa List/Athensa List.exe` | **7.0.0.1257** | ATHENSA List / product resource 4.3 | **2017-04-21** |
| ATHENSA Playout | `Athensa Playout/Athensa Playout.exe` | **7.0.0.1257** | Internal/original product: **AirBox / AirBox.exe** | **2017-04-21** |
| SafeBox | `Athensa LLC/SafeBox/SafeBox.exe` | **7.0.4.155** | SafeBox 7.0 | **2017-05-15** |
| ATHENSA Graphics | `Athensa Graphics/Athensa Graphics.exe` | **7.0.0.959** | Internal/original product: **TitleBox / TitleBox.exe** | **2017-02-02** |

All four main binaries are 32-bit x86 PE applications. The linker timestamps are consistent with the bundled dates: Graphics in February 2017, List/Playout in April 2017, and SafeBox in May 2017.

The copy therefore gives us the exact generation that matches the splash screen, not merely a similar public manual.

## 2. Copy inventory

| Component folder | Files | Approximate size | Important contents |
|---|---:|---:|---|
| ATHENSA List | 81 | 108.9 MB | List executable, AirBox help, Clip Trimmer help, output/check presets, graphics rules, network/event plug-ins, watchdog plug-ins |
| SafeBox | 7 | 7.8 MB | SafeBox executable, ReadMe, changelog, licensing components |
| ATHENSA Playout | 82 | 121.5 MB | Playout plus bundled List, AirBox help, output modules, watchdog/restart, network and router plug-ins |
| ATHENSA Graphics | 122 | 134.1 MB | Graphics/TitleBox, TitleBox help, examples/templates, As-Run logger, data/network components, watchdog |

Machine-readable inventory: `inventory.json`.

## 3. Duplicate List installation

`Athensa LLC/Athensa List/Athensa List.exe` and `Athensa Playout/Athensa List.exe` have the same SHA-256:

```text
c2ca11c60b1b4e791bb6440ff301ae63a5a5cb9b29e49111d5ecb31cec716c3d
```

Their `ABhelp.chm` and `GraphRules.dat` files are also byte-identical. This confirms that the Playout package bundles the same List build rather than a separate incompatible editor.

## 4. Local help recovered

The installed CHM help files were copied locally and decompiled without launching ATHENSA software:

```text
C:/Users/Awakening_PC2/Documents/Athensa-Hermes-Research/local-help/
  AirBox/
  TitleBox/
  ClipTrimmer/
```

These local HTML topics are now searchable and are more useful than the older public PDFs for build-specific research.

## 5. ATHENSA List findings

### Exact feature additions

`Athensa LLC/Athensa List/Documents/WhatsNew.rtf` identifies:

- 4K content support
- HEVC/H.265 support
- AJA Corvid 11/22/44/88 support

### Important co-residency warning

The same file says that when List and Playout run simultaneously on the same server, playlist playback should not be initiated inside List, except on specified Stradis, Sigma, IP, or ASI Pump servers.

**Hermes rule:** treat List as an offline preparation/validation application. Do not use its preview/playback controls on the live playout host unless that exact hardware configuration has been approved and tested.

### Playlist integration

The installed AirBox help confirms:

- Third-party software can create compatible playlists.
- The exact native playlist format is documented in a separately supplied **AirBox SDK**.
- Tab-delimited and comma-separated text schedules can be imported.
- Fixed-width text imports are also supported.
- Import templates map source columns to playlist fields.
- Imports can be saved as daily playlists.
- Daily playlist names use `YYYY_MM_DD_HH_MM_SS.ply`.

No sample `.ply` files and no AirBox SDK were present in the copied program folders.

**Hermes first-stage path:** generate a validated delimited traffic schedule and import it through a known-good ListBox mapping. Do not directly synthesize native `.ply` files until the SDK or verified samples are available.

## 6. ATHENSA Playout findings

### Exact build capabilities

`Athensa Playout/Documents/WhatsNew.rtf` identifies:

- H.265 support
- Collapsible playlist blocks
- UHD 4K output with AJA and DeckLink boards
- UHD 4K content support
- RTMP streaming output
- Multiple-instance virtual output
- Long-term reliability improvements

The package also includes ATHENSA List, Trimmer Server, and ATHENSA Doctor.

### Built-in watchdog and restart

The installed `WatchDog Plug-in` help documents three responses to a detected application malfunction:

1. Display a warning dialog.
2. Switch a supported bypass-relay card.
3. Restart AirBox/ATHENSA Playout.

The copied package contains:

```text
WatchDog/WatchDogDlgPlug.dll
WatchDog/WatchDogRelayPlugin.dll
WatchDog/WatchDogRestartPlug.dll
RestartModule.exe
WatchDogCommon.dll
```

This is a real deterministic recovery mechanism and should remain the first response for a local Playout hang. Hermes should supervise and verify it rather than race it with a second restart action.

### Startup and schedule recovery

The local help confirms:

- launch on Windows startup with a configurable hardware-initialization delay;
- load the last playlist and optionally resume playback;
- resume the previous state, item, and intra-clip position for regular playlists;
- catch up with system time after a failure;
- daily-playlist mode calculates the schedule position using playlist start time and current system time;
- automatically reload changed playlists according to configured rules.

### Logs

Playout generates:

- mandatory daily System logs containing errors/events;
- optional As-Run logs;
- per-playlist or daily As-Run files;
- configurable fields and time formats;
- tab-delimited text output.

These logs are the safest status interface for Hermes. Monitoring them is preferable to continuously scraping the UI.

### Included machine-readable defaults

`pblive.xml` describes supported source-address syntax such as:

```text
FILE://%path%
UDP://%address%:%port%
LIVE://%preset%//
```

It includes a default UDP address of `127.0.0.1`, default port `1234`, optional Program ID, and source field. These are schema defaults, not proof of the production machine's configured values.

`PlayoutPresets.xml` describes media-validation presets and criteria including video type, FPS, audio sample rate, picture size, bitrate, and minimum duration. This can guide a Hermes preflight validator.

### Playout operational risks from the bundled notes

- High-speed copying during playout may cause storage-performance hiccups; SafeBox is recommended for playout-safe replication.
- Stream count/encoding combinations are CPU-dependent.
- MPO dual-monitor mode is unsupported.
- Disabling/re-enabling the network adapter stops outgoing streaming.
- Supported live UDP streams listed for this build are MPEG-2 and H.264.
- Supported ANC data is limited to AFD and closed captions.

## 7. SafeBox findings

SafeBox is **7.0.4 build 155**, newer than the List/Playout build date.

The bundled changelog confirms `.mtd` metadata support and corrected log/live-path behavior.

### Critical production limitations

`SafeBox/Documents/WhatsNew.rtf` states:

1. An unavailable source location slows all other content operations periodically.
2. SafeBox startup is resource-intensive and may disturb playout if both share a workstation.
3. If every file in a destination folder is marked for deletion, the destination folder itself is deleted.
4. **Mapped HDDs must not be used as source folders.**

**Hermes rules:**

- Do not configure a production SafeBox source as a mapped drive letter such as `Z:`. Use the vendor-supported local or UNC arrangement after validation.
- The provided `Z:` folder remains research-only.
- Never allow Hermes to generate deletion rules without dry-run output, scope checks, and explicit approval.
- Do not restart SafeBox during sensitive playout windows on a shared host.
- Monitor source reachability before allowing large transfer queues.

The copied SafeBox folder contains no runtime rule database or operational configuration, so its actual production jobs, source/destination paths, retry intervals, and logs are not represented in this copy.

## 8. ATHENSA Graphics findings

### Exact build and capabilities

Graphics is TitleBox internally, version **7.0.0.959**, dated 2017-02-02 and explicitly documented for Windows 7. Build 959 adds AJA Corvid support.

The folder includes nine `.tbd` example projects and 76 TGA assets, plus `TB_help.chm`, `TBRunLog.exe`, Net Control installer, downloader/text utilities, and graphics/render plug-ins.

### Network control

The installed help confirms:

- `TitleBox Channel ID` must match the corresponding AirBox configuration.
- `NetControl Port` receives commands from third-party applications, including AirBox.
- `Alarm&Control Port` communicates with applications such as AlarmBox or TitleBox Text Client.

The program-folder copy does not include the production registry/settings values, so the actual channel ID and ports remain unknown.

### API events

TitleBox API supports:

```text
EVENT xxx
```

where `xxx >= 1001`. An API event can be assigned to a TitleBox task; receiving the command executes that task.

The complete TitleBox API manual is not present, but the installed help confirms the mechanism.

### Script and external integration surfaces

TitleBox supports:

- Program Script Tasks using Pascal, C++, Visual Basic, or Java-like syntax;
- API-triggered tasks;
- Windows Named Events for synchronizing third-party applications;
- Windows Tasks that can launch `.exe`, `.bat`, or `.cmd` files with parameters;
- ODBC, XML, RSS, HTML, weather, and FileLink data providers;
- template/object control;
- As-Run logging per TitleBox instance.

**Hermes preference:** avoid making TitleBox launch Hermes or arbitrary scripts. Prefer one-way data files, a narrow authenticated bridge, or documented Net Control/API events. This keeps rendering-time software isolated from the reasoning layer.

### Graphics watchdog and known freeze evidence

The TitleBox watchdog can switch a bypass relay after a crash in pass-through mode.

A copied `bugreport.txt` records an actual 2020 incident where `Athensa Graphics.exe` was considered frozen after approximately three hours of uptime. This does not establish the root cause, but it proves that graphics freeze detection and recovery must be part of the channel design.

Bundled limitations also include:

- minimizing TitleBox while using Flash can freeze Flash objects;
- DirectXMedia/sound output uses the default audio device;
- possible DirectXMedia lip-sync issues;
- storage affects animation-from-file performance;
- large animations should use file-backed animation objects;
- UHD projects support only a limited number of static objects in this build.

## 9. Recommended Hermes architecture

### Control plane

Hermes handles:

- content inventory and metadata;
- schedule planning;
- playlist preflight and staging;
- transfer requests;
- log reconciliation;
- process/port/log-health supervision;
- alerts and operator reports;
- escalation decisions.

### Deterministic media plane

ATHENSA handles:

- frame-accurate playout;
- fixed-time scheduling;
- gap handling and recovery position;
- watchdog restart/bypass;
- graphics rendering;
- media replication rules;
- As-Run and System logs.

### Safe integration order

1. **Read-only monitoring:** processes, ports, disk, System logs, As-Run logs.
2. **Schedule generation:** delimited staging file plus independent preflight report.
3. **ListBox-assisted import:** tested mapping and operator-reviewed playlist.
4. **Atomic promotion:** move only a verified daily playlist into the watched folder.
5. **SafeBox integration:** submit or prepare transfer jobs with no deletion capability initially.
6. **Graphics data:** update approved FileLink/XML/ODBC data sources.
7. **Net Control/API:** only after exact ports, protocol, command set, authentication boundary, and rollback have been tested off-air.
8. **Recovery automation:** coordinate ATHENSA watchdog, Windows service/startup behavior, and Hermes escalation so only one component owns each recovery action.

## 10. What the copied folders do not contain

The copy is excellent for binaries, bundled defaults, help, and examples, but it is not a capture of the installed machine's runtime state. Missing items include:

- native AirBox SDK;
- complete TitleBox API manual;
- sample production `.ply` playlists;
- live ListBox import mappings;
- actual AirBox/TitleBox ports and channel IDs;
- SafeBox operational rules and queue database;
- production System and As-Run logs;
- Windows registry settings;
- startup shortcuts/tasks/services;
- WIBU driver/license runtime state;
- output-card and driver configuration.

The next live-machine phase should collect these read-only before any automation is enabled.

## 11. Artifacts created during research

```text
C:/Users/Awakening_PC2/Documents/Athensa-Hermes-Research/
  README.md
  LOCAL_COPY_ANALYSIS.md
  inventory.json
  static-string-findings.json
  manuals/
  local-help/
```

`local-help/` contains searchable, decompiled copies of the three bundled CHM help systems. It also contains three flattened UTF-8 research corpora:

```text
AirBox_searchable.txt       (206 help topics)
TitleBox_searchable.txt     (183 help topics)
ClipTrimmer_searchable.txt  (16 help topics)
```

The original research copy under `Z:` was not modified.