Lattica Build
lattica-build is the pipeline-construction SDK for Lattica workloads.
Use it to define a homomorphic computation graph, attach required tensors/constants, validate metadata compatibility before execution, and emit a deployable artifact.
This package is for pipeline construction only. Use lattica-studio for deployment
and runtime lifecycle operations.
Clear execution is also available locally through HomOp.forward_clear(...) and
HomomorphicPipeline.forward_clear(...). It uses ordinary torch tensors and the
data attached to operators, and does not modify or serialize the homomorphic graph.
Pass the same HomParams used for the build when clear execution is
packing-sensitive.
Installation
Requirements:
- Python
>=3.11
Install:
pip install lattica-build
What this produces
The output is a serialized pipeline artifact (zip) containing:
hom_pipeline.jsonhom_pipeline.safetensors
You hand this artifact to lattica-studio.
60-second quickstart
Build the packaged branching example:
lattica-build --pipeline-module lattica_build.examples.advanced.branching --out /tmp/quickstart_branching.zip
Expected result:
- command exits successfully,
/tmp/quickstart_branching.zipexists,- command prints a JSON summary including members
hom_pipeline.jsonandhom_pipeline.safetensors.
First-time docs path
| Topic | Doc |
|---|---|
| Repository overview and end-to-end workflow | ../README.md |
| Quickstart and runnable examples | examples/README.md |
Pipeline API and data binding (HomomorphicPipeline, set_data, serialization) |
base_classes/README.md |
| Operator composition model | operators/README.md |
| Level/scale budget planning | params/README.md |
Python API
The same build flow is available without the CLI:
from lattica_build import build
from lattica_build.examples.advanced import branching
artifact = build(
branching.Pipeline().build_pipeline(),
branching.Pipeline().build_params(),
"branching.zip",
display_graph=True,
)
print(artifact.path)
build(...) returns a BuildArtifact; pass that object directly to
LatticaStudio.deploy(...).
Build-to-deploy workflow
- Build and serialize a pipeline with
lattica-build. - Pass the artifact to
lattica-studio. - Use
lattica-studiofor deployment/runtime lifecycle operations.
Metadata
Release files for lattica-build 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lattica_build-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for lattica_build-0.5.0-py3-none-any.whl |
Release files / lattica_build-0.5.0-py3-none-any.whl
| Download URL | lattica_build-0.5.0-py3-none-any.whl |
|---|---|
| Size | 30.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8a1d10aa2ba3de86596c122d2c6a181fc38a679c9cc15be52f7fed46f0effde5
|
|
BLAKE2b-256 checksum How to use checksums |
b4adef74a4a278eb4d3aeaffa27b3cf64e4d6911202998f7a1aad9179824f04d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.7.12
|
Security for lattica-build 0.5.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.