3tears-agent-wake 0.14.0__tar.gz

3tears_agent_wake-0.14.0/.gitignore

@@ -0,0 +1,216 @@
+# 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
+.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
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# 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 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/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Claude Code local state
+.claude/
+
+# prawduct session evidence (local governance artifacts, never shipped)
+.prawduct/
+
+# macOS folder metadata
+.DS_Store

3tears_agent_wake-0.14.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mark Pace
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

3tears_agent_wake-0.14.0/PKG-INFO

@@ -0,0 +1,103 @@
+Metadata-Version: 2.4
+Name: 3tears-agent-wake
+Version: 0.14.0
+Summary: Long-running-agent foundation -- wake schedules, fires, webhook subscriptions
+Project-URL: Repository, https://github.com/pacepace/3tears
+Author: pace
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.14
+Requires-Dist: 3tears
+Requires-Dist: 3tears-agent-skills
+Requires-Dist: 3tears-observe
+Requires-Dist: 3tears-scheduled-jobs
+Requires-Dist: apscheduler>=3.10
+Requires-Dist: jinja2>=3
+Requires-Dist: langchain-core
+Requires-Dist: pydantic>=2
+Requires-Dist: uuid-utils
+Provides-Extra: prometheus
+Requires-Dist: prometheus-client>=0.20; extra == 'prometheus'
+Description-Content-Type: text/markdown
+
+# 3tears-agent-wake
+
+Long-running-agent foundation for 3tears-based agents. This package
+ships the schema + Collection layer for three platform tables:
+
+- `agent_wake_schedules` -- one row per active wake schedule for a
+  conversation (cron / one-shot / random-window / etc). Carries a
+  nullable `skill_id` FK referencing the cross-package
+  `agent_skills.skill_id` standalone UNIQUE.
+- `wake_fires` -- one row per wake fire (history; status enum spans
+  `'fired'`, `'fired_silent'`, `'yielded'`, `'skipped_busy'`,
+  `'skipped_rate_limit'`, `'skipped_cap'`, `'skipped_no_handler'`,
+  `'failed'`).
+- `webhook_subscriptions` -- one row per inbound HTTP webhook
+  subscription. Carries nullable `default_skill_id` FK to
+  `agent_skills.skill_id` and Fernet-encrypted `secret_ciphertext`.
+
+Plus three `BaseEntity` subclasses, three `BaseCollection` subclasses,
+and an agent-scope migration registration declaring
+`depends_on=("conversations", "agent_skills")`.
+
+No tick engine, no dispatch handler, no agent tools, and no Pydantic
+API models live in this package.
+
+## Partitioning
+
+All three tables partition by `conversation_id` (wake operations are
+conversation-scoped). The Collections expose `partition_column =
+"conversation_id"` so the workspace partition-column enforcement walker
+audits every SQL string touching these tables for the predicate.
+
+There is intentionally NO database-level FK on `conversation_id` ->
+`conversations(conversation_id)`. The 3tears `conversations` table
+carries a composite PK `(agent_id, conversation_id)` and no standalone
+`UNIQUE (conversation_id)` constraint, so a single-column FK is not
+legal. The same precedent applies in `packages/agent/tools/`
+(`context_items.conversation_id`) and `packages/agent/skills/`
+(`agent_skill_invocations.conversation_id`). Conversation lifecycle is
+governed by app-level cascade through `ConversationsCollection`.
+
+**Orphan-row implication.** Because there is no DB-level FK, deleting a
+row from `conversations` does NOT automatically remove the wake
+schedules, fires, or webhook subscriptions for that conversation.
+They become orphans (rows whose `conversation_id` no longer resolves).
+The partition-column enforcement walker keeps the application blind to
+orphans (every query is filtered by `conversation_id` so an orphan is
+invisible at the read path), but the rows still occupy storage. This
+is the same trade-off agent-tools and agent-skills make. A future
+cross-package cleanup (a TRIGGER on `conversations`-delete that fans
+out to dependent tables, or a periodic GC job in `ConversationsCollection`)
+would close the gap; that work is intentionally cross-cutting and
+out of scope for this package.
+
+## Migration registration
+
+```python
+from threetears.agent.wake import register as register_wake
+from threetears.core.data.migrations import MigrationRunner
+
+runner = MigrationRunner()
+register_wake(runner)
+```
+
+Migrations are agent-scoped and declare
+`depends_on=("conversations", "agent_skills")` -- the canonical
+`MigrationRunner` topologically orders the agent-scope pass so the
+`conversations` + `agent_skills` migrations apply before any wake
+table is created.
+
+## Design references
+
+See `docs/agent-wake/README.md` for the package overview and the
+locked design decisions.

3tears_agent_wake-0.14.0/README.md

@@ -0,0 +1,73 @@
+# 3tears-agent-wake
+
+Long-running-agent foundation for 3tears-based agents. This package
+ships the schema + Collection layer for three platform tables:
+
+- `agent_wake_schedules` -- one row per active wake schedule for a
+  conversation (cron / one-shot / random-window / etc). Carries a
+  nullable `skill_id` FK referencing the cross-package
+  `agent_skills.skill_id` standalone UNIQUE.
+- `wake_fires` -- one row per wake fire (history; status enum spans
+  `'fired'`, `'fired_silent'`, `'yielded'`, `'skipped_busy'`,
+  `'skipped_rate_limit'`, `'skipped_cap'`, `'skipped_no_handler'`,
+  `'failed'`).
+- `webhook_subscriptions` -- one row per inbound HTTP webhook
+  subscription. Carries nullable `default_skill_id` FK to
+  `agent_skills.skill_id` and Fernet-encrypted `secret_ciphertext`.
+
+Plus three `BaseEntity` subclasses, three `BaseCollection` subclasses,
+and an agent-scope migration registration declaring
+`depends_on=("conversations", "agent_skills")`.
+
+No tick engine, no dispatch handler, no agent tools, and no Pydantic
+API models live in this package.
+
+## Partitioning
+
+All three tables partition by `conversation_id` (wake operations are
+conversation-scoped). The Collections expose `partition_column =
+"conversation_id"` so the workspace partition-column enforcement walker
+audits every SQL string touching these tables for the predicate.
+
+There is intentionally NO database-level FK on `conversation_id` ->
+`conversations(conversation_id)`. The 3tears `conversations` table
+carries a composite PK `(agent_id, conversation_id)` and no standalone
+`UNIQUE (conversation_id)` constraint, so a single-column FK is not
+legal. The same precedent applies in `packages/agent/tools/`
+(`context_items.conversation_id`) and `packages/agent/skills/`
+(`agent_skill_invocations.conversation_id`). Conversation lifecycle is
+governed by app-level cascade through `ConversationsCollection`.
+
+**Orphan-row implication.** Because there is no DB-level FK, deleting a
+row from `conversations` does NOT automatically remove the wake
+schedules, fires, or webhook subscriptions for that conversation.
+They become orphans (rows whose `conversation_id` no longer resolves).
+The partition-column enforcement walker keeps the application blind to
+orphans (every query is filtered by `conversation_id` so an orphan is
+invisible at the read path), but the rows still occupy storage. This
+is the same trade-off agent-tools and agent-skills make. A future
+cross-package cleanup (a TRIGGER on `conversations`-delete that fans
+out to dependent tables, or a periodic GC job in `ConversationsCollection`)
+would close the gap; that work is intentionally cross-cutting and
+out of scope for this package.
+
+## Migration registration
+
+```python
+from threetears.agent.wake import register as register_wake
+from threetears.core.data.migrations import MigrationRunner
+
+runner = MigrationRunner()
+register_wake(runner)
+```
+
+Migrations are agent-scoped and declare
+`depends_on=("conversations", "agent_skills")` -- the canonical
+`MigrationRunner` topologically orders the agent-scope pass so the
+`conversations` + `agent_skills` migrations apply before any wake
+table is created.
+
+## Design references
+
+See `docs/agent-wake/README.md` for the package overview and the
+locked design decisions.

3tears_agent_wake-0.14.0/pyproject.toml

@@ -0,0 +1,71 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "3tears-agent-wake"
+version = "0.14.0"
+description = "Long-running-agent foundation -- wake schedules, fires, webhook subscriptions"
+readme = "README.md"
+requires-python = ">=3.14"
+authors = [{name = "pace"}]
+license = "MIT"
+license-files = ["LICENSE"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Framework :: AsyncIO",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+    "Topic :: Software Development :: Libraries",
+    "Typing :: Typed",
+]
+dependencies = [
+    "3tears",
+    "3tears-agent-skills",
+    "3tears-observe",
+    # The cross-pod tick pump (lock + due-scan + CAS-claim + reschedule math)
+    # lives in the generic scheduled-jobs core since S-2; wake's tick is a thin
+    # adapter over it. The transitive ``3tears-nats`` dep (cross-pod lock) now
+    # belongs to that core, not to wake.
+    "3tears-scheduled-jobs",
+    "uuid-utils",
+    # APScheduler is used as a pure utility by the cron-expression validator
+    # (``tools/validators.py`` -- ``CronTrigger.from_crontab``; lazy local
+    # import so non-cron call paths pay zero import cost). The reschedule
+    # math's ``cron`` branch moved to ``3tears-scheduled-jobs`` in S-2, but the
+    # tools layer still validates cron exprs here. Hard dep rather than an extra
+    # so the public ``ScheduleType`` Literal (which includes ``'cron'``) Just
+    # Works without extras-install ceremony.
+    "apscheduler>=3.10",
+    # LangChain BaseTool is the surface every factory returns (mirrors
+    # ``3tears-agent-skills``'s tools layer). Pydantic is the input
+    # schema toolkit. Both are stable, widely-installed wheels.
+    "langchain-core",
+    "pydantic>=2",
+    # Jinja2's SandboxedEnvironment renders the webhook payload
+    # template (shard 04's ``webhook_subscription_create`` validation
+    # path + ``webhook_receive``'s render). Bounded payload + sandbox
+    # mean the dep is opt-in for safety, not power-tool risk.
+    "jinja2>=3",
+]
+
+[project.optional-dependencies]
+# ``prometheus_client`` is optional at runtime -- the metrics module
+# degrades gracefully to no-op when the wheel is absent (mirrors
+# ``3tears-models``'s ``prometheus`` extra). Consumers that want the
+# locked ``3tears_agent_wake_*`` instruments install the extra.
+prometheus = ["prometheus-client>=0.20"]
+
+[project.urls]
+Repository = "https://github.com/pacepace/3tears"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/threetears"]
+
+[tool.uv.sources]
+"3tears-agent-skills" = { workspace = true }
+3tears = { workspace = true }
+3tears-observe = { workspace = true }
+"3tears-scheduled-jobs" = { workspace = true }