Preserve what the model depends on
The application organizes statement evidence, repayment scenarios, recurring reviews, and budget overlays. In hosted mode, a ledger document contains editable state while source PDFs and workbooks are stored as separate checksum-verified blobs.
Updates use strong reads and compare-and-set. Prior revisions are retained, and an old revision receives a conflict instead of replacing newer work. The original local JSON workflow remains available separately.
Import is a controlled transition
Preparation produces an ignored manifest and verifies source checksums without network access. Hosted import is create-only and refuses to overwrite an existing ledger or evidence object. Originals remain available until the imported files have been checked.
Health distinguishes a running application from one that has received its private evidence. That avoids confusing successful deployment with completed data migration.
Create-only import requests include checksums and request protection. A successfully running release with no imported evidence reports that condition rather than seeding invented financial data.
Preserve evidence without moving money
The service initiates no payments or financial API calls. It models source evidence and editable scenarios while retaining the documents on which those scenarios depend. Arithmetic checks answer a narrower question than a live balance confirmation. Keeping that distinction visible makes the workspace useful for review without presenting a local model as a lender's current record.