blaze/libra
1
0
Fork 0
forked from aiolabs/libra
Code Pull requests Activity

Clean up awkward "the Libra" phrasing left over from rename

Browse source 
Replaces entity-sense references to "the Libra" with "the
organization"/"the collective" where Libra was being used as a
stand-in for the original "Castle" entity, and drops the redundant
"(like cooperatives)" parenthetical in DOCUMENTATION.md. Also swaps
the 🏰 emoji in the import helper for ⚖️.

Closes #12

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Padreug 2026-05-07 08:37:30 +02:00
commit b2b2c109a4
9 changed files with 22 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/DOCUMENTATION.md
View file

@ -2,7 +2,7 @@
## Overview
The Libra extension for LNbits implements a double-entry bookkeeping system designed for cooperative/communal living spaces (like cooperatives). It tracks financial relationships between a central entity (the Libra) and multiple users, handling both Lightning Network payments and manual/cash transactions.
The Libra extension for LNbits implements a double-entry bookkeeping system designed for collectives like co-living spaces, makerspaces, and community projects. It tracks financial relationships between a central organization and its members, handling both Lightning Network payments and manual/cash transactions.
## Architecture
@ -411,10 +411,10 @@ Created by `m001_initial` migration:
- `cash` - Cash on hand
- `bank` - Bank Account
- `lightning` - Lightning Balance
- `accounts_receivable` - Money owed to the Libra
- `accounts_receivable` - Money owed to the organization
### Liabilities
- `accounts_payable` - Money owed by the Libra
- `accounts_payable` - Money owed by the organization
### Equity
- `member_equity` - Member contributions
@ -1210,4 +1210,4 @@ The Libra extension provides a solid foundation for double-entry bookkeeping in
5. Equity management features
6. External system integrations (accounting software, tax tools)
The refactoring path is clear: prioritize data integrity, then add reporting/export, then enhance with advanced features. The system is production-ready for basic use cases but needs the recommended enhancements for a full-featured cooperative accounting solution.
The refactoring path is clear: prioritize data integrity, then add reporting/export, then enhance with advanced features. The system is production-ready for basic use cases but needs the recommended enhancements for a full-featured collective accounting solution.