Cube
Can a market result explain exactly why it should be trusted?
An evidence chain for research, backtesting, execution, and monitoring. Every conclusion stays connected to the data and assumptions that produced it.
Different domains, one consistent standard: assumptions should be explicit, evidence should stay attached, and outcomes should be testable.
Can a market result explain exactly why it should be trusted?
An evidence chain for research, backtesting, execution, and monitoring. Every conclusion stays connected to the data and assumptions that produced it.
What changes when price has to answer to physics?
Decision systems for power markets, where timing, physical delivery, regulation, and uncertainty have to coexist in one operating model.
What did we know, when did we know it, and was it healthy?
Infrastructure for finding data, tracing its origin, understanding its freshness, and deciding whether it is reliable enough to use.
Can a belief become more useful by admitting it may be wrong?
A workbench for resolvable questions, explicit probabilities, causal assumptions, and revisions that preserve what changed and why.
Current focus · 2026
A portfolio studio for AI-applied products. Different markets, one operating belief: shorten the distance between an idea and a verified outcome.
Visit 4nace.comMarkets, energy, data infrastructure, forecasting, and AI-native workflows.
Find the weak assumption. Build the smallest useful proof. Keep the evidence attached.
Turning ambitious ideas into measurable systems that can be evaluated and improved.
I’m a self-taught software builder from Italy. I’m most at home turning ambiguous questions into working products—learning the domain, building the system, and testing whether the idea holds up in practice.
For collaborations, product conversations, or difficult technical problems.
Get in touch