Runtime Function Wiring v1

Functions write the operating trail into the runtime.

Runtime Function Wiring connects selected Netlify functions to Supabase records so intake, Work Orders, execution bindings, provider confirmations, pilot state, result contracts, receipts, callbacks, ledger entries, and attestations can move through one OS path.

Open wiring status Wiring manifest Schema

Runtime path

intake
  └─ work_order_dispatch
      └─ execution_binding
          └─ provider_activation
              └─ result_persistence
                  └─ callback_delivery
                      └─ retry_binding

What this binds

Public contracts connect to persistent OS records.

The wiring layer gives each function a shared Supabase helper, consistent response envelopes, and durable write targets for the operating trail.

Intake

Client and agent intake

Intake requests can persist as runtime records and move toward Work Order creation.

Dispatch

Work Order dispatch

Accepted requests bind to Work Orders, routing decisions, queue state, and return contracts.

Execution

Tool command binding

Work Orders bind to TokenOps, FinanceOps, or EnergyOps execution commands and result events.

Provider

Credit funding

Provider confirmations create activation bindings, credit funding events, and settlement receipt records.

Function surfaces

One helper. Multiple operating rails.

Each function can run with the same Supabase service-role environment and return the same pattern: request accepted, record written, next OS link returned.