fleet-stitch — Constraint Manifold Projection for Model Communication
Project model activations to the Eisenstein constraint manifold. Communicate between models without tokenization.
Why
Latent space translation lets models share thoughts at the vector level. But learned latent spaces drift, are model-specific, and are black boxes.
The Eisenstein constraint manifold is:
- Mathematically defined (not learned)
- Deterministic (same activations → same manifold point)
- Cross-model (any model can project to it)
- Discrete (integer arithmetic, no float drift)
- Interpretable (every point has algebraic meaning)
How It Works
- Fit: Learn affine transform from model activations → manifold (one-time)
- Project: Any activation → Eisenstein integer (a, b) on the lattice
- Communicate: Transmit (a, b) instead of the full activation vector
- Inverse: Receiving model projects back to its own activation space
The Stack
Model A activations (4096-dim)
→ affine_A (2-dim Eisenstein point)
→ transmit (2 integers)
→ affine_B_inv (4096-dim)
→ Model B continues reasoning
Composable With
- casting-call-gpu (Oracle1): voice signatures → manifold coordinates
- plato-vector-persistence: store manifold points alongside embeddings
- fleet-constraint-kernel: GPU-accelerated batch projection
- temporal-flux: T_SNAP opcode snaps manifold projections
- physics-clock: temporal dimensions on manifold points
- insight-cfp-bridge: share manifold discoveries as FLUX tiles
Install
pip install fleet-stitch
Quick Start
from fleet_stitch import ManifoldProjector, StitchRegistry
# Fit a projector for your model
proj = ManifoldProjector(input_dim=4096)
proj.fit(training_activations, known_constraint_states)
# Project new activations to manifold
manifold_points = proj.project(new_activations) # (N, 2) integer array
# Register for cross-model stitching
registry = StitchRegistry()
registry.register('my_model', 'manifold', proj)
# Stitch from one model to another
target_activations = registry.stitch('model_a', 'model_b', source_activations)
License
Apache 2.0
Metadata
Release files for fleet-stitch 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 |
|---|---|---|---|---|
| fleet_stitch-0.1.0.tar.gz | 5.3 kB | Without provenance | Details for fleet_stitch-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fleet_stitch-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for fleet_stitch-0.1.0-py3-none-any.whl |
Total release size: 10.0 kB
Release files / fleet_stitch-0.1.0.tar.gz
| Download URL | fleet_stitch-0.1.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c37e392719ae47ede773eeb69149169e6fafac1f5637d3b4254b3ad6d60ead9
|
|
BLAKE2b-256 checksum How to use checksums |
2c129b59d17c3fb1025c39feee0f9126505020e23405efc8f1c08f8f44a747e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / fleet_stitch-0.1.0-py3-none-any.whl
| Download URL | fleet_stitch-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c27e645be17a0dccbc1df2f61a53ce6c440fbc7b4abc51d1b5e3a313400810f6
|
|
BLAKE2b-256 checksum How to use checksums |
87f13c370321744215a393ebf17f93acdd37930d0aafba1d9e240246a35efc0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for fleet-stitch 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.
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.