fractalHTTP/RPC/IPC API library with composition via combinators

The API is inert data. Transports, validation, and types are opt-in layers composed onto the core.

Inert-data API tree

Endpoints are plain data composed from a small set of primitives — not registered procedures. The structure is traversable and reflectable.

HTTP server, typed client, OpenAPI schema, and test runner all walk the same tree. Define once, derive all surfaces.

Transports, validation, and auth are opt-in combinators. The core mandates nothing — features advertise capabilities and interpreters filter by them.