alphaboard 0.1.0__tar.gz

alphaboard-0.1.0/.gitignore

@@ -0,0 +1,84 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+.venv/
+venv/
+env/
+ENV/
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+*.egg-info/
+*.egg
+MANIFEST
+
+# uv
+.uv-cache/
+
+# Testing / coverage
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+.tox/
+.nox/
+coverage.xml
+*.cover
+.hypothesis/
+
+# Type checkers / linters
+.mypy_cache/
+.dmypy.json
+.pyre/
+.ruff_cache/
+
+# Environment / secrets
+.env
+.env.local
+.env.*.local
+*.pem
+*.key
+secrets/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+.DS_Store
+Thumbs.db
+
+# Docker / data
+postgres-data/
+pgdata/
+grafana-data/
+
+# Logs
+*.log
+logs/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Node (for future React dashboard)
+node_modules/
+.next/
+out/
+dist-frontend/
+
+# OS / misc
+*.bak
+*.tmp
+
+# Claude Code session config (personal permission allowlists)
+.claude/
+
+# VS Code workspace files (editor-local)
+*.code-workspace

alphaboard-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

alphaboard-0.1.0/PKG-INFO

@@ -0,0 +1,190 @@
+Metadata-Version: 2.5
+Name: alphaboard
+Version: 0.1.0
+Summary: AlphaBoard SDK — strategy-level monitoring for algorithmic traders. Pushes trades, positions, equity, and heartbeats to an AlphaBoard server without ever blocking your trading loop.
+Project-URL: Homepage, https://github.com/opmau/AlphaBoard
+Project-URL: Repository, https://github.com/opmau/AlphaBoard
+Project-URL: Issues, https://github.com/opmau/AlphaBoard/issues
+Project-URL: Documentation, https://github.com/opmau/AlphaBoard/tree/main/docs
+Author-email: Adam King <adm.king@gmail.com>
+License: Apache-2.0
+License-File: LICENSE
+Keywords: algotrading,monitoring,observability,quant,trading
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business :: Financial :: Investment
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.28.0
+Requires-Dist: tomli>=2.0; python_version < '3.11'
+Description-Content-Type: text/markdown
+
+# alphaboard
+
+Python SDK for [AlphaBoard](https://github.com/opmau/AlphaBoard) — strategy-level monitoring and reconciliation for algorithmic traders. (Formerly `stratops`; renamed to the single brand in OPM-762.)
+
+```python
+from alphaboard import AlphaBoard
+
+tracker = AlphaBoard(
+    strategy="momentum_eth",
+    broker="hyperliquid",
+    account="main",
+)
+
+# Inside your trade execution function:
+tracker.log_trade(symbol="ETH-PERP", side="buy", quantity=0.5, price=3800)
+
+# Periodic sync:
+tracker.sync_positions([{"symbol": "ETH-PERP", "quantity": 1.5, "avg_entry_price": 3750}])
+tracker.log_equity(equity=50_000, cash=10_000)
+tracker.heartbeat(open_positions=1)
+```
+
+## Configuration
+
+Connection settings resolve in this order (highest priority first):
+
+1. **Constructor parameters** — `AlphaBoard(api_url=..., api_key=...)`
+2. **Environment variables** — `ALPHABOARD_API_URL`, `ALPHABOARD_API_KEY`
+3. **Config file** — `~/.alphaboard/config.toml` (override path via `ALPHABOARD_CONFIG`)
+4. **Built-in defaults** — `http://localhost:8000`, no key
+
+The legacy `STRATOPS_*` env vars and `~/.stratops/config.toml` are still read
+as a fallback (one-time deprecation warning) — switch to the new names.
+
+Example `~/.alphaboard/config.toml`:
+
+```toml
+api_url = "https://alphaboard.example.com"
+api_key = "sk_..."
+# Optional: turn on the durable spool (see below)
+spool_dir = "C:/alphaboard-spool"
+```
+
+## Is it actually connected? (`alphaboard doctor`)
+
+Installing the SDK and seeing no errors proves nothing — the SDK never raises,
+by design, so a completely misconfigured client looks exactly like a working
+one from inside your strategy. `alphaboard doctor` is the one command that
+answers *am I being watched?*:
+
+```bash
+alphaboard doctor
+alphaboard doctor --api-url https://alphaboard.example.com --api-key sk_...
+```
+
+It runs four checks in order and stops at the first failure, so you fix causes
+rather than symptoms:
+
+| Check | Answers |
+| --- | --- |
+| `api` | Is the server reachable, and is its database connected? |
+| `auth` | Does your API key authenticate? |
+| `probe` | Does ingestion accept a real write? |
+| `coverage` | The census: every strategy and account, the age of each stream, and a verdict of LIVE / DEGRADED / SILENT. |
+
+Exit codes make it usable from a scheduled task or a CI step: **2** if the API
+or the key is broken, **1** if everything is reachable but something is not
+reporting, **0** if all four pass.
+
+Two properties are worth knowing about, because they are the difference between
+a diagnostic and a placebo:
+
+- **It creates nothing.** The write probe is a single infrastructure heartbeat
+  that deliberately carries **no strategy name**. A probe posted under a real
+  strategy would refresh that strategy's heartbeat stream *and* forward a
+  success ping to its external monitor — so a strategy that had been dead for a
+  day would read LIVE on the very next line of the diagnostic's own output, and
+  its real alert would be silenced. Pass `--no-probe` to skip the write
+  entirely and run read-only.
+- **Zero strategies is a failure, not a pass.** "0/0 live" is technically full
+  coverage and is exactly the reassuring lie that hides a pipe that was never
+  connected.
+
+## Durable spool (no-data-loss mode)
+
+By default the SDK buffers events in memory only — a crash or an extended
+server outage can drop events (your trading is never affected either way).
+Setting a `spool_dir` (constructor param, `ALPHABOARD_SPOOL_DIR`, or the config
+file) turns on a disk-backed outbox:
+
+```python
+tracker = AlphaBoard(strategy="momentum_eth", spool_dir="C:/alphaboard-spool")
+```
+
+- Events are mirrored to a SQLite WAL file by the background worker and
+  deleted only after the server confirms receipt — they survive `SIGKILL`,
+  power loss, and outages of any length.
+- Replays reuse the **same** idempotency keys and carry the **original**
+  event timestamps, so the server deduplicates them: at-least-once on the
+  wire, effectively-once end-to-end.
+- The spool is bounded by rows, bytes, and age (defaults: 1M rows / 512 MB /
+  7 days; tune via `spool_max_rows`, `spool_max_bytes`, `spool_max_age_s`).
+  On breach it drops oldest and surfaces the count via
+  `tracker.spool_dropped_count` — an indefinite outage can't fill your disk.
+- Any spool failure (disk full, locked, corrupt) degrades the SDK back to
+  memory-only. Durability never becomes a new way to crash the host.
+
+## Backfill (historical seeding + gap recovery)
+
+`alphaboard backfill` replays a historical CSV — a broker statement, a Zorro
+log, your engine's own journal — through the server's batch endpoints with
+**deterministic** idempotency keys (UUIDv5 of each row's business key), so
+re-running the same file or window is a no-op, never a duplicate:
+
+```bash
+alphaboard backfill trades.csv  --kind trades --strategy momo --broker ib --account main
+alphaboard backfill equity.csv  --kind equity --strategy momo --mapping '{"Time": "snapshot_at", "Equity": "equity"}'
+alphaboard backfill positions.csv --kind positions --strategy momo --broker ib --account main --dry-run
+```
+
+- `--kind` is `trades`, `equity`, or `positions`; `--mapping` renames CSV
+  headers to canonical fields (same convention as the server's CSV import).
+- `--strategy/--broker/--account` fill in routing fields the CSV doesn't
+  carry; columns present in the file win.
+- `--since/--until` window on the row's *event* time; `--dry-run` validates
+  and counts without sending.
+- Rows must carry their original `executed_at`/`snapshot_at` — backfill
+  refuses to stamp wall-clock-at-import times onto history.
+- Also available in code: `tracker.backfill("trades.csv", kind="trades")`.
+
+## Design
+
+The SDK is **observation-path only**. It never sits between your strategy and the broker. The single hard guarantee:
+
+> `tracker.log_trade(...)` returns in microseconds, never blocks, and never raises.
+
+Every public method enqueues an event into a bounded in-memory deque (default 10 000 items, drop-oldest on overflow), and returns immediately. A daemon background thread batches events, posts them to the AlphaBoard API with exponential backoff, and never lets an exception escape back to user code.
+
+If the AlphaBoard server is unreachable, events back up in the queue until it returns or the queue overflows. **Your trading continues unaffected.**
+
+On process shutdown, an `atexit` hook drains the queue with a bounded timeout (default 5s) so events from the final loop iteration aren't lost.
+
+## Install
+
+```bash
+pip install alphaboard
+```
+
+That pulls in `httpx` and its transitive dependencies and nothing else —
+eight packages total. The SDK deliberately has no dependency on the API server,
+the dashboard, or anything else in the workspace, so it installs cleanly into a
+strategy process that shares none of them.
+
+Working on the SDK itself? Install it from a checkout instead:
+
+```bash
+pip install ./packages/sdk
+```
+
+## Licence
+
+Apache 2.0.

alphaboard-0.1.0/README.md

@@ -0,0 +1,162 @@
+# alphaboard
+
+Python SDK for [AlphaBoard](https://github.com/opmau/AlphaBoard) — strategy-level monitoring and reconciliation for algorithmic traders. (Formerly `stratops`; renamed to the single brand in OPM-762.)
+
+```python
+from alphaboard import AlphaBoard
+
+tracker = AlphaBoard(
+    strategy="momentum_eth",
+    broker="hyperliquid",
+    account="main",
+)
+
+# Inside your trade execution function:
+tracker.log_trade(symbol="ETH-PERP", side="buy", quantity=0.5, price=3800)
+
+# Periodic sync:
+tracker.sync_positions([{"symbol": "ETH-PERP", "quantity": 1.5, "avg_entry_price": 3750}])
+tracker.log_equity(equity=50_000, cash=10_000)
+tracker.heartbeat(open_positions=1)
+```
+
+## Configuration
+
+Connection settings resolve in this order (highest priority first):
+
+1. **Constructor parameters** — `AlphaBoard(api_url=..., api_key=...)`
+2. **Environment variables** — `ALPHABOARD_API_URL`, `ALPHABOARD_API_KEY`
+3. **Config file** — `~/.alphaboard/config.toml` (override path via `ALPHABOARD_CONFIG`)
+4. **Built-in defaults** — `http://localhost:8000`, no key
+
+The legacy `STRATOPS_*` env vars and `~/.stratops/config.toml` are still read
+as a fallback (one-time deprecation warning) — switch to the new names.
+
+Example `~/.alphaboard/config.toml`:
+
+```toml
+api_url = "https://alphaboard.example.com"
+api_key = "sk_..."
+# Optional: turn on the durable spool (see below)
+spool_dir = "C:/alphaboard-spool"
+```
+
+## Is it actually connected? (`alphaboard doctor`)
+
+Installing the SDK and seeing no errors proves nothing — the SDK never raises,
+by design, so a completely misconfigured client looks exactly like a working
+one from inside your strategy. `alphaboard doctor` is the one command that
+answers *am I being watched?*:
+
+```bash
+alphaboard doctor
+alphaboard doctor --api-url https://alphaboard.example.com --api-key sk_...
+```
+
+It runs four checks in order and stops at the first failure, so you fix causes
+rather than symptoms:
+
+| Check | Answers |
+| --- | --- |
+| `api` | Is the server reachable, and is its database connected? |
+| `auth` | Does your API key authenticate? |
+| `probe` | Does ingestion accept a real write? |
+| `coverage` | The census: every strategy and account, the age of each stream, and a verdict of LIVE / DEGRADED / SILENT. |
+
+Exit codes make it usable from a scheduled task or a CI step: **2** if the API
+or the key is broken, **1** if everything is reachable but something is not
+reporting, **0** if all four pass.
+
+Two properties are worth knowing about, because they are the difference between
+a diagnostic and a placebo:
+
+- **It creates nothing.** The write probe is a single infrastructure heartbeat
+  that deliberately carries **no strategy name**. A probe posted under a real
+  strategy would refresh that strategy's heartbeat stream *and* forward a
+  success ping to its external monitor — so a strategy that had been dead for a
+  day would read LIVE on the very next line of the diagnostic's own output, and
+  its real alert would be silenced. Pass `--no-probe` to skip the write
+  entirely and run read-only.
+- **Zero strategies is a failure, not a pass.** "0/0 live" is technically full
+  coverage and is exactly the reassuring lie that hides a pipe that was never
+  connected.
+
+## Durable spool (no-data-loss mode)
+
+By default the SDK buffers events in memory only — a crash or an extended
+server outage can drop events (your trading is never affected either way).
+Setting a `spool_dir` (constructor param, `ALPHABOARD_SPOOL_DIR`, or the config
+file) turns on a disk-backed outbox:
+
+```python
+tracker = AlphaBoard(strategy="momentum_eth", spool_dir="C:/alphaboard-spool")
+```
+
+- Events are mirrored to a SQLite WAL file by the background worker and
+  deleted only after the server confirms receipt — they survive `SIGKILL`,
+  power loss, and outages of any length.
+- Replays reuse the **same** idempotency keys and carry the **original**
+  event timestamps, so the server deduplicates them: at-least-once on the
+  wire, effectively-once end-to-end.
+- The spool is bounded by rows, bytes, and age (defaults: 1M rows / 512 MB /
+  7 days; tune via `spool_max_rows`, `spool_max_bytes`, `spool_max_age_s`).
+  On breach it drops oldest and surfaces the count via
+  `tracker.spool_dropped_count` — an indefinite outage can't fill your disk.
+- Any spool failure (disk full, locked, corrupt) degrades the SDK back to
+  memory-only. Durability never becomes a new way to crash the host.
+
+## Backfill (historical seeding + gap recovery)
+
+`alphaboard backfill` replays a historical CSV — a broker statement, a Zorro
+log, your engine's own journal — through the server's batch endpoints with
+**deterministic** idempotency keys (UUIDv5 of each row's business key), so
+re-running the same file or window is a no-op, never a duplicate:
+
+```bash
+alphaboard backfill trades.csv  --kind trades --strategy momo --broker ib --account main
+alphaboard backfill equity.csv  --kind equity --strategy momo --mapping '{"Time": "snapshot_at", "Equity": "equity"}'
+alphaboard backfill positions.csv --kind positions --strategy momo --broker ib --account main --dry-run
+```
+
+- `--kind` is `trades`, `equity`, or `positions`; `--mapping` renames CSV
+  headers to canonical fields (same convention as the server's CSV import).
+- `--strategy/--broker/--account` fill in routing fields the CSV doesn't
+  carry; columns present in the file win.
+- `--since/--until` window on the row's *event* time; `--dry-run` validates
+  and counts without sending.
+- Rows must carry their original `executed_at`/`snapshot_at` — backfill
+  refuses to stamp wall-clock-at-import times onto history.
+- Also available in code: `tracker.backfill("trades.csv", kind="trades")`.
+
+## Design
+
+The SDK is **observation-path only**. It never sits between your strategy and the broker. The single hard guarantee:
+
+> `tracker.log_trade(...)` returns in microseconds, never blocks, and never raises.
+
+Every public method enqueues an event into a bounded in-memory deque (default 10 000 items, drop-oldest on overflow), and returns immediately. A daemon background thread batches events, posts them to the AlphaBoard API with exponential backoff, and never lets an exception escape back to user code.
+
+If the AlphaBoard server is unreachable, events back up in the queue until it returns or the queue overflows. **Your trading continues unaffected.**
+
+On process shutdown, an `atexit` hook drains the queue with a bounded timeout (default 5s) so events from the final loop iteration aren't lost.
+
+## Install
+
+```bash
+pip install alphaboard
+```
+
+That pulls in `httpx` and its transitive dependencies and nothing else —
+eight packages total. The SDK deliberately has no dependency on the API server,
+the dashboard, or anything else in the workspace, so it installs cleanly into a
+strategy process that shares none of them.
+
+Working on the SDK itself? Install it from a checkout instead:
+
+```bash
+pip install ./packages/sdk
+```
+
+## Licence
+
+Apache 2.0.

alphaboard-0.1.0/alphaboard/__init__.py

@@ -0,0 +1,30 @@
+"""alphaboard — Python SDK for AlphaBoard.
+
+Quick start:
+
+    from alphaboard import AlphaBoard
+
+    tracker = AlphaBoard(
+        strategy="momentum_eth",
+        broker="hyperliquid",
+        account="main",
+        # api_url and api_key fall back to ALPHABOARD_API_URL / ALPHABOARD_API_KEY
+    )
+
+    tracker.log_trade(symbol="ETH-PERP", side="buy", quantity=0.5, price=3800)
+    tracker.heartbeat(open_positions=1)
+
+The SDK is observation-path only. `log_trade()` enqueues and returns in
+microseconds — it never blocks the trading loop and never raises. A daemon
+background thread batches events, posts them with exponential backoff, and
+suppresses all exceptions.
+"""
+
+from alphaboard._backfill import BackfillError, BackfillResult
+
+# `StratOps` is the deprecated pre-rename alias (OPM-762), re-exported only so
+# the burn-in VPS keeps importing until it picks up the rename.
+from alphaboard.client import AlphaBoard, StratOps
+
+__version__ = "0.1.0"
+__all__ = ["AlphaBoard", "BackfillError", "BackfillResult", "StratOps", "__version__"]