Pavis: A Dumb Proxy for Boring Reloads

This is a write-up of the core design constraint behind Pavis: the runtime is intentionally non-interpreting.

All semantic work (defaults, validation, binding, compilation) happens before deployment. The runtime only executes a fully materialized artifact.

The goal is to make reload, rollback, and recovery mechanically boring by removing runtime inference and learned state from the data plane.

Happy to answer questions or clarify design trade-offs.