Skip to content

Commit dc04cec

Browse files
omarakhmedov-webomarakhmedov-web
authored
Update article-signals-whyplusplus_bilingual_v1.html
1 parent 9c98acc commit dc04cec

1 file changed

Lines changed: 82 additions & 69 deletions

File tree

‎article-signals-whyplusplus_bilingual_v1.html‎

Lines changed: 82 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -1,71 +1,84 @@
1-
<!DOCTYPE html>
1+
<!doctype html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="utf-8">
5+
<meta name="viewport" content="width=device-width, initial-scale=1">
6+
<title>Signals &amp; Why++ — Metridex</title>
7+
<meta name="description" content="A pragmatic framework for collecting signals and articulating the Why++ — the evidence‑based rationale behind an assessment.">
8+
<link rel="stylesheet" href="/styles.css">
9+
<script src="/script.js" defer></script>
10+
</head>
11+
<body>
12+
<main class="article-content container" style="max-width:920px;margin:40px auto;padding:0 16px;">
13+
<header style="margin-bottom:20px;">
14+
<h1>Signals &amp; Why++</h1>
15+
<p class="muted" style="opacity:.8;">Updated October 03, 2025</p>
16+
</header>
217

3-
<html lang="en"><head><meta charset="utf-8"/><meta content="width=device-width, initial-scale=1" name="viewport"/><title>Metridex — Signals &amp; Why++</title><meta content="How QuickScan converts raw checks into an explainable verdict with Why++ factors — ." name="description"/><link href="styles.css" rel="stylesheet"/><link href="/logo/favicon-32.png?v=3" rel="icon" sizes="32x32" type="image/png"/><link href="/logo/favicon-16.png?v=3" rel="icon" sizes="16x16" type="image/png"/><link href="/logo/apple-touch-icon.png?v=3" rel="apple-touch-icon" sizes="180x180"/><link href="/logo/favicon.ico?v=3" rel="icon"/><link href="/logo/site.webmanifest?v=3" rel="manifest"/><style>.article-meta{font-size:0.9rem;color:#9aa3af;margin:8px 0 18px}
4-
.article-nav{display:flex;gap:12px;flex-wrap:wrap;margin-top:28px}
5-
.article-nav a{padding:10px 14px;border:1px solid #2a2a2a;border-radius:10px;text-decoration:none}
6-
.article-nav a:hover{background:#0b0b0b}</style><style>.article-body{margin-top:56px}</style><style>.article-kicker{font-size:.9rem;color:#9aa3af;margin-top:8px}
7-
.article-author{font-size:.95rem;color:#c7cdd6;margin-top:6px}
8-
.article-body{margin-top:56px}</style><style>/* AURUM-DELTA: spacing under fixed header */
9-
.article-offset{padding-top:140px}
10-
/* visibility */
11-
.lang-block{display:none}
12-
.lang-block.active{display:block}
13-
.lang-switch{margin:10px 0 0;display:flex;gap:8px;align-items:center}
14-
.lang-switch button{padding:6px 10px;border:1px solid #2a2a2a;border-radius:8px;background:transparent;cursor:pointer}
15-
.lang-switch button.active{background:#0b0b0b}</style><style>
16-
/* AURUM-DELTA OVERRIDES — spacing + switcher visuals */
17-
.article-body{margin-top:8px !important} /* was ~56px; closer by ~1.5cm */
18-
.article-nav{margin-top:9px !important} /* was 28px; lifted by ~0.5cm */
18+
<section>
19+
<h2>What is a signal?</h2>
20+
<p>A signal is any observable piece of evidence that informs the reliability, traction, or risk profile of a project. One signal is rarely conclusive; the strength comes from combining multiple independent signals.</p>
21+
</section>
1922

20-
/* Language switcher: brighter, like homepage */
21-
.lang-switch{margin-top:10px; gap:10px}
22-
.lang-switch button{
23-
padding:8px 14px;
24-
border:1px solid #3b3b3b;
25-
border-radius:10px;
26-
background:rgba(255,255,255,0.04);
27-
color:#e5e7eb;
28-
font-weight:600;
29-
letter-spacing:.2px;
30-
}
31-
.lang-switch button:hover{background:rgba(255,255,255,0.08)}
32-
.lang-switch button.active{
33-
background:#1f2937;
34-
border-color:#6b7280;
35-
color:#ffffff;
36-
}
37-
</style><!-- MDX_EN_ONLY_NoBase -->
38-
</head><body class="article-offset lux"><header class="nav"><div class="container nav-inner nav-container-wide"><div class="brand"><img alt="Metridex" class="brand-logo" src="/logo/metridex_logo_header.png"/></div><nav class="nav-links"><a href="/articles.html">All articles</a><a href="videos.html">Videos</a><a href="help.html">Help</a></nav><div class="nav-actions"><button class="icon-btn" id="themeToggle" title="Toggle theme">🌙</button></div></div></header><section class="hero-subtle"><div class="container"><div class="flex-row space-between" style="display:flex; align-items:center; justify-content:space-between; gap:16px;"><div><h1 style="margin-top:0.25rem">Signals &amp; Why++</h1><div class="article-kicker">Guide · Sep 29, 2025</div><div class="article-author">— Omar Ahmad, Founder of Metridex</div><div class="article-body"></div></div></div></div></section><section class="section"><div class="container article"><!-- EN --><div class="article-content"><p><strong>TL;DR</strong>: QuickScan aggregates a small set of high-signal checks and explains the verdict via <em>Why++</em> — short, auditable reasons you can trust in a chat.</p><h2>1) The signal set</h2><div class="kpi-grid"><div class="kpi"><h3>Pair context</h3><p>Liquidity, FDV/MC, 24h volume, short-term Δ (DexScreener).</p></div><div class="kpi"><h3>On-chain</h3><p>Bytecode presence, proxy/admin flags, holders &amp; LP concentration.</p></div><div class="kpi"><h3>Hygiene</h3><p>WHOIS/RDAP, SSL issuer/expiry, Wayback snapshots.</p></div></div><h2>2) Scoring to verdict</h2><p>We bucket risk as <code>Low</code>/<code>Medium</code>/<code>High</code>. Each bucket is driven by thresholds (e.g., LP ≥ X%, top holders ≤ Y%). Grey zones resolve via tie‑breakers (age, hygiene, recent Δ).</p><h2>3) Why++: explainability</h2><p>Every verdict includes 3–6 concise reasons, e.g. <em>“High liquidity”</em>, <em>“Contract missing”</em>, <em>“No Wayback snapshots”</em>. Reasons map 1:1 to checks and link back to sources in the HTML report.</p><h2>4) Limits &amp; design choices</h2><ul><li><strong>Speed over breadth</strong>: we prefer fewer, stronger checks you can see in chat.</li><li><strong>First pass</strong>: meant to filter, not to replace due diligence.</li><li><strong>Transparent tradeoffs</strong>: Why++ always states <em>why</em>, not just a score.</li></ul><h2>5) What’s next</h2><p>Share links (TTL), PDF export, watchlists/alerts (lite), deeper LP-lock analytics, more chains.</p><p>Note: You can Watch any token to be alerted when these “Why++” factors change materially (lite cadence).</p><hr/><p><strong>Try it</strong>: <a href="https://t.me/MetridexBot" rel="noopener" target="_blank">@MetridexBot</a> • <a href="https://metridex.com" rel="noopener" target="_blank">metridex.com</a></p></div><!-- RU --><div class="kpi"><h3>Ончейн</h3><p>Наличие байткода, прокси/админ-флаги, холдеры и концентрация LP.</p></div><div class="kpi"><h3>Гигиена</h3><p>WHOIS/RDAP, издатель/срок SSL, снимки Wayback.</p></div></div><h2>2) От баллов к вердикту</h2><p>Риск — <code>Low</code>/<code>Medium</code>/<code>High</code>. Каждая корзина задаётся порогами (например, LP ≥ X%, топ‑холдеры ≤ Y%). Серые зоны решаем тай‑брейкерами (возраст, гигиена, недавние Δ).</p><h2>3) Why++: пояснимость</h2><p>В каждом вердикте 3–6 коротких причин: <em>«Высокая ликвидность»</em>, <em>«Контракт отсутствует»</em>, <em>«Нет снимков Wayback»</em>. Причины 1:1 соответствуют проверкам и в HTML‑отчёте ведут к источникам.</p><h2>4) Ограничения и дизайн‑выборы</h2><ul><li><strong>Скорость вместо широты</strong>: меньше, но сильнее — и видно прямо в чате.</li><li><strong>Первый проход</strong>: фильтр, а не замена дью‑дилидженса.</li><li><strong>Прозрачные компромиссы</strong>: Why++ всегда поясняет <em>почему</em>, а не просто очко.</li></ul><h2>5) Что дальше</h2><p>Шер‑ссылки (TTL), экспорт PDF, watchlists/alerts (lite), расширенная аналитика LP‑lock, больше сетей.</p><p>Примечание: Добавьте токен в Watch, чтобы получать оповещения при существенных изменениях факторов «Why++» (lite‑каденс).</p><hr/><p><strong>Попробовать</strong>: <a href="https://t.me/MetridexBot" rel="noopener" target="_blank">@MetridexBot</a> • <a href="https://metridex.com" rel="noopener" target="_blank">metridex.com</a></p></section><footer class="footer"><div class="container"><p>© <span id="year"></span> Metridex.</p></div></footer><div class="article-nav"><a href="/article-whois-wayback_bilingual_v2.html">← Back to Articles</a><a href="/article-whois-wayback_bilingual_v2.html">← Prev: WHOIS &amp; Wayback checks</a></div><script>(function(){
39-
function switchTo(lang){
40-
document.documentElement.setAttribute('lang', lang);
41-
var blocks = document.querySelectorAll('.lang-block');
42-
blocks.forEach(function(el){
43-
if (el.classList.contains('lang-' + lang)){
44-
el.classList.add('active');
45-
el.style.display = 'block';
46-
} else {
47-
el.classList.remove('active');
48-
el.style.display = 'none';
49-
}
50-
});
51-
document.querySelectorAll('.lang-switch [data-lang]').forEach(function(btn){
52-
btn.classList.toggle('active', btn.getAttribute('data-lang')===lang);
53-
});
54-
try{ localStorage.setItem('lang', lang); }catch(e){}
55-
}
56-
var pref = 'en';
57-
try{
58-
var s = localStorage.getItem('lang');
59-
if (s === 'ru' || s === 'en') pref = s;
60-
}catch(e){}
61-
// initial
62-
switchTo(pref);
63-
// hook buttons
64-
document.addEventListener('click', function(e){
65-
var t = e.target;
66-
if (t && t.matches('.lang-switch [data-lang]')){
67-
e.preventDefault();
68-
switchTo(t.getAttribute('data-lang'));
69-
}
70-
});
71-
})();</script></body></html>
23+
<section>
24+
<h2>Signal categories</h2>
25+
<ul>
26+
<li><strong>Founders &amp; team:</strong> verifiable identities, prior outcomes, consistent public presence.</li>
27+
<li><strong>Product &amp; code:</strong> live product, public repos, release cadence, security posture.</li>
28+
<li><strong>Traction:</strong> real users, meaningful usage metrics, credible partners.</li>
29+
<li><strong>Finance:</strong> funding history, cap table transparency (when public), revenue hints.</li>
30+
<li><strong>Market &amp; regulation:</strong> target geography, licensing needs, comparable players.</li>
31+
<li><strong>Reputation:</strong> press coverage, community feedback, incident history.</li>
32+
</ul>
33+
</section>
34+
35+
<section>
36+
<h2>The Why++</h2>
37+
<p><em>Why++</em> is the short, defensible rationale that stitches your signals into a coherent conclusion. It should be clear enough for a stakeholder to act on, and specific enough to audit later.</p>
38+
<p>Good Why++ statements are: (1) evidence‑anchored, (2) falsifiable, and (3) scoped to the decision at hand.</p>
39+
</section>
40+
41+
<section>
42+
<h2>How to write a solid Why++</h2>
43+
<ol>
44+
<li><strong>Start with the question.</strong> e.g., “Should we integrate X as a data source this quarter?”</li>
45+
<li><strong>List the strongest signals.</strong> Pick 3–7 independent signals with sources.</li>
46+
<li><strong>State the conclusion and risk.</strong> “Proceed, gated by security review,” or “Defer; traction unclear.”</li>
47+
<li><strong>Call out unknowns.</strong> Surface the top 1–3 gaps that could change the decision.</li>
48+
</ol>
49+
</section>
50+
51+
<section>
52+
<h2>Examples</h2>
53+
<h3>Proceed (guarded)</h3>
54+
<ul>
55+
<li>Founding team with shipped products; public profiles consistent over 3+ years.</li>
56+
<li>Live API with uptime history; security page with responsible disclosure.</li>
57+
<li>Paying customers named; integration docs are adequate.</li>
58+
<li><em>Why++:</em> Evidence supports a limited integration behind feature flags; revisit in 60 days.</li>
59+
</ul>
60+
<h3>Defer</h3>
61+
<ul>
62+
<li>Domain registered 2 months ago; marketing claims multi‑year traction.</li>
63+
<li>Missing legal pages; no independent press or case studies.</li>
64+
<li><em>Why++:</em> Insufficient proof; reassess after credible milestones.</li>
65+
</ul>
66+
</section>
67+
68+
<section>
69+
<h2>Checklist</h2>
70+
<ul>
71+
<li>Signals are independent and cited.</li>
72+
<li>Why++ references the signals directly.</li>
73+
<li>Risks and unknowns are explicit.</li>
74+
<li>Decision is actionable and time‑boxed.</li>
75+
</ul>
76+
</section>
77+
78+
<footer class="article-nav" style="display:flex;gap:12px;justify-content:space-between;align-items:center;margin:36px 0 24px;">
79+
<a class="btn prev" href="/article-whois-wayback_bilingual_v2.html">← Previous: WHOIS &amp; Wayback checks</a>
80+
<a class="btn all" href="/articles.html">All articles</a>
81+
</footer>
82+
</main>
83+
</body>
84+
</html>

0 commit comments

Comments
 (0)