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 wide unless configured -- see below; 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).
Embedding width
intentions.embedding is a plain pgvector vector(N), and N is a deployment setting: agent-memory's width, so one embedding provider serves both corpora. It defaults to 1024, so a host that configures nothing is unaffected. Give the same embedding_dim to threetears.agent.intention.migrations.register(runner, embedding_dim=...), IntentionsCollection(..., embedding_dim=...) and intentions_table(metadata, embedding_dim=...).
- Ceilings. PostgreSQL's pgvector HNSW index takes at most 2,000 dimensions; YugabyteDB's
ybhnswup to 16,000 (nohalfvecthere, so the column staysvector).registerrefuses a width below 1 or above 16,000; v001 refuses a width above 2,000 on PostgreSQL before any statement runs. - Writes are checked. A save whose embedding is not the collection's width is refused with a
ValueErrornaming both widths, before any SQL runs. - An existing schema keeps its width.
await verify_embedding_width(store, embedding_dim)(threetears.agent.intention.embedding_width, also exported from the package root) raisesEmbeddingWidthMismatchwhenintentions.embeddingis another width. - Changing it is an operator action.
await resize_embedding_width(store, embedding_dim)dropsix_intentions_embedding_hnsw, alters the column withUSING NULL, recreates the index under its own name and options, and returns how many embeddings it cleared. Every want keeps its content and loses its embedding, so re-embed them. Nothing runs it automatically. Run it with writes to these tables stopped: on YugabyteDB the column change is a table rewrite, and writes made while it runs may be lost ("Concurrent DMLs may not be reflected in the new table", yugabyte-db issue 19860).
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.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_intention-0.72.0.tar.gz | 58.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_agent_intention-0.72.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 93.6 kB
Release files / 3tears_agent_intention-0.72.0.tar.gz
| Download URL | 3tears_agent_intention-0.72.0.tar.gz |
|---|---|
| Size | 58.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef305bb9930efc78504ad8903dd0af343f311d46a6e3fc36e010ec2e109eb1c8
|
|
BLAKE2b-256 checksum How to use checksums |
f0b45086342ae3b5d375a81d989cc0186d5d41281a3ec9430eb746e924c5efdd
|
| 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_intention-0.72.0-py3-none-any.whl
| Download URL | 3tears_agent_intention-0.72.0-py3-none-any.whl |
|---|---|
| Size | 35.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b09067923b5755dd3e40dea0cc75e47fc5d063440525519748c715cfdabfc985
|
|
BLAKE2b-256 checksum How to use checksums |
9d4feca9287572bbbd6ec512c258133a95a5c0eaf8f856ac0a7720ed408bd433
|
| 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-intention 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_intention-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.
