System Status: Warming Up
Checking system health.View status
Checking session
Public proof recordReal tracked signallosspending windowIntegrity: Verified
Forensic rowDetected Jun 3, 11:04 PM UTC
Share proof record
Frozen-friendly record: detection time, recorded rationale, posture at detection, checkpoints, integrity hash. Not marketing copy.
Executive summaryCompleted as a loss (-0.4%)

VIRTUAL/DEUS was detected on BASE / aerodrome-v2 with a blocked posture. The signal is currently pending window with 1 of 4 checkpoints recorded. The system blocked the setup, but the recorded outcome does not yet show a clear avoided-loss case.

1 complete checkpoints2 pending
Routing & metadata (frozen)How this row was classified for the public surface
Ledger fields
Product lane · alpha
Operator actionSame model as radar cards
How to read this signal
CompletedReadiness high
ActionDo not act on this lane.
Promote when—
Breaks ifpolicy or coverage blocks row

Signal arc (structured read)Change on record: Guardrails stay active while recent movement (-0.4%) remains mixed — keep this in review, not promotion Outcome on record: loss Recorded risk edge: policy or coverage blocks row Liquidity structure supports follow-through instead of fragility

Outcome on record (loss) — read as retrospective context here.

VIRTUAL/DEUS launch radar signal

Blocked by execution mode mismatch. Outcome tracking later marked the 30m window as a loss.

BASEaerodrome-v2blockedsmart wallet detectedcorrelatedguardrail blocked
Record index
Detected atJun 3, 11:04 PM UTC
Published atJun 3, 11:36 PM UTC
Overall score60
Posture at detectionblocked
Verification IDproof_fdaf45656644df40
Integrity hashVerified
Outcome checkpoints1 of 4 recorded
Shareable recordExports use the same fields as this page.

PNG/JSON/text exports pull from the stored public projection—posture, checkpoints, verification ID, integrity metadata.

Share this proof record
Detected Jun 3, 11:04 PM UTC · BASE / aerodrome-v2 · Alpha · loss outcome at 30m · loss -0.4% on ledger · verification proof_fdaf45656644df40
No-edit / trust notes

Hashes gate tampering: if the payload drifts, integrity shows mismatch while still rendering the locked snapshot for audit.

Timestamps above are rendered from stored ISO fields, not rewritten for narrative
Posture reflects what the system recorded at surfacing—not retrofitted after outcomes
Losses and blocked rows use the same classification rules as methodology
Exports are derived from the identical JSON payload used for verification
Framing (stored)
This was detected at Jun 3, 11:04 PM UTC before the outcome.

This text is part of the persisted public projection. It explains detection context and evaluator posture without exposing workspace-only controls.

Integrity: VerifiedHash version v1

The current proof content matches the stored public hash for this published record.

Final classificationloss
Best move-0.4%
Worst move-0.4%
Latest move-0.4%
Rationale

Reasoning

Blocked by execution mode mismatch. Outcome tracking later marked the 30m window as a loss.

Why this mattered

The score mix indicates how much structural quality, risk, and momentum support this setup has right now.

Decision reasoning

Decision=watch with structural=54, risk=66, momentum=84.44; promotion requires cleaner reinforcement.

Risk context

Risk and control layers are shaping whether this setup can move forward.

Strategy posture

No strategy recommendation is attached yet.

Risk / uncertainty

What could limit this setup

blocked

Blocked by execution mode mismatch.

The opportunity can still be reviewed, but the current path stops before execution.

Outcome summary

Outcome summary

loss

Loss is classified from the latest completed 30m checkpoint.

Classification window: 30m
Completed checkpoints: 1 · Pending checkpoints: 2
Decision impact

Why the posture mattered

Blocked with no clear downside yet

The system blocked the setup, but the recorded outcome does not yet show a clear avoided-loss case.

Cautionary setup
Timeline

Timeline & timestamps

Detecteddetected
Jun 3, 11:04 PM UTC
VIRTUAL/DEUS observed on BASE / aerodrome-v2. Detection timestamp is stored as shown.
Reasoning (policy snapshot)rationale
Jun 3, 11:04 PM UTC
Blocked by execution mode mismatch. Outcome tracking later marked the 30m window as a loss.
Posture at detectionblocked
Jun 3, 11:04 PM UTC
Execution support posture was recorded as blocked at the time of surfacing.
Published to public ledgerverified
Jun 3, 11:36 PM UTC
Verification ID proof_fdaf45656644df40 locked at publication. This page renders the same payload the hash covers.
5m checkpointpending
Pending
This checkpoint has not been recorded yet.
30m checkpointloss
Jun 3, 11:35 PM UTC
Outcome recorded as loss with -0.4% move.
4h checkpointpending
Pending
This checkpoint has not been recorded yet.
24h checkpointpending
Pending
This checkpoint has not been recorded yet.
Current statuspending_window
Jun 3, 11:36 PM UTC
Evaluator / integrity state: pending window.
Outcome chart

How the tracked move evolved

30m -0.4%
Shareable proof

Export-ready proof cards

Kahramana Intelligence
blocked
Opportunity proof
VIRTUAL (VIRTUAL)
DEUS (DEUS)
VIRTUAL/DEUSVIRTUAL / DEUS
BASEaerodrome-v2Detected Jun 3, 11:04 PM UTC
Overall score
60
Liquidity
$80578.82m
Why this matters

Blocked by execution mode mismatch. Outcome tracking later marked the 30m window as a loss.

smart wallet detectedcorrelatedguardrail blockedblocked
Outcome context
30m loss -0.4%
Verification ID: proof_fdaf45656644df40
Kahramana Intelligence
loss
Outcome proof

VIRTUAL/DEUS

BASEDetected Jun 3, 11:04 PM UTC30m window
Outcome after 30m
-0.4%
Context

This was detected at Jun 3, 11:04 PM UTC before the outcome. Outcome tracking recorded this 30m snapshot afterward.

lossguardrail context present
Kahramana Intelligence
blocked
Guardrail proof

VIRTUAL/DEUS

BASEDetected Jun 3, 11:04 PM UTC
Why action was blocked

Creator or deployer history includes fast-dump or rug-like patterns.

Detected value
—
Required threshold
—
Guardrail blocked30m -0.4%
Outcome windows

Outcome checkpoints

5m
Checkpoint still collecting
Pending
30m
Tracked outcome recorded
-0.4%
4h
Checkpoint still collecting
Pending
24h
Checkpoint still collecting
Pending
Guardrail context

What the system said no to

execution mode mismatchwarning

Creator or deployer history includes fast-dump or rug-like patterns.

execution mode mismatchwarning

Related opportunities repeat across chains or venues with suspicious wallet or behavior context.

suspicious wallet behaviorwarning

Wallet history indicates suspicious launch behavior or fast-dump risk.

Radar shows Alpha and Watch bands with the same posture discipline. Guided demo walks paper-default execution context without implying live automation.
Soft unlock
Want more signals like this?

Unlock a small preview of how similar signals are surfaced privately. The public proof stays open either way.

Unlock preview
Share this signal or join the waitlist to reveal a soft preview. No signup wall, no aggressive gating.
Join waitlist → unlockGet notified when more private access opens. Unlock the preview after you join.
Email only. No hype list. No fake urgency.
Signals are tracked before moves. Outcomes stay public.
Private access is limited to keep signal quality high.