For developers
Documentation your engineers never write, and can audit.
Sabí reads merged pull requests and linked tickets with read-only access, rewrites only the affected blocks, and runs documented flows against your test environment. Every block cites the commit or ticket it came from.
Book a technical sessionRecord a payment
Payments APIPOST /v1/invoices/{invoice_id}/payments
{ "amount": 250.00, "currency": "EUR" }Response{ "status": "partially_paid", "balance_due": 350.00 }Changed in 8.3: amount can be lower than the balance due. The invoice status becomes partially_paid.
From change #1147Backed by a ticket or change
Ledgerline is a demo company.
What triggers a run
- A merged pull request with a linked ticket.
- Changes to routes, API schema, UI strings or feature flags.
- Refactors that change no behaviour trigger nothing.
Two kinds of verification
Executable
Documented flows run against your test environment, with screenshots attached.
Evidence
Every conceptual claim is bound to a commit, ticket or file. Claims without a source are removed or flagged.
Checked in the productBacked by a ticket or changeNeeds a human lookDidn't work, held back
What the page says
Enter the amount you received and click Save.
What Sabí saw in Ledgerline
Record payment · INV-2031
Bakkerij de Vries
Amount received
€250.00
Invoice total €600.00
SaveChecked in the productChecked 2 minutes ago on a test version of Ledgerline · Replay
Ledgerline is a demo company.
Content model
- Pages are stored as blocks, not markdown files.
- Versions are immutable.
- Human edits are kept as overlays and survive regeneration.
- Export everything to Markdown whenever you want.
In the beta today
[Confirm list.]
On the roadmap
[Confirm list.]
See it read your repository.
One area, thirty minutes, with the verification report.
Book a technical sessionSabí
Product documentation that writes itself, then checks itself.