finledgerpoli

AI code review for financial software that keeps your code local and backs every finding with evidence.

Why finledgerpoli

• Hosted AI reviewers need your source; finledgerpoli runs on your machine and is offline by default. You approve anything that leaves it.
• AI findings can be wrong; reproduce them with your own checks and tie each one to the exact code version.
• AI spend is easy to lose track of; it enforces daily and monthly limits locally and shows spend against them.
• Suggested fixes can be risky; every patch needs your approval and can be rolled back. Nothing merges, deploys or trades by itself.

Who it's for

Built for developers of institutional financial software — rebalancers, optimizers, risk and tax-lot engines — where a one-cent rounding error or an unexpected change in trades is a real incident.

Why not a general AI code reviewer? Hosted reviewers ask you to send your code and trust their retention policies. finledgerpoli keeps review state and evidence on your machine, ties findings to the exact code version, and tracks estimated spend and unresolved charges locally. Remote providers receive the requests you explicitly approve.

Quick start

Python 3.11+ is required; Git is needed for source workflows. Install with pipx:

pipx install finledgerpoli
finassist demo
finassist init
finassist dashboard

In your own repository, finassist init --detect proposes a configuration from its committed layout, and your first run walks through a first review in five steps.

The package is finledgerpoli, the command is finassist (finledgerpoli also works). For an existing Python environment, pip install finledgerpoli is also supported. The demo needs no key, model download or container; it runs fictional finance checks, not a model-quality benchmark. The dashboard ships prebuilt, makes no external requests and binds only to 127.0.0.1; Node is needed only for frontend development.

From source

git clone https://github.com/EleutheroiEdge/finance-dev-assistant.git
cd finance-dev-assistant
python3 -m venv .venv
.venv/bin/python -m pip install .
.venv/bin/finassist demo
.venv/bin/finassist init
.venv/bin/finassist dashboard

On Windows PowerShell, use py -3 -m venv .venv, then .\.venv\Scripts\python.exe -m pip install . and .\.venv\Scripts\finassist.exe demo. No activation or execution-policy change is required. macOS/Linux use the commands above. See platform setup for UTF-8, permissions, Git modes and Docker Desktop details.

Upgrading

Use the package manager that installed finledgerpoli:

pipx upgrade finledgerpoli
uv tool upgrade finledgerpoli
python -m pip install --upgrade finledgerpoli

Upgrades never edit project configuration or evidence. Run finassist doctor after updating. finassist update status --json shows cached update information; finassist update --dry-run prints the detected command, and --yes explicitly runs it for a supported installation. Notices are off by default. Teams can pin a reviewed version, for example pipx install finledgerpoli==0.9.0, and roll back with pipx install finledgerpoli==0.4.0 --force. With uv use uv tool install finledgerpoli==0.9.0; with pip use python -m pip install finledgerpoli==0.9.0 in the intended environment.

For a release that includes a finledgerpoli-<VERSION>-requirements.txt asset, replace <VERSION> with the reviewed release number and use the intended Python environment (prefer a fresh virtual environment):

python -m pip install --require-hashes --only-binary=:all: -r "https://github.com/EleutheroiEdge/finance-dev-assistant/releases/download/v<VERSION>/finledgerpoli-<VERSION>-requirements.txt"
finassist doctor

The asset pins the exact release wheel hash and every runtime dependency. Earlier releases without this asset still require a consumer-maintained lock. pipx does not verify this requirements file; use pip for this hash-enforced installation.

Configuration and evidence migrations are separate explicit commands. After migrating evidence with 0.5.0 or later, a downgrade below 0.5.0 sees only the pre-migration evidence. Keep both files and restore the preserved backup for a full rollback; later observations are not merged automatically. See the upgrade guide or run finassist guide upgrading offline.

How it works

1. Plan: choose the exact commits, screen source and inspect what will be reviewed.
2. Review: use a finance, quant or custom checklist with your chosen model, or inspect risks offline.
3. Reproduce: run your approved checks against the committed source and compare the evidence.
4. Propose: inspect the exact patch, approve it and keep a guarded recovery copy.
5. Audit: save evidence for your change records, including approvals, spend and unknown outcomes.

Start offline from the repository you want to review, after inspecting its configuration and source policy:

finassist --config finassist.json plan --repo . --base main --head HEAD \
  --output .finassist/context.json
finassist --config finassist.json review --packet .finassist/context.json \
  --output .finassist/offline-review.json

Offline analysis does not claim a model review or test execution. Remote model use requires an explicit provider, model, endpoint, price assumptions, named key environment variable, network permission and approval of the exact outgoing request. There is no automatic provider fallback. See provider setup. Download the original terminal recording and play it locally with asciinema play docs/images/demo.cast.txt; no hosting account is needed.

Dashboard

All displayed spend, tokens, findings and review activity are fictional; these light-theme screenshots use an isolated synthetic fixture and call no provider.

Preview configuration changes before explicitly confirming a save; keys are shown only as present or absent.

See recorded spend against daily and monthly limits, pending charges, checks and review activity.

Inspect local configuration and capabilities without calling a model or testing a container daemon.

Use it with AI agents

Use the portable instructions with Claude Code, Codex and Cursor: agent guide. Point an agent at llms.txt to find the public guides. Run finassist guide agents for offline help; your project's rules and approvals still apply.

Guides

For unattended PR validation, use the GitHub Actions check gate. It runs approved isolated checks under a pinned policy from the PR's base revision and publishes a reduced job summary. Version-1 policies run deterministic checks only. A reviewed version-2 policy adds the policy-approved model review: the model step screens source and returns findings with file references; it reproduces nothing itself, posts no commit status or comment, and its spend limits are per run and per day against a retained state directory.

Safety and limits

• Advisory only. A valid report, plausible citation or matching hash does not prove a defect, correctness or professional suitability. Your project's specifications and authorized people own financial rules and approvals. Profiles guide reviews; they do not train model weights or confer professional credentials.
• Local-first, no telemetry. Offline is the default, regardless of existing keys. Uncommitted work is excluded. Remote reviews and GitHub inspection require explicit configuration and approval. Protocol compatibility tests use fake transports; not every model or service has been live-tested.
• Inspect outgoing content. Screening conservatively rejects common private, binary and sensitive formats, but cannot prove confidentiality. Inspect every outgoing request. There is no guard-bypass switch. Keep .finassist/, keys, client data and private artifacts out of Git.
• Execution needs a reviewed check. Container isolation depends on the image, daemon and host. Instructions and Python checks are not security sandboxes. Local execution requires explicit opt-in and has no OS filesystem isolation. The dashboard cannot run reviews, checks, shell commands, merges or deployments.
• Budgets are local estimates. Prices come from your configuration; limits are not provider-enforced billing caps. Unknown charges remain reserved across days and months and are not retried automatically. Missing usage is unknown, not zero. Pending charges and incomplete runs block a ready-for-review result.
• Evidence has limits. Review prerequisites grant no merge, deployment or financial authority. Local audit hashes cannot defeat a malicious rewrite of all state by the same user. Generated files need independent build verification; a green result cannot prove vulnerability absence.
• Recovery is guarded. Rollback refuses to overwrite later edits. Interrupted changes need reconciliation from the saved backup; multi-file changes and configuration saves are not atomic against other same-user writers. The local dashboard does not protect against other processes running as you.

Contribute

python -m pip install -r requirements-dev.lock
python -m pip install --no-deps --no-build-isolation -e .
python -m pytest -q
ruff check src tests scripts
finassist demo
finassist scan --repo .

Use synthetic fixtures and fake provider transports. See contributing, architecture and media reproduction. Forks must update repository links and maintainer settings. Posture badges describe repository settings; they do not establish vulnerability absence.

License

MIT licensed. See LICENSE.