Byk documentation

The single documentation home for the supported native Byk client and the 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.

Desktop client

Byk Desktop signs a user in natively, persists the session in Keychain, and hosts the existing Wisent trading assistant in an authenticated WKWebView. The client owns authentication, session hosting, app-shell state, and signed updates; it does not own trading logic.

• Quick start — run or build the macOS client.
• Client architecture — follow authentication, cookie seeding, and retained-page state.
• Client boundaries — credentials, network ownership, updates, and support.

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