3tears Agent Intention
Standing-wants corpus for LLM agents. An intention is agent-authored deliberation output -- a want the agent is holding onto ("ask Pace about the migration", "check whether the wake threads are firing") -- with its own status lifecycle, salience decay, and restraint brakes so the agent surfaces a want at most occasionally rather than every turn.
Part of the 3tears framework.
Installation
pip install 3tears-agent-intention
Why a separate package (not a memory of kind=intention)
Memory is a hard-delete-only user-fact taxonomy with immutable scope columns and no
lifecycle. An intention is all lifecycle: open -> asked -> granted / dropped, a
partial index for "find the open wants", and a validated status value set. Riding the
shared memory_type PG enum would pollute a user-fact taxonomy with an agent-internal
control construct and force an irreversible enum add on six consumers.
Enhance-first is still honoured: intention consumes the reusable salience/decay
substrate the agent/memory enhancement built (the same salience column shape and
the shared apply_salience_decay helper), rather than reinventing it.
Components
intentions table
Partition on agent_id; composite PK (agent_id, intention_id); CAS on date_updated
(mirrors memory). Columns: status (PG enum intention_status), content,
embedding (pgvector 1024, for dedup on log), salience (NUMERIC(5,4), reuses the
decay substrate), last_decayed_at (decay anchor), last_surfaced_at (cooldown
anchor), source_memory_id / source_conversation_id (soft-ref provenance, no FK).
User isolation is a user_id WHERE clause, not RBAC
Every metallm user shares one agent_id, so the partition isolates nothing and the
agent-owner RBAC short-circuit sees every want. user_id is the only boundary: the
collection's user-facing reads take user_id as a required parameter, and every
consumer read filters on it.
Versioning policy
The package version moves in lockstep with the rest of the 3tears monorepo -- every package tracks the framework git tag.
1 maintainer
Metadata
1 maintainer
Release files for 3tears-agent-intention 0.68.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 | |
|---|---|---|---|
| 3tears_agent_intention-0.68.0.tar.gz | 50.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_agent_intention-0.68.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.5 kB
Release files / 3tears_agent_intention-0.68.0.tar.gz
| Download URL | 3tears_agent_intention-0.68.0.tar.gz |
|---|---|
| Size | 50.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5bddfdff657c12e073101a0e2617a1f8948b801887a666ba580bbc5f645bf0d1
|
|
BLAKE2b-256 checksum How to use checksums |
709328d2c25af129f697353e58306c940565f8cf02c3e232e3c3660304110bfb
|
| 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 14, 2026.
Transparency logRelease files / 3tears_agent_intention-0.68.0-py3-none-any.whl
| Download URL | 3tears_agent_intention-0.68.0-py3-none-any.whl |
|---|---|
| Size | 31.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3dd136113d76f5927219ff754f47c725a95ab51fb2257aefb1750a5e7c46eecd
|
|
BLAKE2b-256 checksum How to use checksums |
a42259f787be0a930f52fb4f0d6929366922163d5f318192c30316d54edac193
|
| 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 14, 2026.
Transparency log
