This piece first appeared as an Article on X. Same text, same figures.
Every fund has a diagram somewhere in a deck: three boxes, two arrows, a word like "proprietary" in the middle. SLVCE publishes the whole machine instead. Atlas, at atlas.slyce.xyz, is a three-dimensional map of every part of the system, what it does, what feeds it and what it feeds, drawn live in the browser. This is a guide to reading it.
What you are looking at
Atlas draws the system as an organism: 43 nodes and 71 connections, arranged in rings around a nucleus. The nucleus is SLVCE Core, the market-neutral liquidity strategy the firm was built around. Around it sit the rings: the external environment (exchanges, on-chain venues, the Solana network, an oracle network, an options venue), market data (the live tape, a reference oracle, pool state, the basis surface), the risk contours (treasury rebalancer, market conditions, leverage signal, capital stabilization, shared protection, Edge, research, the capital rail), state and records, the APIs and telemetry, and finally the interfaces you actually touch: One, the portal, KPI, Deep, the Journal.
Each connection has a kind and a direction. Data flow, capital flow, command and control, read and serve, depends on. A thicker line is a primary artery. A bigger node is a higher tier: T0 is the nucleus, T1 critical, T2 operational, T3 peripheral. Drag to orbit, scroll to zoom, tap a node to open it, tap a connection to see what flows where.
How to read it in five minutes
Open SLVCE Core. The panel says what it is in one paragraph: it observes the live market, forms decisions from the current state and never from a price forecast, gates them through risk, and executes. Revenue follows from execution quality and trade-flow structure. Three facts are printed at a glance: style market-neutral, forecasting none, leverage none. Below them, its four inputs and four outputs, each a link to the node on the other end.
Now follow one input backwards. Market Tape is the eye of the whole system: full trade tape, order-book depth and best bid and offer across the major venues. Next to it, Reference Oracle is a second, independent price, cross-checked against the venue mid for staleness and deviation, so the system is never hostage to one feed lying.
Then follow one output forwards. State and Ledger is the single source of truth: every decision, fill and capital operation is written there first, so the numbers an investor sees are reconstructed from the record, never asserted. The Reporting Store next to it is the read model the investor surfaces draw from, kept separate from the write path so nobody reports through the window they trade through.
Finally, the contours. Capital Stabilization is a standing options collar that defends principal against sharp, broad drawdowns. Shared Protection is the same layer mutualised across the whole book, its value shared by units at NAV. Treasury Rebalancer keeps each holding near its target mix as prices drift, with moves that are soft and capped per cycle. Leverage Signal reads how much leverage other participants have stacked, a tail-risk early warning. Every one of these is a node you can open and a set of connections you can trace.
What is deliberately left out
Atlas is the public twin of the operator's own map. Same organism, same rings, and every figure, every internal path, every account-level number removed. The descriptions sit at the altitude of process, not numbers: what a part does and why it exists, never how much it holds. The editing rule for the public manifest is written into the file itself: nothing in it may reveal a real figure, a hostname, an account, or anything that is not already public on deep.slyce.xyz.
That is the trade the map makes. You can see the whole shape of the machine and every dependency in it. You cannot see the money. The money is on the pages built for it: kpi.slyce.xyz for the live numbers, deep.slyce.xyz for every marked day and its attestation.
Why publish the map at all
An investor's real questions about a fund are structural. What happens when the price feed lies? What stands between a drawdown and my principal? Who can write to the ledger, and who can only read it? Where does a number on my screen come from? A returns chart answers none of them. A map with every dependency drawn does, and it lets you ask the next question with the node open in front of you.
The architecture note in the Journal, The Architecture Behind SLVCE, is the prose version of the same map: engines make return, the ledger keeps the truth, surfaces are windows. Atlas is the version you can turn in your hands.
Open it at atlas.slyce.xyz. Start with the nucleus and follow one line out.
Top comments (0)