Operator modules

Source: shared/api-core/src/lib/zeqOperatorModules.ts.

Beyond the closed-form solvers, each operator can also carry its own time-driven formula as a module. This is the surface that lets an operator be evaluated as a function of the Zeqond clock rather than only as a static closed form.

The shape

Each module exposes:

calculate(current_utp, phase, phase_radians, time_seconds) → { OP_ID: numericValue, ... }

OperatorBundle aggregates the modules into one map plus a weighted-sum helper. Modules run over a UTPContext (the shared physical/kernel constants — k_B, temperature, ħ, c, G, …), with DEFAULT_UTP_CONTEXT as the standard set.

Core families

CORE_FAMILIES / CORE_42_PREFIXES define the 42-operator kinematic bootstrap set; isCoreFamilyOperator(id) and isCore42Operator(id) classify an operator against it.

Opt-in only

The module path is engaged only when SolverInput.useOperatorModules === true. The default compute path — the dedicated closed-form solvers and the ODE master-equation fallback — is completely unaffected. Operator modules are an additive surface for time-resolved operator evaluation, not a replacement for the solvers.