Boundaries & support
Byk deliberately owns a narrow native-client boundary and keeps credentials, product behavior, and commercial status explicit.
Credentials
The publishable Supabase anonymous key ships in BykIOSCore.AppConfig. The authenticated user session lives in the login Keychain. The repository contains no service-role key, model credential, or other secret.
Network
Normal operation contacts the Supabase authentication endpoints and the Wisent trading web surface. A signed bundle also contacts an update feed only when a valid HTTPS feed is configured.
Product ownership
| Byk owns | Byk does not own |
|---|---|
| Native email-code sign-in | Trading logic |
| Keychain session persistence | Assistant logic |
| Web-session cookie seeding | Account management |
| macOS shell and page-health state | The underlying web product |
| Signed app update integration | Standalone commerce |
Commercial status
Byk is on commercial hold. The product must not receive a standalone checkout, paid entitlement, or independent public launch. Re-entry requires a stable product contract, independent buyer, and independent outcome.
Support
- Reproducible defects: open an issue in wisent-ai/byk-desktop with the macOS version,
swift --version, and the exact on-screen message. - Commercial questions: the machine-readable commercial status and its referenced strategy record are authoritative.
- Security reports: report privately to Wisent; never open a public issue containing a vulnerability or credential.