Onboarding, trust, and credentials.
Agent and client access can bind to trust state, credential envelopes, callback routes, and scoped tool permissions.
Supabase Runtime Deployment Pack v1
Deploy the OS tables that carry live runtime state.
The deployment pack gives Wever Labs one ordered Supabase path for onboarding, trust, credentials, quotes, provider routes, credits, Work Orders, execution bindings, result contracts, receipts, callbacks, ledgers, and attestations.
What gets deployed
Durable records for the operating loop.
The pack turns the rail map into Supabase tables that the Netlify functions can read and write during controlled pilot runs.
Quotes, provider routes, and credits.
Provider confirmations resolve into credit funding records, settlement receipts, and run eligibility.
Intake, Work Orders, and execution binding.
Accepted intake creates Work Orders, routing decisions, execution commands, and result events.
Results, receipts, callbacks, and proof.
Result contracts, usage receipts, callback delivery, ledger events, and attestations preserve the trail.
Deployment assets
One pack for Supabase activation.
Apply the combined migration, run the smoke tests, and use the manifest to keep environment variables, table order, and first-pilot assumptions visible.
Next activation step
Wire the functions to the deployed tables.
After deployment, Runtime Function Wiring should connect the existing Netlify function stubs to Supabase reads and writes for intake, dispatch, execution binding, provider activation, result persistence, and callback state.