Application
The long-lived desired resource: release, configuration, deployments, spend, history, and lifecycle.
Liskov for Acurast builders
Liskov.
You already deploy jobs.
Liskov gives them a lifecycle.
Keep Acurast’s phone processors, hardware-backed execution, real-world network edge, schedules, assignment, and chain settlement. Liskov adds source or pinned releases, managed configuration, bounded actions, and exact runtime evidence.
Live The end-to-end publication path is available now.
Business use only. You must be at least 18. Liskov is currently available only for business use. Do not create an organisation for personal, family or household use. If you believe your use is business use and need help, contact hello@proof.computer.
01 — Map the primitives
No renamed chain concepts.
A product layer around them.
Liskov keeps its own records separate from Acurast’s. That distinction makes the system easier to operate and the evidence easier to interpret.
Deployment
One recorded attempt or generation to realize an immutable effective policy.
Job
The time-boxed network registration with schedule, assignment, and processor evidence.
Runtime instance
One process boot inside a job, identified separately when a process restarts.
02 — Product boundaries
The network stays the network.
The control plane stays accountable.
Liskov coordinates customer intent; Acurast executes network jobs. Neither product absorbs the other’s responsibility.
Execution-network facts
- Job registration and the time-boxed schedule
- Open-market processor assignment
- Processor identity and chain events
- Network settlement evidence
- The execution environment on the phone
Application intent and operation
- Organizations, Applications, teams, and roles
- GitHub release and artifact evidence
- Effective policy, managed configuration, and secrets
- Posture, Action Plans, logs, and lifecycle
- USD Service Credit quote, reserve, charge, and history
03 — What Liskov adds
From a successful submit
to an operable Application.
The value is not another deploy command. It is the durable context and safe operating surface around each network transition.
01Release
GitHub identity becomes release evidence.
The reusable workflow builds and pins without a long-lived Liskov token or spend-capable credential.
- Repository, ref, commit, and workflow identity
- CID and SHA-256 artifact identity
- Strict manifest and immutable effective policy
02Operate
Network states become customer decisions.
Posture and Action Plans distinguish normal waiting from the exact blocker or bounded action that needs attention.
- Scoped activity, deployment timelines, and logs
- Once, continuous, or interval execution across organization-wide job slots
- Managed Runtime SSH for exact running jobs
03Prove
Separate facts become one inspectable chain.
Trace the selected release through its effective policy and Acurast job to signed contact from a particular runtime instance.
- Assignment is not confused with readiness
- Processor history is organization-scoped
- Every proof states what it does not establish
04 — Repository path
The path is deliberate.
So is the spend.
Source import, publication, execution, and closeout are live. The workflow binds exact GitHub authority before draft import, then keeps dry-run inspection separate from the spend-bearing publish action.
Author and validate the manifest
Choose source or pinned release, JavaScript or curated native image, execution mode, job count, configuration, logging, placement, lifecycle, and spend.
Bind the exact GitHub source
Import a source-mode draft with repository, ref, workflow, manifest path, and optional artifact evidence bound by GitHub OIDC.
Preflight, publish, and explain
Dry-run first; publication checks entitlement, exact authority, policy, available Service Credits, and explicit confirmation before creating the immutable effective policy.
Follow posture, evidence, and lifecycle
Operate the resulting Application through Console or the supported public CLI.
Use the complete, checked workflow in the Liskov documentation →
05 — What comes next
A clear product now.
More room to grow.
The current release does not yet include public ingress, arbitrary native images, durable state, placement diversity, or alternate SSH providers.
Check the canonical capability matrix before you design a workload →
For Acurast builders
Keep the primitives.
Gain the lifecycle.
Start with the product boundaries and the supported GitHub path. Continue in Console if your organization already has access.