minutehand 0.0.1__tar.gz

minutehand-0.0.1/.gitignore

@@ -0,0 +1,235 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# uv
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Minutehand run state
+.state*/
+*.db
+*.db-wal
+*.db-shm
+
+# A run kept by `minutehand run` from the folder it was started in
+.minutehand/
+
+# Throwaway files of a working session, never committed
+.scratch/
+
+# The Node recipe's packages, installed by npm ci in its folder
+node_modules/

minutehand-0.0.1/LICENSE.md

@@ -0,0 +1,105 @@
+# Functional Source License, Version 1.1, ALv2 Future License
+
+## Abbreviation
+
+FSL-1.1-ALv2
+
+## Notice
+
+Copyright 2026 Alknoma
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to
+use, copy, modify, create derivative works, publicly perform, publicly display
+and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or
+service that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software
+   that exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee
+   using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to
+the infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software,
+you must include a copy of or a link to these Terms and Conditions and not
+remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
+PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
+SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
+EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of
+the Software, you have no right under these Terms and Conditions to use our
+trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the Apache License, Version 2.0 that is effective on the second anniversary of
+the date we make the Software available. On or after that date, you may use the
+Software under the Apache License, Version 2.0, in which case the following
+will apply:
+
+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.

minutehand-0.0.1/PKG-INFO

@@ -0,0 +1,179 @@
+Metadata-Version: 2.5
+Name: minutehand
+Version: 0.0.1
+Summary: Build your proactive agent yourself: simulated days, fake services, real findings.
+Project-URL: Repository, https://github.com/Alknoma/minutehand
+Project-URL: Issues, https://github.com/Alknoma/minutehand/issues
+Project-URL: Documentation, https://github.com/Alknoma/minutehand/tree/integration-main/docs
+Author: Alknoma
+License-Expression: FSL-1.1-ALv2
+License-File: LICENSE.md
+Keywords: agents,ai-agents,evaluation,fakes,proxy,pytest,simulation,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: Software Development :: Testing :: Mocking
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: asgiref>=3.8
+Requires-Dist: certifi>=2024.2.2
+Requires-Dist: flask>=3
+Requires-Dist: httpx>=0.27
+Requires-Dist: jsonschema>=4.20
+Requires-Dist: mcp<2,>=1.2
+Requires-Dist: mitmproxy<13,>=12
+Requires-Dist: moto[server]>=5.2
+Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.27
+Requires-Dist: opentelemetry-proto>=1.27
+Requires-Dist: opentelemetry-sdk>=1.27
+Requires-Dist: protobuf>=5
+Requires-Dist: pydantic>=2.9
+Requires-Dist: pyyaml>=6
+Requires-Dist: starlette>=0.40
+Requires-Dist: uvicorn>=0.30
+Requires-Dist: wsproto>=1.2
+Requires-Dist: zstandard>=0.23
+Provides-Extra: grpc
+Requires-Dist: google-cloud-tasks>=2.16; extra == 'grpc'
+Requires-Dist: grpcio>=1.60; extra == 'grpc'
+Description-Content-Type: text/markdown
+
+# Minutehand
+
+Minutehand runs your proactive agent through simulated days of work in a few seconds and tells you how well it
+carried the work. The agent talks to fake Slack, Teams, Asana, Jira, YouTrack, Notion, GitHub, Google Drive and others,
+with people who answer late or not at all. Minutehand owns the clock, records every change in an append-only
+log, and runs checks on the result. Each failure names the design that fixes it. A finished run can be forked
+from a checkpoint with the prompt, the model, a person or the world changed, and played forward again.
+
+The agent's code does not change. Minutehand starts the agent's own command, or reaches one already running,
+and points it at the fakes through its environment: `HTTPS_PROXY`, `NO_PROXY` and a CA bundle.
+
+## Install
+
+You need [uv](https://docs.astral.sh/uv/). It fetches Python 3.12 if you do not have it.
+
+```bash
+uv tool install git+https://github.com/Alknoma/minutehand@integration-main
+```
+
+This puts the `minutehand` command in an environment of its own, apart from your agent's dependencies. Minutehand
+is not published on PyPI.
+
+## Quick start
+
+The example agent is in the repository, so clone it for the example files:
+
+```bash
+git clone --depth 1 -b integration-main https://github.com/Alknoma/minutehand
+cd minutehand/examples/follow_up
+python3 -m venv .venv && .venv/bin/pip install slack_sdk    # the agent's one library, in the agent's own Python
+
+minutehand run scenario.yaml --agent agent.yaml -- .venv/bin/python agent.py
+# exits 0: Rosa answers after a day and a half, and the agent tells Owen and finishes
+
+AGENT_BEHAVIOUR=forgetful minutehand run scenario_silent.yaml --agent agent.yaml -- .venv/bin/python agent.py
+# exits 1: Rosa never answers, the agent never follows up, and no_follow_up names the fix
+
+minutehand runs                  # every run, one line each
+minutehand findings <run_id>     # a run's findings again, and the checkpoints it can be forked from
+minutehand view                  # the runs in a browser, at http://127.0.0.1:8081/
+```
+
+Each run takes a few seconds. Runs are kept in `.minutehand/` in the folder you ran them from. The example's
+`README.md` explains both runs line by line.
+
+To try your own agent, write an agent file (`minutehand schema agent` prints its JSON Schema) and a scenario,
+check them with `minutehand validate`, and run `minutehand doctor -- <your agent's command>` to find any HTTP
+client in the agent that would go around the proxy.
+
+## How the agent touches Minutehand
+
+Almost nothing is required. An agent that takes its goal by message and books its own wakes implements no
+endpoint. An agent can also take a wake (a `POST` carrying the simulated `now`), answer a report (still working,
+done, when to wake next), take pushed events in each provider's own format, and list its own inboxes for the
+simulated people to decide. Hosts no fake answers are declared in the agent file: acknowledge, pass through,
+replay, or forward to an emulator of your own. `docs/agent-contract.md` lists every touch point, and
+`schemas/agent-api.openapi.json` describes the endpoints.
+
+## Status
+
+Built and tested (`docs/design.md`, "What exists", counts the tests for each part):
+
+- The proxy, the run loop, the store (SQLite, one file per run and its forks), forks from a checkpoint with the
+  agent's own state restored and verified, and `minutehand serve` for test suites that open many worlds at once.
+- Providers: Slack, Microsoft Teams and Graph, Asana, Jira, YouTrack, Notion, GitHub, Google Drive with Docs and Slides,
+  AWS EventBridge Scheduler and SQS (through moto), and Google Cloud Tasks over its REST transport.
+- 19 checks, the scorecard and 10 patterns. Among them, `planned_past_due` flags a follow-up that was on time
+  only because something other than the agent's own plan woke it; the loop's table of what was due is recorded
+  to answer that. `reported_against_world` holds what the agent says it is waiting on against what the world
+  shows.
+- Checks of the agent's own, kept beside its agent file (`checks:`) and run with Minutehand's.
+- Dispatch rules: a scenario can deliver the agent's own wakes late, twice or not at all, and a fork can change
+  them (`DispatchChange`).
+- Outbound capture, with `--capture-unknown` for a first run: `reads` passes only GET, HEAD and OPTIONS, and
+  `model` lets a model stand in for a service nobody declared once the agent writes to it.
+- The agent's machine: `machine:` commands in a scenario change files at a moment, and the folders an agent file
+  `watches:` are recorded as they change. The `file_removed` expectation reads them.
+- MCP: an agent's tool calls are recorded over HTTP through the proxy, and over standard input and output with
+  `minutehand mcp-relay`. The `tool_called` expectation reads them. `minutehand mcp` serves the tools a coding
+  agent uses to run scenarios and read findings.
+- The agent's own OpenTelemetry received and joined to the world events it caused; telemetry out over OTLP.
+- The run viewer (`minutehand view`), `doctor`, `validate` and `schema`, and a container image (`Dockerfile`)
+  that serves by default.
+
+Experimental: `Contained`, an agent in a gVisor sandbox whose clock Minutehand owns, so timers in the agent's own
+process become its wakes with no code change. It needs a patched gVisor that is kept outside this repository,
+and has been run on arm64 only.
+
+Checked by hand, not in the test suite: an agent in containers (`docs/containers.md`).
+
+Not built: people written by a model, checks a model judges, generated providers, a faked system clock
+(`libfaketime`), the hosted service. No fake has been checked against the real service's wire details; each is
+tested against the service's own client library. `docs/design.md`, "Known issues", lists the limits of what is
+built.
+
+## Docs
+
+| Page | What it covers |
+|---|---|
+| `docs/design.md` | The design, what exists, and its known limits |
+| `docs/agent-contract.md` | Every way an agent and Minutehand touch |
+| `docs/capture.md` | Hosts no fake answers: acknowledge, pass through, replay, `--capture-unknown` |
+| `docs/containers.md` | An agent in a container, and the Docker `NO_PROXY` trap |
+| `docs/serve.md` | `minutehand serve`, for a test suite |
+| `docs/external-emulators.md` | Forwarding a host to a fake of your own |
+| `docs/inboxes.md` | Work that waits on a person in the agent's own product |
+| `docs/reference-agent.md` | A larger example: two processes, a job queue, email, a model API |
+
+## Scenarios to start from
+
+`minutehand scenarios` lists a library of ready-made situations (a person goes quiet, answers late, is away with a
+delegate; an approval is rejected or never decided; a deadline moves; a scheduled wake comes late, twice or never).
+`minutehand scenarios new --all --goal ... --owner 'Name <email>' --ask 'Name <email>'` writes each out with your
+values. See `docs/scenarios.md`.
+
+## Develop
+
+From a checkout:
+
+```bash
+uv sync
+uv run pytest -q -n auto
+uv run pyright
+uv run python -m lints
+uv run ruff check . && uv run ruff format --check .
+```
+
+`CLAUDE.md` is the house rules, `CONTRIBUTING.md` how to contribute, and `docs/lints.md` argues each lint.
+`uv tool install .` installs the checkout's own `minutehand`.
+
+Licensed under the Functional Source License 1.1 (Apache-2.0 future licence); see `LICENSE.md`.

minutehand-0.0.1/README.md

@@ -0,0 +1,131 @@
+# Minutehand
+
+Minutehand runs your proactive agent through simulated days of work in a few seconds and tells you how well it
+carried the work. The agent talks to fake Slack, Teams, Asana, Jira, YouTrack, Notion, GitHub, Google Drive and others,
+with people who answer late or not at all. Minutehand owns the clock, records every change in an append-only
+log, and runs checks on the result. Each failure names the design that fixes it. A finished run can be forked
+from a checkpoint with the prompt, the model, a person or the world changed, and played forward again.
+
+The agent's code does not change. Minutehand starts the agent's own command, or reaches one already running,
+and points it at the fakes through its environment: `HTTPS_PROXY`, `NO_PROXY` and a CA bundle.
+
+## Install
+
+You need [uv](https://docs.astral.sh/uv/). It fetches Python 3.12 if you do not have it.
+
+```bash
+uv tool install git+https://github.com/Alknoma/minutehand@integration-main
+```
+
+This puts the `minutehand` command in an environment of its own, apart from your agent's dependencies. Minutehand
+is not published on PyPI.
+
+## Quick start
+
+The example agent is in the repository, so clone it for the example files:
+
+```bash
+git clone --depth 1 -b integration-main https://github.com/Alknoma/minutehand
+cd minutehand/examples/follow_up
+python3 -m venv .venv && .venv/bin/pip install slack_sdk    # the agent's one library, in the agent's own Python
+
+minutehand run scenario.yaml --agent agent.yaml -- .venv/bin/python agent.py
+# exits 0: Rosa answers after a day and a half, and the agent tells Owen and finishes
+
+AGENT_BEHAVIOUR=forgetful minutehand run scenario_silent.yaml --agent agent.yaml -- .venv/bin/python agent.py
+# exits 1: Rosa never answers, the agent never follows up, and no_follow_up names the fix
+
+minutehand runs                  # every run, one line each
+minutehand findings <run_id>     # a run's findings again, and the checkpoints it can be forked from
+minutehand view                  # the runs in a browser, at http://127.0.0.1:8081/
+```
+
+Each run takes a few seconds. Runs are kept in `.minutehand/` in the folder you ran them from. The example's
+`README.md` explains both runs line by line.
+
+To try your own agent, write an agent file (`minutehand schema agent` prints its JSON Schema) and a scenario,
+check them with `minutehand validate`, and run `minutehand doctor -- <your agent's command>` to find any HTTP
+client in the agent that would go around the proxy.
+
+## How the agent touches Minutehand
+
+Almost nothing is required. An agent that takes its goal by message and books its own wakes implements no
+endpoint. An agent can also take a wake (a `POST` carrying the simulated `now`), answer a report (still working,
+done, when to wake next), take pushed events in each provider's own format, and list its own inboxes for the
+simulated people to decide. Hosts no fake answers are declared in the agent file: acknowledge, pass through,
+replay, or forward to an emulator of your own. `docs/agent-contract.md` lists every touch point, and
+`schemas/agent-api.openapi.json` describes the endpoints.
+
+## Status
+
+Built and tested (`docs/design.md`, "What exists", counts the tests for each part):
+
+- The proxy, the run loop, the store (SQLite, one file per run and its forks), forks from a checkpoint with the
+  agent's own state restored and verified, and `minutehand serve` for test suites that open many worlds at once.
+- Providers: Slack, Microsoft Teams and Graph, Asana, Jira, YouTrack, Notion, GitHub, Google Drive with Docs and Slides,
+  AWS EventBridge Scheduler and SQS (through moto), and Google Cloud Tasks over its REST transport.
+- 19 checks, the scorecard and 10 patterns. Among them, `planned_past_due` flags a follow-up that was on time
+  only because something other than the agent's own plan woke it; the loop's table of what was due is recorded
+  to answer that. `reported_against_world` holds what the agent says it is waiting on against what the world
+  shows.
+- Checks of the agent's own, kept beside its agent file (`checks:`) and run with Minutehand's.
+- Dispatch rules: a scenario can deliver the agent's own wakes late, twice or not at all, and a fork can change
+  them (`DispatchChange`).
+- Outbound capture, with `--capture-unknown` for a first run: `reads` passes only GET, HEAD and OPTIONS, and
+  `model` lets a model stand in for a service nobody declared once the agent writes to it.
+- The agent's machine: `machine:` commands in a scenario change files at a moment, and the folders an agent file
+  `watches:` are recorded as they change. The `file_removed` expectation reads them.
+- MCP: an agent's tool calls are recorded over HTTP through the proxy, and over standard input and output with
+  `minutehand mcp-relay`. The `tool_called` expectation reads them. `minutehand mcp` serves the tools a coding
+  agent uses to run scenarios and read findings.
+- The agent's own OpenTelemetry received and joined to the world events it caused; telemetry out over OTLP.
+- The run viewer (`minutehand view`), `doctor`, `validate` and `schema`, and a container image (`Dockerfile`)
+  that serves by default.
+
+Experimental: `Contained`, an agent in a gVisor sandbox whose clock Minutehand owns, so timers in the agent's own
+process become its wakes with no code change. It needs a patched gVisor that is kept outside this repository,
+and has been run on arm64 only.
+
+Checked by hand, not in the test suite: an agent in containers (`docs/containers.md`).
+
+Not built: people written by a model, checks a model judges, generated providers, a faked system clock
+(`libfaketime`), the hosted service. No fake has been checked against the real service's wire details; each is
+tested against the service's own client library. `docs/design.md`, "Known issues", lists the limits of what is
+built.
+
+## Docs
+
+| Page | What it covers |
+|---|---|
+| `docs/design.md` | The design, what exists, and its known limits |
+| `docs/agent-contract.md` | Every way an agent and Minutehand touch |
+| `docs/capture.md` | Hosts no fake answers: acknowledge, pass through, replay, `--capture-unknown` |
+| `docs/containers.md` | An agent in a container, and the Docker `NO_PROXY` trap |
+| `docs/serve.md` | `minutehand serve`, for a test suite |
+| `docs/external-emulators.md` | Forwarding a host to a fake of your own |
+| `docs/inboxes.md` | Work that waits on a person in the agent's own product |
+| `docs/reference-agent.md` | A larger example: two processes, a job queue, email, a model API |
+
+## Scenarios to start from
+
+`minutehand scenarios` lists a library of ready-made situations (a person goes quiet, answers late, is away with a
+delegate; an approval is rejected or never decided; a deadline moves; a scheduled wake comes late, twice or never).
+`minutehand scenarios new --all --goal ... --owner 'Name <email>' --ask 'Name <email>'` writes each out with your
+values. See `docs/scenarios.md`.
+
+## Develop
+
+From a checkout:
+
+```bash
+uv sync
+uv run pytest -q -n auto
+uv run pyright
+uv run python -m lints
+uv run ruff check . && uv run ruff format --check .
+```
+
+`CLAUDE.md` is the house rules, `CONTRIBUTING.md` how to contribute, and `docs/lints.md` argues each lint.
+`uv tool install .` installs the checkout's own `minutehand`.
+
+Licensed under the Functional Source License 1.1 (Apache-2.0 future licence); see `LICENSE.md`.

minutehand-0.0.1/examples/external_emulator/agent.py

@@ -0,0 +1,24 @@
+"""A ten-line stand-in for an agent: each wake it files a customer with the payments API and asks for its list,
+through whatever proxy its environment names. It knows nothing of Minutehand or of the emulator answering it."""
+
+import json
+import os
+import sys
+import time
+import urllib.error
+import urllib.request
+from datetime import datetime, timedelta
+
+wake = json.load(sys.stdin)
+now = datetime.fromisoformat(wake["now"])
+time.sleep(float(os.environ.get("EXAMPLE_PAUSE", "0")))  # a slow agent: time to kill the emulator mid-run
+for method, path, body in (("POST", "/v1/customers", b"email=rosa%40example.com"), ("GET", "/v1/customers", None)):
+    asked = urllib.request.Request(
+        f"https://api.stripe.com{path}", data=body, method=method, headers={"authorization": "Bearer sk_test_123"}
+    )
+    try:
+        urllib.request.urlopen(asked, timeout=30).read()
+    except urllib.error.HTTPError as refused:
+        print(f"{method} {path}: {refused.code} {refused.read()[:200]!r}", file=sys.stderr)
+done = wake["reason"] != "start" and now.hour >= 12
+print(json.dumps({"status": "done" if done else "idle", "next_wake": (now + timedelta(hours=1)).isoformat()}))

minutehand-0.0.1/examples/external_emulator/agent.yaml

@@ -0,0 +1,17 @@
+# The agent file: the payments API's real host is forwarded to stripe-mock, a ready-made open-source emulator,
+# run in a container Minutehand starts on a free port and stops with the run.
+name: payments_example
+wakes:
+  - {kind: command, argv: [python, agent.py]}
+outbound:
+  - host: api.stripe.com
+    kind: forward
+    emulator: stripe
+emulators:
+  - name: stripe
+    upstream: {url: "http://127.0.0.1:{port}"}
+    command: [docker, run, --rm, --name, minutehand-ext-stripe, -p, "{port}:12111", "stripe/stripe-mock:latest"]
+    ready: {kind: http, path: /v1/charges, status: 401}   # answers 401 to a call with no key once it is up
+    ready_within: PT60S
+    health: {every: PT1S, fails: 2}
+    faithful: [{status: 402}]                            # a declined card is Stripe's own answer