89004c052c
Sixteenth PR of the alarms-over-gateway epic (docs/plans/alarms-over-gateway.md). Closes the documentation sweep the plan calls for. - docs/AlarmTracking.md — promoted top-level v2-final architecture doc (was a worktree-only draft pre-epic). Covers the three alarm sources (Galaxy MxAccess driver-native / Galaxy sub-attribute fallback / scripted alarms), how they converge on AlarmConditionService, the Acknowledge routing decision in DriverNodeManager (driver-native preferred over IWritable sub-attribute fallback), the sidecar historian write-back path for non-Galaxy producers, and cross-references to the plan + v1 archive. - docs/v1/AlarmTracking.md — banner pointing readers at the v2 doc; preserved as historical record. - docs/drivers/Galaxy.md — capability list updated to include IAlarmSource (now eight capabilities, restored by B.2). Replaced the "IAlarmSource retired in 7.2" sentence with the restoration note + cross-link to docs/AlarmTracking.md. - docs/plans/alarms-over-gateway.md — completion banner at the top of the plan, marking 14 of 16 PRs shipped 2026-04-30 and noting that A.2 + A.4 + D.1 are the hardware-gated follow-up. Memory entries updated separately: - project_alarms_over_gateway_epic.md (new) — epic summary + per-PR digest. - project_galaxy_via_mxgateway.md — added "Alarms restored" bullet pointing at the new architecture. - project_server_history_alarm_subsystems.md — bullet 2 updated to describe the new ack-routing decision (B.3) + bullet 3 added describing the historian write-back path that B.4 + C.1 + C.2 light up. - MEMORY.md index — new pointer entry. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
v1 documentation archive
This folder contains documentation that described the original v1
in-process MXAccess architecture (Galaxy.Host + Galaxy.Proxy +
Galaxy.Shared three-project split, .NET 4.8 x86 + COM apartment, the
OtOpcUaGalaxyHost Windows service). That architecture was retired in
PR 7.2 (merged 2026-04-30 at commit ae7106d). These docs are kept as
the historical record of how the system worked before the v2-mxgw
migration; treat their content as accurate at the time of writing, NOT
as current state.
For current architecture see:
CLAUDE.md— agent-facing v2 overviewdocs/drivers/Galaxy.md— current Galaxy driver docdocs/v2/Galaxy.ParityRig.md— current testing setupdocs/v2/Galaxy.Performance.md— observability + perf
| File | What it covered |
|---|---|
AlarmTracking.md |
v1 alarm-tracking flow through the in-process MXAccess client |
Configuration.md |
v1 server configuration (OTOPCUA_GALAXY_* env vars now live in mxaccessgw config) |
DataTypeMapping.md |
Galaxy mx_data_type → OPC UA type mapping (still accurate as a reference; the live mapping logic is in src/ZB.MOM.WW.OtOpcUa.Driver.Galaxy/Browse/DataTypeMap.cs) |
HistoricalDataAccess.md |
v1 IHistoryProvider on the Host side; current path is the server-level HistoryRouter + Wonderware sidecar |
Subscriptions.md |
v1 MXAccess subscription mechanics; current path uses gateway StreamEvents |
drivers/Galaxy-Repository.md |
v1 Host-side ZB SQL repository client; the gateway owns this path now |
drivers/Galaxy-Test-Fixture.md |
v1 test-fixture setup (parity tests + Galaxy.Host EXE spawn) |
reqs/GalaxyRepositoryReqs.md, reqs/MxAccessClientReqs.md |
Original Phase 0 requirements; satisfied in mxaccessgw repo today |
reqs/ServiceHostReqs.md |
Service-hosting requirements including OtOpcUaGalaxyHost (GHX-* section); only OtOpcUa server hosting remains in scope post-7.2 |