The framework layer — a convenience bow over Phyxius primitives. Transports are opt-in peers, invariants are preserved, every call expressible in primitives underneath.

Basic building blocks for web applications

Validator-agnostic runtime type validation — the contract, not the implementation

EXPLORATORY (find-shape): the composition of state-machine legality, migration-style evidence, and the handler into one durable step.

Journal log export with pluggable sinks — stdout, OTLP HTTP, file

Database boundary — transaction-as-context, typed errors, driver-agnostic

The universal work-unit primitive — typed, supervised, decision-forcing

Scheduler adapter — time-driven handler invocations via pluggable Schedule values

Poor-man's APM — rolling percentiles, error rates, threshold alerts composed from Journal + Atom + Clock

Queue adapter — broker-agnostic consumer that invokes handlers per message

HTTP adapter — Node http.Server → handler invocations

Evidence-gated schema / infrastructure migrations — expand-and-contract as a typed value with wrong-until-proven-otherwise transitions

Third-party integration primitive — ConnectorSpec extends HandlerSpec, typed ConnectorError union, HTTP mapping helpers

Functional programming primitives for exception-free, composable code

Atom-backed circuit breaker — Clock-driven state machine for fail-fast on persistent failure

Retry policies as data — Clock-driven, Budget-aware execution

Pure AsyncLocalStorage primitive for typed thread-local data

Observability utilities for manipulating context data

Temporal utilities for controlling function execution timing

Pure named computation with shadow deployment — experimentation, versioning, and gradual rollout as a primitive