Permission comes from policy
Machine identities are scoped, expiring and revocable. Ownership, grants and leases are checked by the service. A model proposal cannot authorize access or expand those grants.
Authority you can inspect. Results you can check.
Permission, readiness, verification and acceptance are separate decisions. Their basis remains inspectable in operating state.
Connect your AIThe boundaries are
part of the environment.
These mechanisms support the current local implementation. They do not establish universal security, model correctness or production certification.
Work runs within a defined boundary
Registered code checks run in nonroot, read-only, network-disabled containers with no host mounts. The current executor is bounded to two source formats; it is not a general host execution interface.
Evidence belongs to a specific result
Artifact hashes, context versions and native checks bind proof to the candidate that was actually checked. New observations invalidate affected proof and acceptance.
Human visibility is separate from machine authority
A one-use code pairs a short-lived read-only browser view. Machine credentials stay with the calling AI. Pairing is not a grant to execute work.
Release retains the record
Cleanup withdraws temporary resources. Retained sources, artifacts and event history support inspection; release is not a data-erasure request or a shutdown of shared runtime services.
Private formation, with an explicit development limit.
This host uses pinned Qwen3 0.6B for private environment formation. It is an integration proof, with no silent model fallback or established production reasoning guarantee. The connected AI supplies its own candidate; OPERE does not attest that AI’s model identity.
What you can use today
Local private formation, registered coding and JSON report work, isolated native checks, HTTP and MCP access, source revisions, explicit caller acceptance and retained evidence.
Availability depends on a configured model service, isolated executor and running worker. General-domain formation, continuous sensing, physical actuation and distributed provisioning remain unavailable. Account authorization and resource-grant flows in the walkthrough are prototypes.
Read the operating boundaries