README
10 is the technical company of a group working across research, markets, and applied technology. It builds and holds the systems the group's operating entities run on, and licenses them within the group and selectively outside it. All engineering in the group is done here.
1 Usage
- Tabs
- readme · systems · releases · careers. Keys 1 to 4, or click. Each tab is a command; the console echoes it.
- Sidecar
- the index of the active tab. ↑ ↓ move, enter selects.
- Pane
- the selected item. The path bar shows its file, commit and date; the same appears when the cursor rests on any text.
- Console
- / brings it to the front and begins a command; esc switches back to the workspace, and the console stays open behind it. /help lists commands, /help <command> explains one. ↑ ↓ recall history; tab completes.
- Theme
- follows the system. /theme dark · light · system overrides it, stored on this device.
- Reboot
- r, or /reboot. Runs the boot sequence again and resets the workspace: tab, selection, scrollback. Theme and history persist. /log reprints the boot log.
- Storage
- nothing is sent unless you send it: /contact and /releases transmit what you enter, and a game replay only if you submit it. Nothing else.
2 Systems
- Market data
- ingestion from venues and vendors; normalisation; point-in-time storage of ticks, bars, reference data and calendars
- Market modelling
- price, volatility and microstructure models calibrated to tracked data; regime identification
- Simulation
- replay and generative engines; execution simulation with fill, spread, impact and latency models; environments in which people or algorithms act under codified conditions
- Signal research
- feature pipelines over market and behavioural data; out-of-sample and walk-forward validation; leakage controls; correction for the number of trials
- Decision modelling
- models of human decision-making under uncertainty from recorded decision records; separation of skill from variance against algorithmic baselines
- Portfolio and risk
- position sizing, exposure and drawdown constraints, covariance and factor estimation, scenario analysis; risk conditions codified and evaluated deterministically
- Rule engines
- codified determinations executed without discretion and reproducible from inputs
- Deployment
- validated signal to systematic and discretionary deployment; pre-trade checks; paper and live parity; human authorisation for irreversible actions
- Learning systems
- training and evaluation pipelines; pinned data versions; model registry with provenance
- Operating infrastructure
- messaging, identity and access, permissioned retrieval, document generation, this site
Detail under systems.
3 Methods
- Determinism
- rule evaluation is a pure function of recorded state; same inputs, same outputs, replayable
- Time
- every record carries its timestamp and clock; evaluation times are published before they apply
- Versioning
- rules, datasets and documents are versioned; changes announced before effect; prior versions readable
- Disclosure
- fill, spread, commission and slippage models are documented for those acting under them
- Testing
- property tests on rule engines; recorded sessions replayed against new rule versions; invariants checked continuously
- Review
- a change is accepted on the strength of its mechanism, not its author, the principal's included
- Vocabulary
- terms are defined once, in the agreements; the code uses the same names
- Provenance
- every artefact carries file, section, version, date and commit; statuses are distinct: draft, stated, in use, approved
4 Constraints
10 builds and holds systems. It deploys no capital and holds no client assets; deployment is the mandate of the group's operating entities, under their own risk conditions.
Simulated environments route no order to a venue. Deployment systems do, with pre-trade checks against the risk engine, and a person's recorded authorisation for any irreversible action.
Determinations that must not depend on judgement are executed by rules, with no discretionary step.
No number is displayed that is not measured.
Data is used for the purpose stated when it was contributed.
What can be checked is published. The rest is disclosed by introduction.
5 Interfaces
- Within the group
- systems and datasets licensed to operating entities under intra-group agreements
- Outside the group
- datasets and systems licensed to systematic investors and developers of decision systems, by introduction: io@10.xyz
- Parent
- heliopause.inc
README.md · v2 · 2026-10-07 · 12eeed9