SAPIENEDGE
SHADOW
ACCOUNT$22,486
POSITIONFLAT
MARKETCLOSED 09:16:56 ET
SNAPSHOTDEAD age6.8h

Live today's alert tape

SESSION2026-10-05 ALERTS0 SHOWN0
SHADOW MODE · NOTHING WAS SENT. No order left this machine. Every ticket on this page is a proposal on a screen — the click is a human's.

His size is the author's own fill. Our size is what this account would take under its own ceilings — and on a refusal it is zero, not the number the ticket would have used. The gap between the two columns is the entire point of this screen.

TIMECONTRACTACTION HIS SIZEOUR SIZE OURS : HISVERDICT
No alert for 2026-10-05. Last session with alerts: 2026-08-03.

Position what is actually deployed right now

FLAT
SEM_POSICAO · the bot's state document is intact and says flat

The bot's own state document is intact and reports flat. Nothing is deployed.

Protection — what the engine would do now

no open position to protect

Risk the ceilings in force and what is left of today

ENGINEOK
DAILY LOSS BUDGET$0.00 / $444
TRADES TODAY0 / 3
PREMIUM ENVELOPE$0.00 / $2,000

Ceilings in force

Envelope$2,000hard ceiling on premium deployed at once
Equity reference$22,200declarado_humano:live SnapTrade read taken in the Classic
Exposure per trade2.5%
Risk per stop2.5%
Exposure total5.0%
Daily loss$444
Max trades / day3
Max concurrent1
Hard contract cap1
Max round-trip spread5.0%
Default stop25.0%

Policy conflicts (resolved to the tighter side)

VERBATIM FROM ANOTHER MODULE · the lines below were written by the engine that produced them (sapien/protecao.py, sapien/risco.py) and are printed exactly as received. Those modules speak Portuguese; this screen does not translate them, because a paraphrased engine reason is a reason nobody can grep for in the engine.

Brakes

Kill-file directory/root/ophi-sapien-data/kill
WritableYESa brake that cannot be pulled is not a brake
Kill files presentnone present

PORTOES_NAO_AVALIADOS · risk gates were NOT evaluated: they require a live two-sided quote and a fresh bar, neither of which exists on this read-only port. A gate list built from zeros passes every ceiling.

History the alert corpus, graded

STATEOK SOURCEEnhancedMarket alert corpus, grouped by POSITION
GROUPED BY POSITION, NOT BY ALERT. One position is one entry and every exit that unwinds it; each position counts once, weighted by quantity. Counting per message weights every partial trim as if it were a whole trade — winners exit in many messages and losers in one, so the per message average is inflated by roughly an order of magnitude and can flip the sign of the result.
POSITIONS
427
WIN RATE
67.4%
MEAN RETURN
+3.76%
PROFIT FACTOR
1.30
return scale, size-independent
MEDIAN
+12.73%
BEST
+257.14%
WORST
-99.75%
PROFIT FACTOR ($)
1.37
the author's dollars at the author's size

Cumulative return

SERIES NOT PUBLISHED · the snapshot carries aggregates only (n, win rate, mean, median, profit factor) and no per-position series. This chart draws the moment edge_dados publishes historico.retornos_pct (per-position returns, in chronological order) or historico.curva (cumulative points). Nothing is drawn from the mean and the extremes: a curve inferred from three aggregates is an invented curve.

Waiting on one upstream key: historico.retornos_pct or historico.curva.

Why this is grouped by position

PER POSITION
+3.76%
the honest figure
PER MESSAGE
+28.88%
the trap
EXITS / WINNER
5.06
EXITS / LOSER
1.41

Winners are scaled out over many messages, losers exit in one. Averaging per message weights every trim as a whole trade and inflates the mean by roughly an order of magnitude. The number this dashboard reports is the position one, weighted by size.

Sample accounting

Chains seen434
Graded427
Closed in corpus406
Entry never seen21
Excluded — no exit5
Excluded — ungradeable2
Every chain accounted forYESif this is NO, a position vanished and the sample is lying about its own n

Cross-check against the source's own published P&L

weighted mean of the slices vs the 'PnL total' the source itself published at the end of the chain — in-corpus ground truth for the grouping

Comparable chains325
Agree318
Disagree7tolerance 2.0 pp

computed on the RETURN scale: each position counts once, independent of its dollar size. This is the size-independent figure and the only one that transfers to this account.

Journal the day, in order

SESSION2026-10-05 AS OF09:16:56 ET
DERIVED TIMELINE. The snapshot publishes no journal block, so this is assembled from the alert tape, the open position and the watcher heartbeat. It is not sapien/journal.py's append-only day file, and it does not claim to be.
TIMEKINDWHAT
Watcher stateNUNCA_ESCREVEU
Watcher files0
Heartbeat ageUNKNOWN

VIGIA_NUNCA_ESCREVEU · the watcher output directory does not exist: it has never written. This is different from 'its heartbeat is late'.