Quick definition
Treeova's database-driven economic layer governing the Triobol lifecycle. Single source of truth for every economic constant, with structured governance alerts and an append-only audit trail.
Why a dedicated engine
Early in Treeova's life, plan allowances, per-feature costs, and provider markups lived in multiple constant files. That guaranteed eventual drift. The Triconomic Engine consolidates all of it into a small set of database tables that every consumer — Stripe webhooks, the agent executor, the navigator, the admin panel — reads through one resolver with a 60-second cache.
Live peg to provider costs
When OpenRouter changes a model's price, a database trigger automatically recomputes the Triobol cost of every feature that uses that model. There are no hardcoded markup numbers in edge functions — the markup multiplier lives in the economic configuration table and flows through to per-feature costs via SQL.
Governance and audit
Every economic change writes to an append-only audit log. A quarterly automated review flags rows where the spread between cost and price has drifted outside policy. Refunds, grants, and adjustments all flow through versioned RPCs with advisory locking so concurrent writes can't corrupt a user's balance.
Go deeper
The full technical methodology behind Triconomic Engine is documented in the Treeova whitepaper series.
Read the Triconomic Engine whitepaper →