Active stack
FractiAI now presents one clean production lane: Juicy Juicy Snap (OFC) as the public compile surface on SING 9, Syntheverse as orchestration, Basenet as public settlement rail. The pages are tuned for smooth flow first, deep docs second.
One tight signal: plain speech, inspectable links, and one coherent runtime story from QUESTFEST surface through Hood compile to GitHub-run APIs.
What ships right now
- Juicy Juicy Snap (OFC) — in-browser compile (Juicy Juicy Snap page); bench + RTL in FractiAI/digital-pru. Metabolize · Crystallize · Animate · squeeze.
- Syntheverse layer — recursive orchestration model for 13 channels and 4 electron states across story, ritual, and firmware logic.
- Syntheverse on Basenet — public rail identity anchored to current Base-facing address:
0x3563388d0e1c2d66a004e5e57717dc6d7e568be3.
Genesis rail info
Current published rail identifier used across live surfaces:
Basenet public rail
Syntheverse genesis reference
0x3563388d0e1c2d66a004e5e57717dc6d7e568be3
This is the currently exposed Base-facing identity in the active stack. The dedicated contract registry page can expand this with chain IDs and deployment proofs in the next pass.
The team
Pru Mendez
Founder · Juicy Juicy Snap / Syntheverse architect
pru@fractiai.com
Leads the active runtime lane across Juicy Juicy Snap compile discipline, Syntheverse flow grammar, and the production bridge from plain-language surface to firmware-level coherence controls.
Daniel Ari Friedman, Ph.D.
Co-founder · systems architect · CEO
daniel@fractiai.com
Drives systems integration and verification discipline so Syntheverse stays auditable from public narrative through to execution layer behavior.
Read lanes
Contact
FractiAI is focused on one active path: Juicy Juicy Snap (OFC) + Syntheverse + Basenet.
Open science & code
Public work lives on GitHub and indexed artifacts on Zenodo. This page only links active stack lanes.