Live experiment · Publicly observable This page describes a live trading experiment conducted on the operator’s own capital, with realized results publicly logged in the Ekantik Discord journal. Nothing on this page constitutes an offer to sell, or a solicitation of an offer to buy, any security or interest in any investment product. Trajectory figures shown are hypothetical and projected, not realized. Past performance is not indicative of future results.
LIVE | Last fill:
Updated:
Live Experiment · Q2 2026 · Publicly Observable

A live, publicly observable experiment testing whether a disclosed-protocol architecture can compress approximately three doublings — roughly 10× into a twelve-month window.

A doubling is log2 math, not motivation. Three doublings is 8×; three-and-a-third is about 10×; four is 16×. So “10×” isn’t a leap — it’s just over three doublings. The architecture below is built to deliver this compression on operator capital, under locked falsifiability conditions, with every fill posted before exit.

Public method. Public trades. Public falsifiability. Anyone in the world can watch it.

Experiment state Live · Sample: qualified trades · Rolling EV: · Triggers fired: — / 4 · Falsifiability Gate: Armed

A 12-month experiment is Tense-2 work — execution inside the next four quarters. The doublings it produces are Tense-3 evidence — the multi-year arc the doctrine describes. The point of running this in public is to make the bridge between the two visible. Reality Calibration Protocol ↗

01 · The Method

The disclosed protocol.
Every parameter. Locked.

The experiment runs against a specific, named protocol. The protocol is not under operator discretion. It is not modified under stress. It does not adapt to the operator’s confidence level. It is the same on a winning week as on a losing one. The protocol is below in full.

01.1 · Never Lose Money — the base discipline

“Rule No. 1: Never lose money. Rule No. 2: Never forget Rule No. 1.” — Warren Buffett

Every durable “never-lose” system — casinos, insurers, Berkshire — runs on the same four principles. The outer rings protect the inner core: you only deploy where the edge is proven, you size so no single bet can hurt you, and you cap the downside so a bad regime can never cause permanent impairment.

Positive Expectancy

A structural edge that tilts the odds in your favor. Deploy only where advantage can be mathematically proven — never on hope.

Instrumented in §02 (live EV) & §03 (edge landscape)
Expected Value

Positive average return per unit of risk, computed before every entry — and re-measured on every fill.

Instrumented in §02 (the EV formula, live)
Position Sizing

Never risk too much on a single bet. Size proportionally to capital and edge — 1 ES per buffer, expressible as ≤ 10 MES.

Instrumented in §01.2 (the trigger ladder)
Risk Management

Pre-committed caps and circuit breakers that ensure survival: weekly max-loss stand-downs and the falsifiability gate.

Instrumented in §04 (Sit-Out) & §05 (the gates)

The reason the downside cap matters more than the upside is arithmetic: losses and gains are not symmetric. A loss needs a disproportionately larger gain just to return to even — and past a point, recovery stops being a question of edge and becomes a question of luck.

Drawdown takenGain required to recover
−10%+11%
−25%+33%
−50%+100%
−75%+300%
−90%+900%

What enforces it is adherence, not cushion: the working capital is $5,000 per unit, and a single ES contract requires only ~$500 in day-trade margin — so the position is always a fraction of the capital. So long as the four principles hold and the stand-down architecture (§04 Sit-Out, §05 gates) fires on schedule, losses are capped before the $5,000 can reach the risk-of-ruin zone — the point from which no remaining edge could recover it.

01.1.1 · The capital architecture · what the $5K assumes behind it

Active capital is the smallest tier. The buffer behind it is the largest.

The foundational design separates the working unit (active capital at risk) from the larger risk-capital buffer held behind it. Positive expectancy alone is not enough — it compounds only when the buffer behind it is large enough to absorb realistic drawdowns without forcing capitulation. The 1× / 6–10× / 2× pyramid below is the design; the table beside it maps it onto this experiment.

Ultra-safe growth · the capital architecture Compounding Buffer 2× · ~$10K Positive Expectancy (1×) $5,000 · working unit Buffer (6–10×) ~$30K – $50K risk capital held in reserve · not deployed *1× = minimum capital buffer to be profitable on positive-expectancy alone

Implementation on this experiment

Positive Expectancy unit
$5,000 working unit — the active capital deployed in the market. The operator’s position size is anchored here so positive expectancy can express across a meaningful sample (R-expectancy +0.30R/trade live, 84 trades).
6–10× Risk-capital buffer
$30,000 – $50,000 held in reserve, not deployed in active positions. This is what makes the architecture work: ordinary drawdowns on the $5K unit are absorbed by the buffer behind it; the operator never trades scared because the active capital is a fraction of the risk capital.
Compounding buffer
~$10,000 accumulated profit — earned via the buffer-trigger ladder (§01.2). This is what funds position-size scale-up: each $5K of accumulated profit is one buffer that releases one additional ES contract, up to the 4-ES cap.

Suitability · read carefully before acting on this experiment with your own capital

This architecture presumes a buffer ratio of at least 6× the working unit. If you are considering acting on what this experiment publishes with your own capital, the structural premise is that you have roughly $30,000 of risk capital you can afford to lose entirely sitting behind whatever you might deploy in an active position — not the $5,000 working unit alone. Without the buffer, you don’t have the architecture; you have the working unit by itself, which is materially more fragile than what the design contemplates. The operator runs this on personal capital under that architecture; observers without comparable buffer should treat what is published here as research input, not as a signal to follow into live capital deployment. Nothing on this page constitutes an offer, a solicitation, or personalized investment advice.

01.2 · The Trigger Ladder

Four buffers. Each fires when realized profit crosses the threshold.

Buffer 1 $5,000 accumulated profit Add 1 ES → 2 ES running
Buffer 2 $10,000 cumulative profit Add 1 ES → 3 ES running
Buffer 3 $15,000 cumulative profit Add 1 ES → 4 ES running
Buffer 4 $20,000 cumulative profit Position locked at 4 ES · evaluate next cycle

One ES contract per buffer. Each buffer adds exactly one ES-contract of exposure — which the operator may express as up to ten MES contracts (10 MES = 1 ES) while staying within the one-ES-per-buffer ceiling. The base unit starts at 1 ES (≤ 10 MES); each trigger raises the ceiling by one ES, to a maximum of four. Each trigger requires a fresh $5,000 of accumulated profit before firing. No early activation. No discretionary override. The trigger fires when the milestone is reached, or it does not fire. The operator’s confidence is not an input. Each trigger fire is announced in the public Discord journal within 24 hours.

Prefer to watch the buffers advance as it happens? The whole experiment runs in the open — follow the live trade journal in the public Discord. Every fill is posted by hand the moment an order goes in, so expect a short delay between the live execution and the post — close, but not to the millisecond.

01.3 · The Risk Parameters
ParameterThresholdConsequence
Per-contract max weekly loss$1,000No more trades that week — stand down to next session
Consecutive weekly violations2 in a rowStand down for the remainder of the month
Rolling 100-trade realized EV$0 / tradeFalsifiability Gate fires — see Section 05
01.4 · The Cumulative Trajectory

Three trajectories. Published in equal weight.

ScenarioStartAfter Q1After Q2After Q3After Q4Doublings (log2)
Cooperative regime all triggers fire $5,000$10,000$20,000$35,000$55,000≈ 3.46 doublings (11×)
Floor regime 1 contract throughout $5,000~$6,500~$8,000~$9,500~$11,000≈ 1.14 doublings (2.2×)
Realistic envelope friction-adjusted $5,000$6–9k$7–17k$8–32k$10–50k ≈2–10×≈ 1.0–3.3 doublings (2–10×)

About the figures above. The trajectory table presents three illustrative outcome scenarios — cooperative, floor, and realistic-envelope — derived from the documented experimental protocol applied to a $5,000 reference allocation. These are hypothetical and projected figures, not realized results. They are presented for the purpose of describing the architecture’s structural behavior under stated regime conditions.

Hypothetical performance has inherent limitations. It does not reflect actual trading and cannot completely account for the impact of real-market factors on the execution of the protocol. The scenarios shown are derived from a defined methodology and assume continuous protocol execution under the stated regime conditions — assumptions that may not hold in live markets.

The figures should not be relied upon as a prediction of actual results. Past performance is not indicative of future results. Realized performance may differ materially from any scenario shown. The Falsifiability Gate (Section 05) supersedes all trajectory logic and halts the protocol if the rolling-100-trade expectancy crosses zero, regardless of capital level reached.

Three trajectories. Published in equal weight. The experiment’s success is defined as reaching the cooperative-regime endpoint without the falsifiability gate firing. The experiment’s “quiet outcome” is the floor case — capital preserved, edge expressed linearly, no triggers reached. The experiment’s failure case is the gate firing. All three are disclosed in advance.

What 12 months might look like

Aspirational equity arc · $5K → $50K in 12 months

One illustrative path under the doubling doctrine. The engine compounds via buffer-earned scaling 1 → 4 ES as the profit buffer accumulates. Cooperative target: 10× the working unit in 12 months — approximately three doublings plus change. Hard constraint: the trailing floor (HWM − 10% of working unit) representing the structural sit-out architecture — drawdown from any peak is bounded by the weekly cap and monthly stand-down cadence.

Aspirational · under stated assumptions. The cadence rules, position-scaling logic, and target multiples shown below are design intent — the cooperative scenario where all four buffers fire. The live reference dataset (84 closed trades · Feb–May 2026 · net +$6,695 · R-expectancy +0.30R) supports the underlying methodology; the rules below extend it. Nothing on this page constitutes a forecast or guarantee.
Engine balance · multiplier of working unit · stair-step, sized up by buffer Trailing floor (peak − 10% of working unit) Position scale-up · buffer fired
10× ($50K) 8× ($40K) 6× ($30K) 4× ($20K) 2× ($10K) 1× start ($5K) 0 mo 2 4 6 8 10 12 pos: 1 ES ↑ 2 ES · Buffer 1 ↑ 3 ES · Buffer 2 ↑ 4 ES (cap) · Buffer 3 ↗ floor: peak − 10% YEAR-END · TARGET 10× ($50K) aspirational · cooperative regime DOUBLINGS ≈ 3.3 (log₂ 10) WORKING UNIT × MULTIPLIER · $5K BASE

Engine target

10× ($5K→$50K)
earned doublings · cooperative

Doublings (log2)

≈ 3.3
log2(10) = 3.32

Hard constraint

Peak − 10%
structural sit-out · weekly $1K cap

Position scaling

1 → 4 ES
earned by profit buffer · cap at 4

Realistic envelope

2× — 10×
friction-adjusted band

Per-trade risk

~6% of unit
realized avg $303 / $5K · live

↑ All eight kill conditions are armed at every step

The ladder halts when any one fires — regardless of which step has been reached. These are the existing sit-out, falsifiability, and fidelity conditions on the live protocol; nothing new is invented for this visualization.

KC-01Rolling-100 EV ≤ $0/tradeEdge Gate · Expression Layer
KC-02Weekly $1,000 cap hitPer-contract · stand down rest of week
KC-032 consecutive losing weeksMonthly stand-down
KC-04Attribution breach (C-01)Missing tag or hand-applied H1
KC-05Rule-mod breach (C-02)Unwitnessed protocol modification
KC-06Daily routine < 95% (C-03)Pre-market visualizations · 30-day rolling
KC-07Loss streak > 4Battery Test 7 · discipline ceiling
KC-08Fidelity T2/T3 activeBinding Interpretation Rule · gate suspended

Disciplined Risk

Risk per trade stays anchored to a fixed fraction of the working unit. The dollar amount grows because the unit grows; the percentage never escalates. Realized average is currently ~$303/trade on the $5K unit (live, 84 trades).

Earned Leverage

Position size advances only when verified profits compound the base. The second ES contract is paid for by the first. Scale is earned — never borrowed, never assumed, never on operator confidence.

Velocity Compounds

Each buffer shortens the time to the next as throughput grows linearly with contract count. By the 4-ES ceiling, the engine is doing the heavy lifting and dollar outcomes climb non-linearly. 10× is just over three doublings — not a leap.

Aspirational and illustrative. Headline targets (10× engine, ≈3.3 doublings, 12-month window) are design intent, not forecasts. The cooperative scenario assumes all four buffers fire; the realistic envelope is 2×–10× (friction-adjusted). The trailing floor at HWM − 10% represents the structural intent of the existing sit-out cadence (weekly $1,000 cap + 2-week-loss monthly stand-down) — markets can gap and slip; nothing on this page is a guarantee. Past performance is not indicative of future results. Sample is pre-asymptotic at 84 closed trades.

02 · The Math, Live · From the Operator’s Account

The edge, calculated live.
Every fill. Every recalculation.

From the operator’s ES futures account. Computed live from closed fills. Recalculated each time a fill closes. No backtest values. No simulation. The numbers below populate from the live trade journal.

The Expected-Value Formula

How the edge is calculated. Every fill. Every recalculation.

From the operator’s ES futures account. Computed live from closed fills. Recalculated each time a fill closes. No backtest values. No simulation. The numbers below populate from the live trade journal.

Expected Value Formula · ES Futures · All-Time
Win Rate
—.—%
W / L
×
Avg Win
+— pts
$ per contract
Loss Rate × Avg Loss
−— pts
$ per contract
=
Edge per Trade
+—.—R
$ per trade
at % daily risk
EV = (Win% × Avg Win pts) − (Loss% × Avg Loss pts) EV = (% × + pts) − (% × pts) EV = + pts − pts EV = + pts per trade  ≡  +R  ≡  $ per trade
A win rate of on an asymmetric trade structure produces a realized edge of + per trade. Risk per contract is held constant at % of working capital. Variance loses to math at sample sizes where the central limit theorem dominates.
Sample Window
trades
Risk Budget
$/day
Win / Loss Ratio

Live, from the operator’s ES futures account. Sample is pre-asymptotic at this size. Past performance is not indicative of future results.

03 · The Edge Landscape · Where the operator’s edge sits

Where this sits in the doctrine. The doctrine’s Probability × Payoff Matrix names Probabilistic Edge & Positive Expectancy as one of eight paths in the High-Probability / High-Payoff quadrant. The migration formula is the same one the experiment runs: positive expectancy + volume + manageable failures. The table below is what that path looks like when instrumented, set against every other documented edge category in capital markets. See the matrix ↗

Every documented edge in capital markets. And where ours sits.

Six rows. Five reference points. One operator. Each row represents a category of capital deployment with documented edge characteristics. The Ekantik row is where our ES futures operator sits inside this universe.

Edge Landscape
Capital deployment by category
Ekantik row: extrapolated from live ES fills · as of
Strategycategory of capital deployment Edge / Occurrence% of capital-at-risk per trade Frequency / Motrades per month Annual R (unsized) · ranked ↓edge × frequency × 12, in R-units ½ Kelly Allocation ? Kelly Criterion
Optimal fraction of total portfolio capital to deploy for a given edge — not the same as the “Edge / Occurrence” column, which is % of capital-at-risk per single trade. Half-Kelly halves variance while retaining most of the geometric growth.
% of total portfolio capital
Casino · American RouletteHouse operator +5.26% ≥ 2,400 ≈ 1,500 R 1.4%
Trend-Following CTAsSystematic managed futures +0.5–1% 10 – 30 ≈ 56 R 2.5–7.5%
Stat-Arb Pairs / BasketsQuantitative mean-reversion +0.5–2% 200 – 500 ≈ 42 R 1.5–4%
High-Frequency Market-MakingSpread capture · sub-second +0.017% ≈ 100k+ ≈ 26 R ≈ 0.005%
Ekantik · ES FuturesAll-time · live operator account +% R %
Retail Day-Trader · medianESMA / FINRA aggregated negative 500 + − 30 R 0%
negative edge

Annual R is shown unsized — i.e., before applying the Kelly position-size recommendation in the rightmost column. The relevant metric for capital deployment is Annual R × Kelly Allocation, which is where structural edge actually expresses itself.

Sources. Casino house-edge figures: standard gaming regulatory disclosures; vary by table rules and machine class. Trend-following CTA performance characteristics: SocGen CTA Index, BarclayHedge CTA reports. Stat-arb edge characteristics: academic literature on equity pairs trading and statistical arbitrage. HFT market-making spread economics: SEC Tick Size Pilot data and academic market microstructure literature. Retail trader loss rates: ESMA aggregated broker disclosures, FINRA consumer alerts.

The Ekantik row is computed live from closed fills on the operator’s ES futures account, published in the public Discord trade journal, and recalculated each time a fill closes. Sample is pre-asymptotic at the current trade count. Past performance is not indicative of future results.

The operator.

“The best metaphor for the last decade is building aircraft autopilot software. You document failure modes before passengers board.”

Hiren Desai  ·  Founder & CIO  ·  Ekantik Capital Advisors

01

Cybersecurity origin

Resilient systems are built by studying what breaks them. Not by hoping they work.

02

Decade of practice

Stress-testing regimes. Mapping failure modes. Refining controls until behavior is predictable across the envelope.

03

Operator capital deployed

Personal risk capital on every fill in the public Discord log. Not pooled. Not managed. Not shared.

The edge described above is the output of that decade. The experiment is how it gets tested in public.

“Rule No. 1: Never lose money. Rule No. 2: Never forget Rule No. 1.”

— Warren Buffett
04 · The Architecture

How the experiment survives long enough to express itself.

Every experiment needs the conditions under which it admits the hypothesis is wrong. Every architecture needs the conditions under which the operator stops, regardless of conviction. The architecture below is the experimental envelope. The Falsifiability Gate (Section 05) is the experiment’s termination protocol.

01

Layer 01  ·  Never Lose Money

Rule No. 1, made structural — through adherence to the rules, not a cash cushion. Because a loss needs a disproportionately larger gain to recover (−50% needs +100% back), the discipline is engineered to stop losses long before capital reaches the point from which it cannot recover.

  • Working capital  ·  $5,000 per unit — the capital at work.
  • Position  ·  one ES contract requires only ~$500 in day-trade margin — a fraction of the working capital, never the whole.
  • Protection  ·  the never-lose principles (positive expectancy, expected value, position sizing) plus the Sit-Out and Falsifiability stand-downs cap the downside before the math turns unrecoverable.
02

Layer 02  ·  The Sit-Out Architecture

Pre-committed rules. No exceptions. No renegotiation.

  • Daily  ·  1 max loss  →  stand down. Resume next session.
  • Weekly  ·  $1,000 max loss per contract  →  stand down for the remainder of the week.
  • Edge recovery  ·  2 consecutive losing weeks  →  virtual account, full month.
05 · The Two Falsifiability Gates

Two gates. Both binding. Both reported live.

This is Condition V of a legitimate founding thesisnamed abandonment condition — operationalized in code, witnessed under countersignature, and structurally impossible for the operator to modify under stress. The doctrine names this condition. The architecture below executes it.

An experiment without a falsifiability condition is not an experiment. It is faith. This one runs two gates in parallel, from day one. The Expression Layer watches the edge’s realized math for decay. The Fidelity Layer watches whether the published method is what is actually running — cognitive, structural, and substrate discipline. Both were written before any outside capital is at risk, locked under witness countersignature.

Expression Gate Monitoring Rolling-100 EV: / trade · R: (size-neutral)
Fidelity Gate Monitoring Stand-down tier: T0 — Normal
The Binding Interpretation Rule

Edge-Gate firings while a Fidelity-Layer T2 or T3 breach is active in the rolling 30-day window are interpretation-suspended pending operator remediation. The edge cannot be declared falsified from data generated during a known transmission-fidelity breach.

This is published as a load-bearing architectural commitment, not buried in a protocol document. It is what makes parallel monitoring structurally coherent.

Stage 1 · Fidelity Layer — is the published method what is actually running?
01

Per-Trade Attribution Discipline

Auto-tracked · live from 5/22

Every qualified trade carries an operator tag — H2 (process breached) or H3 (variance), logged before the next entry against a pre-decision log. H1 (edge failed) is never tagged per trade — that verdict belongs to the Expression Gate’s rolling-100 reading, not to any single trade. A hand-applied H1 is itself a breach.

Tags filed (rolling 100)
Breaches (rolling 30)

Threshold: zero breaches inside rolling 100-trade window.

02

Rule-Modification Integrity

Witness-attested

Zero unannounced or witness-uncountersigned protocol modifications. Every change: 48-hour cool-off · written justification (which layer it addresses) · witness countersignature · public disclosure within 24 hours.

Unauthorized modifications
Days since last modification

Threshold: binary — zero breaches, period.

03

Daily Routine Adherence

Auto-tracked · live from 5/22

Three pre-committed daily visualizations, filed before market open: winning/stress rehearsal, predisposal trade decisions, and scaling-up/down law. Scaling triggers are not judgment calls.

Adherence (rolling 30 days)
Current streak

Threshold: ≥ 95% completion across rolling 30 trading days.

Stage 2 · Expression Layer — is the validated edge still expressing?
Edge

The Edge Gate

The condition under which the experiment ends. Live rolling-100 EV: / trade · rolling-100 R: per unit risked. The dollar figure is the locked trigger; the R figure is size-neutral — it does not move when position size scales across buffers, so it reads the edge cleanly through the doubling.

Trigger  ·  Statistical death
Rolling 100-qualified-trade realized expectancy drops to $0 per trade — the edge crosses into net-negative territory. The gate is active (provisional) from 80 trades and binding at 100; an 80-trade window carries only ~12% more sampling error than 100, so the safety net is live well before the full sample, while the binding call waits for it.
Action  ·  Immediate stand-down
New entries drop to zero size next session. Open positions close at their next defined exit per original trade plan. Strategy moves to research-only. Public Discord notification within 24 hours, including the rolling-100 expectancy figure and the trade ID that satisfied the trigger.
Re-deploy gate  ·  Earned re-entry only
Fresh out-of-sample test of ≥ +$50 per trade over 50 qualified trades (on virtual / paper / prop-firm capital)  ·  written re-derivation of the structural cause of decay  ·  48-hour cool-off after both. All three required.

Read the locked protocol (v2) → Doc Ref: FP-V2-2026-05  ·  Expression + Fidelity layers

Fidelity-Layer stand-down — graduated by breach type
Tier 1 · Logged breach

Single isolated breach of Criterion 01 or 03.

Logged within 24h + Discord entry. Witness review within 7 days. Stage-1 counter resets to zero. No size/operational change. Resume immediate.

Tier 2 · Conditions reduced

3+ breaches of Criterion 01/03 in rolling 30 trades, or sustained sub-95% routine adherence.

Position cut to minimum (1 MES, no scaling) for next 20 qualified trades. Daily filing under witness oversight. Resume on 20 clean min-size trades + witness countersignature.

Tier 3 · Full cessation

Any Criterion 02 breach, or a second Tier 2 inside rolling 100 trades.

Immediate cessation. Discord entry within 24h with structural cause. Witness structural review. Resume on countersigned remediation + 30-day calendar gap + 20 min-size trades.

Calibration: launch is 5/22/2026. Per-trade attribution (Criterion 01) is auto-tracked live from launch; the first 30 days are observation-only while baseline adherence is established, binding from day 31. Witness: Manish Dharod, with binding authority over modifications, breach classifications, and Stage-1 resumption events (locked protocol, Article VII). The remaining Phase-3 automation — daily-routine scoring, automated breach detection, and the stand-down state machine — rolls out within 30–60 days of launch.

Stand-Down State · Live

The current operating state — in public, in real time.

Failure-state visibility equals success-state visibility. This widget renders the real operating tier with the same prominence whether it’s normal operations or a Tier-3 cessation. No retroactive editing — the audit trail is the artifact.

Stand-Down State T0 — Normal Operations
Last eventNone on record
Stage 1 counter— qualified trades
Active breach events0
Pending witness reviews0

Resumption conditions

08 · Live Evidence

The experiment, instrumented.

Every metric below is realized — measured from closed fills on the operator’s own capital, recalculated as each new fill closes. Trigger fires render with timestamps. The full instrumentation lives on the experiment dashboard.

Win Rate

Live · closed trades

Profit Factor

Gross wins ÷ gross losses

EV per trade

Per unit of risk · live realized

Avg risk per trade

What 1R equals in dollars · live realized

R-multiple distribution  ·  the asymmetry

Avg win in R-units
Avg loss in R-units
Win : Loss ratio A winning trade outperforms a losing trade by this multiple, in R.

Win rate and R-multiple move independently. A strategy can lose more trades and still earn more per unit of risk — if wins are large enough relative to losses. This is the structural reason R-expectancy holds.

Risk profile  ·  what the strategy has actually tolerated

Drawdown is the path the Falsifiability Gate watches.

Headroom (above) shows what the edge could mathematically support. This is what it has cost the operator’s personal capital to produce the live record — the variance the defense architecture has weathered without modification.

Max realized drawdown computing… at live sizing · per 1 ES contract equivalent
Longest losing streak computing… Battery Test 7 threshold: ≤ 4 consecutive losses
Worst single trade computing… single deepest realized hit
Recovery from max DD computing… trades to restore the prior peak

Computing live risk profile…

Sample Equity Arc — $5,000 working unit · live

Live equity progression on the operator’s own capital, from the $5,000 working unit. The arc prints as each Discord fill closes; each dashed line marks a $5,000 profit-buffer threshold (full mechanism in §01.2 Trigger Ladder; aspirational 12-month path in the Compounding Ladder above). Capital resets to the working unit annually.

Current balance
Net P&L
Profit buffers reached

Monthly P&L — contribution per month

Net dollar result per month, summed from closed fills. Green = profitable month, red = losing month. Independent monthly cash signal — not cumulative wealth.

Past performance is not indicative of future results. Sample is pre-asymptotic at this size. Realized expectancy is published live and is the authoritative reference.

The Architecture, At Scale

Three principles. Three real-life proofs.

The same defense-plus-compounding architecture, demonstrated by the operators best known for each underlying principle.

Principle 01

“Permanent capital, redeployed at higher returns.”

Never-lose foundation

Insurance float as a low-cost, near-permanent capital base. Strict underwriting discipline. Conservative leverage. Survival before scale.

Compounding engine

~20% CAGR over five decades, compounded by redeploying float into high-ROIC operating businesses rather than chasing variance.

Principle 02

“Capped capacity preserves the edge × time product.”

Never-lose foundation

Refused new outside capital at the exact moment doing so would have diluted the edge. Strict position-size and risk-budget rules. Employee-only since 1993.

Compounding engine

Small mechanical edges, executed without exception, at a size the market can absorb without degrading the edge. The math compounds because the cap was set before the temptation arrived.

Principle 03

“Risk-controlled architecture survives every regime.”

Never-lose foundation

Risk limits, position-size controls, and a capital base sized so no single event can take the firm out. Declines external capital that would dilute discipline.

Compounding engine

Small edges × massive volume × strict risk management × decades of operation. Compounding measured in firm equity, not portfolio returns.

We are not inventing this. We are applying the same architecture to a live, publicly conducted experiment — a documented, falsifiable trading edge with personal capital on every fill.

06 · Participation

Two ways to engage with the experiment.

The experiment is publicly conducted. The purpose of publication is credibility — to put a real architecture, a real method, and a real falsifiability gate in front of anyone who cares to evaluate them. Two ways to engage, both honest about what they are.

Witness the experiment

Free · Unlimited · Public Discord community

Watch every trade as it executes. See the EV calculation update fill-by-fill. Watch the trigger ladder fire. See the Falsifiability Gate run. Engage with other observers. Ask questions of the operator. No fee, no cap, no relationship required.

One honest caveat: each fill is posted to Discord by hand, the moment an order is placed. Because a human logs it, expect a short delay between the live execution and the journal entry — the posts track the trades closely, but not to the millisecond.

The Discord is more than a journal. It is the community around the work — where the method gets discussed, where edge cases get debated, and where the experiment is observed by people who want to think rigorously about what it shows.

Join the public Discord

Reach out with questions

Concepts · Methodology · Context · Fit

If something about the experiment raises questions — about the method, about the underlying concepts, about how to think about this in your own context — the operator is reachable directly. Drop a note. The form below opens a private conversation.

No agenda on either side. Just a real exchange about the work and whatever you want to understand about it.

Reach out

Sustainability — Verified Eight Ways

Edge sustainability. Verified eight ways.

Every edge can look real in a small sample. This is the battery we re-run against live trade data to prove it isn’t. The edge claim in the comparison map above is only credible if the battery says it is. Run it on our data. Run it on yours.

Or run it on your own trade data. Your file never leaves your device.

Loading…

Showing YOUR uploaded data. Results below are computed on your trades. Click "Reset to Ekantik sample" to return.
Loading battery…
Run the battery on your own data

Upload a Tradovate CSV, Discord JSON export, or paste raw Discord alert messages. The full 8-test battery runs in your browser — your data never leaves your device.

Step 1 — Upload a file

Step 2 — or paste text

Step 3 — Run the battery

Full Glossary — Understanding the 8 Tests

Click any attribute above, or expand a card below, for the deep dive — analogy, pass/fail examples, threshold rationale, and the math behind the number.

Loading glossary…
Battery history — every past run, archived
Month Sample Size Tests Passed Snapshot
Loading…
View the battery source code →

A battery is only as credible as the data feeding it. The next section is how you can see every fill, in real time, as it happens.

Validation — your eyes, not our word

Every fill, in public.

Every metric on this page is computed from these fills. You can watch each one happen.

Live Alerts

Last 5 fills
Loading…

Live mirror of the last 5 fills from the Discord trade journal. The journal is open to anyone — no submission required — and every executed trade posts there in real time.

Discord posts run ~60 seconds behind the actual fill.

The operator types each alert in by hand after the order is entered at the broker, so by the time you read “Short @ 7141” on Discord the entry was already taken. The feed exists so you can verify every fill against real markets and study how the strategy reasons about entries, exits, sizing, and stops — it is a window into the mechanism, not a signal to follow. Don’t try to mirror entries off the timestamps.

Public Trade Log

ID Date/Time Dir Entry Exit Pts $ P&L Result R
Loading…

Full log available. Download it, run it through any evaluator you trust.

The doctrine’s close, restated here.
Don’t pick a profession. Pick a mechanism.

This page is one mechanism, running live, in public. The doctrine is the framework for recognizing the structural signature when you see it in your own domain — your career, your business, your capital allocation, your edge.

09 · Reach Out

Reach out.

Have a question about the experiment, the method, or how to think about this in your own context? Drop a note below. The operator reads each one personally. This is a private inquiry path — not an application, not an offer acceptance, and not an expression of intent to participate in anything.

Replies typically within 48 hours. Submissions establish a private contact channel; they create no obligation on either side. This form collects no financial information and does not constitute an application, subscription, or expression of intent to invest.

Note received.

Thanks for reaching out. The operator reads each note personally and typically replies within 48 hours. This exchange creates no obligation on either side.