intent-envelope
A declared intent envelope states what an AI agent is for: the tools it may call, the data it may touch, who it may contact, what it may spend, and which actions always need a named human. The envelope is written before the agent runs and checked in code at every tool call, so a boundary does not depend on the model behaving.
This release is a placeholder that reserves the name while the specification is written. It contains no working code yet.
- The approach: https://securedai.org/agent-intent
- The six-layer architecture it belongs to: https://securedai.org/architecture
- Source, once published: https://github.com/securedai/intent-envelope
Maintained by SecuredAI.org.
1 maintainer
Metadata
1 maintainer
Release files for intent-envelope 0.0.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 | Actions |
|---|---|---|---|---|
| intent_envelope-0.0.0.tar.gz | 1.3 kB | Without provenance | Details for intent_envelope-0.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| intent_envelope-0.0.0-py3-none-any.whl | Python 3 | none | any | Details for intent_envelope-0.0.0-py3-none-any.whl |
Total release size: 3.0 kB
Release files / intent_envelope-0.0.0.tar.gz
| Download URL | intent_envelope-0.0.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
345277c7b63be31bc336c48850d7c48ea52fb174328af4276914484d28cd9200
|
|
BLAKE2b-256 checksum How to use checksums |
8642cc0fd99a03290582dfa93287246152106c4842a9a9fce216c33caf9a0cd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / intent_envelope-0.0.0-py3-none-any.whl
| Download URL | intent_envelope-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fac7cdbe97cd0b5c00bb8942ca053bea938111ad88e4224fcdedee381e0192b
|
|
BLAKE2b-256 checksum How to use checksums |
df6771d1ec24e1ab63e58079cb4f35adce1c5c3d0753e71bb64a1c0de6f9313b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for intent-envelope 0.0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
