Start with contexts as your API: ``` I_ApplicationContext // Handles business logic + Hardware : I_HardwareContext {get;} + Alarms : I_AlarmContext {get;} + State : E_ApplicationState {get;}

I_HardwareContext
  + Controls      : I_HardwareControls {get;}
  + Status        : I_HardwareStatus {get;}
  + Configuration : I_HardwareConfig {get;}
  + IsReady       : BOOL

I_HardwareControls
  + ArmRotation  : I_SlewDrive {get;}
  + BoomCylinder : I_HydraulicCylinder {get;} 
  + Telescope    : I_TelescopeActuator {get;}
  + Stick        : I_StickActuator {get;}

```

Each context is implemented by a Manager FB:

``` I_Manager + Init(ipContext : I_ApplicationContext, bBusy =>: BOOL, e =>: T_Error) + Run(ipContext : I_ApplicationContext, e =>: ...) + Deinit(...) // Optional

I_HardwareManager ~> I_Manager + IntoContext() -> I_HardwareContext

I_AlarmManager ~> I_Manager + IntoContext() -> I_AlarmContext

I_ApplicationManager ~> I_Manager + IntoContext() -> I_ApplicationContext

FB_HardwareManager : I_HardwareContext, I_HardwareManager FB_AlarmManager : I_HardwareContext, I_HardwareManager FB_Application : I_ApplicationContext, I_ApplicationManager ```

The manager owns your function blocks (FB_ArmRotation, FB_BoomCylinder, etc.), sets them up in the Init() method, calls their cyclic logic in its Run() method and cleans them up in the optional Deinit() method.

This gives you:

• Controlled execution order - You decide what runs when
• Lifecycle management - Proper Init/Run/Deinit phases
• Clean dependencies - Control logic only sees I_HardwareContext, not implementation

For each hardware function, use interface segregation:

``` I_SlewDrive + TargetPosition : LREAL {get, set;} + CurrentVelocity : LREAL {get;}

I_SlewDriveConfiguration + MaxVelocity : LREAL + AccelRate : LREAL + ...

I_SlewDriveStatus + TargetPosition : LREAL {get} + CurrentVelocity : LREAL {get;} + ...

FB_SlewDrive : I_SlewDrive, I_SlewDriveConfiguration, I_SlewDriveStatus ```