API Status and Evidence
Hexis separates existence from confidence:
| Label | Evidence | Guidance |
|---|---|---|
| Supported | Bound in Java and used by an official script | Preferred for normal scripts |
| Advanced | Bound and intentionally public, but low-level or sharp-edged | Use with narrow testing |
| Experimental | Bound, but not found in current official scripts | Expect contract changes |
| Internal | Debug, maintenance, or security-sensitive surface | Excluded from public artifacts |
The public reference is a source snapshot. It does not claim that every option, server state, timeout, or error path has completed live acceptance testing.
Compatibility
Each page names the module source version and commit used to generate it. If your Hexis build differs, prefer calls already used by its bundled official scripts and validate unfamiliar behavior in a controlled context.
Why internal members are absent
The reference documents the supported scripting product, not every maintenance hook present in the implementation. A member that should never be user-facing must ultimately be removed or gated in the runtime; documentation is not a security boundary.