06Roadmap

Current Status

Payment processing follows a deliberately conservative rollout. One automated payment provider is fully integrated and live today, including hosted checkout, dual-approval payout, notification verification, and live balance reconciliation. A second provider is built and ready but not yet the default. Manual, staff-confirmed bank transfer remains the safe fallback any misconfiguration lands on automatically. A genuinely sophisticated, staff-tunable operations layer is already live, not just planned: structuring-detection thresholds, dual-approval thresholds for both withdrawals and revenue entries, per-member ownership caps on both new raises and secondary trades, and separate tax withholding rates are all settings a staff member can change without any engineering work.

The shape of recent engineering work reads as a genuine post-launch hardening phase, not early build-out: closing money-handling edge cases in ownership limits and payout processing, encrypting sensitive data at rest, and tightening error handling across the board. What remains unfinished is tracked formally and deliberately rather than scattered informally, itself a signal of discipline worth noting.

What's Next

Taken directly from the team's own internal assessment of what is not yet built:

• Public technical documentation currently covers roughly a third of the platform's internal capabilities; the rest is not yet externally documented.
• The internal system that broadcasts events between different parts of the platform runs in a single process today; a more durable, distributed version is the planned upgrade once that guarantee needs to become absolute.
• Resale windows and governance proposals are opened and closed manually by staff today. The scheduling infrastructure for automatic, deadline-driven closing exists but is not yet connected.
• The holding-period safeguard on newly acquired units is built but ships turned off by default.
• Automatic refunding of a raise that times out unfilled needs a background scheduling capability and is explicitly deferred; a manual staff cancellation is today's workaround.
• A second automated payment provider beyond the two already covered has not yet been integrated.