Operational
Evidence engine
Baseline + four atomic perturbations + one joint execution stress
System status / disclosure
What is live.
What is not.
EPSILON separates working behavior from future ambition. This page is the public contract for method, data, and limitations.
Operational
Rejection rule
Machine-evaluable metric, operator, threshold, and required scope
Operational
Portable artifact
epsilon.evidence.v2 JSON with calculation checksum and data fingerprint
Documented
Execution timing
Signals use information through the prior close; positions apply to the next return
Not connected
Real-capital execution
Research instrument only; no orders, brokerage, or custody
Evaluation access
Historical adapter
Adjusted daily bars are queried server-side under the owner’s provider account and remain subject to provider terms.
Method / no hidden leap
What the verdict means.
Pre-register
A claim is paired with a metric, comparison operator, threshold, and perturbation scope before computation.
Lag signals
Historical strategies use only information available through the prior close. This prevents same-period look-ahead.
Perturb locally
Four one-factor runs isolate sensitivity; one joint stress exposes execution interactions. Survival is evidence of local robustness, not proof.
Keep the trail
The export includes configuration, exact outcomes, baseline ledger, provider provenance, limitations, and a deterministic checksum. The checksum detects changes; it is not a signature or proof of origin.
Limitations / read before use
Honest boundaries.
- Not investment advice.Results are research outputs and do not recommend trades or predict future performance.
- Historical universes are user-selected.EPSILON does not yet provide a point-in-time constituent database, so survivorship bias remains possible.
- Adjusted bars simplify reality.Daily close-to-close simulation omits intraday liquidity, market impact, taxes, borrow constraints, and partial fills.
- Public open corpus is pending.The bundled corpus manifest remains unapproved; it is not used by the production engine.
- No account or storage layer.Claims and settings are processed to produce the response and are not stored by EPSILON.