satay 0.1.0__tar.gz

satay-0.1.0/.gitignore

@@ -0,0 +1,47 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+
+# Environments
+.venv/
+venv/
+
+# Tooling caches
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+
+# Coverage
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Satay project-local data dir (ADR-0017), and the one `make demo` writes to
+.satay/
+.satay-demo/
+
+# Agent worktrees land in .claude/worktrees/ and must never be committed.
+.claude/
+
+# Scratch space for throwaway working files. Nothing in the build references it,
+# and an unignored scratch dir is a well-worn route for stray output — or a
+# credential pasted somewhere "temporary" — to reach a commit.
+scratchpad/
+
+# Studio frontend (ADR-0013/0018): source lives in studio/; the built bundle is
+# vendored to src/satay/_studio_assets/ and IS committed (served by the V5 process).
+studio/node_modules/
+studio/dist/
+studio/.svelte-kit/
+studio/*.tsbuildinfo
+studio/vite.config.ts.timestamp-*
+
+# Editor / OS
+.DS_Store
+*.swp
+.idea/
+.vscode/

satay-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 2026 The Satay Runtime Authors
+
+   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.

satay-0.1.0/PKG-INFO

@@ -0,0 +1,168 @@
+Metadata-Version: 2.5
+Name: satay
+Version: 0.1.0
+Summary: Satay Runtime — a local-first durable-execution runtime for async Python workflows.
+Project-URL: Homepage, https://github.com/leejianrong/satay-runtime
+Project-URL: Repository, https://github.com/leejianrong/satay-runtime
+Author-email: Jian <leejianrong2@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: asyncio,durable-execution,event-sourcing,replay,workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Provides-Extra: studio
+Requires-Dist: fastapi>=0.110; extra == 'studio'
+Requires-Dist: pydantic>=2.6; extra == 'studio'
+Requires-Dist: typer>=0.12; extra == 'studio'
+Requires-Dist: uvicorn>=0.29; extra == 'studio'
+Description-Content-Type: text/markdown
+
+# Satay Runtime
+
+Satay is a **local-first durable-execution runtime** for async Python. You write
+ordinary `async def` workflows and tasks; Satay records every durable call to an
+append-only journal and, on crash, **replays the workflow from the top** — reusing
+recorded results and re-executing only what never finished. No external
+infrastructure: it runs in one process over SQLite.
+
+```python
+import satay
+
+@satay.task()
+async def charge(amount: int) -> str: ...
+
+@satay.workflow
+async def checkout(order):
+    receipt = await charge(order["total"])
+    return receipt
+```
+
+The debugger — **Satay Studio**, a local web UI over an HTTP read API — ships in the
+optional `satay[studio]` extra, so applications that embed Satay never carry the
+FastAPI/uvicorn/JS stack into production.
+
+**Documentation: [leejianrong.github.io/satay-runtime](https://leejianrong.github.io/satay-runtime/)**
+— the tutorial, the cookbook, the Studio guide, and the honest account of what the runtime
+does not do.
+
+## Status
+
+**The MVP is built and the full suite is green (V1–V8).** Trust the code over the docs:
+`docs/` describes the intended full system, and where docs and code disagree the code
+wins. `uv run pytest -q` prints the current test count.
+
+What works today:
+
+- **Durable core + replay.** Workflows replay from the top against an append-only
+  SQLite journal (`PRAGMA user_version` schema, forward-only migrations, WAL); recorded
+  results are reused and only unfinished work re-executes.
+- **Execution guarantees.** Retries with capped exponential backoff and jittered delays
+  off an injected clock, at-least-once task execution, runtime-derived idempotency keys
+  readable inside a task body, replay nondeterminism detection (strict by default — a
+  divergent replay raises rather than returning a plausible wrong answer), and a separate
+  `effect_safety` policy that guards retryable side-effecting tasks.
+- **Time and events.** Durable `sleep`, `wait_for_event`/`send_event` over a persistent
+  inbox, and a timer + event poll loop with FIFO delivery and event-wins-over-timeout.
+  `async with satay.run_app() as store:` gives a plain script that loop — journal open,
+  worker running, both torn down on exit — with no `satay dev` and no optional extra.
+- **Composition.** `map`, `gather`, and `start_child`, each item a keyed durable call, so
+  a crash mid-fan-out resumes with completed items reused and only unresolved items re-run.
+- **Control plane.** An HTTP control + read API (start, cancel, send event, fork; run
+  list, timeline, tree, task detail, compare) with a redactor applied to every read and a
+  loopback/token security guard.
+- **Studio.** The Satay Studio SPA ships as a built bundle served by the same process.
+- **Forking and versioning.** Fork a run from a prefix, compare two runs call-by-call, and
+  a code-version stamp with a strict/warn/off mismatch policy on resume.
+- **`satay dev`.** One command brings up the lock, store, worker, and Studio server, and
+  tears them down in reverse.
+- **Payload spill.** Encoded payloads over 256 KiB spill to content-addressed blob files
+  transparently on write and rehydrate on read.
+
+Deliberate MVP gaps, so the honesty survives contact:
+
+- **No blob GC.** No run deletion and no compaction; blobs accumulate under `./.satay/`
+  and removal is manual (ADR-0004). A future GC has to be reference-aware, since forks
+  share blobs with their source run.
+- **Fan-out is fail-fast only.** No collect / `return_exceptions` mode for
+  `map`/`gather`/`start_child`; the first failure raises and sibling results are discarded
+  (ADR-0020).
+- **`satay runs show` is frozen at the V1 event subset** (ADR-0016). Timer, event,
+  cancellation, and fork events render as bare type lines; Studio covers the rest.
+- **Fork only accepts terminal runs** (ADR-0004) — completed, failed, or cancelled.
+- **One process, one writer.** No PostgreSQL backend, no multi-worker or distributed
+  execution. The cross-process data-dir lock is POSIX `flock` and only `satay dev` takes it.
+- **Async only.** Sync (non-async) workflows and tasks are unsupported.
+- **Nondeterminism detection is runtime-only** and compares the durable-call schedule,
+  not arguments; there is no static analysis of workflow bodies, and no automatic
+  migration of long-running workflows across code versions.
+- **Windows is best-effort** and SQLite on network filesystems is unsupported (ADR-0019).
+
+See `docs/` for the specs and `CLAUDE.md` for the build brief.
+
+## Requirements
+
+- Python **3.12 or 3.13**
+- [`uv`](https://docs.astral.sh/uv/) for environment and dependency management
+- Linux/macOS first-class; Windows best-effort (SQLite on local disk only)
+
+## Dev quickstart
+
+```bash
+uv sync                              # create the venv, install deps + dev group
+uv run ruff check .                  # lint
+uv run ruff format --check .         # format check
+uv run mypy src                      # type-check (strict)
+uv run pytest tests/unit -q          # unit tests
+```
+
+The integration and e2e tests that cover Studio and the HTTP API need the `studio` extra;
+without it they skip themselves and the reported count silently drops:
+
+```bash
+uv sync --extra studio               # then run the full suite
+uv run pytest -q
+```
+
+Or via the Makefile:
+
+```bash
+make dev      # uv sync
+make check    # ruff + mypy
+make test     # unit tests
+make ci       # everything CI runs
+```
+
+Install the pre-push hook (runs the cheap gates before every push):
+
+```bash
+make install-hooks            # or: ./scripts/install-hooks.sh
+```
+
+## Layout
+
+```
+src/satay/        runtime core (pure Python, near-zero dependencies)
+  api/            author decorators, primitives, run handle, TaskContext
+  replay/         replay engine, identity, nondeterminism
+  journal/        event model + Store seam + codec
+  executor/       TaskExecutor seam + LocalTaskExecutor
+  timers/         timer + event poll loop
+  control/        HTTP control + read API   (satay[studio])
+  versioning/     code-version stamper
+  blobs/          payload spill
+  devstack/       `satay dev` orchestrator  (satay[studio])
+  testing/        fault injection, manual clock, seeded RNG, fixtures
+  cli/            core argparse CLI (`satay runs show`)
+tests/{unit,integration,e2e}/
+docs/             specs + ADRs
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

satay-0.1.0/README.md

@@ -0,0 +1,143 @@
+# Satay Runtime
+
+Satay is a **local-first durable-execution runtime** for async Python. You write
+ordinary `async def` workflows and tasks; Satay records every durable call to an
+append-only journal and, on crash, **replays the workflow from the top** — reusing
+recorded results and re-executing only what never finished. No external
+infrastructure: it runs in one process over SQLite.
+
+```python
+import satay
+
+@satay.task()
+async def charge(amount: int) -> str: ...
+
+@satay.workflow
+async def checkout(order):
+    receipt = await charge(order["total"])
+    return receipt
+```
+
+The debugger — **Satay Studio**, a local web UI over an HTTP read API — ships in the
+optional `satay[studio]` extra, so applications that embed Satay never carry the
+FastAPI/uvicorn/JS stack into production.
+
+**Documentation: [leejianrong.github.io/satay-runtime](https://leejianrong.github.io/satay-runtime/)**
+— the tutorial, the cookbook, the Studio guide, and the honest account of what the runtime
+does not do.
+
+## Status
+
+**The MVP is built and the full suite is green (V1–V8).** Trust the code over the docs:
+`docs/` describes the intended full system, and where docs and code disagree the code
+wins. `uv run pytest -q` prints the current test count.
+
+What works today:
+
+- **Durable core + replay.** Workflows replay from the top against an append-only
+  SQLite journal (`PRAGMA user_version` schema, forward-only migrations, WAL); recorded
+  results are reused and only unfinished work re-executes.
+- **Execution guarantees.** Retries with capped exponential backoff and jittered delays
+  off an injected clock, at-least-once task execution, runtime-derived idempotency keys
+  readable inside a task body, replay nondeterminism detection (strict by default — a
+  divergent replay raises rather than returning a plausible wrong answer), and a separate
+  `effect_safety` policy that guards retryable side-effecting tasks.
+- **Time and events.** Durable `sleep`, `wait_for_event`/`send_event` over a persistent
+  inbox, and a timer + event poll loop with FIFO delivery and event-wins-over-timeout.
+  `async with satay.run_app() as store:` gives a plain script that loop — journal open,
+  worker running, both torn down on exit — with no `satay dev` and no optional extra.
+- **Composition.** `map`, `gather`, and `start_child`, each item a keyed durable call, so
+  a crash mid-fan-out resumes with completed items reused and only unresolved items re-run.
+- **Control plane.** An HTTP control + read API (start, cancel, send event, fork; run
+  list, timeline, tree, task detail, compare) with a redactor applied to every read and a
+  loopback/token security guard.
+- **Studio.** The Satay Studio SPA ships as a built bundle served by the same process.
+- **Forking and versioning.** Fork a run from a prefix, compare two runs call-by-call, and
+  a code-version stamp with a strict/warn/off mismatch policy on resume.
+- **`satay dev`.** One command brings up the lock, store, worker, and Studio server, and
+  tears them down in reverse.
+- **Payload spill.** Encoded payloads over 256 KiB spill to content-addressed blob files
+  transparently on write and rehydrate on read.
+
+Deliberate MVP gaps, so the honesty survives contact:
+
+- **No blob GC.** No run deletion and no compaction; blobs accumulate under `./.satay/`
+  and removal is manual (ADR-0004). A future GC has to be reference-aware, since forks
+  share blobs with their source run.
+- **Fan-out is fail-fast only.** No collect / `return_exceptions` mode for
+  `map`/`gather`/`start_child`; the first failure raises and sibling results are discarded
+  (ADR-0020).
+- **`satay runs show` is frozen at the V1 event subset** (ADR-0016). Timer, event,
+  cancellation, and fork events render as bare type lines; Studio covers the rest.
+- **Fork only accepts terminal runs** (ADR-0004) — completed, failed, or cancelled.
+- **One process, one writer.** No PostgreSQL backend, no multi-worker or distributed
+  execution. The cross-process data-dir lock is POSIX `flock` and only `satay dev` takes it.
+- **Async only.** Sync (non-async) workflows and tasks are unsupported.
+- **Nondeterminism detection is runtime-only** and compares the durable-call schedule,
+  not arguments; there is no static analysis of workflow bodies, and no automatic
+  migration of long-running workflows across code versions.
+- **Windows is best-effort** and SQLite on network filesystems is unsupported (ADR-0019).
+
+See `docs/` for the specs and `CLAUDE.md` for the build brief.
+
+## Requirements
+
+- Python **3.12 or 3.13**
+- [`uv`](https://docs.astral.sh/uv/) for environment and dependency management
+- Linux/macOS first-class; Windows best-effort (SQLite on local disk only)
+
+## Dev quickstart
+
+```bash
+uv sync                              # create the venv, install deps + dev group
+uv run ruff check .                  # lint
+uv run ruff format --check .         # format check
+uv run mypy src                      # type-check (strict)
+uv run pytest tests/unit -q          # unit tests
+```
+
+The integration and e2e tests that cover Studio and the HTTP API need the `studio` extra;
+without it they skip themselves and the reported count silently drops:
+
+```bash
+uv sync --extra studio               # then run the full suite
+uv run pytest -q
+```
+
+Or via the Makefile:
+
+```bash
+make dev      # uv sync
+make check    # ruff + mypy
+make test     # unit tests
+make ci       # everything CI runs
+```
+
+Install the pre-push hook (runs the cheap gates before every push):
+
+```bash
+make install-hooks            # or: ./scripts/install-hooks.sh
+```
+
+## Layout
+
+```
+src/satay/        runtime core (pure Python, near-zero dependencies)
+  api/            author decorators, primitives, run handle, TaskContext
+  replay/         replay engine, identity, nondeterminism
+  journal/        event model + Store seam + codec
+  executor/       TaskExecutor seam + LocalTaskExecutor
+  timers/         timer + event poll loop
+  control/        HTTP control + read API   (satay[studio])
+  versioning/     code-version stamper
+  blobs/          payload spill
+  devstack/       `satay dev` orchestrator  (satay[studio])
+  testing/        fault injection, manual clock, seeded RNG, fixtures
+  cli/            core argparse CLI (`satay runs show`)
+tests/{unit,integration,e2e}/
+docs/             specs + ADRs
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).