TriFi · flagship system
The Tokenized Asset Manager
A fleet of autonomous daemons that allocates and manages capital across Solana DeFi without a person in the loop. It is TriFi's own system, running against real wallets on dedicated hardware — which is the only reason we are willing to describe it as evidence of anything.
- Fleet14 strategy daemons
- ChainSolana
- Decision layerClaude, inside hard limits
- Operating modeContinuous, unattended
Anatomy of a cycle
What one strategy actually does when it wakes up.
Every daemon in the fleet runs the same seven-beat cycle, whatever it trades. The shape is deliberately boring and identical across strategies — it is what makes fourteen independent processes reviewable by one person.
01 directive
Re-read the mandate
Load the portfolio manager's current directive from disk. Budget, base currency and posture can have changed since the last cycle; nothing is cached across cycles.
02 snapshot
Measure reality
Read on-chain balances, open positions, health factors and accrued fees. The wallet is the source of truth — the state file is a record, never an assumption.
03 gate
Check the rails first
Drawdown, stop-loss, trailing stop, peg deviation and reserve floors are evaluated before any model is consulted. If a rail trips, the cycle acts on it and stops.
04 advise
Ask for a decision
A strategy-specific advisor gets the snapshot, market context and its own guardrails, and returns a structured recommendation — validated against a schema, retried on failure, costed per call.
05 bound
Clamp the answer
The recommendation is checked against position-size caps, leverage ceilings, allowed mints and slippage budgets. Out-of-range answers are clamped or rejected, never executed as given.
06 execute
Settle on-chain
Routes are quoted, transactions signed by that strategy's own key and submitted with RPC failover. Actual gas and slippage are recorded against the estimate that justified the trade.
07 persist
Write it down
State is written atomically, telemetry is emitted, and any excess above the strategy's budget is swept back toward the portfolio manager on the shared housekeeping tick.
Runs on every cycle
- directive reload
- balance + position snapshot
- risk-rail evaluation
- schema-validated advisor call
- guardrail clamp
- routed execution
- cost + slippage capture
- atomic state write
Cadence varies by strategy — mechanical rotation re-evaluates in minutes, leveraged carry in hours — but the beats never reorder. Rails are always checked before the advisor is asked, and the advisor's answer is always clamped before anything is signed.
Safety architecture
The model decides. The rails hold.
Every serious question about autonomous finance reduces to one: what happens when the model is wrong? The answer has to be structural, because it will be wrong. In TAM, everything that can lose money is deterministic, tested, and not up for negotiation.
One wallet per strategy
Blast radius is a design parameter. Each daemon signs with its own key, so a failure — a bad route, a stuck position, a compromised dependency — is bounded by that strategy's capital and cannot reach the rest of the book.
Rails outrank the advisor
Stop-losses, trailing stops, drawdown halts, peg-deviation exits, reserve floors, position-size caps and rate-limit backoffs are pure mechanical code, evaluated before the model is consulted. No prompt and no clever reasoning can talk past them.
Every dollar path is a tested pure function
Math is separated from I/O throughout, so anything that decides what to trade or how much to move is a pure function with unit tests over its happy path, its edges and its failure modes. Bug fixes ship with the regression test that would have caught them.
Atomic, recoverable state
Every daemon persists to its own JSON file with a temp-write-then-rename, and recovers from the temp file on load. A crash mid-write cannot corrupt the record of what a strategy is actually holding.
Drain before shutdown
A restart signal does not kill work in flight. Each daemon finishes its current cycle, saves state, then exits — so a routine deploy can never strand an unconfirmed swap outside the state file.
An auditor that isn't part of the fleet
The watchdog runs out-of-process on its own schedule, reads state and logs from the outside, and escalates to a human. A daemon that has silently stopped thinking still gets caught, because nothing asks it to report on itself.
Operating posture
The point of automating a book is not to trade more. It is to make the boring decisions correctly, every single time, at three in the morning, without anyone watching.
Preserve
Capital first, growth second
When a strategy has no good opportunity it receives no budget and stands down. Idle stablecoins earn supply yield rather than being forced into a trade to look busy.
Contain
Failures stay local
Separate processes, separate keys, separate state. Nothing in the design lets one strategy's worst day become the fleet's worst day.
Observe
Assume it will drift
Estimates get calibrated against realised costs, logs are analysed for the failures nobody thought to alert on, and an independent watchdog escalates when a daemon goes quiet.
Build with us
Need a system that survives real capital?
TAM is not a product you can buy — it is TriFi's own book, and the reason we can talk credibly about autonomy with consequences. If you're building something in that territory, we'd like to hear about it.
Not an offer of, or solicitation for, any investment or financial service.