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 nullableskill_idFK referencing the cross-packageagent_skills.skill_idstandalone UNIQUE.wake_fires-- one row per wake fire (history; the statuses aretypes.FireStatus, among them'checked_quiet': a check that found nothing, no turn ran, not counted by the fire limits).webhook_subscriptions-- one row per inbound HTTP webhook subscription. Carries nullabledefault_skill_idFK toagent_skills.skill_idand Fernet-encryptedsecret_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
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.
1 maintainer
Metadata
1 maintainer
Release files for 3tears-agent-wake 0.72.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| 3tears_agent_wake-0.72.0.tar.gz | 241.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_agent_wake-0.72.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 397.2 kB
Release files / 3tears_agent_wake-0.72.0.tar.gz
| Download URL | 3tears_agent_wake-0.72.0.tar.gz |
|---|---|
| Size | 241.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9e36e2578044d880cd41096c500e0c2fcfa03d0fe313e9be7eaf8b85f6dd036
|
|
BLAKE2b-256 checksum How to use checksums |
3429fea0a01bf3b2830a08e4e2f6e54f6c2b3a0ea19e9af708793eba7f7bec2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / 3tears_agent_wake-0.72.0-py3-none-any.whl
| Download URL | 3tears_agent_wake-0.72.0-py3-none-any.whl |
|---|---|
| Size | 155.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3e3dc7951a924d2ca96432db7da838b9afa093da935a8943882bea2cdc6a194
|
|
BLAKE2b-256 checksum How to use checksums |
63a78f389c4633bc839589bee832463ee3d930310d7b547627f8855e96caedbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for 3tears-agent-wake 0.72.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for 3tears_agent_wake-0.72.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
