Near term
Treasury operations
- Tighten policy enforcement across vault, proposal, and stream workflows.
- Stronger treasury activity review, exports, and operational reporting.
- Cleaner organization workspace handoff into shared create and execution flows.
Streams and payroll
- Expand stream history, batch history, and audit views.
- Better recurring payroll controls and treasury-linked operating views.
- Document and expose the supported stream family set across product and docs.
Governance operations
- Proposal templates for treasury payouts, grants, and budget motions.
- Connect proposal review to downstream treasury execution and audit traces.
- Role-aware governance workflows in the organization workspace.
Protocol expansion
Schedule families
- More contract-backed schedule families beyond the current linear, hybrid, recurring, milestone, and bounded-tranche set.
- Treasury-controlled stream operations that improve the BCH covenant model without hiding state transitions.
Distribution and treasury scale
- Larger and more operationally friendly distribution sets.
- Better batch execution paths across treasury-linked covenant families.
- Stronger multi-asset treasury handling for BCH and CashTokens.
Verification and tooling
- Expand artifact-based contract verification.
- More scripted live-smoke coverage for networked test environments.
- Better developer-facing tooling around deployment, auditability, and integration.
Product infrastructure
API and indexing
- Stronger server-side filtering and pagination across high-volume treasury and stream feeds.
- Better organization-scoped history surfaces and exportable audit views.
- More stable developer-facing interfaces for integrations and internal tooling.
Operator tooling
- Richer alerts for treasury movements, stream changes, and proposal state transitions.
- Cleaner operator dashboards for roles, activity, and execution readiness.
- More complete operational views for batch history and stream lifecycle monitoring.
Longer-term research
These items stay research-heavy and only move forward when both the BCH covenant model and the product need are clear:- Privacy-preserving treasury and payroll disclosures.
- Oracle-aware accounting or denomination layers where they materially improve treasury operations.
- Advanced custom schedule modeling beyond the current bounded-tranche approach.
The roadmap is written from what FlowGuard ships today. Planned work should extend the current BCH-native model rather than replace it with a story the contracts do not support.