punctual-scheduler 0.0.1a0__tar.gz

punctual_scheduler-0.0.1a0/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Default owner for everything in the repo.
+*       @TheJohnMatti

punctual_scheduler-0.0.1a0/.github/dependabot.yml

@@ -0,0 +1,24 @@
+version: 2
+updates:
+  # GitHub Actions in .github/workflows/*
+  - package-ecosystem: github-actions
+    directory: "/"
+    schedule:
+      interval: monthly
+    groups:
+      actions:
+        patterns: ["*"]
+    commit-message:
+      prefix: ci
+
+  # Python deps (pyproject). Runtime set is deliberately tiny (DESIGN D7); this
+  # mostly tracks the dev toolchain.
+  - package-ecosystem: pip
+    directory: "/"
+    schedule:
+      interval: monthly
+    groups:
+      python:
+        patterns: ["*"]
+    commit-message:
+      prefix: build

punctual_scheduler-0.0.1a0/.github/pull_request_template.md

@@ -0,0 +1,20 @@
+<!--
+Title must be a Conventional Commit, e.g. `feat(scheduler): catch-up on restart`
+(enforced by the `conventional-title` check). It becomes the squash-merge subject.
+-->
+
+## What
+
+<!-- One or two sentences. What does this change and why. -->
+
+## Design
+
+<!-- Link the DESIGN.md entry (D#/O#) this implements or changes. If this makes a
+     new non-obvious choice, add an entry in the same PR. -->
+
+## Checklist
+
+- [ ] `docs/DESIGN.md` updated (or N/A — no design decision here)
+- [ ] Tests cover the new behaviour
+- [ ] `ruff check` / `ruff format` / `mypy` / `pytest` pass locally
+- [ ] No new runtime dependency (or: justified below, per DESIGN D7)

punctual_scheduler-0.0.1a0/.github/workflows/ci.yml

@@ -0,0 +1,72 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# One in-flight run per branch / PR; new pushes cancel the stale run.
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # hatch-vcs reads the version from git history + tags
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - run: pip install -e ".[dev]"
+      - run: ruff check .
+      - run: ruff format --check .
+
+  typecheck:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # hatch-vcs reads the version from git history + tags
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - run: pip install -e ".[dev]"
+      - run: mypy
+
+  audit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # hatch-vcs reads the version from git history + tags
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - run: pip install -e .
+      - run: pipx run pip-audit
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # hatch-vcs reads the version from git history + tags
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+          cache: pip
+      - run: pip install -e ".[dev]"
+      - run: pytest -q --cov --cov-report=term-missing

punctual_scheduler-0.0.1a0/.github/workflows/codeql.yml

@@ -0,0 +1,27 @@
+name: codeql
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: "0 6 * * 1" # Mondays 06:00 UTC
+
+concurrency:
+  group: codeql-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - uses: github/codeql-action/init@v3
+        with:
+          languages: python
+          queries: security-and-quality
+      - uses: github/codeql-action/analyze@v3

punctual_scheduler-0.0.1a0/.github/workflows/pr-title.yml

@@ -0,0 +1,34 @@
+name: pr-title
+
+# Asserts the PR title is a valid Conventional Commit, so the squash-merge
+# subject line (and an eventual generated changelog) stays clean.
+
+on:
+  pull_request:
+    types: [opened, edited, reopened, synchronize]
+
+permissions:
+  pull-requests: read
+
+jobs:
+  conventional-title:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          # keep in sync with the types used in commit history
+          types: |
+            feat
+            fix
+            chore
+            docs
+            refactor
+            test
+            perf
+            ci
+            build
+          requireScope: false
+          # No subject-case rule: Dependabot ("Bump …") and other bots
+          # capitalise, and fighting that isn't worth the friction.

punctual_scheduler-0.0.1a0/.github/workflows/release.yml

@@ -0,0 +1,69 @@
+name: release
+
+# Cut a release by pushing a tag:  git tag v0.0.1 && git push origin v0.0.1
+# Builds sdist + wheel, publishes to PyPI via OIDC trusted publishing (no token),
+# and creates a GitHub Release with the artifacts attached.
+#
+# One-time setup on PyPI (cannot be done from CI): add a "pending publisher" at
+# https://pypi.org/manage/account/publishing/ —
+#   PyPI Project Name: punctual-scheduler
+#   Owner:             TheJohnMatti
+#   Repository name:   punctual
+#   Workflow name:     release.yml
+#   Environment name:  pypi
+# The matching `pypi` GitHub environment (tag-only deploy policy) already exists.
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # hatch-vcs needs full history + tags for the version
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pipx run build
+      - run: pipx run twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/punctual-scheduler
+    permissions:
+      id-token: write # OIDC token for trusted publishing
+      contents: read
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  github-release:
+    needs: pypi
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: softprops/action-gh-release@v2
+        with:
+          files: dist/*
+          generate_release_notes: true

punctual_scheduler-0.0.1a0/.gitignore

@@ -0,0 +1,31 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+build/
+dist/
+.venv/
+venv/
+
+# punctual runtime state (never commit a state DB)
+*.db
+*.db-wal
+*.db-shm
+punctual.toml.local
+state/
+
+# editors / OS
+.idea/
+.vscode/
+*.swp
+.DS_Store
+
+# uv (not committed — dev envs resolve from pyproject; revisit if we adopt `uv sync` in CI)
+uv.lock

punctual_scheduler-0.0.1a0/.pre-commit-config.yaml

@@ -0,0 +1,19 @@
+# Fast, deterministic hooks only. Type-checking (mypy) runs in CI, not here —
+# it is slow and environment-sensitive.  `pre-commit install` to enable.
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: check-toml
+      - id: check-yaml
+      - id: check-merge-conflict
+      - id: check-added-large-files
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.5
+    hooks:
+      - id: ruff-check
+        args: [--fix]
+      - id: ruff-format

punctual_scheduler-0.0.1a0/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+## Dev setup
+
+The environment is [uv](https://docs.astral.sh/uv/)-managed.
+
+```console
+uv pip install -e ".[dev]"
+uv run pre-commit install    # ruff + hygiene hooks on every commit
+```
+
+## Checks (all run in CI)
+
+| Command | What |
+|---|---|
+| `ruff check .` | lint |
+| `ruff format --check .` | formatting |
+| `mypy` | strict type-checking (`src/` only) |
+| `pytest -q` | tests, on 3.12 and 3.13 |
+
+`pre-commit run --all-files` covers the first two plus file hygiene.
+
+## Pull requests
+
+- PR titles must be [Conventional Commits](https://www.conventionalcommits.org/)
+  (`feat:`, `fix:`, `chore:`, `docs:`, `refactor:`, `test:`, `perf:`, `ci:`,
+  `build:`) — enforced by the `pr-title` check. The title becomes the
+  squash-merge subject.
+- Every non-obvious design choice gets an entry in [`docs/DESIGN.md`](docs/DESIGN.md).
+- Keep the runtime dependency set minimal (currently `click` + `croniter` — see
+  DESIGN D7).
+
+## Releasing
+
+Fully tag-driven — `hatch-vcs` derives the version from the tag, so there is no
+version to bump anywhere.
+
+```console
+git tag v0.1.0        # -> package version 0.1.0
+git push origin v0.1.0
+```
+
+The `release` workflow builds the sdist + wheel, publishes to PyPI via OIDC
+trusted publishing (no API token), and opens a GitHub Release. Between tags,
+local builds get a dev version like `0.1.dev7+g1a2b3c4`.
+
+One-time PyPI setup (not yet done): add a pending publisher at
+<https://pypi.org/manage/account/publishing/> — project `punctual-scheduler`,
+owner `TheJohnMatti`, repo `punctual`, workflow `release.yml`, environment
+`pypi`.

punctual_scheduler-0.0.1a0/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.

punctual_scheduler-0.0.1a0/PKG-INFO

@@ -0,0 +1,123 @@
+Metadata-Version: 2.5
+Name: punctual-scheduler
+Version: 0.0.1a0
+Summary: The reliability layer cron never had: retries, catch-up, dependencies, observability, exactly-once. One process, zero infra.
+Project-URL: Homepage, https://github.com/TheJohnMatti/punctual
+Project-URL: Source, https://github.com/TheJohnMatti/punctual
+Project-URL: Issues, https://github.com/TheJohnMatti/punctual/issues
+Author: John Matti
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: cron,daemon,jobs,reliability,scheduler,sre
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: System :: Systems Administration
+Requires-Python: >=3.12
+Requires-Dist: click>=8.1
+Requires-Dist: croniter>=3.0
+Provides-Extra: dev
+Requires-Dist: hypothesis>=6; extra == 'dev'
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: pre-commit>=3.8; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
+Requires-Dist: pytest-cov>=5; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# punctual
+
+**The reliability layer `cron` never had.** One long-running process, zero
+infrastructure, a config file that reads like a crontab — plus the five things
+every team ends up bolting onto cron by hand:
+
+| | `cron` | `punctual` |
+|---|---|---|
+| Retries / backoff | ✗ | ✓ |
+| Catch-up after downtime | ✗ (silently skips) | ✓ (per-job policy) |
+| Dependencies between jobs | ✗ | ✓ (`after = [...]`, no DAG file) |
+| "Did the 3am job run?" | ✗ | ✓ (durable run history, metrics, traces) |
+| Exactly-once under overlap/restart | ✗ | ✓ (claim-before-run) |
+
+Not Airflow. Airflow (and Dagster, Temporal, …) assume a database, a scheduler
+process, a web server, a worker pool, and that you'll rewrite your jobs as DAGs.
+That's right at 500 jobs and 12 engineers. `punctual` is for the machine with
+6 scripts on it — which is most machines.
+
+> Status: **pre-alpha, under active design.** See [`docs/DESIGN.md`](docs/DESIGN.md)
+> for the decisions made so far and the ones still open.
+
+## The shape of it
+
+```toml
+# punctual.toml
+[job.scrape]
+schedule  = "*/10 * * * *"
+command   = "python -m sniper.scrape"
+on_missed = "skip"                       # skip | run_latest | run_each
+
+[job.retrain]
+schedule  = "0 8 * * 1"
+command   = "python -m sniper.retrain"
+after     = ["scrape"]                   # dependency edge
+timeout   = "45m"
+retries   = { max = 3, backoff = "exponential" }
+on_fail   = "ntfy://my-topic"            # page after retries are exhausted
+```
+
+```console
+$ punctual run                 # start the daemon (put this under systemd/launchd)
+$ punctual plan                # next 24h of fires, timezone/DST-aware
+$ punctual history retrain     # every run: when, how long, exit code, output
+$ punctual why retrain         # explain the last scheduling decision   (coming)
+$ punctual tui                 # live dashboard                          (coming)
+```
+
+## Quickstart
+
+```console
+$ uv tool install git+https://github.com/TheJohnMatti/punctual   # or: pipx install …
+
+$ mkdir -p ~/.config/punctual && cat > ~/.config/punctual/punctual.toml <<'EOF'
+[job.heartbeat]
+schedule = "* * * * * */30"     # every 30s — 6-field cron: seconds go LAST
+command  = "date -u +%FT%TZ"
+
+[job.backup]
+schedule = "0 3 * * *"          # 03:00 daily
+command  = "restic backup /home/me"
+EOF
+
+$ punctual -c ~/.config/punctual/punctual.toml validate
+$ punctual -c ~/.config/punctual/punctual.toml run      # Ctrl-C drains, then exits
+# ...in another shell:
+$ punctual -c ~/.config/punctual/punctual.toml history
+  09-01 14:30  heartbeat   succeeded    0.0s  exit   0
+  09-01 14:30  backup      succeeded   12.4s  exit   0
+```
+
+State lives in `~/.local/state/punctual/punctual.db` (override with `$PUNCTUAL_DB`).
+To keep it running, install a service — see [`packaging/`](packaging/).
+
+> **What works today (M1 slice 1):** scheduling from now, subprocess execution
+> with output capture, timeouts, durable history. **Not yet:** catch-up after
+> downtime, retries, `why` / `tui`. See [`docs/DESIGN.md`](docs/DESIGN.md).
+
+## Design principles
+
+1. **A missed run is an incident, not a shrug.** cron's original sin is silence.
+2. **Zero infra to start.** Embedded SQLite. No server, no broker, no web app.
+3. **Crontab-shaped.** If you can write a crontab you can write a `punctual.toml`.
+4. **Exactly-once is at-least-once + idempotency.** We're honest about that and
+   build the idempotency in.
+5. **Grows, doesn't bloat.** Single node → leader-elected cluster → durable
+   in-process steps, same core.
+
+## License
+
+Apache-2.0.