Fundamentum
The code Iterum, Domi and Vocatio share
PersonalPythonuvADKGemini · ClaudeTerraform
Problem
Sometimes I lack order when I build: I tend to wander down different paths.
Fundamentum is my harness for that. Iterum, Domi and Vocatio needed the same things (priced models, metering, events and guardrails), so I moved them into a versioned chassis each app installs by git tag. Anything missing goes into the chassis first, with tests.
How it works
- Iterum · Domi · Vocatioapps
- Fundamentumv1.0.0 by tag
- Models and costtask → model registry
- Guardrails and evalsscope · budget · gate
- 01Each task gets its model from a registry that requires a price.
- 02Every call goes through ADK and is metered with model, tokens and cost.
- 03Scope and budget guardrails, plus an eval runner with a cost and latency gate.
Decisions
DECISION 01
No model call outside ADK.
A test in each app fails if anyone calls a model another way. That keeps every call metered.
DECISION 02
Every model carries its price.
The registry rejects a model without its price, and each app can switch a task’s model with an environment variable, without touching code.
Result
Version 1.0 shipped in October 2026, and Iterum already runs on it.
MY ROLEPersonal project.Design and code.