Current scope
| Area | Status |
|---|---|
| Product | Local-first terminal and execution gateway for AI agents |
| First venue | Hyperliquid |
| Default network | Testnet |
| Other venues | Aster and Lighter planned |
| Source | Publication planned at launch; development repository currently private |
| Licence model | Apache-2.0 core; commercial source licence for the console |
| Release | Dependent on acceptance gates, not a calendar date |
What exists in development
The source includes signing and venue clients, market and account reads, guarded execution paths, a local hash-chained ledger, risk controls and parts of the operator console. It is no longer a prototype with only two read tools.
The 7 September execution review found integration failures despite passing component tests. Repairs now have local regression coverage, including durable submission state and selected restart and cancellation scenarios. Local fixtures do not prove that the same flow has passed against the venue.
No claim of an independent security audit, production reliability or strategy performance is made here.
What must be demonstrated next
| Gate | Evidence required |
|---|---|
| Guarded execution | Policy holds through signing, concurrent commitments and venue submission. |
| Operator supervision | Pairing, revocation, approvals, policy editing and halt work through the real desktop lifecycle. |
| Recovery | Disconnects, ambiguous responses, partial fills and restart reconcile without lost evidence or blind retries. |
| Defensive controls | Cancellation delivery, retry behavior and dead-man behavior are confirmed against the venue. |
| Supervised pilot | Starting state and activation are verified; an authorized testnet scenario completes with reconciled evidence. |
| Release | A fresh operator can complete documented setup and a testnet trade using a verifiable build. |
The next priority is proving the assembled system. More features do not close an execution or recovery gate.
Documentation revisions
7 September 2026 — whitepaper v0.3 and manifesto rev 02. The whitepaper now distinguishes local policy, venue permissions and capital allocation; explains uncertain execution and recovery; and states the remaining validation gates. The manifesto centers on operator authority and responsibility. The other public pages have been aligned with that account model and project status.
Earlier claims that a loss threshold guarantees a maximum loss, or that a stolen key remains constrained by local guardrails, were incorrect and have been removed. The old claims of universally available sub-accounts and a two-tool-only implementation have also been corrected.
7 September 2026 — website analytics. Cloudflare Web Analytics enabled and the privacy disclosure updated. Builds check the publish directory for sensitive artifacts before upload. Desktop application telemetry remains absent.
4 September 2026 — public information pages. Terms, Privacy and Answers published; fonts moved to this site's origin; mobile layouts improved; unsupported download and live-venue claims removed.
Follow the project
Read the whitepaper for architecture and limits, the manifesto for principles, and For agents for the integration boundary.
To request a launch notification, email hello@oppen.xyz. We receive your address and message for that purpose; there is no web signup form or automatic subscription. You can ask us to remove the request. See Privacy.