System Status: Warming Up
Checking system health.View status
Kahramana
Checking session
Public proof recordReal tracked signalinsufficient datapending windowIntegrity: Verified
Forensic rowDetected May 18, 4:15 PM UTC
Share proof record
Frozen-friendly record: detection time, recorded rationale, posture at detection, checkpoints, integrity hash. Not marketing copy.
Executive summaryStill pending window

USDC/SOL was detected on SOLANA / pumpfun with a signal only posture. The signal is currently pending window with 1 of 4 checkpoints recorded. There is not enough tracked outcome data yet to make a responsible decision-impact claim.

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
AlphaReadiness medium
ActionObserve — context only.
Promote whenwhen execution posture opens paper or guarded
Breaks ifstaleness weakens operating context · staleness downgrades confidence

Signal arc (structured read)Alpha-class surface: observe — monitor context without a promoted action. Signal-only — no automated execution implied Recorded risk edge: staleness weakens operating context Liquidity structure supports follow-through instead of fragility

USDC/SOL launch radar signal

Overall score is 73 with structural 95, risk 30, and momentum 51.

SOLANApumpfunsignal onlysmart wallet detectedcorrelated
Record index
Detected atMay 18, 4:15 PM UTC
Published atMay 18, 4:16 PM UTC
Overall score73
Posture at detectionsignal only
Verification IDproof_c6ef4b2312b7b58d
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 signal
Key metrics: signal only posture · insufficient data outcome at 30m · verification proof_c6ef4b2312b7b58d
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 18, 4:15 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 classificationinsufficient data
Best moveinsufficient data
Worst moveinsufficient data
Latest moveinsufficient data
Rationale

Reasoning

Overall score is 73 with structural 95, risk 30, and momentum 51.

Why this mattered

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

Decision reasoning

SOLANA launch-style opportunity with sufficient structural and liquidity support. Decision=signal, structural=95, risk=30, momentum=50.87.

Risk context

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

Strategy posture

The system recommends launch sniper because the opportunity fits that strategy family better than the alternatives.

Risk / uncertainty

What could limit this setup

signal only

Solana paper execution is available while live execution remains disabled.

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

Outcome summary

Outcome summary

insufficient data

Outcome stayed neutral at the latest completed 30m checkpoint.

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

Why the posture mattered

Data incomplete

There is not enough tracked outcome data yet to make a responsible decision-impact claim.

Timeline

Timeline & timestamps

Detecteddetected
May 18, 4:15 PM UTC
USDC/SOL observed on SOLANA / pumpfun. Detection timestamp is stored as shown.
Reasoning (policy snapshot)rationale
May 18, 4:15 PM UTC
Overall score is 73 with structural 95, risk 30, and momentum 51.
Posture at detectionsignal_only
May 18, 4:15 PM UTC
Execution support posture was recorded as signal only at the time of surfacing.
Published to public ledgerverified
May 18, 4:16 PM UTC
Verification ID proof_c6ef4b2312b7b58d locked at publication. This page renders the same payload the hash covers.
5m checkpointpending
Pending
This checkpoint has not been recorded yet.
30m checkpointinsufficient_data
May 18, 4:49 PM UTC
Outcome recorded as insufficient data with insufficient data move.
4h checkpointpending
Pending
This checkpoint has not been recorded yet.
24h checkpointpending
Pending
This checkpoint has not been recorded yet.
Current statuspending_window
May 18, 4:16 PM UTC
Evaluator / integrity state: pending window.
Outcome chart

How the tracked move evolved

No numeric outcome chart is available yet for this proof item.

Shareable proof

Export-ready proof cards

Kahramana Intelligence
signal only
Opportunity proof
USD Coin (USDC)
Solana (SOL)
USDC/SOLUSD Coin / Solana
SOLANApumpfunDetected May 18, 4:15 PM UTC
Overall score
73
Liquidity
$333.0k
Why this matters

Overall score is 73 with structural 95, risk 30, and momentum 51.

smart wallet detectedcorrelatedsignal only
Outcome context
30m insufficient data
Verification ID: proof_c6ef4b2312b7b58d
Kahramana Intelligence
insufficient data
Outcome proof

USDC/SOL

SOLANADetected May 18, 4:15 PM UTC30m window
Outcome after 30m
insufficient data
Context

This was detected at May 18, 4:15 PM UTC before the outcome. Outcome tracking recorded this 30m snapshot afterward.

insufficient dataguardrail context present
Kahramana Intelligence
blocked
Guardrail proof

USDC/SOL

SOLANADetected May 18, 4:15 PM UTC
Why action was blocked

Routing produced a pending rather than fully routed signal because binding or requirements are incomplete.

Detected value
—
Required threshold
—
Guardrail blockedOutcome still pending
Outcome windows

Outcome checkpoints

5m
Checkpoint still collecting
Pending
30m
Tracked outcome recorded
insufficient data
4h
Checkpoint still collecting
Pending
24h
Checkpoint still collecting
Pending
Guardrail context

What the system said no to

execution mode mismatchwarning

Routing produced a pending rather than fully routed signal because binding or requirements are incomplete.

unsupported execution pathinfo

Execution support on this chain remains intentionally guarded or unsupported.

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.