Question 1

What is Kahramana?

Accepted Answer

Kahramana is a proof-linked decision intelligence system for crypto operators. It detects setups, assigns explicit execution posture (signal-only, paper-first paths, guarded execution where supported, or blocked), and tracks outcomes in public records. It is not a passive signal feed and not a promise that someone else will trade for you.

Question 2

What does "decision intelligence" mean?

Accepted Answer

It means the product is built around a disciplined loop: what was observed, why it mattered under the current policy version, what posture applies, what happened next in time-boxed checkpoints, and what was published for audit. The output is evidence for operator judgment—not a scoreboard optimized for marketing.

Question 3

Why is the platform paper-first?

Accepted Answer

Paper-first means the default honest stance is simulation and review: you can pressure-test posture, guardrails, and outcomes before any live path is even offered. Live or guarded execution only appears where venue support, credentials, runtime coverage, and policy genuinely allow it—not as a default casino mode.

Question 4

Why are losses visible?

Accepted Answer

Because hiding unfavorable outcomes would destroy auditability. When a checkpoint resolves as a loss under the published rules, it stays labeled that way on the proof record. The point is integrity over comfort—not a claim that losses are impossible.

Question 5

Why are some metrics intentionally withheld?

Accepted Answer

Sparse or unstable samples produce headline numbers that lie loudly. Kahramana withholds aggregate performance marketing until the decision-grade ledger is meaningful, and explains that policy publicly on the Building the Ledger page (`/performance`) instead of flashing fake precision.

Question 6

Can proof records be edited later?

Accepted Answer

Published public proof is treated as an integrity surface: you should not expect silent rewrites of outcomes after publication to make history look cleaner. Verification metadata exists so independent readers can reason about what was published and when.

Question 7

What is a proof hash?

Accepted Answer

It is a deterministic fingerprint of the published payload at the time of publication. It is there so “what we claimed was live” is tied to a specific record, not a moving story.

Question 8

Why do some proof records stay sparse?

Accepted Answer

Because reality is sometimes incomplete: windows still open, checkpoints pending, venues missing data, or the setup never reached a state worth over-claiming. Sparse data stays sparse on purpose instead of being backfilled to look decisive.

Question 9

What does "no retroactive edits" mean?

Accepted Answer

It means the product posture is methodology-first: classification uses defensible checkpoints under published rules, and marketing language should not pretend the past changed when a nicer label becomes convenient.

Question 10

Are losing signals hidden?

Accepted Answer

No. A loss that is the honest classification under the rules remains visible on the proof page alongside wins and neutral outcomes. Filtering losses for comfort would break the point of public proof.

Question 11

Does Kahramana execute trades automatically?

Accepted Answer

Not in the “hands-off bot” sense. The system can surface execution-ready posture where product and venue support exist, but it does not replace operator judgment with autonomous gambling. Paper-first remains the honest default; guarded execution is bounded by policy and capability—not hype.

Question 12

What does "signal-only" mean?

Accepted Answer

Signal-only means the row is visible for review, but the path is not presented as execution-ready: you get detection and rationale without a claim that the stack can or should route capital on your behalf.

Question 13

What is "guarded execution"?

Accepted Answer

Guarded execution (often shown as guarded-live eligibility in the product) means any live-adjacent pathway is explicitly gated: credentials, venue readiness, runtime coverage, and risk posture must line up. It is the opposite of silent always-on trading.

Question 14

What does "execution-ready" mean?

Accepted Answer

Execution-ready describes capability posture (for example paper-ready), not a moral guarantee. It means the product believes the path is supported enough to discuss next steps in the operator workflow—not that outcomes are assured.

Question 15

What is the difference between paper, semi-auto, and live execution?

Accepted Answer

Paper is simulated / non-live capital paths used to review behavior. Semi-auto refers to supervised operator-in-the-loop workflows where the product supports stepping through actions with explicit controls—not unattended autopilot. Live or guarded-live paths only exist where the system explicitly says they are supported, and they remain bounded by guardrails.

Question 16

Why does Kahramana not publish aggressive win-rate claims?

Accepted Answer

Because headline win rates from thin samples read like marketing and behave like lies. Kahramana publishes methodology and withholds aggregate performance billboards until the decision-grade sample is meaningful; see `/performance` (Building the Ledger). Numeric aggregates for observers who want them remain on `/public-performance` when summaries exist.

Question 17

What counts as "decision-grade"?

Accepted Answer

Decision-grade is the stricter slice of tracked observations used when discussing serious operator utility—not every watch row counts the same way. The exact rules are public in methodology; the important part is that it is a defined bar, not vibes.

Question 18

When will aggregate performance be published?

Accepted Answer

When the ledger policy described on `/performance` is met: enough decision-grade resolved outcomes under a stable methodology window so aggregates are not dominated by noise. Until then, the honest surface is per-row proof and radar—not a fake scoreboard.

Question 19

Why are small samples dangerous?

Accepted Answer

A handful of outcomes can produce extreme percentages that reverse next week. Publishing them as hero metrics would trade integrity for excitement. Kahramana prefers visible losses and honest sample discipline over vanity charts.

Question 20

How is this different from Telegram signal groups?

Accepted Answer

Telegram groups often optimize for engagement: late entries, deleted messages, and unverifiable track records. Kahramana is built around published proof records, explicit posture, and checkpointed outcomes—including losses—with a methodology you can read and re-check.

Question 21

How is this different from Nansen or Arkham?

Accepted Answer

Explorers and labels are invaluable for raw chain intelligence. Kahramana adds an operator layer: scoring context, explicit guardrails, posture, and proof-linked decision records meant for disciplined review—not a replacement for those tools, and not the same product category.

Question 22

Why is the platform paid?

Accepted Answer

Earlier private intelligence, private tracking, sessions, and execution posture tooling cost real compute and engineering time. Starter stays free so you can evaluate integrity on public surfaces; paid tiers fund the full operator workflow without selling your attention to the loudest promoter.

Question 23

Who is Kahramana NOT for?

Accepted Answer

Anyone looking for guaranteed profits, passive copy-trading, or fully autonomous trading with no judgment. If you want anonymous hype with no accountability record, this will feel slow on purpose.

Question 24

Is Kahramana connected to my exchange account?

Accepted Answer

Only when you explicitly connect credentials for supported workflows. There is no implied blanket link to your exchange simply from reading public radar or proof pages.

Question 25

Does Kahramana custody funds?

Accepted Answer

No. Kahramana is software intelligence and workflow—not a custodial fund product. Capital stays at your venues and under your controls; the product’s job is to be honest about posture and limits.

Question 26

What data is stored?

Accepted Answer

Operational data includes what is required to run the product: accounts, workspace configuration, billing references where applicable, signals, proof payloads, checkpoints, and audit logs. It is not sold as a trading-performance guarantee dataset.

Question 27

Is there a legal company behind the platform?

Accepted Answer

Yes. Kahramana is operated with Infraengineering s.r.o., based in Prague, Czech Republic. That is the boring factual answer—use the contact page if you need formal correspondence channels.

Straight answers.

Still have questions?