pickle-strategy-sdk 0.5.0__tar.gz

pickle_strategy_sdk-0.5.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.
+

pickle_strategy_sdk-0.5.0/NOTICE

@@ -0,0 +1,10 @@
+Pickle Strategy SDK
+Copyright 2026 PickleTech
+
+This product includes software developed by PickleTech.
+
+The installed ladder example includes observations retrieved from Federal
+Reserve Economic Data (FRED), Federal Reserve Bank of St. Louis, and credited
+on the cited series pages to the Board of Governors of the Federal Reserve
+System (US). The modeled instruments and reference prices derived by PickleTech
+are educational values, not observed or executable market quotes.

pickle_strategy_sdk-0.5.0/PKG-INFO

@@ -0,0 +1,219 @@
+Metadata-Version: 2.4
+Name: pickle-strategy-sdk
+Version: 0.5.0
+Summary: Broker-neutral contracts and hosting tools for Pickle strategies
+License-Expression: Apache-2.0
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: simplejson<4,>=3.20
+Requires-Dist: starlette<1,>=0.47
+Requires-Dist: uvicorn<1,>=0.34
+Provides-Extra: test
+Requires-Dist: httpx<1,>=0.28; extra == "test"
+Requires-Dist: pytest<10,>=9; extra == "test"
+Dynamic: license-file
+
+# Pickle strategy SDK
+
+`pickle-strategy-sdk` is the broker-neutral contract and hosting package for
+Pickle strategies. It contains no brokerage, live market-data, backtest,
+calibration, SQLite, SciPy, or pandas code.
+
+Python 3.13 or later is required.
+
+Install it from PyPI:
+
+```sh
+python -m pip install pickle-strategy-sdk
+```
+
+## Quickstart
+
+A strategy is a plain synchronous callable. The `@strategy_service` decorator
+returns the function unchanged, so direct calls and HTTP calls run the same
+implementation:
+
+<!-- readme-quickstart -->
+```python
+from datetime import UTC, datetime
+from decimal import Decimal
+
+from pickle_strategy import BrokerAccountSnapshot, CashBalance, TicketRequest
+from pickle_strategy.examples import ladder_strategy
+
+as_of = datetime(2026, 6, 30, 16, tzinfo=UTC)
+snapshot = BrokerAccountSnapshot(
+    "exe_quickstart", as_of, "USD", cash=(CashBalance("USD", Decimal("100000")),)
+)
+ticket = ladder_strategy(TicketRequest("req_quickstart", "exe_quickstart", as_of, snapshot))
+```
+
+Serve any installed example over HTTP instead:
+
+```sh
+pickle-strategy serve pickle_strategy.examples.null_strategy:null_strategy \
+  --allow-unauthenticated
+pickle-strategy serve pickle_strategy.examples.ladder_strategy:ladder_strategy \
+  --hmac-secret-env PICKLE_STRATEGY_KEY
+```
+
+The command listens on `127.0.0.1:8000`. `GET /health` returns
+`{"status":"ok"}`; `POST /strategy` takes a JSON `TicketRequest` and returns a
+`TradeTicket`. The hosted adapter accepts JSON request bodies up to 1 MiB by
+default; embedded hosts can set a different positive byte limit with
+`create_app(strategy, max_request_body_bytes=...)`.
+
+## Authenticating Pickle's calls
+
+Serving is not open by default. `serve` requires either
+`--hmac-secret-env NAME`, naming the environment variable that holds the key
+Pickle signs with, or `--allow-unauthenticated`, which is refused on any
+address but loopback. `create_app` makes the same choice explicit and raises
+unless exactly one of `verifier=HmacVerifier(...)` or
+`allow_unauthenticated=True` is given.
+
+```python
+from pickle_strategy import HmacVerifier, create_app
+from pickle_strategy.examples import ladder_strategy
+
+app = create_app(ladder_strategy, verifier=HmacVerifier([key]))
+```
+
+An `HmacVerifier` checks an HMAC-SHA256 signature over the raw request body,
+the send time, and `request_id`; enforces a bounded replay window that defaults
+to five minutes; and rejects a signature it has already accepted inside that
+window. It accepts several keys at once so a rotation can deploy the new key
+before Pickle switches to it. Authentication is carried entirely in headers, so
+it adds no field to the `TicketRequest` payload and no schema version.
+
+Pickle sends three headers. `X-Pickle-Timestamp` is the RFC 3339 UTC send time
+to seconds precision, `X-Pickle-Request-Id` is the body's `request_id`, and
+`X-Pickle-Signature` is `v1=` followed by the lowercase hex SHA-256 HMAC of
+these four values joined by single newlines, in order:
+
+```text
+pickle-strategy-auth-v1
+<X-Pickle-Timestamp>
+<X-Pickle-Request-Id>
+<raw request body>
+```
+
+The body is signed as the exact bytes on the wire, so a verifier must never
+re-serialize the JSON before checking. A rejected request is answered `401`
+with one of `missing_signature`, `malformed_signature`, `invalid_signature`,
+`expired_signature`, or `replayed_signature`.
+
+A signature authenticates a request but does not encrypt it, so serve the
+endpoint over TLS. The verifier never forgets a signature that is still inside
+its replay window; if it cannot track another one safely it answers
+`503 replay_cache_exhausted` rather than dropping a still-valid entry.
+
+Since `0.3.0`, `create_app` requires that explicit choice; earlier versions
+had no verifier and served every request unsigned. Callers that relied on that
+pass `allow_unauthenticated=True`.
+
+## Receiving execution reports
+
+A deployment with a callback URL receives a signed execution report for each
+material event of its orders. Receiving them is optional, and needs `0.5.0` or
+later. A handler is a
+synchronous function marked `@report_handler`; pass it to `create_app` with a
+`ReportVerifier` built from the deployment's callback key, which is not the
+request key, and the app serves `POST /reports`:
+
+```python
+from pickle_strategy import (
+    ExecutionReport,
+    HmacVerifier,
+    ReportVerifier,
+    create_app,
+    report_handler,
+)
+
+@report_handler
+def record(report: ExecutionReport) -> None:
+    store.save_once(report.event_id, report)   # idempotent by event_id
+
+app = create_app(
+    strategy,
+    verifier=HmacVerifier([request_key]),
+    report_handler=record,
+    report_verifier=ReportVerifier([callback_key]),
+)
+```
+
+`create_report_app(record, verifier=ReportVerifier([callback_key]))` serves
+reports alone, for a deployment that runs no hosted strategy. The report route
+has its own development opt-out, `allow_unauthenticated_reports=True`, so
+`allow_unauthenticated` on the strategy route never opens it. From the command
+line, `serve` takes `--report-handler module:function` and
+`--report-secret-env NAME`, and `--allow-unauthenticated`, loopback only, opens
+both routes.
+
+A report is signed like a strategy request, in its own context, so a signature
+for one never verifies as the other. It carries `X-Pickle-Timestamp`,
+`X-Pickle-Event-Id`, `X-Pickle-Delivery-Id`, and `X-Pickle-Signature` over:
+
+```text
+pickle-execution-report-v1
+<X-Pickle-Timestamp>
+<X-Pickle-Event-Id>
+<X-Pickle-Delivery-Id>
+<raw request body>
+```
+
+`ReportVerifier.verify(headers, body)` applies the same window and replay rules
+as `HmacVerifier`, decodes the report, and refuses one whose signed
+`X-Pickle-Event-Id` is not the body's `event_id` (`mismatched_event_id`).
+Rejections are answered `401`; a signed body that is not JSON, `400`, and one
+that is not a report, `422`.
+
+Delivery is at least once. Pickle retries a delivery your receiver does not
+acknowledge with backoff, each time under a new delivery ID and signature, for
+at least about an hour and a half, and longer while many reports wait for your
+receiver, before it dead-letters the report for an operator to replay. Reports
+about a customer Pickle has deactivated are held back and not sent at all. An
+acknowledgement can be lost after the handler ran, so the same report can
+arrive more than once. Deduplicate by
+`event_id` in your own store, and return only once the report is recorded:
+an exception answers `500`, and Pickle delivers the report again. Order and
+gaps are in the body: `event_sequence` counts the reports for one execution
+and callback URL from 1.
+
+## Contract version
+
+Since `0.4.0`, the SDK speaks schema version `3.0`. Its decoders accept any
+`3.x` payload and ignore fields they do not know, so a later additive minor
+version still decodes, and its encoders emit exactly `3.0`. A ticket is
+versioned from the request it answers, so a strategy always answers at a
+version Pickle can read. Pickle reads a ticket strictly: it refuses one at a
+later minor than its request, or with a field its version does not define. A
+request recorded under `1.0` or `2.0` decodes strictly at that version, and a
+strategy's ticket answers it at the same version. The normative schemas are
+under `docs/contracts/v3` in the Pickle repository.
+
+## The ladder example
+
+The ladder is backed by frozen public FRED federal-funds and Treasury-yield
+observations plus deterministic modeled prices covering 2026-01-02 through
+2026-06-30. It serves requests from 2026-01-02T21:00Z, when its first modeled
+prices become available, rejects requests outside that window with
+`422 request_rejected`, and is not suitable for live trading. Its prices are
+not observed or executable. Runtime performs no network or database access and
+adds no SDK dependency.
+
+## License
+
+The `pickle-strategy-sdk` distribution is licensed under the Apache License
+2.0. It may be used in commercial and proprietary strategies without requiring
+those strategies to be open source. Redistributors must follow the license and
+preserve the attribution in the packaged `NOTICE`. Both `LICENSE` and `NOTICE`
+ship inside the wheel and source distribution.
+
+This license applies to the SDK distribution rooted in this directory. It does
+not license the rest of the private `PickleTech/pickle` repository. FRED source
+observations retain the attribution and reuse terms identified in the packaged
+source metadata; the Apache-2.0 grant applies to Pickle's code and derived-data
+implementation, not as a claim of ownership over FRED observations.

pickle_strategy_sdk-0.5.0/README.md

@@ -0,0 +1,202 @@
+# Pickle strategy SDK
+
+`pickle-strategy-sdk` is the broker-neutral contract and hosting package for
+Pickle strategies. It contains no brokerage, live market-data, backtest,
+calibration, SQLite, SciPy, or pandas code.
+
+Python 3.13 or later is required.
+
+Install it from PyPI:
+
+```sh
+python -m pip install pickle-strategy-sdk
+```
+
+## Quickstart
+
+A strategy is a plain synchronous callable. The `@strategy_service` decorator
+returns the function unchanged, so direct calls and HTTP calls run the same
+implementation:
+
+<!-- readme-quickstart -->
+```python
+from datetime import UTC, datetime
+from decimal import Decimal
+
+from pickle_strategy import BrokerAccountSnapshot, CashBalance, TicketRequest
+from pickle_strategy.examples import ladder_strategy
+
+as_of = datetime(2026, 6, 30, 16, tzinfo=UTC)
+snapshot = BrokerAccountSnapshot(
+    "exe_quickstart", as_of, "USD", cash=(CashBalance("USD", Decimal("100000")),)
+)
+ticket = ladder_strategy(TicketRequest("req_quickstart", "exe_quickstart", as_of, snapshot))
+```
+
+Serve any installed example over HTTP instead:
+
+```sh
+pickle-strategy serve pickle_strategy.examples.null_strategy:null_strategy \
+  --allow-unauthenticated
+pickle-strategy serve pickle_strategy.examples.ladder_strategy:ladder_strategy \
+  --hmac-secret-env PICKLE_STRATEGY_KEY
+```
+
+The command listens on `127.0.0.1:8000`. `GET /health` returns
+`{"status":"ok"}`; `POST /strategy` takes a JSON `TicketRequest` and returns a
+`TradeTicket`. The hosted adapter accepts JSON request bodies up to 1 MiB by
+default; embedded hosts can set a different positive byte limit with
+`create_app(strategy, max_request_body_bytes=...)`.
+
+## Authenticating Pickle's calls
+
+Serving is not open by default. `serve` requires either
+`--hmac-secret-env NAME`, naming the environment variable that holds the key
+Pickle signs with, or `--allow-unauthenticated`, which is refused on any
+address but loopback. `create_app` makes the same choice explicit and raises
+unless exactly one of `verifier=HmacVerifier(...)` or
+`allow_unauthenticated=True` is given.
+
+```python
+from pickle_strategy import HmacVerifier, create_app
+from pickle_strategy.examples import ladder_strategy
+
+app = create_app(ladder_strategy, verifier=HmacVerifier([key]))
+```
+
+An `HmacVerifier` checks an HMAC-SHA256 signature over the raw request body,
+the send time, and `request_id`; enforces a bounded replay window that defaults
+to five minutes; and rejects a signature it has already accepted inside that
+window. It accepts several keys at once so a rotation can deploy the new key
+before Pickle switches to it. Authentication is carried entirely in headers, so
+it adds no field to the `TicketRequest` payload and no schema version.
+
+Pickle sends three headers. `X-Pickle-Timestamp` is the RFC 3339 UTC send time
+to seconds precision, `X-Pickle-Request-Id` is the body's `request_id`, and
+`X-Pickle-Signature` is `v1=` followed by the lowercase hex SHA-256 HMAC of
+these four values joined by single newlines, in order:
+
+```text
+pickle-strategy-auth-v1
+<X-Pickle-Timestamp>
+<X-Pickle-Request-Id>
+<raw request body>
+```
+
+The body is signed as the exact bytes on the wire, so a verifier must never
+re-serialize the JSON before checking. A rejected request is answered `401`
+with one of `missing_signature`, `malformed_signature`, `invalid_signature`,
+`expired_signature`, or `replayed_signature`.
+
+A signature authenticates a request but does not encrypt it, so serve the
+endpoint over TLS. The verifier never forgets a signature that is still inside
+its replay window; if it cannot track another one safely it answers
+`503 replay_cache_exhausted` rather than dropping a still-valid entry.
+
+Since `0.3.0`, `create_app` requires that explicit choice; earlier versions
+had no verifier and served every request unsigned. Callers that relied on that
+pass `allow_unauthenticated=True`.
+
+## Receiving execution reports
+
+A deployment with a callback URL receives a signed execution report for each
+material event of its orders. Receiving them is optional, and needs `0.5.0` or
+later. A handler is a
+synchronous function marked `@report_handler`; pass it to `create_app` with a
+`ReportVerifier` built from the deployment's callback key, which is not the
+request key, and the app serves `POST /reports`:
+
+```python
+from pickle_strategy import (
+    ExecutionReport,
+    HmacVerifier,
+    ReportVerifier,
+    create_app,
+    report_handler,
+)
+
+@report_handler
+def record(report: ExecutionReport) -> None:
+    store.save_once(report.event_id, report)   # idempotent by event_id
+
+app = create_app(
+    strategy,
+    verifier=HmacVerifier([request_key]),
+    report_handler=record,
+    report_verifier=ReportVerifier([callback_key]),
+)
+```
+
+`create_report_app(record, verifier=ReportVerifier([callback_key]))` serves
+reports alone, for a deployment that runs no hosted strategy. The report route
+has its own development opt-out, `allow_unauthenticated_reports=True`, so
+`allow_unauthenticated` on the strategy route never opens it. From the command
+line, `serve` takes `--report-handler module:function` and
+`--report-secret-env NAME`, and `--allow-unauthenticated`, loopback only, opens
+both routes.
+
+A report is signed like a strategy request, in its own context, so a signature
+for one never verifies as the other. It carries `X-Pickle-Timestamp`,
+`X-Pickle-Event-Id`, `X-Pickle-Delivery-Id`, and `X-Pickle-Signature` over:
+
+```text
+pickle-execution-report-v1
+<X-Pickle-Timestamp>
+<X-Pickle-Event-Id>
+<X-Pickle-Delivery-Id>
+<raw request body>
+```
+
+`ReportVerifier.verify(headers, body)` applies the same window and replay rules
+as `HmacVerifier`, decodes the report, and refuses one whose signed
+`X-Pickle-Event-Id` is not the body's `event_id` (`mismatched_event_id`).
+Rejections are answered `401`; a signed body that is not JSON, `400`, and one
+that is not a report, `422`.
+
+Delivery is at least once. Pickle retries a delivery your receiver does not
+acknowledge with backoff, each time under a new delivery ID and signature, for
+at least about an hour and a half, and longer while many reports wait for your
+receiver, before it dead-letters the report for an operator to replay. Reports
+about a customer Pickle has deactivated are held back and not sent at all. An
+acknowledgement can be lost after the handler ran, so the same report can
+arrive more than once. Deduplicate by
+`event_id` in your own store, and return only once the report is recorded:
+an exception answers `500`, and Pickle delivers the report again. Order and
+gaps are in the body: `event_sequence` counts the reports for one execution
+and callback URL from 1.
+
+## Contract version
+
+Since `0.4.0`, the SDK speaks schema version `3.0`. Its decoders accept any
+`3.x` payload and ignore fields they do not know, so a later additive minor
+version still decodes, and its encoders emit exactly `3.0`. A ticket is
+versioned from the request it answers, so a strategy always answers at a
+version Pickle can read. Pickle reads a ticket strictly: it refuses one at a
+later minor than its request, or with a field its version does not define. A
+request recorded under `1.0` or `2.0` decodes strictly at that version, and a
+strategy's ticket answers it at the same version. The normative schemas are
+under `docs/contracts/v3` in the Pickle repository.
+
+## The ladder example
+
+The ladder is backed by frozen public FRED federal-funds and Treasury-yield
+observations plus deterministic modeled prices covering 2026-01-02 through
+2026-06-30. It serves requests from 2026-01-02T21:00Z, when its first modeled
+prices become available, rejects requests outside that window with
+`422 request_rejected`, and is not suitable for live trading. Its prices are
+not observed or executable. Runtime performs no network or database access and
+adds no SDK dependency.
+
+## License
+
+The `pickle-strategy-sdk` distribution is licensed under the Apache License
+2.0. It may be used in commercial and proprietary strategies without requiring
+those strategies to be open source. Redistributors must follow the license and
+preserve the attribution in the packaged `NOTICE`. Both `LICENSE` and `NOTICE`
+ship inside the wheel and source distribution.
+
+This license applies to the SDK distribution rooted in this directory. It does
+not license the rest of the private `PickleTech/pickle` repository. FRED source
+observations retain the attribution and reuse terms identified in the packaged
+source metadata; the Apache-2.0 grant applies to Pickle's code and derived-data
+implementation, not as a claim of ownership over FRED observations.

pickle_strategy_sdk-0.5.0/pyproject.toml

@@ -0,0 +1,33 @@
+[build-system]
+requires = ["setuptools>=77.0.3"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "pickle-strategy-sdk"
+version = "0.5.0"
+description = "Broker-neutral contracts and hosting tools for Pickle strategies"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+requires-python = ">=3.13"
+dependencies = [
+    "simplejson>=3.20,<4",
+    "starlette>=0.47,<1",
+    "uvicorn>=0.34,<1",
+]
+
+[project.optional-dependencies]
+test = [
+    "httpx>=0.28,<1",
+    "pytest>=9,<10",
+]
+
+[project.scripts]
+pickle-strategy = "pickle_strategy.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+include = ["pickle_strategy*"]
+
+[tool.setuptools.package-data]
+"pickle_strategy.examples" = ["data/ladder/*.csv", "data/ladder/*.json"]

pickle_strategy_sdk-0.5.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+