RESEARCH CORPUS / WORKSTATION
Searchable paper corpus: SQLite index, readable source exports, and a verified provenance manifest.
C:\\Users\\yasin\\.codex\\work\\merquan-corpus-20260725-v4\\corpus.sqlite · extracted_text\\ · verified_manifest.jsonl
SYNTRAD / MERQUAN REFERENCE
DATA STORAGE REFERENCE
Where MERQUAN’s current research corpus, QTS snapshots, live DTN market files, and Syntrad interface are stored. Use this page as a map of the real storage locations and their intended jobs.
TERNFS STATUS: ARCHITECTURAL REFERENCE ONLY — NOT DEPLOYED IN MERQUAN TODAY.
corpus.sqlite · extracted_text\\ · verified_manifest.jsonl
QTS FACTORY / 161
Non-live QTS code, immutable eligibility snapshots, receipts, quality audits, and shadow-only model outputs. Live DTN data remains on 139.
161:/opt/merquan/qts-factory/factory/161:/opt/merquan/qts-factory/artifacts/
161:/opt/merquan/qts-factory/docs/
LIVE DTN & MARKET REGISTRY / 139
Authoritative instrument taxonomy, DTN/IQFeed market-symbol master, and active front-month contract list.
139:/opt/merquan/replay-bridge/data/instrument_taxonomy_registry.json139:/opt/merquan/iqfeed/data/iqfeed_market_symbols.zip
139:/opt/merquan/iqfeed/data/frontmonths.tsv
SYNTRAD INTERFACE / 161
The deployed Syntrad single-page terminal and this reference tab.
161:/var/www/syntrad/index.htmlTERNFS / FUTURE FILE SYSTEM
TernFS is XTX Markets’ distributed filesystem design. When deployed, file contents are split into immutable blocks across storage services; a registry stores the metadata that says which blocks form each file. It is not one folder on one server.
Status today: not deployed — no TernFS files stored in MERQUAN.TernFS source checkout (remote only): 161:/opt/merquan/qts-factory/vendor/ternfs/
Pinned source commit: 855fcfb7a812f2ce0648f06ed56dec8f8ba839f4
TernFS status: source is available for inspection; the distributed filesystem is not deployed.
Current MERQUAN files: storage locations listed above.
TERNFS TECHNICAL BRIEF
Why the implementation is split between C++ and Go, how it is built, and where it fits—and does not fit—in MERQUAN.
C++ SIDE / METADATA & CONSENSUS
- ternregistry — one logical instance; deployment topology and storage statistics; RocksDB persistence with five-node consensus via LogsDB.
- ternshard — 256 logical instances; filesystem metadata including attributes, directory listings, file-to-block maps, and block-service-to-file maps; UDP bincode request/response.
- terncdc — Cross-Directory Coordinator; serialized transactions for create, remove, and move operations that span directories.
GO SIDE / DATA PATH & OPERATIONS
- ternblocks — block service; one logical instance per disk. It streams blobs from disk to TCP and may move to C++ if performance later requires it.
- ternweb — stateless UI and JSON API; terncli — migrate and defrag; terngc — GC, scrubber, and migrator daemons.
- ternfuse, terns3, and the xtx/ternfs/client Go library provide client and integration paths.
FASTEST CLIENT PATH
ternfs.ko is the C Linux kernel module: the fastest client path. It is Linux-only.
FUSE remains available as a Go client path where a kernel module is not appropriate.
BUILD & TEST
Build modes:
./build.sh alpine # Docker / fully static./build.sh ubuntu
./build.sh release # host dependencies
ci.py runs integration tests. ternrun starts a full local instance: 256 shards, CDC, registry, block services, web, GC, and a FUSE mount.
HONEST PLATFORM CONSTRAINTS
TernFS is Linux-native. Docker Desktop or WSL2 can build the containerised Go/C++ services; the kernel module and its qemu tests are Linux-only.
Under MERQUAN’s current remote-only policy, we do not use a Windows workstation for this source. The remote checkout on 161 can be read, built, modified, and extended in a Linux container.
MERQUAN RELEVANCE & LIMITS
This matches a smaller-scale version of XTX’s stated use case: cold raw market data flowing into short-lived random-access datasets between GPU jobs.
- Immutable/write-once files: good for raw tick archives and versioned research snapshots.
- Not for tiny files: the project expects median files around 2 MB; per-symbol small mutable updates do not fit.
- Permissionless: authentication is deferred to a gateway. The production S3 gateway is not open-sourced; terns3 is a minimal starting point.
THE DECISION IN ONE LINE
TernFS is a data-lake substrate for large immutable datasets—not a mutable store, not an order-routing system, and not a replacement for a live market database.
Remote source only: 161:/opt/merquan/qts-factory/vendor/ternfs/ · Commit: 855fcfb7a812f2ce0648f06ed56dec8f8ba839f4WHAT WE CAN USE THIS FOR
- Research: search papers and trace claims back to a source file.
- Market identity: resolve a logical market to its certified cash, futures, or options provider symbol.
- Data lineage: see where a model input came from, when it was captured, and what hash proves its version.
- QTS gating: build read-only eligibility snapshots before any shadow-only model work.
- Future storage design: use TernFS ideas—immutable files, registry metadata, integrity checks, and replication—when MERQUAN is ready to deploy a distributed data fabric.
