Overview & behavior
A .PLCX file declares language version, entry, runtime, interface, pinned dependencies and denied capabilities.
Editing a contract cannot legitimately grant forbidden networking, OS files or external process execution.
Integration: The publish pipeline validates content, writes versioned assets and checks permissions server-side.
Validation checklist: confirm prerequisites, execute the smallest working example, test error handling, inspect expected output and preserve the last working release.
main.PL · editable sample
LIVE CONCEPT PREVIEW
OPERATIONS GUIDE
PLCX contracts
This command sample is intentionally not executed in your browser.
Browser demonstration only. Editing source changes preview labels; execution and security behavior require the real native PVM or AEGIS gateway.
Practical verification
- Use the actual native compiler, validator or gateway to confirm behavior.
- Check the installed version and execution contract before publishing.
- Review capabilities and failure states, including unsupported runtime operations.
- Save immutable versioned bundles only after checking the output.