A pre-committed operational charter · v1.5 · Majority Opinion Predisposal Strategy + Synthetic-Passive Overlay
Governing both engines of Ekantik 500: the Majority Opinion Predisposal Strategy on ES & MES futures (the active engine), and the synthetic-passive overlay on the SPY foundation (new in v1.3). Issued by the operator. Witness-locked. Publicly disclosed. Modification subject to a 48-hour cool-off and written justification.
| Document | Falsifiability Protocol · Locked Operational Charter |
| Version | 1.6 — Revision to Article V (Fidelity Layer). The fixed 2-contract ceiling is removed; contract count now scales with NLV at Standard sizing of 1 /ES per $100K NLV, earned through accumulated profit buffer, with no upper cap. Rationale: the v1.5 ceiling assumed a portfolio-margin capacity tied to a specific account size; uncapping with explicit Standard sizing makes the architecture honestly scale with capital. The 0.5% per-contract risk anchor is preserved verbatim — total per-trade exposure now scales as 0.5% × Standard contract count, and the ED-05b hard kill scales correspondingly to a consistent 5% of NLV at Standard sizing regardless of account size. All ED thresholds and other articles preserved verbatim. Witness countersigned. (v1.5 history: contract-count ceiling made explicit at 2 /ES, now superseded. v1.4 history: ED-05b hard kill revised from −75 ES pts → −100 ES pts ($5,000 per contract); OP-06 bi-weekly size reduction revised from 1/5 of normal → 1/2 of normal. ED-05a, the bootstrap rationale, and Article VIII (added v1.3) unchanged.) Change log appended to each affected article. |
| Reference | FP-MOPS-V1.6-2026-06 |
| Strategy | Majority Opinion Predisposal Strategy · ES / MES Futures |
| Vehicle | Ekantik 500 · Active /ES Engine Layer |
| Issuing entity | Ekantik Capital Advisors LLC · Maple Grove, MN |
| Date locked | ____ May 2026 |
| Distribution | Public · epig500.ekantikcapital.com |
Every credible system pre-defines the conditions under which it admits failure. Most trading operations do not. This one defines two — and runs them in parallel.
The Expression Layer (Articles I–III) defines the precise statistical threshold at which the operator agrees the Majority Opinion Predisposal edge is dead, the stand-down sequence, and the re-deployment gate. The Fidelity Layer (Articles V–VI) defines the criteria under which the operator admits the published method is not what is actually running — independent of whether the edge itself is sound.
The two layers are bound by a single interpretation rule. The edge cannot be declared falsified using data produced while transmission fidelity is in breach. Both layers are reported on the public page in real time.
The operator agrees to declare the edge statistically dead upon satisfaction of any one of the following conditions, evaluated continuously across the documented qualified-trade record:
A qualified trade is one entered and exited under all operative documented rules, unaffected by execution error, platform malfunction, or extraordinary market event. The trigger is satisfied at the close of the trade that first brings any of the conditions to its threshold.
The reference dataset shows documented per-trade EV of +$117 with standard error over a 100-trade window of ~$43. The $0 threshold (ED-01) sits roughly 2.7 standard errors below documented EV — statistical evidence of collapse, not noise. The remaining seven conditions probe different failure topologies (distributional shift, asymmetry decay, outlier dependence, tail-risk breach, ruin-line proximity). The edge is declared dead when any one of the eight fires.
The original v1 specification set a single −30 ES-point kill, calibrated to the worst observed max DD of the reference dataset (−29.14 pts in original order). That calibration was inappropriately tight. Bootstrapping the 227 trades with 50,000 random orderings — preserving the empirical edge but resampling the path — yields the distribution of max DDs that the same edge naturally produces:
1st pct: −75.6 pts · 5th pct: −61.7 · 25th pct: −47.1 · median: −39.6 · 75th pct: −33.8 · 95th pct: −27.8
The observed −29 pt DD therefore sits at the ~93rd percentile of bootstrap orderings — the historical record happened to be on the lucky side of the distribution. A −30 pt kill would fire in approximately 95% of random orderings under the same healthy edge: a kill on noise, not signal. The split-tier replacement, anchored to bootstrap percentiles, preserves the gate's intent while passing the variance-of-the-same-edge test:
ED-05a (warning, −45 pts) sits between the median (−40) and the 25th percentile (−47). Firing here means the operator is in the worse 75% of paths under a known-healthy edge — worth a Tier-2 conditions-reduced response, not a hard cessation. ED-05b (hard kill, −100 pts ≈ $5,000 per /ES contract) sits beyond the 1st percentile of the bootstrap (which was −75.6 pts). Crossing it is therefore even stronger evidence of edge failure than the prior v1.1–v1.3 −75 threshold — well under 1% of paths under the documented edge reach this line. The round-number, dollar-anchored ceiling preserves the architecture-linked intent while making the cap operationally intuitive for size-up decisions.
Change log (v1.4): hard kill threshold revised from −75 pts → −100 pts ($5,000 per /ES). The v1.1–v1.3 figure was bootstrap-derived (1st percentile of 50,000 reference-dataset orderings); the v1.4 figure sits deeper, accepting a fractionally lower false-positive rate in exchange for a round dollar-anchored cap. ED-05a (warning, −45 pts) unchanged. Bootstrap percentiles for reference: 1st −75.6 · 5th −61.7 · 25th −47.1 · median −39.6.
Bootstrap script and result CSV will be published alongside this protocol as bootstrap-ed05.csv for independent verification. Investors at any account size can re-run the analysis using the public reference dataset.
Upon satisfaction of any trigger condition in Article I, immediately and without exception:
The strategy does not return to live deployment until all three conditions are satisfied:
Stand-down requires only evidence that one of the eight Expression-Layer thresholds was crossed. Re-deployment requires evidence of meaningfully positive expectancy (+$50 per trade) plus a battery pass plus written structural diagnosis. Quick to fail; slow to forgive. The asymmetry is deliberate: false positives on cessation are recoverable; false positives on resumption are not.
Any modification to this protocol — thresholds, window sizes, action steps, re-deployment criteria, cool-off periods, or any Fidelity-Layer criterion — is subject to:
Is the published method what is actually running? Each criterion is pre-committed, observable, binary-checkable, and time-bounded — mapping to a distinct layer of operator fidelity: substrate, intraday, structural, cognitive.
Sizing anchor & Standard sizing (OP-anchor · revised v1.6). Per-contract risk is fixed at 0.5% of NLV — the architectural anchor; it never escalates. Contract count scales with capital at Standard sizing: 1 /ES per $100K NLV, with each contract earned through accumulated profit buffer, never assumed. There is no fixed ceiling — the engine scales with the account. At Standard sizing, total per-trade exposure therefore scales as 0.5% × contract count, and the ED-05b hard kill scales correspondingly to a consistent 5% of NLV regardless of account size. Scaling at a faster rate than Standard requires explicit witness sign-off per Article IV.
Every entry follows the published Majority Opinion Predisposal rule set without modification. The frozen process is the experimental constant; any modification mid-flight resets the evidence window. The witness — not the operator — approves any rule change, subject to the Article IV protocol.
After any closed losing trade, no further entries that session. The day ends on the first loss — regardless of setup quality, conviction, or remaining time. This is the load-bearing intraday rule: it structurally eliminates revenge-trading, instrument-switching, and post-loss impulsivity in a single bound. There is no exception for "the next setup looks good." The day is over.
Cumulative same-day P&L is bounded by a trailing high-water mark floor. The floor starts at −0.5% of NLV (one trade's worth of risk at the architectural anchor) and ratchets up automatically as accumulated profit creates buffer above the prior peak. Replaces the v1.0 fixed −12 ES point cap, which did not scale with account size or with realized profit.
Every qualified trade receives an operator attribution tag — H2 (process breached) or H3 (variance) — logged before the next entry, against a pre-decision log (rationale, expected outcome, frozen-process checklist). H3 is the resting attribution; H2 is the exception. H1 (edge failed) is not an operator attribution and is never applied to a single trade. "Edge failed" is a verdict about the strategy, knowable only across a sample — so it is system-derived: H1 is declared solely by the Expression Gate's rolling-window verdicts (Article I), subject to the Binding Interpretation Rule. H1 is locked out at the per-trade level by design.
2–3 consecutive losing trading days within a single calendar week triggers a mandatory sit-down for the remainder of that week. The engine resumes on the following Monday at standard sizing, pending witness review of the loss cluster. This is the bridge between the intraday discipline (OP-02 / OP-03) and the structural cessation rules (Tier 2 / Tier 3): it dampens variance clustering before it escalates.
A second consecutive losing week (where "losing week" is any week ending net-negative on closed trades) triggers an immediate sizing reduction to half of normal — for example 5 /MES in place of 1 /ES, an equivalent 50% cut in dollar exposure per trade while preserving the same instrument's tick mechanics. The reduction holds until OP-07 reinstatement conditions are met. Daily filings transition to witness oversight for the duration of the reduction window.
Standard sizing reinstates only after 5 good trades at the OP-06 reduced size. A "good trade" is a closed trade with: no OP-rule breach; correct H2/H3 attribution per OP-04; and contribution to a net-positive cumulative P&L across the 5-trade window. Witness countersigns the reinstatement event. If the OP-06 window produces a third consecutive losing week, escalation to Stage-1 Tier-2 cessation is automatic.
| Tier | Trigger | Response | Resume |
|---|---|---|---|
| T1Logged breach | Single isolated breach of OP-02, OP-04, or OP-05 (weekly sit-down event). | Logged within 24h + Discord entry. Witness review within 7 days, written corrective action. Counter resets to zero. No size or operational change. | Immediate; counter restarts at zero. |
| T2Conditions reduced | 2+ breaches of OP-02 or OP-03 in rolling 30 trades. OP-04 H1 misapplication. OP-06 automatic trigger (2nd consecutive losing week). OP-07 reinstatement breach. | Position cut to minimum sizing (1 MES, no scaling, no /ES) for next 20 qualified trades. Daily filing under witness oversight. Counter resets. Trading continues at reduced conditions. | 20 clean minimum-size trades + witness countersignature. |
| T3Full cessation | Any OP-01 breach. Or a second T2 inside rolling 100 trades. | Immediate cessation; new entries → zero next session; open positions exit per plan. Discord entry within 24h with breach, structural cause, remediation pathway. Witness convenes structural review. Protocol update if breach revealed structural inadequacy. | Witness-countersigned remediation artifact + 30-day calendar gap + 20 minimum-size trades. |
Calibration. The first 30 days following public launch are observation-only while baseline adherence is established; the Fidelity Layer is binding from day 31. The Expression Layer (Articles I–III) is binding from day one.
The named witness for this protocol is Manish Dharod, who holds authority over: modification approvals (Article IV), breach tier classifications (Article VI), Stage-1 resumption events (T2 / T3), and overlay-rule lockings (Article VIII). The witness signs that protocol was followed; the witness does not endorse the substance of any decision or modification.
witness-audits.json. Without the monthly artifact, the "witness reviews monthly" claim is itself in breach.Status note (v1.3): The structure of the overlay's two gates — Fidelity and Expression — is committed in this article. The quantitative thresholds (specific trigger conditions, exposure step sizes, beat-or-protect %) are documented here as design intent. They will be locked under Article IV's modification protocol (48-hour cool-off, written justification, witness countersignature by Manish Dharod) before any investor capital is deployed. Until lock, the overlay is illustrated on the public page as a hypothetical-inputs calculator; it does not run on live capital. This article describes what the overlay will be under the locked v1.3.
The synthetic-passive overlay reduces the SPY foundation's exposure only when published, rules-based triggers fire — never on discretion, sentiment, or short-term price action. The full default state is 100% of the foundation allocation invested, and the overlay steps aside only when both of two conditions hold: (1) price is exhausted at the highs, and (2) a real seller is showing up — the "who-would-sell-here?" test. Price high + no seller = stay long. The overlay carries three published exposure states, set by who is selling:
The wrong-line rule — if the operator misjudges: at every exposure decision, mark the level a dip of that size should hold. A daily close below that line → drop one rung. No debate.
Restoration — stepping back in: re-entry begins when sellers exhaust and buyers return — fundamentals fine, exhaustion complete. Half first → full on confirmation. The deeper the drawdown, the more time required before re-entry. Restoration is rules-based with the same confirmation discipline; no discretionary "I think the bottom is in" overrides.
Kill switch: over a full cycle, if the overlay doesn't beat or protect more than just holding → go pure passive. This is the VIII.B Expression gate below, stated in execution terms.
The exact seller-confirmation criteria, exhaustion definitions, wrong-line placement rules, lookback windows, and re-entry confirmation logic are the quantitative thresholds referenced in the status note above. They will be locked before capital deploys.
The overlay's expression gate measures whether the rules above are actually producing the asymmetry they claim. The test is cycle-level (not month-level or year-level) because asymmetric capture only proves itself across at least one full market cycle including a meaningful drawdown.
The synthetic-passive overlay and the futures engine share one account. When the overlay reduces SPY exposure (State B or C), the SPY collateral backing the futures engine's portfolio margin reduces with it. The two are coordinated by rule, not improvised:
Every overlay decision — each State A → B step-down, each B → C deepening, each restoration — is published to the live dashboard within 24 hours, alongside the trigger conditions that fired. The rolling overlay-alpha figure (5-year then cycle-level) is computed live and visible. The overlay's Fidelity-Layer compliance is part of the monthly witness audit (Article VII).
By signature, the operator attests this protocol was derived prior to the deployment of member capital and is hereby locked as the governing operational charter for the Majority Opinion Predisposal Strategy. Witness signature attests only that the modification protocol was followed.