ORCEST DESIGN-PARTNER PROGRAM

Hosted access is not open yet.

The public OCB specification and the local OPR engineering candidate are available now. Hosted control-plane onboarding remains approval-gated, and no public API registration endpoint or issued API key is represented by this page.

1. Prepare a design-partner brief

This local form is a planning aid only. It does not submit data or request an API key.

2. What is usable today

OPR runs locally on Windows x64 through its CLI, stable C ABI, .NET SDK, or loopback sidecar. The public release page provides the package hash, browser-local verifier, 25-gate status, and known limitations.

orcctx.exe repository-context --repository . \ --outcome "map the affected code and tests" orcctx.exe --store .opr resolve-policy \ --tenant acme --project continuity \ --capability export_secret

The package is an unsigned engineering candidate, not a production service.

3. Organization data model

Organizations keep the right to control retention, residency, and model routing. ORCEST uses OCB to ensure no hidden policy drift between model swaps.

4. Gates before hosted access

  • Production identity and tenant isolation evidence
  • TLS, durable idempotency, quotas, and abuse controls
  • Backup, restore, canary, and rollback acceptance
  • An active request endpoint with an explicit privacy notice