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

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

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

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

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

HTTP adapter — Node http.Server → handler invocations

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

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

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

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

Functional programming primitives for exception-free, composable code

Pure AsyncLocalStorage primitive for typed thread-local data

Observability utilities for manipulating context data

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

Type-safe configuration management with hot reloading, multiple sources, and observability

Temporal utilities for controlling function execution timing

Acquire/release with guaranteed cleanup — composable resource bracketing