JARVIS-backed stance, evidence flow, and adaptive restraint.
The Living Algo
A trading OS with restraint in motion.
A public operating record for ETA: aggregate run actions, evidence progress, safety stance, and strategy lifecycle state without exposing restricted topology or controls.
Operating layers
One system, three public-safe roles.
ETA separates adaptive policy, governance, and dissent so public visitors see the operating shape without seeing control surfaces.
Public map
Clustered architecture, not restricted topology.
Six conceptual roles run the loop: the regime judge reads market state, the edge court tries candidates, the risk governor bounds exposure, the promotion lock holds allocation, the evidence publisher writes the record, and the retirement bench logs what stepped down. The public surface shows the roles and their posture. It does not publish source paths, control-plane wiring, execution details, or command affordances.
Boundary reader
Select a domain for public-safe detailThis scanner explains what can be shown publicly while execution controls, topology, account fields, and diagnostics stay off page.
Strategy lifecycle
Weak candidates are supposed to stay gated.
ETA treats non-promotion as a feature of the operating system. Research, paper soak, quarantine, and allocation eligibility are separate public states.
Ideas under thesis review. No allocation implication.
Prior paper roster closed; retained as shadow benchmarks and negative controls.
Excluded from promotion until evidence-backed edge recovers.
No public claim of investability or unmanaged promotion.
Gate stance
Promotion waits until the gates agree.
Public visitors see coarse gate state. Approved operators see the full review record.
Evidence gate
Evidence receipts must clear sample quality and review requirements.
Risk gate
Order-entry and promotion controls stay protected when runtime safety is unresolved.
Operator gate
Operator approval is required for allocation-affecting changes.
Public boundary
No website route can mutate execution, runtime, strategy, or account state.
Trust boundary
Readable proof, restricted controls.
- Published record
- Integrity state, strategy lifecycle classes, proof records, and public-safe ops status.
- Protected review
- Identity data, financial fields, restricted review records, system topology, and controls.
- Never implied
- No return promise, no advice, no solicitation, and no claim that paper evidence predicts future results.
Every public value is aggregate or categorical by design; sensitive records, identity-bearing fields, and control actions stay outside the website read model.
- Runtime system signals are translated through a public projection model.
- Restricted topology, diagnostics, execution artifacts, and controls are redacted.
- The website route is covered by source-contract, render, and build verification.