01
Evidence
Heracles
What is happening in my training?
An evidence-aware resistance-training system that turns workout logs into interpretable strength and hypertrophy signals.
Personal systems, made legible.
Understand the system.
Then change it.
Fabbro Systems is a family of software for turning complex personal systems into structured evidence, interpretable state and deliberate action.
01EvidenceObserve what is actually happening.
02StateBuild an interpretable current model.
03ActionTurn desired change into execution.
Current architecture
Three systems. Three different jobs.
The products exchange useful outputs without collapsing their responsibilities. Heracles goes deep on a domain. Kleos models the broader person. Ariadne organizes desired movement.
HeraclesEvidence
→KleosState
→AriadneAction
Products
Specialist systems, not one giant app.
Each product keeps a clear responsibility and its own interface, models and vocabulary. The family resemblance comes from shared principles rather than forced sameness.
02
State
Kleos
Where am I now, and how is that changing?
A personal intelligence system that turns fragmented evidence into an auditable model of current state across multiple life domains.
03
Action
Ariadne
Given where I am and where I want to go, what should I do next?
An AI-assisted personal strategy system that connects long-term direction to priorities, opportunities, projects and tasks.
Operating principles
Inspectability over magic.
Fabbro Systems treats uncertainty, provenance and model boundaries as product features, not implementation details.
Explicit models
Prefer understandable models over opaque scores and unexplained recommendations.
Meaningful information
Collect information because it helps interpretation or action, not because it is easy to count.
Clear boundaries
Keep observation, interpretation and action separate enough to inspect and contest.
Visible uncertainty
Expose provenance, limitations, coverage and confidence whenever they materially affect meaning.
Fabbro Systems
Complexity should become navigable, not invisible.
The current family began as owner-focused personal software. The public layer exists to make the systems, their assumptions and their architecture understandable from the outside.