OpenVMX AA–OVMX2–CS
CS

The compatibility surface

A catalogue of every VMS facility OpenVMX has taken on, item by item, on two axes: how far it is built (from absent, through stub and partial, to implemented and oracle-verified) and whether it does the real thing or only reports success. This is the shape of the gap, not a wall of green.

This is a self-reported map. Status and authenticity are the project's own assessment, catalogued in docs/compat/ and regenerated from that source on each release — not an independent audit. Facade-risk marks a surface that returns plausible success without doing the work, or fakes shared state per process; these are bugs the project actively hunts (invariant INV-6), and they are shown here on purpose. Source of truth: the register on GitHub.
1

Coverage shape

The whole surface at a glance. The bar is an ordinal ladder — worst to best, left to right — so the pale hatched band on the right is exactly the work not yet done.

Facade-risk

—

Surfaces that report success without doing the real work, or fake per-process copies of shared state. Tracked as a bug class (INV-6) and cross-referenced to the Draper faithfulness register. See the full index →

Showing 0 of 0 items
2

Facade-risk index

Every surface currently flagged facade-risk. Publishing them is the point: the map names its own soft spots. Each is a candidate bug: a routine that answers without doing the work, or per-process state pretending to be shared.