Byk documentation

The single documentation home for Byk's supported existing-account action, native clients and CLI, and its non-operational trading-platform reference corpus.

Commercial and operational hold: Byk is not a standalone paid product. The trading reference must not be operated with real money, accounts, credentials, customer funds, checkout, paid entitlements, token issuance, or autonomous production execution. Importing historical account records does not relax that hold.

Bring existing account records

Byk can adopt portfolio and watchlist records plus historical CLOSED or CANCELLED positions from a wisent.app.account-data.v1 JSON export. The signed-in account owner validates the complete document before one atomic write. The operation preserves existing account data and cannot create an active position, place an order, move funds, connect a broker, enable live trading, or start the held autonomous economy.

Import existing Byk account data documents the accepted format, record outcomes, refusal meanings, exact CLI invocation, and the web, macOS, and iOS locations.

Clients

• Desktop quick start — run or build the macOS client.
• Desktop architecture — follow authentication, account operations, and app-shell state.
• iOS client — use the shared identity and native Settings surface.
• Client boundaries — credentials, network ownership, updates, and support.
• Byk CLI reference — install and invoke the independent bin/byk.mjs client.

Trading platform reference

The retained trading corpus describes an autonomous startup-economy model, its runtime and web API, and its release configuration. It is published for reviewers to understand intended economics and real capability boundaries by reading source, never as an operating guide.

• Platform status — the hold, supported review use, and source ownership.
• Economy & lifecycle — entrepreneur and worker roles, genesis, operation, success, and death conditions.
• Runtime architecture — coordinator, agent loops, durable state, credentials, and external effects.
• API lifecycle — web endpoints and the pitch-to-heartbeat lifecycle.
• Releases & configuration — artifact provenance and explicit endpoint requirements.

Source repositories