-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
Tiana_ edited this page May 30, 2026
·
1 revision
Public release plan. Approximate dates, not commitments. Updated quarterly.
| Release | Date | Theme | Status |
|---|---|---|---|
| v0.1.0 | 2026-06-30 | Ledger Foundation | Active |
| v0.2.0 | 2026-08-15 | Payments + Decision Engine | Planned |
| v0.3.0 | 2026-10-31 | Compliance + AI Copilot | Planned |
| v0.4.0 | 2026-12-31 | Sandbox UI + SDKs + DX | Planned |
| v1.0.0 | 2027-Q2 | Production-stable | Planned |
| v1.5.0 | 2027-Q4 | TigerBeetle, ISO 20022, Reporting | Tentative |
| v2.0.0 | 2028+ | Commercial layer | Tentative |
Includes:
- Double-entry ledger (accounts, transactions, entries, balances)
- Time-travel balance queries (Killer Feature)
- Idempotency on all writes
- Outbox pattern foundation
- Sandbox bank adapter
- Helm chart, docker-compose
- Observability (Prometheus + OTel + Grafana dashboards)
- OpenAPI 3.1 spec
Tested with:
- Property tests (1000-iteration invariants)
- Concurrency tests (100 concurrent posters)
- Performance: 1000 tx/sec sustained, p99 < 300ms
Sprint plan: Sprint-01-Ledger-Foundation Epic: Epic-01-Ledger
Includes:
- Full payment lifecycle (initiate, retry, cancel, webhook callback)
- Outbox dispatcher + Kafka event flow
- Decision Engine standalone (also published as Maven library)
- LLM-powered rule synthesis (optional plug-in)
- Replay mode (run new ruleset against historical decisions, diff)
Standalone repo: tiana-code/decision-engine extracted from main repo
Includes:
- KYC orchestration framework + sandbox provider
- AML rules engine (uses Decision Engine)
- Compliance case management (operator workflow)
- AI AML Copilot plug-in (LLM explains alerts, drafts SAR/STR drafts)
- Time-travel ledger query end-to-end (already in v0.1, polished)
- Replay Mode for Decision Engine
- GDPR Compliance Engine foundations (Killer Feature #6)
- Compliance-as-Code GitOps pattern (Killer Feature #2)
Includes:
- React 19 sandbox dashboard (account browser, transaction explorer, payment initiator, decision log viewer, compliance case board)
- CLI tool
fincorefor local management - Kotlin SDK (
com.fincore:sdk-kotlin) - TypeScript SDK (
@fincore/sdk-typescript) - Postman / Insomnia collection
- Docs site (Docusaurus on GitHub Pages)
- ISO 20022 PACS.008 mapping (preview)
- Webhook subscription test harness
Includes:
- Public SLO commitments
- Penetration testing complete
- SOC 2 Type II readiness checklist
- Multi-region pattern documented (active-passive)
- DR drill runbook validated
- Auto-regulatory-reporting (SAR/STR drafts) - Killer Feature #9
- Tamper-evident audit trail (HMAC chains) - Killer Feature #12
- Plug-in marketplace launch (alpha) - Killer Feature #13
Includes:
-
TigerBeetle adapter (
fincore-tigerbeetle-adapterseparate repo) - ISO 20022 native (PACS.008, PAIN.001, CAMT.053) - Killer Feature #7
- Auto regulatory reporting full
- Multi-region active-active (preview)
Possible includes (if community signals demand):
- FinCore Cloud (managed SaaS)
- Enterprise support contracts
- Multi-region active-active stable
- AI Reconciliation (Killer Feature #16)
- Embedded LLM customer support
This is hypothetical pending Y1-Y2 traction.
| Year | Theme |
|---|---|
| 2026 | MVP + Decision Engine + Compliance |
| 2027 | Production-stable + advanced features (TigerBeetle, ISO, reporting) |
| 2028 | Commercial layer if warranted |
| 2029 | Multi-region, marketplace, ecosystem |
| 2030 | License auto-conversion: v0.1.0 → Apache 2.0; subsequent releases roll over |
| 2031+ | Maintenance + community-driven features |
- No Multi-tenancy (deployment-level only - see Vision)
- No Mobile SDKs (web SDK is enough for our audience)
- No Crypto/digital asset custody (out of scope, requires regulatory presence)
- No Frontend for end users (adopter responsibility)
- No Card processing primitives (delegated to card processors)
- No FX rate management (delegated to bank providers)
- No Hosted SaaS until v2.0 (commitment)
If you need any of the above, FinCore Engine is the wrong choice; consider Modern Treasury, Adyen, or build it yourself on top of FinCore.
- Reliability / SLO impact (reliability work prioritized when error budget burns)
- Maintainer priorities (opinionated, based on architectural soundness and project health)
- Community input (GitHub Issues and Discussions weighted by participation)
- Adopter feedback (direct feedback via SECURITY.md email)
- Sponsor input (GitHub Sponsors at higher tiers)
No "vote" system - maintainer-driven with transparent rationale.
Roadmap reviewed at end of each quarter:
- 2026-Q2 (Jun 30): post v0.1.0 launch
- 2026-Q3 (Sep 30): post v0.2.0
- 2026-Q4 (Dec 31): post v0.3.0 + v0.4.0
- 2027-Q1: pre-v1.0 prep
Each review:
- Update dates based on actual progress
- Add new tickets surfaced from community
- Re-rank priorities
- Document deviations in release notes or status page update
- Vision - long-term direction
- Epics - work breakdown
- Sprint-01-Ledger-Foundation - current sprint
- CHANGELOG.md - what shipped (auto-generated)
- Overview
- Services
- Data Model
- Domain Model
- Event Flow
- Security
- Observability
- Resilience
- SLA / SLI / SLO