Roadmap
Institutional Roadmap
Key milestones for JIL Sovereign policy and attestation infrastructure. Factual timeline, no hype.
Q1 2026 Complete
Foundation and Validation
- External engineering verification complete - system verification of the settlement protocol, MPC key management, and cryptographic signing across the compliance network by Emerging Technologies, LLC (Scottsdale, AZ) and BlockChainX (Hyderabad, India), report JIL-CSVR-2026-001. That is an engineering verification engagement, not a security audit: the independent external security audit of the L1 has not been engaged.
- 10 JIL-operated signing nodes active across 10 policy zones, with an active consensus set drawn from that fleet
- 350+ production services deployed and operational
- 177 patent claims filed
Q2 2026 Active
Production Settlement Protocol
- Pre-production settlement protocol live - full settlement flow operational with threshold cryptographic signing across the active set on the 10-node JIL-operated fleet (hybrid-signed) and sub-2-second finality. The 20-node fabric is a planned Q4 2026 target.
- Cross-chain bridge operational for ETH, USDC, USDT, WBTC, DAI
- Institutional API documentation and sandbox environment available
- Settlement execution layer integrated with the verification layer - deterministic batch execution with fair ordering, no front-running, no MEV extraction
- SentinelAI fleet monitoring active across all signing nodes with automated health recovery
Q3 2026 Planned
Institutional POC and Integration
- First institutional proof-of-concept corridor - controlled settlement corridor with selected institutional participants
- NACHA/SWIFT integration gateway - translation layer enabling interoperability between JIL settlement and traditional payment rails
- Institutional onboarding toolkit - compliance documentation, integration guides, and dedicated support channel
Q4 2026 Planned
Compliance Certification
- Target: engage an audit firm for a SOC 2 Type I controls assessment. No firm is engaged today
- Institutional settlement volume reporting and analytics dashboard
- Enhanced compliance engine with configurable policy templates for different regulatory jurisdictions
- Additional independent signing nodes provisioned based on settlement volume requirements
2027 Planned
Expansion
- Signing-node partner expansion - onboarding additional independent operators to increase network distribution and geographic coverage
- Additional jurisdiction onboarding - extending compliance coverage based on institutional demand and regulatory developments
- SOC 2 Type II certification, sequenced after an audit firm is engaged. No firm is engaged today and no date is committed
- Advanced settlement corridors - multi-asset, multi-jurisdiction settlement flows for complex institutional transactions
Strategic Track · Platform Compliance Inheritance
Compliance posture by inheritance: Snowflake Native App + Databricks Brickbuilder.
In parallel to the standalone Build Track above, JIL is shipping native deployments inside the customer's existing certified data platform - Snowflake Container Services and Databricks Apps. The customer's data plane is unchanged. JIL services run as containers inside the customer's account. The customer's data plane keeps its own certified posture: HITRUST r2, SOC 2 Type II, ISO 27001, HIPAA + BAA, FedRAMP MOD, PCI DSS - already in place at Snowflake and Databricks, covering their platforms and not JIL. JIL Cloud (Amazon EKS) is the third path for federal and air-gap workloads.
Q2 2026 Active
Snowflake Native App - Snowpark Container Services
- Verdict Engine running inside customer Snowflake account via Snowpark Container Services
- Runs inside the customer's certified Snowflake boundary: HITRUST r2, SOC 2 Type 2, ISO 27001, HIPAA + BAA, FedRAMP MOD and PCI DSS cover Snowflake's platform, not JIL
- Customer data never leaves customer account; hashes only cross to CourtChain™
- Marketplace listing in flight
Q3 2026 Active
Databricks Brickbuilder Apps
- Verdict Engine deployed inside customer Databricks workspace
- Delta Lake substrate, Unity Catalog governance, Photon query engine
- Same inherited compliance posture as Snowflake (HITRUST / SOC 2 / ISO 27001 / HIPAA / FedRAMP MOD)
- Best fit for lakehouse-native, ML-heavy customers running Unity Catalog
Q4 2026 Planned
JIL Cloud - Amazon EKS
- Direct deployment on JIL-operated EKS infrastructure (KMS, IAM, GuardDuty)
- Target: SOC 2 Type 1, then Type 2. Compliance automation vendor not yet selected and no audit firm is engaged
- Target: HITRUST i1, then r2. No authorized external assessor is engaged
- FedRAMP MOD roadmap, GovRAMP Ready 3-4 months, StateRAMP roadmap
- For federal customers requiring authorization paths and any institution requiring maximum operational control
Q1 2027 Planned
Federal Channel Activation
- Channel partnerships through Accenture Federal Services, Leidos, SAIC, Peraton
- 60-120 day path to fielded capability under partner ATO/FedRAMP authorities
- Reference Medicare model: 12.5% of disclosed PI spend (annual, capped) plus 10% contingency on net cash recovered. 4-year retroactive scan baseline. 90-day pilot, $1M all-in, asymmetric downside (contingency drops 10% to 7.5% on miss), ~$786M net to partnership
- Cross-agency CREB™ evidence reuse across CMS, OIG, DOJ, federal program integrity
Note: This roadmap reflects current plans and may be adjusted based on regulatory developments, market conditions, and institutional feedback. All dates are targets, not commitments. For the latest status and evidence of completed milestones, visit the Proof Artifacts page.
Policy and Attestation Infrastructure
Interested in participating?
We welcome conversations with institutions interested in early access to policy and attestation infrastructure or independent signing-node partnership.