System Status: Warming Up
Checking system health.View status
Kahramana
Checking session
Public proof recordReal tracked signallossintegrity warningIntegrity: Mismatch
Forensic rowDetected May 3, 12:37 AM 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 (-2.3%)

BSB/USDC was detected on BASE / aerodrome-v2 with a blocked posture. The signal is currently integrity warning 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 checkpoints0 pending
Routing & metadata (frozen)How this row was classified for the public surface
Ledger fields
Product lane · alphaSignal tier · public resolved
Operator actionSame model as radar cards
How to read this signal
CompletedReadiness high
ActionDo not act on this lane.
Promote when—
Breaks iffreshness and novelty window · staleness weakens operating context · integrity or record mismatch · policy or coverage blocks row · staleness downgrades confidence · integrity issue downgrades trust

Signal arc (structured read)Change on record: BSB/USDC stays in Watch because current evidence is incomplete for strategy promotion Outcome on record: loss Recorded risk edge: freshness and novelty window Liquidity structure supports follow-through instead of fragility

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

BSB/USDC launch radar signal

Action stops at paper first because execution support is not available on this path.

BASEaerodrome-v2blockedsmart wallet detectedcorrelatedguardrail blockedpublic resolved
Record index
Detected atMay 3, 12:37 AM UTC
Published atMay 3, 12:44 AM UTC
Overall score68
Posture at detectionblocked
Verification IDproof_0347ea7a1b1ee307
Integrity hashMismatch
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 signal
Key metrics: blocked posture · loss outcome at 30m · verification proof_0347ea7a1b1ee307
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 May 3, 12:37 AM 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: MismatchHash version v1

The currently computed proof hash does not match the stored public hash. The locked public snapshot is still rendered, but this record should be reviewed.

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

Reasoning

Action stops at paper first because execution support is not available on this path.

Why it surfaced

BSB/USDC stays in Watch because current evidence is incomplete for strategy promotion

What happened after

Moved -0.02% before failing.

Public posture

Resolved. Kept visible for proof and tracked outcome context, not as a live prompt.

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: 0
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
May 3, 12:37 AM UTC
BSB/USDC observed on BASE / aerodrome-v2. Detection timestamp is stored as shown.
Reasoning (policy snapshot)rationale
May 3, 12:37 AM UTC
Action stops at paper first because execution support is not available on this path.
Posture at detectionblocked
May 3, 12:37 AM UTC
Execution support posture was recorded as blocked at the time of surfacing.
Published to public ledgermismatch
May 3, 12:44 AM UTC
Verification ID proof_0347ea7a1b1ee307 locked at publication. This page renders the same payload the hash covers.
5m checkpointpending
Pending
This checkpoint has not been recorded yet.
30m checkpointloss
May 3, 1:12 AM UTC
Outcome recorded as loss with -2.3% move.
4h checkpointpending
Pending
This checkpoint has not been recorded yet.
24h checkpointpending
Pending
This checkpoint has not been recorded yet.
Current statusintegrity_warning
May 3, 12:44 AM UTC
Evaluator / integrity state: integrity warning.
Outcome chart

How the tracked move evolved

30m -2.3%
Shareable proof

Export-ready proof cards

Kahramana Intelligence
blocked
Opportunity proof
BSB (BSB)
USD Coin (USDC)
BSB/USDCBSB / USD Coin
BASEaerodrome-v2Detected May 3, 12:37 AM UTC
Overall score
68
Liquidity
$191.6k
Why this matters

Action stops at paper first because execution support is not available on this path.

smart wallet detectedcorrelatedguardrail blockedpublic resolved
Outcome context
30m loss -2.3%
Verification ID: proof_0347ea7a1b1ee307
Kahramana Intelligence
loss
Outcome proof

BSB/USDC

BASEDetected May 3, 12:37 AM UTC30m window
Outcome after 30m
-2.3%
Context

This was detected at May 3, 12:37 AM UTC before the outcome. Outcome tracking recorded this 30m snapshot afterward.

lossguardrail context present
Kahramana Intelligence
blocked
Guardrail proof

BSB/USDC

BASEDetected May 3, 12:37 AM UTC
Why action was blocked

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

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

Outcome checkpoints

5m
Checkpoint still collecting
Pending
30m
Tracked outcome recorded
-2.3%
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.