Available
A public interface or workflow exists, its boundary is documented, and the supported contract line is named.
Releases & Compatibility
Evidence before compatibility claims
PLEXA integrations move from planned to preview and available only with a named contract, documented limits, and repeatable verification.
Preview
Implementation evidence exists, but packaging, compatibility, or the public surface may still change.
Planned
The integration direction is useful context. It must not be interpreted as released functionality or a delivery date.
Publication gate
What every integration entry needs
Compatibility is maintained as release evidence, not as an unqualified technology list.
- A named PLEXA or HorstOS contract version.
- The tested third-party software version.
- A capability-level description of what works.
- Known limits, including missing control or hardware verification.
- A repeatable guide or automated compatibility check.