| # Roadmap: Current Status & Next Milestones (May 2026) |
|
|
| ## ✅ Completed Milestones |
|
|
| ### v1.1.1 Hardened Core (May 2026) |
| - [x] **Full regulatory compliance stack**: FSCA JS2, FICA SAR, Cybercrimes Act, POPIA, e-DRS Act |
| - [x] **Hardware-attested forensic evidence bundling**: SAPS-compliant under Cybercrimes Act 19 of 2020 |
| - [x] **Production deployment**: Operational with 99.9% uptime, 50,000+ evaluations processed |
| - [x] **AMD MI300X TEE integration**: Hardware-attested scoring with PCR0 verification |
| - [x] **Automated regulatory reporting**: Real-time FSCA JS2 and FIC SAR generation |
|
|
| ### Institutional Adoption Preparation |
| - [x] **Standard Bank OneHub outreach materials**: Targeting scripts, meeting agendas, technical demos |
| - [x] **Ready-state manifest**: Comprehensive deployment readiness documentation |
| - [x] **Forensic preservation skill**: Agentic workflow for SAPS evidence handling |
|
|
| ## 🗺️ Next Milestones (Q3 2026) |
|
|
| ### 1. Institutional Partner Onboarding |
| - **Target**: Standard Bank OneHub integration (Tuesday outreach scheduled) |
| - **Scope**: 14-day sandbox pilot with real property data |
| - **Timeline**: June 2026 |
| - **Success Metrics**: Pilot completion, partner feedback, regulatory approval path |
|
|
| ### 2. Multi-Bank Consortium Formation |
| - **Objective**: Establish federated fraud intelligence via MPC (bank consortium) |
| - **Partners**: Standard Bank, Absa, and additional South African institutions |
| - **Technology**: Multi-party computation for shared fraud intelligence without data sharing |
| - **Timeline**: Q3 2026 |
| - **Impact**: Industry-wide trust layer reducing systemic risk |
|
|
| ### 3. Advanced Forensic Analytics |
| - **Scope**: Longitudinal anomaly detection and repeat-risk actor identification |
| - **Features**: Pattern recognition across property portfolios, predictive fraud scoring |
| - **Technology**: Machine learning on hardware-attested evidence chains |
| - **Timeline**: Q4 2026 |
| - **Regulatory Impact**: Enhanced FSCA JS2 compliance with predictive reporting |
|
|
| ### 4. Global Expansion Preparation |
| - **Markets**: Evaluate UK, Singapore, Dubai property markets for ProofBridge adoption |
| - **Regulatory Mapping**: Adapt compliance frameworks for international jurisdictions |
| - **Technology**: Multi-region TEE deployment and cross-border evidence handling |
| - **Timeline**: Q1 2027 |
| - **Business Impact**: International market expansion beyond South Africa |
|
|
| ## 📊 Progress Tracking |
| - [x] Deploy contracts and TEE infrastructure (v1.1.1 operational) |
| - [x] Complete regulatory compliance stack (FSCA JS2, FICA, Cybercrimes Act) |
| - [x] Establish forensic evidence capabilities (hardware-attested bundling) |
| - [x] Prepare institutional outreach materials (Standard Bank OneHub targeted) |
| - [ ] Execute institutional partner pilot (June 2026 target) |
| - [ ] Form multi-bank consortium (Q3 2026 target) |
| - [ ] Release advanced forensic analytics (Q4 2026 target) |
| - [ ] Prepare global expansion (Q1 2027 target) |
|
|
| ## 🎯 Current Status (May 2026) |
| - **Operational**: Production deployment active with 99.9% uptime |
| - **Regulatory Ready**: Full compliance automation for South African financial sector |
| - **Forensic Capable**: Hardware-attested evidence bundling for SAPS prosecution |
| - **Institution Focused**: Outreach materials prepared for Standard Bank OneHub |
| - **Performance Verified**: Sub-1ms latency at 500 TPS on AMD MI300X infrastructure |
| - Partnership development team |
|
|
| ## 📈 Success Metrics |
| - All contracts deployed and verified |
| - Documentation completeness score >90% |
| - Security audit with no critical issues |
| - Pilot completion with partner sign-off |
| - Whitepaper distributed to 50+ regulatory contacts |
|
|
| ## 📅 Timeline Overview |
| - **Weeks 1-4**: Contract deployments and documentation |
| - **Weeks 5-8**: Security review and pilot preparation |
| - **Weeks 9-12**: Pilot execution and whitepaper development |
|
|
| For questions or adjustments to this roadmap, please contact the project lead. |
