Complete specification for rewriting Swarmops v5 as using.cash v6: - Proposal: scope buckets (Working Rewrite / First Beyond Working / Maybe), non-goals (governance, geography, memberships permanently cut) - Design: 18 architectural decisions including preserved patterns (Basic/Logic, stored procs, credential split), new patterns (repository classes, chain abstraction, rate providers), and operational concerns (Galera awareness, continuation transactions, VAT booking, OOD denormalization) - Specs: 17 capability specifications with SHALL/MUST requirements and WHEN/THEN scenarios, covering accounting core, AP/AR, crypto treasury, exchange rates, organizations, users/auth, documents, comms, dashboard, end-of-month, backend worker, event bus, data migration, API layer, frontend app, and CI/packaging - Tasks: 145 implementation tasks grouped by subsystem, ordered by dependency (migration gates API/frontend work) Two rounds of adversarial review incorporated. Made-with: Cursor
27 lines
1.4 KiB
YAML
27 lines
1.4 KiB
YAML
schema: spec-driven
|
|
|
|
context: |
|
|
Legacy codebase "Swarmops" being modernized as "using.cash" (v6).
|
|
Originally a Pirate Party membership register (~20 years old), pivoted to crypto-centric accounting.
|
|
|
|
Current stack: C# on .NET Framework 4.5.2 / Mono, ASP.NET WebForms frontend, MySQL, hand-written ADO.NET (SwarmDb partial class), stored procedures for all writes, read/write/admin credential split.
|
|
|
|
Target stack: C# on .NET 8+ / ASP.NET Core (backend), React + Material UI + TypeScript + Vite (frontend), MySQL, Gitea Actions CI, Docker.
|
|
|
|
Namespace rename: Swarmops.* → UsingCash.*
|
|
|
|
Key preserved patterns: Basic/Logic two-tier inheritance, PluralBase<T> collections, stored procedure writes, read/write/admin DB credential split, Money as Int64 smallest-units, exchange rates via BTC hub.
|
|
|
|
Domain: double-entry accounting, AP/AR, crypto treasury (BCH-first, abstractable), multi-tenant organizations, RBAC.
|
|
|
|
v5 database preserved untouched; v6 gets a clean schema via one-time ETL migration. Closed ledger periods are legally presentation-immutable.
|
|
|
|
rules:
|
|
proposal:
|
|
- Reference the three scope buckets (Working Rewrite, First Beyond Working, Maybe/Later)
|
|
- Include a Non-goals section for permanently cut features
|
|
tasks:
|
|
- Group tasks by subsystem (database, backend, frontend, migration, CI)
|
|
- Each task should be independently implementable and testable
|
|
- Prefer smaller tasks that can be completed in a focused session
|