Core membership
Testing Floor
$20/month
- Run standardised tests on listed strategies
- Submit evidence and earn Verified Tester
- Take bounties such as Find the Failure
- Build evidence-based reputation
Selius · Established 2026
The Quantitative
Guild
A quantitative software guild with a living testing economy.
built → tested → challenged → optimised → verified → observed → evolved
Click to explore · Scroll to zoom · Drag to pan · Double-click to reset
DescendI · The Light Castle
Strategies under
observation.
The Observatory is the calm, cinematic layer. You watch software being tested in the open, and every claim links to its evidence.
The Testing Floor
The operating environment.
The public website is the gateway. The Floor is where the work happens. Traders test software, developers prove what they built, and each result is attached to the record it came from.
Free for everyone who joins
Vidette
Equity guard · dynamic drawdown control · MT5
$179 Free when you join
No account needed
Free Observer
- Watch the Observatory and Arena matches
- Inspect public strategy cards and evidence
- Read methodology and version history
Live
The Floor is quiet.
The live feed connects at launch. Nothing on this page is simulated: when tests run, they appear here. Until then it stays quiet.
Research feed
Evidence, not noise.
Instead of social posts, the feed carries evidence events you can trace back to their source.
- OOSOut-of-sample test completed
- REPCommunity reproduced an execution issue
- PARParameter sensitivity identified
- VERDeveloper released a new version
- CRUCrucible checkpoint completed
- ObserveStrategies under observation
- Open a matchConfigurations race a standardised segment
- InspectStrategy DNA, evidence, checkpoints
- Find the failureTake a bounty
- JoinTesting Floor · $20/month
- TestRun it and submit evidence
- Verified TesterReputation updates
Verity · example message“Your result reproduced an existing execution observation. I've attached it to the strategy record.”
II · Project Raccoon (working name)
It only touches
what you hand it.
The optional desktop companion connects your local MetaTrader project to the Guild. You choose the folder, and you choose what leaves the machine.
Local repository scanner
Provenance, not surveillance.
Raccoon maps how the files in a project you select relate to each other. Nothing is uploaded silently. Source code never leaves the machine by default.
Local project graph
What leaves the machine?
Raccoon never scans the whole computer and never collects unrelated files. You pick the project root, and you tick each artifact before it's shared.
Local evidence verification
When a developer submits an .ex5, a .set and a Strategy Tester report, the platform links them. Where it's technically possible, it checks:
- File hashes
- Version
- Symbol
- Timeframe
- Test dates
- Configuration
- Result metadata
III · The Tunnel
Enter the
Glitched Arena.
Where the Observatory is calm, the Arena runs hot. Strategies race identical historical conditions under a published protocol. It's a controlled research competition and doesn't predict live results.
The Glitched Arena
Same data. Same execution. Same rules.
Arena matchNo match live
- Market
- —
- Timeframe
- —
- Dataset
- —
- Execution model
- —
- Participants
- —
The next match publishes its protocol here before it starts. Anyone can watch without an account. You see only what the competition exposes: no private source and no private parameters.
What a match measures
A strategy can do well under one protocol and badly under another, so the protocol is always shown. Raw profit is never the only score.
Spectator mode
- Inspect public strategy cards
- View the methodology, public evidence and Arena history
- Open developer profiles
- Follow a strategy after you sign up
Anonymous viewers can't influence rankings.
Community challenge · example format
M5 Breakout Challenge
- Fixed dataset
- Fixed execution
- Fixed spread
- Fixed risk model
- No look-ahead
- No future data
Participants submit strategies. The platform runs the same test on each one, so it's a real software competition.
IV · The Dark Castle
Survive the
Crucible.
Strategies face hostile historical and simulated conditions. It's intense, and it stays scientifically honest: nothing here is ever called “crash proof”.
The Crucible
Stress scenario. Extreme regime. Historical shock.
Crucible checkpoint
CHECKPOINT —
- Strategy
- —
- Scenario
- —
- Execution delay
- —
- Historical window
- —
- Degradation
- —
- Status
- Awaiting first run
What “Survived” means
A run is marked SURVIVED only if all of these hold. Otherwise it's FAILED. The label is never a judgement call.
Antifragility Index
It's a published formula, not a magic score. A strategy isn't called antifragile because it made money in one crisis.
Physical artifact
The Crucible Award
Black stone base, dark metal and an emerald accent. Each is engraved with the strategy, developer, year and Crucible designation. It's awarded against published eligibility criteria, never for the highest return.
The Crucible BoardSort by any column. There's no single blended score.
| The board is filled only from real, completed checkpoints. None are recorded yet. | ||||||
Market quietNo transactions recordedThe ticker only shows real events
V · The Exchange · Parameter Intelligence
Tested configurations, not securities.
The Exchange is where you find tested software configurations. Exchange words like market, ask, volume and depth describe access to software and data. They're never financial instruments.
Parameter configuration
— · v— · —
AskNo listings yet
Last salesNone recorded
- Demand
- —
- Verification
- —
Parameter behaviour
TAKE PROFIT
- Range tested
- —
- Observed sensitivity
- —
- Stable region
- —
- OOS behaviour
- —
- Execution sensitivity
- —
This fills in from validated tests. It isn't a magic optimiser.
Configuration labels
- VCVerified Configuration
- OCObserved Configuration
- HSHigh-Sensitivity Configuration
- OOSOOS Configuration
We never use “winning parameters” unless the evidence supports it.
Parameter heat map0 validated cells
Each cell must trace to a real test configuration. Until one exists, the cell stays hatched. We never draw a heat map from made-up data.
Configuration compiler
PARAMETER TYPE ERROR
StopLoss · expected numeric · received string
An example of how the compiler explains a failure. A file the system knows is malformed is never handed to you.
Component market
Entry+Risk+Session+Exit+Spread=Compiled configuration
If components conflict, you see CONFIGURATION CONFLICT and no file is generated. Every compiled file carries a Configuration ID, source version, component IDs and a validation hash, so it can be reproduced.
VI · The Ten
10 Founding Nodes.
The first participants of the Guild. Their status is founding membership, reputation, access and provenance. It isn't an investment and it can't be traded. Select a stone to scan it.
The physical stone card
Black stone with engraved typography, a restrained serial, a small gemstone detail and a Selius identity. The QR/NFC holds only a non-secret reference. Authorisation stays on the server, a lost card can be revoked, and a replacement keeps the same Founder identity.
What “lifetime” means
Founder status doesn't give platform authority. There's no administrative control unless a role explicitly grants it.
VII · The way in
Enter at the level that fits you.
The $20 Testing Floor is the easiest way in. Every tier above it is optional.
Verified VendorIdentity, business or product verified against published criteria. It isn't proof of profitability.
Verified StrategyThe strategy's claims match its attached evidence under a stated protocol.
Verified TestThis test run was reproduced and its provenance checked.
Community TestedMembers have tested it. It hasn't been formally verified.
VIII · The Archive
A permanent evidence library.
Strategy versionsTest reportsResearch
Bounty findingsArena resultsCrucible checkpoints
Developer historiesConfiguration records
The Archive opens with its first verified record.
IX · The loop
The ecosystem compounds.
Verity is the intelligence layer. It prepares evidence and connects the records, and it never acts as an invisible judge.
The moat isn't the number of EAs