lucille-sdk
The stable contract a product builds against to run on the Lucille platform, without importing the Lucille backend.
It is interface only — around 800 lines, no dependencies, stdlib-only by design. A product imports the declaration surface and the capability seams; a host registers concrete providers behind those seams before the product is imported. In-process that host is the Lucille backend; out-of-process it is the product's own runtime.
from lucille_sdk import Integration, IntegrationDescriptor
from lucille_sdk.services import get_message_compose
from lucille_sdk.telegram import settled_text
What is in it
| Module | What it declares |
|---|---|
integration |
Integration base class, settings-provider seam |
specs |
IntegrationDescriptor, action/service/intent/recipe specs |
services |
identity, jobs, LLM, messaging seams |
storage |
object-storage seam |
telegram |
Telegram client seam, and the shared settle text rule |
scheduling |
user-job scheduling seam |
feedback |
feedback-ticket seam |
Each seam is a register_*_provider() / get_*() pair, so the product calls a
capability without knowing what implements it. The exception is settled_text,
a pure rule with no host-specific behaviour, imported directly.
Why it is published
A product repository has to be able to install this in isolation — in CI, and on a contributor's machine — without credentials for the platform's own repository. That is the whole reason it is a separate distribution rather than a package inside the backend.
Versioning
The contract is what other repositories pin, so a breaking change to a seam signature is a major bump. Adding a seam, or a field with a default, is a minor one.
Metadata
Release files for lucille-sdk 0.1.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 |
|---|---|---|---|---|
| lucille_sdk-0.1.0.tar.gz | 11.8 kB | With provenance | Details for lucille_sdk-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lucille_sdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lucille_sdk-0.1.0-py3-none-any.whl |
Total release size: 25.8 kB
Release files / lucille_sdk-0.1.0.tar.gz
| Download URL | lucille_sdk-0.1.0.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4416fdfe911a1cd9a2812a248cbaa6969fdde304cb728bb19e5cf40fb4a7de09
|
|
BLAKE2b-256 checksum How to use checksums |
931208fff64aab738baf9caf65613709a010ab109133b794637b213bd81d6596
|
| 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 Sep 11, 2026.
Transparency logRelease files / lucille_sdk-0.1.0-py3-none-any.whl
| Download URL | lucille_sdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e2f97136935b4309fe5c6f4eb9245c1549e585117155b7d25c222d6d5b78c9b
|
|
BLAKE2b-256 checksum How to use checksums |
de775458236649116037287fa5f5e354566c0a061293ba235236f3c8f50741f7
|
| 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 Sep 11, 2026.
Transparency logSecurity for lucille-sdk 0.1.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 lucille_sdk-0.1.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 Sep 11, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.