Skip to main content

Phase 4: Controllers and Synchronization

Status:Planned
Tags:Hls4mlControllerGlobal Throttle
Last modified:

Goal

Add global throttling as a scalar synchronization mechanism over raw update proposals, with optional ฮบ safety bounds represented as constraints rather than per-layer direction changes.

Linked Tasksโ€‹

Controller Orderโ€‹

Implement controllers in this order:

CTRL-NONE
CTRL-GT-ORDER-0
CTRL-GT-ORDER-1
CTRL-GT-ORDER-2
CTRL-GT-ORDER-2-QA

CTRL-NONE is a required debugging path, not an optional feature.

ฮบ Couplingโ€‹

ฮบ budgeting should be represented as a safety envelope when enabled. Global throttling remains the direction-preserving learning-speed controller.

The combined scalar should have the shape:

alpha = min(alpha_curvature, alpha_kappa)

where alpha_kappa is the largest scalar that keeps the proposed global update inside the ฮบ-safe set. This preserves the raw update direction instead of applying unrelated per-layer scaling.

Synchronization Pointโ€‹

The simple reference implementation should use a two-phase schedule:

1. forward + loss + backpass
2. compute raw updates and global metrics
3. compute alpha
4. apply alpha-scaled updates

The delayed-alpha schedule can be tested later against this baseline. It may be useful, but it should not define the first correctness path.

Exit Criteriaโ€‹

Phase 4 is done when the one-Dense CSIM can report loss, gradient metrics, alpha, and updated weights for CTRL-NONE and CTRL-GT-ORDER-0.