Capabilities and limits
This page is the availability owner. Guides contain only supported recipes.
| Label | Meaning |
|---|---|
| v1 | Supported customer behavior. |
| Release-gated v1 | Accepted v1 behavior whose final release artifact or rollout is not yet available. Do not assume it is live. |
| Preview | Controlled availability with a different support or trust boundary. |
| Internal | Platform/compatibility behavior or a typed field not enabled for customers. |
| Not v1 | Deliberately outside the launch product. |
Account, Marketplace, and release
| Capability | Availability |
|---|---|
| GitHub sign-in; browser-confirmed CLI login | v1 for an existing account. Creating a new account is invitation-only: signing in with an identity that has no Liskov account does not create one, and returns an invitation-only notice instead. Request an invitation through the wait-list form; an invitation arrives by email as a single-use link that expires in 14 days. Existing accounts, sessions, and CLI logins are unaffected |
| Organizations, persistent and request-scoped CLI selection, team invitations, assignable roles | v1; the plan seat allowance is enforced at invite time with no overage, and while paid plan activation is release-gated every organization resolves to the Free allowance of one seat. New non-personal organizations require a two-letter business-establishment country and the versioned, non-pre-ticked business-purpose/18+/authority statement. Personal, family, and household use is not supported |
| Service Credit balance, reservation, and ledger reads | v1; read-only surfaces are supported for an existing organization (Console Account, Billing & funding, Ledger, the Application execution detail's 30-day charge window, and the Applications list's Spend 30d and retired archive's Lifetime spend; CLI billing/transaction reads) |
| Plan catalog and plans page | v1 read of the catalog on /organizations/new/plan; paid attach, trial start, and production collection remain release-gated |
| Plan selection and terms acceptance | Release-gated v1; the commercial go-live decision is not complete. Writing a plan id does not activate a paid plan |
| Stripe USD checkout and Service Credit issuance | Release-gated v1; checkout is disabled for customer use and internal acceptance must not be treated as availability. The prepared admission control can pause new purchases while preserving signed completion of earlier paid purchases. The prepared contract uses automatic tax and billing/tax-ID collection, creates a Stripe invoice/receipt, and mints only the pre-tax Service Credit face value |
| Paid subscription activation | Release-gated; a written plan id does not activate a paid plan. Usable only after reconciled Autumn/Stripe payment. Production paid billing is not enabled; recovery of an existing payment action is available only in an enabled billing environment |
| Curated first-party Marketplace launch | Release-gated v1; limited to internal first-party engineering acceptance |
| Uptime Prober | Release-gated v1; an internal first-party acceptance fixture, not a supported customer offering |
| OpenClaw offering | Release-gated v1; no versioned descriptor was present at the reviewed release |
| Third-party Marketplace publishing/payouts | Not v1 |
| Manifest V4 publication | Closed: a V4 manifest cannot be published; existing V4 Applications keep running until they are retired. Author retained Manifest V5. |
| Manifest V4 draft import | Closed: new V4 imports are refused with v4_publication_disabled. Create an Application and bind retained Manifest V5 source instead. |
| Retained Manifest V5 / Policy V5 exact pair | v1; exact RC sha256:549272988045e9357c4945850706569ed8dc7f0c6f419b7cf5c57d54b294bb10, with one or two jobs and the retained source/runtime/schedule/spend/configuration/logging surface |
| Local V5 manifest drafting with the liskov-policy skill | v1 authoring aid at skill release 1.0.0 (git tag v1.0.0). It writes a local proof.liskov.application-manifest version 5 file and runs proof liskov application manifest validate. It does not publish, deploy, reserve, or charge. Manifest V4 and schema version 6 are outside the skill. |
| Retained V5 GitHub source import | v1; repository, allowed refs, workflow identity, and manifest path are bound to the Application by an organization admin before publication, and every build attests them; liskov-github-actions v1.2.4 contains the exact-bound import (aa1b83f) |
| Reusable GitHub build/pin/OIDC workflow | v1; moving v2 tag from v2.0.0, at v2.2.0 since 11 October 2026 with acurast-app.yml unchanged from v2.1.0; the v1 contract was verified at v1.3.2 |
| Pinned first-party IPFS bundle | v1 |
| Encrypted JavaScript payload delivery | Release-gated v1; production execution is verified with Actions v1.3.2 and SDK 0.3.30. General availability still requires the registered V5 source-publication release |
| Private customer code inside Cargo images | Not v1; private source access, TEE execution and encrypted JavaScript do not establish job-authorized Cargo cache reuse |
| General customer-authored Cargo/runtime image | Internal; from liskov-github-actions v2.2.0 the @v2 runtime-image workflows take a retained V5 source document instead of importing a Manifest V4, but no @v2 runtime-image run has been observed in production and the path is not a customer capability. See the released contract |
Runtime, placement, and lifecycle
| Capability | Availability / limit |
|---|---|
Node.js background bundle and runtime SDK 0.3.38 | v1 |
Job runtime context — runtime.context from bootstrap and POST /api/jobs/runtime-context | Release-gated v1; SDK v0.3.38; public availability waits for the diagnostic readback (BKLG-20260714-9xxm) |
| Managed variables and managed secrets | v1. SDK-enabled V5 JavaScript can fetch declared public variables through signed runtime-env when Acurast delivery is late; raw bundles still use Acurast. V5 customer-secret installation uses runtime-contact 0.10.40 or SDK 0.3.32; existing artifacts must be rebuilt. |
Managed Application logging through Console and proof liskov application logs, including live follow and full-history pagination through the CLI; signed diagnostics | v1 |
| Outbound networking and declared quota | v1 |
| Liskov-hosted HTTP/SSH ingress | Not v1 |
| Runtime SSH into your own running job, Liskov-operated relay | Preview on Developer and above; Liskov operates the relay and cannot read the session. The relay is a single machine: if it is lost, open sessions drop until it returns and you reconnect; your jobs are unaffected. If the processor relaunches the job's sandbox, managed SSH reconnects on its own, usually within a minute, under a new host key that CLI 0.16.0 and later ask you to confirm. A helper that stops cleanly, or an SSH sidecar that keeps failing, still ends managed SSH for that job until the next run; the job itself is unaffected. Relay traffic counts against your plan's included log volume and is charged at the log overage rate above it. A key's access can be withdrawn at once without republishing; a session already open drains rather than being cut |
| Retained V5 managed Runtime SSH policy path | Preview on Developer and above; native-image-only access.ssh.provider.kind: liskov_managed, with organization operator keys snapshotted into each exact-job attachment (register at least one key before the Application's first launch); the relay's single-machine blast radius, the sandbox-relaunch reconnect, the helper/sidecar blast radius and metered relay traffic apply as on the row above |
| Runtime SSH into your own running job, your own Tailscale network | Preview on Pro and above; listed as Roadmap in Integrations until a live policy version can name it; requires a Tailscale account you own |
| Native direct IPv6 peer discovery on retained V5 jobs | Internal, release-gated pilot; liskov.discovery.v2 has a released immutable native helper 0.12.0, runtime image/payload and serving producer for the internal Planetarium pilot on schemaVersion 5. Live two-peer acceptance and customer promotion remain gated. It is not a customer path, does not require V6 or Tailscale, and gives no placement or complete-membership guarantee. JavaScript and older images are outside the first scope |
| Simultaneous jobs | Manifest V4 is v1 at exactly 1; retained V5 is v1 at one or two jobs; higher schema ceilings are not availability |
| Organization Application cap on new starts | v1; organization_over_plan_caps with feature: max_applications, used, and limit refuses all customer publish/deploy, Run, and resume starts and fresh scheduled starts before spend. Already-running continuous renewals, recovery, and replacement continue through their usual checks. Pause keeps an Application slot; completed retirement releases it. CLI typed refusal output requires 0.17.0. Run again, fixed-interval execution, and paid-plan activation retain their release gates. See Application cap refusals |
| Organization job-slot pool | v1; enforced at publish, resume, run, and new scheduled starts. See Job slots |
| Open-market processor selection | v1 |
| Exact processor selection during Acurast warmup | v1 for an authored processor ID. Direct assignment can target a newly registered processor while its chain status is WarmupUntil; open-market selection still requires Active. All other placement, funding, and runtime gates apply. |
| Manager/static selection, placement groups, topology constraints | Internal |
| Job schedule | v1; durationMs >= 60000, maxStartDelayMs <= 3600000, and a supplied start cannot be more than 24 hours ahead |
| Renewal after scheduled end | v1 |
| Renewal before end with fixed lead | v1; 60,000–1,800,000 ms and no more than half the job duration |
| Automatic renewal lead | Internal |
| Immediate or next-renewal update | v1 |
| Existing jobs run to scheduled end | v1 |
| Cooperative cease | Release-gated v1 |
Fixed-interval execution (Manifest V5 execution.mode: interval) | Release-gated v1; the schema accepts every and an optional until, but no interval run has been observed in production and Liskov does not yet launch an interval Application: it stops before any Service Credit reserve or job is created. The accepted behavior is one occurrence per boundary, no overlap, no catch-up burst after a pause or outage, and a recorded skip for a missed boundary. Cron, calendar, and local-time schedules are not v1 |
| Launch retry budget | v1; maxRetries 0–10, default 5 |
| Runtime replace-after-failure | Internal; v1 waits for scheduled end |
| Native finalized chain-failure recovery | Internal; release-gated. Continuous recovery is the first delivery scope, not a released customer capability. The accepted once/interval design uses only the original remaining run window and separately awaits implementation and release. Observation alone authorizes no additional spend; no global activation is promised |
| Early replacement of a retained V5 job that never makes signed contact | Release-gated v1; the bounded recovery path is not a supported customer capability yet |
Operation, money, and custody
| Capability | Availability |
|---|---|
| V5 organization Max spend per deploy and its funds stop | Release-gated v1; the accepted guard compares each member attempt's custody-plus-fee reserve with the USD maxSpendPerDeploy limit at launch, including renewal. Equality passes; lowering the limit can stop the next renewal. Serving enforcement, the funds-stop readback, and the complete customer path still require release verification. See Spend limits |
| Canonical posture, Action Plan, deployment/job timeline | v1 |
| Console Activity event detail, shareable event link, previous/next, Range picker, and event context | Release-gated v1; merged in Console source d51724df1c83846ebdf391d88cd930bc33bbd1cd with the one-event read in API source adedc6dff4bba0ea6f4f52ec97f8783010e2b3d9, but not yet accepted on the deployed Console. The Activity feed and the bounded CLI read are unchanged |
| Console Coverage and Executions convergence strip | v1; proof.liskov.execution-convergence.v1 on production Console 96e3f0638d948b24b516ed7713761784ad62c80f against API 2db522130b314a044f7c50ee530c610d32868b4e. Intended capacity is distinct from remaining charges. Quiet is not stalled. |
CLI execution-convergence sibling on application execution show | Release-gated v1; not present in documented @proof-computer/proof-cli-liskov 0.14.0 nor npm 0.15.0 (6cc262d4d73bab607cc8326dece7f3094ed2731d). Source 150b7c96d0caa23e757222dd1eb0288db48a368d is not a released package. |
Interval schedule line in Console Coverage and on application execution show | Release-gated v1, with fixed-interval execution. Both clients print only the boundary Liskov's schedule owner recorded, judged against the same read: next run, run due with a run still active, run due with no run started, no next run while stopped, no next run scheduled, or next run not reported. Console source 6dea483b58c9ea0847f3429b16e0eef1959bea3f; CLI source 8a930c4 is not in npm 0.15.0 |
| Desired-execution candidate writer selection | Internal; incumbent remains selected until a later authorized activation |
| Organization-gated processor record in Console | v1; your deployment history, runtime contact, operability, and chain-published hardware are visible on every plan; fleet reliability, register liveness, placement assessments, confidence, conflict, and watermark require Enterprise |
| Proof chain and signed runtime-instance evidence | v1 |
| Pause/resume future planning | v1 |
Re-running a completed once Application | Release-gated v1; an explicit re-arm against the Application's current published revision, not a recovery retry — it authorizes one more occurrence and does not promise a launch. The Console's Run again control is deployed, and @proof-computer/proof-cli-liskov 0.14.0 contains the CLI's application run, but no end-to-end run has been observed, so the path is not supported yet |
| Supported bounded Action Plan retry | v1 |
| Release a job held on proven application failure, without publishing a new policy version | v1; a hold is taken only on the job's own signed fatal or an explicit debug.holdOnFailure, and a release re-admits that job under the version already published |
| Safe retirement and immutable receipt | v1 |
| Force stop/delete bypass | Internal; no public bypass |
| Operator adjudication of a review-blocked retirement lineage | Internal; a platform operator action, never a customer action |
| Managed custody | v1 default |
| Per-job cap, reserve, final charge, release, history | v1 |
| Managed no-report settlement | v1 billing rule; after the strict report deadline, scanner-proven absence is not billed, closes at zero charge, releases the full reserve, and needs no customer action |
| Customer crypto deposit, swap, balance, withdrawal | Not v1 |
| Self-custody signer | Preview; not in normal navigation until availability is confirmed, and the managed no-report billing rule does not reverse or refund immutable ACU movement |
Product boundaries
Acurast Tunnel may be used by an exact curated offering; it does not become a general repository capability. Frozen historical implementations and migration workflows are not customer features.
Valid V4 syntax does not permit a new import or publication: both are refused
with v4_publication_disabled. Use retained Manifest V5 for new publications.
Typed requests outside this matrix can return unsupported_policy_feature
or entitlement_exceeded.