orditect-adapter-local
Local-file reference implementation of the
orditect-protocol storage contracts (document-family).
Purpose
- Document-family representative for the protocol 1.0 freeze criterion.
- Zero-infrastructure backend: the full recovery/governance plane runs against plain files — no Redis, no database, no services.
- First producer of the trace bundle data form: a directory layout of ndjson envelope rows + JSON payloads, readable by any consumer without importing orditect.
Layout (trace bundle form)
<root>/
snapshots.ndjson # op envelope rows: {"v","op","ts","data"}
audit.ndjson # op "append"
deps.ndjson # op "edge_write"
results/<stream_id>.json
content/sha256/<aa>/<digest> # content-addressed blobs
content/sha256/<aa>/<digest>.meta.json
Writers are single-process and write-atomic (tmp file + rename). Readers fold the ndjson streams into their query views on access.
Capability declaration
concurrency_domain = "process" (T10 Revision 0.1.2): the atomicity
guarantee holds within one process (guarded by an asyncio lock). A second
process may read/write the same directory, but cross-process atomicity is
NOT declared.
Scale boundary
Designed for ~10k-row scale per stream file (read-path folding is O(n)). This is the document-family reference — not a production-scale store.
Structure
store = LocalFileStore("/path/to/dir")
store.content # ContentWriter + ContentReader
store.audit # AuditWriter + AuditReader
store.result # ResultWriter + ResultReader
store.snapshot # SnapshotWriter + SnapshotReader
store.dependency # DependencyWriter + DependencyReader
Each part is independently usable and exposes its own capabilities
property, mirroring the per-domain-part structure of the memory adapter.
Durability & append semantics
atomic_write_*(content blobs, result manifests) uses tmp-file + rename: readers never observe a partially written file.- ndjson appends (snapshots / audit / deps) are best-effort: a crash mid-append may lose the tail row. Torn tail rows are skipped silently on read (by design, matching append-only log semantics).
- The adapter does not fsync. For crash durability, use the PostgreSQL adapter. This is a development / small-scale reference backend.
- Read paths fold streams on access (O(n) per query); write paths that dedup or guard scan the stream first (O(n) per write). Sized for ~10k rows per stream file, not production scale.
Metadata
Release files for orditect-adapter-local 0.1.7
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 |
|---|---|---|---|---|
| orditect_adapter_local-0.1.7.tar.gz | 17.8 kB | With provenance | Details for orditect_adapter_local-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| orditect_adapter_local-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for orditect_adapter_local-0.1.7-py3-none-any.whl |
Total release size: 36.1 kB
Release files / orditect_adapter_local-0.1.7.tar.gz
| Download URL | orditect_adapter_local-0.1.7.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38d1c72e90a240333b4ae7e4377aae095fcebf97bbe0fdab2675a7f96bc6169a
|
|
BLAKE2b-256 checksum How to use checksums |
796905cef393d5874736c13bba67433eb3352c796514db5b7315fc7d938ffbd3
|
| 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 22, 2026.
Transparency logRelease files / orditect_adapter_local-0.1.7-py3-none-any.whl
| Download URL | orditect_adapter_local-0.1.7-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ad7ffff633d028c8c7533f4812799a6de335e8ed1fe431bc4ffd88277d44f15
|
|
BLAKE2b-256 checksum How to use checksums |
2def4fc2fabe4ed0b18c958ce8c9540bbd5e1588664384c3c9ef5a5fd1d2adcf
|
| 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 22, 2026.
Transparency logSecurity for orditect-adapter-local 0.1.7
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
Both files in this release have been uploaded with provenance metadata.
Attestation for orditect_adapter_local-0.1.7.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 22, 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.