unitbook
status: pre-alpha
A standalone, offline, harness-agnostic ledger for one pooled trading account with several investors. It answers one question exactly: if this investor withdrew today, how much would they receive — and can they prove it?
- Pure Python package. No server, no database, no bot, no TUI, no vendor SDK, no network call in the core.
- Append-only, hash-chained, signed event log → per-lot units → NAV per unit → performance fee by unit burn → per-investor statements in the trader's own spreadsheet layout.
- Every number is reproducible from the log with no model in the loop. Agents drive it; they never compute it.
Install
Distribution channel is not finalized yet — see docs/gitops/RELEASING.md. For
now, run from source:
uv sync
uv run unitbook
Operator
Two commands, both outside the licensed surface — admin is dispatched before the verb
parser and never appears in schema, the MCP tool list, or AGENTS.md:
UNITBOOK_OPERATOR_SEED=$(pass unitbook/operator-seed) unitbook admin issue --holder "Вася" > license.json
unitbook admin revoke <license_id> --root .
revoke edits the source tree (adds the id to revoked.json, bumps the patch version in
pyproject.toml and src/unitbook/__init__.py) and prints the tag command; it does not run
git, tag or push. Tagging and pushing the release stay a deliberate second action.
License
Proprietary. Copyright (c) 2026 Gesamt Team. Licensed to named users only; see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for unitbook 0.1.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 | Reset |
|---|---|---|---|---|
| unitbook-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / unitbook-0.1.0-py3-none-any.whl
| Download URL | unitbook-0.1.0-py3-none-any.whl |
|---|---|
| Size | 124.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f76ac90fe10c51a23854bf59ac112be0b91011f89ea4577bac19d54dcd379ba
|
|
BLAKE2b-256 checksum How to use checksums |
75762ab57ab1c3f1f5fabb20c3aba8b4dde537f76c7214b066f074d7fe97c60a
|
| 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 3, 2026.
Transparency log
