Rust/Python extensionpoly-kvv0.1.0-alpha.1

poly-kv-python

Optional PyO3 sidecar bindings for poly-kv bulk receipt experiments.

Inspect dependency lens ↓

01 · Documented scope

What this package says it does.

Optional PyO3 sidecar bindings for poly-kv bulk receipt experiments.

Package identitypoly-kv-pythonpoly-kv/crates/poly-kv-python

rust:poly-kv-python

Contract shapeFfi Binding

Library target · no binary target

Workspace positionPoly Kv

nested-poly-kv · not a root member

License declarationMIT OR Apache-2.0

Evidence source: workspace-inherited

02 · Capability surface

Recorded responsibilities.

These statements are preserved from package metadata and documentation recovered by the audit. They describe intended scope, not independent performance verification.

01
PyO3 native bindings
02
Python shape and block validation
03
bulk receipt experiments
04
maturin distribution surface

03 · Dependency lens

Position in the system.

The graph distinguishes outgoing sibling dependencies, derived inbound dependents, and explicitly recorded related packages. Lines describe catalog relationships—not execution order or runtime activation.

Depends on · 1

poly-kvCompression, vector storage, and evaluation

Used by · 0

No inbound sibling dependency was derived from this catalog.

Recorded as related · 0

No additional related package was recorded.

04 · Package contract

Features, targets, and workspace state.

Manifest-level facts remain separate from documentation claims and registry observations, keeping each evidence source legible.

A / TARGETSMANIFEST AUDITED

Library target: Yes
Binary target: No
Package README: No
Root workspace member: No
Root default member: No
Excluded from root: Yes

B / FEATURE GROUPS0 RECORDED

No named Cargo feature groups were recorded.

05 · Publication evidence

Cargo publishing allowed · no owner match.

Cargo permits publication, but no exact RecursiveIntell-owned crates.io release appears in the observed registry inventory. Permission is not proof of publication.

Evidence state key: unverifiedManifest publish: Not applicable / not establishedCargo publish allowed by default: YesRegistry history present: NoRegistry ownership verified: Not applicable / not establishedExact-name registry match: Not applicable / not established

No publish=false gate is declared; this does not prove the package is published to crates.io.

06 · Maturity and limits

Signals with their boundaries intact.

Maturity is a catalog status supported by observed signals. It is not a security review, service-level commitment, correctness proof, or suitability determination.

StatusExperimental Alpha

Version 0.1.0-alpha.1.
Crate-level docs/manifest used because README is absent.
Maintained in a nested/excluded workspace.

Known limitations2 recorded

No package README was found; scope is derived from manifest metadata and crate-level documentation.
Alpha optional sidecar; the Python distribution is declared through poly-kv/pyproject.toml.

Update evidenceMay 28, 2026

Phase 3: P3-polykv — poly-kv workspace merge

Method: repository commit search matched the package name
Matched SHA: a2cee0a501d8d9182f081cbcacedb1054a5fbafb

Commit-search evidence is package-name based and may not equal the exact last path modification.

Inspect matched commit ↗

07 · Source trail

Continue the inspection.

RecursiveIntell/Libraries is private; monorepo source links require authorization.

ATLAS EVIDENCE BOUNDARY

Package manifests, package READMEs, crate-level docs, workspace status files, and package-name commit search. No source implementation bodies or secrets are reproduced.

p32-schema-compat / 011027f77fc7a53c6ecb05300d5c34144370fa3b

RESOLVING ROUTEFollowing the evidence boundary…

Cargo publishing allowed · no owner match.

Cargo permits publication, but no exact RecursiveIntell-owned crates.io release appears in the observed registry inventory. Permission is not proof of publication.

No publish=false gate is declared; this does not prove the package is published to crates.io.