Optional native Python Core–FogVault owner
datafog_fogvault is a separate 1.0.0 ABI3 extension for Python
3.10+. It delegates persistence, session authority and save/activation to the
existing Rust datafog-fogvault-native::Owner; it does not load browser WASM,
duplicate encryption, or change the existing datafog_core Python package.
Install datafog-fogvault==1.0.0 from PyPI. The Linux x64 wheel requires glibc
2.34 or later; native macOS ARM64 and Windows x64 wheels are also qualified.
python -m pip install datafog-fogvault==1.0.0
Its qualification build uses Rust 1.94.1, while Core keeps its Rust 1.88 floor.
Create, save and reopen
import secrets
from datafog_fogvault import NativeWorkspace
tenant = "private-routing-id" # Host authentication/authorization is separate.
record_id, namespace = secrets.token_bytes(16), secrets.token_bytes(16)
owner = NativeWorkspace.create_new(
tenant, protected_control_path, vault_path, password_bytes,
record_id, namespace, secrets.token_bytes(16), secrets.token_bytes(16),
)
text = "Email alice@example.test"
finding = {"entityType": "EMAIL", "matchedText": "alice@example.test",
"range": {"unit": "utf8_bytes", "start": 6, "end": len(text)}}
plan = owner.prepare_review(tenant, [{"text": text,
"scannerFindings": [finding], "userSelections": []}], secrets.token_bytes(16))
show_local_review(plan.previews(tenant))
# The application must obtain approval of this exact still-current review.
saved = owner.commit(tenant, plan, True, secrets.token_bytes(16))
show_approved_copy_surface(saved["previews"][0])
owner.close(tenant)
owner = NativeWorkspace.open_existing(
tenant, protected_control_path, vault_path, password_bytes,
record_id, namespace, expected_head=saved["head"],
)
assert owner.restore(tenant, saved["previews"][0]) == text
owner.close(tenant)
Review/copy functions and credential input are host application code. Sources, returned strings and all foreign copies remain the application's cleanup duty. No method sends a message or proves remote delivery.
The host must establish an independently protected control namespace, separate
from the attacker who may replace vault files. Two different paths alone do not
provide that isolation. create_new requires a new control namespace and new
vault; it never silently opens existing files. open_existing requires both
existing stores. Failed creation can leave an empty newly created control
namespace; no existing vault is deleted or overwritten to repair it.
This release supports password-only admission with the existing baseline
KDF, 16 MiB payloads, 88-byte binding metadata and 64 records. Those are explicit
host admission settings, not a hardware guarantee. profile defaults to
password_only; other profiles reject unsupported_profile before creation.
Device/provider and recovery-factor custody are not implemented by this Python
binding and never fall back silently to passwords. The records still use the
shared DFVBRG01 namespace/record/complete-head binding.
Values, ownership and failure
- Every instance/plan/stream method requires the exact original opaque tenant
string, and executes only on its creator OS thread. Invalid routing returns
wrong_tenant; wrong-thread use returnswrong_thread, without PyO3's unsendable-object panic. Tenant strings are routing assertions, not proof of authentication; the host owns tenant-to-path authorization. - No raw Workspace, FogVault, plaintext bundle export or prepared-plan import is exposed. Plans belong to one owner; foreign or consumed plans reject. Lock, close and owner garbage collection revoke retained plans/streams. Calls are synchronous on the calling Python thread and hold the GIL.
- Approval must be the literal Python
True, not1, truthy objects or strings. A known rejected approval does not save. Confirmed save precedes activation; only successfulcommitreturns approved handoff text. - IDs are exact, nonzero 16-byte Python
bytes.WorkspaceHead.revisionis a lossless Pythonint; construction rejects bool, float, string, negative and overflowing values. Commit IDs are exact 16-byte bytes, with no lossy numeric transport. Heads are immutable. Passwords are bytes, never normalized strings. - Nested findings/review/operation/conversation dictionaries use the current Core camelCase fields and zero-based, end-exclusive byte/code-point/UTF-16 ranges. The findings transport accepts exact built-in dict/list/scalar values, not arbitrary objects/accessors. It bounds depth to 32, dictionary keys to 100, list entries to 100,000, total nodes to 1,000,000 and logical strings/nodes to 16 MiB. Core applies its own semantic and resource bounds afterward. Bytes in dictionaries represent only fixed 16-byte IDs; bundle/feed bytes have separate bounded transports. These logical bounds are not a peak-memory SLA.
FogVaultWorkspaceErrorexposes a content-freecode. Core failures retain finding/input indexes, marker ranges and review conflicts. AnOutcomeUnknownorsaved_but_not_activatederror includes its exactrequest_idbytes. Error messages do not copy passwords, paths, source text or raw provider details.
reconcile(tenant, request_id) reconciles the retained owner without reactivating
Core. After process restart, NativeWorkspace.reconcile_existing(tenant, control_path, vault_path, request_id) returns only an exact receipt from the
registered vault; it grants no decrypted Core owner or plaintext. Authenticate
and open_existing afterward, then prepare and approve fresh work. Never infer
rollback, automatically replay an old approved mutation or resend transport.
Conversations, streams and recovery
Use prepare_conversation_send, retain plan.send_intents, commit its pending
state, then hand off. Only a trusted host observation of the exact attempt
permits prepare_observed_send, followed by its own approved save. Timeouts stay
pending; prepare_definitely_not_sent needs actual non-delivery evidence.
Scoped restore and its streams delegate Core's pending/wrong-chat checks.
restore_stream(tenant, encoding="utf8", progressive=False, logical_id=None)
returns an opaque owned stream. UTF-8 feeds require bytes; UTF-16 feeds require
exact integer lists without bools/floats or out-of-range units. Strict buffering
releases no feed text. Progressive mode is explicit and irreversible; terminal
errors retain actual delivered counters and complete=False, with no failed-call
text. Malformed feed transport is rejected through Core's opposite-encoding
failure path so it terminates the response rather than silently skipping data.
Explicit reset starts a fresh response at the same admitted head; it does not
undo output already returned.
import_authenticated_bundle requires a separately authenticated/decrypted Core
bundle, its expected namespace/full head, a fresh recovery operation, and literal
approval. It delegates source recovery staging to the shared migration helper,
creates fresh destination stores/keys and publishes through Rust Owner. The
source archive is unchanged. It neither decrypts legacy backup files nor defines
future v1 snapshot bytes. No recovered result grants transport permission.
The public stub lists the current subset: ordinary/batch/combined review, policy changes, recovery, conversation preparation/confirmation, scoped/unscoped reports and streams, counts/history/operations, and reconciliation. The original Core Python SDK remains available for other Core operations; this package does not claim every Rust Owner convenience method is exposed yet.
Build and installed proof
Use the declared toolchain and build an actual wheel, then install it into a Core-owned isolated environment:
RUSTUP_TOOLCHAIN=1.94.1 maturin build --release --locked \
--manifest-path integrations/fogvault-python/Cargo.toml \
--out integrations/fogvault-python/dist
python3 -m venv target/fogvault-python-venv
target/fogvault-python-venv/bin/python -m pip install --no-index integrations/fogvault-python/dist/*.whl
target/fogvault-python-venv/bin/python -I integrations/fogvault-python/tests/test_installed.py
On Windows use the venv's Scripts/python.exe. The installed tests execute the
actual compiled module and registered SQLite adapter with synthetic data. They
cover persistence/reopen, Unicode coordinates, literal approval, tenant/thread
and foreign-plan isolation, writer conflicts, recovery, conversations, stream
revocation/failures, malformed inputs and receipt-only restart reconciliation.
They do not qualify physical providers, power cuts, every OS/Python version,
real shipping-host authentication, registry publication, or production security.
If Python result conversion fails after a confirmed save, the owner and its
children are revoked. The best-effort error has code="outcome_unknown", the
exact request_id, and requires_reopen=True; reconcile the request and reopen
instead of retrying the change. Tests cover ordinary confirmed saves and reopen;
they do not force allocation exhaustion or guarantee reporting after process OOM.
Only one prepared change may be active per integrated owner. A second preparation
returns resource_limit before Core clones its state. Discarding, dropping or
consuming the change releases the slot even if an older wrapper remains retained;
closing the owner revokes all its authority. Read-only review and restore streams
remain available. This is a per-owner plan limit, not a global memory budget; see
combined resource observations.
Metadata
Release files for datafog-fogvault 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datafog_fogvault-1.1.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for datafog_fogvault-1.1.0-cp310-abi3-win_amd64.whl |
| datafog_fogvault-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.34+ x86-64 | Details for datafog_fogvault-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl |
| datafog_fogvault-1.1.0-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for datafog_fogvault-1.1.0-cp310-abi3-macosx_11_0_arm64.whl |
Total release size: 7.9 MB
Release files / datafog_fogvault-1.1.0-cp310-abi3-win_amd64.whl
| Download URL | datafog_fogvault-1.1.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c11fde39ca4edfb9d7e891854cf7feb3325dada14e49150467305d5f2abd56b1
|
|
BLAKE2b-256 checksum How to use checksums |
fed904ef6c0785d03fbabb1a19f9759ad556fc845eb0bca050f15f5c5650fea4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / datafog_fogvault-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl
| Download URL | datafog_fogvault-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
01836597f17d15422389ba6d14d554bfdca7f0ca78385bc13598fefc5bee524d
|
|
BLAKE2b-256 checksum How to use checksums |
d22ee0f26bdd0505c9901bb1589e47052dee0c6bf212ce0727c49a1010ec95b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / datafog_fogvault-1.1.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | datafog_fogvault-1.1.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
5dd1caf9ff9f6521694305f6d2932a04fdf736378812f18801c1be4022e21aed
|
|
BLAKE2b-256 checksum How to use checksums |
e05519481596a7730fe01a47891689e194077a104c31dc2d8c25d1f0bf99ce30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logSecurity for datafog-fogvault 1.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 3 files in this release have been uploaded with provenance metadata.
Attestation for datafog_fogvault-1.1.0-cp310-abi3-win_amd64.whl
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 Nov 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.