{
  "object": "jepeta_high_intent_answer",
  "schemaVersion": "1.0.0",
  "language": "en",
  "category": "interpretation",
  "question": "What do PASS, WARN, and BLOCK mean in token risk screening?",
  "intent": "Interpret Jepeta policy decisions correctly",
  "directAnswer": "PASS, WARN, and BLOCK are policy decisions, not predictions. BLOCK means Jepeta observed a configured hard blocker. WARN means one or more material risks or evidence-quality issues require review. PASS means no configured WARN/BLOCK condition was observed in the available evidence; it never means guaranteed safe.",
  "canonicalUrl": "https://jepeta.dev/guides/what-does-pass-warn-block-mean-token-risk/",
  "jsonUrl": "https://jepeta.dev/guides/what-does-pass-warn-block-mean-token-risk/index.json",
  "sections": [
    {
      "heading": "Why a policy label is useful",
      "paragraphs": [
        "Raw security and market fields can be hard to consume consistently in a human or automated workflow. A policy label gives an execution layer a deterministic first action: stop, review, or continue to its own rules.",
        "The label is most useful when the underlying evidence remains visible. Without that evidence, a score or color can create false confidence."
      ]
    },
    {
      "heading": "Evidence stays primary",
      "paragraphs": [
        "Jepeta exposes the decision alongside honeypot, mintability, tax, liquidity, concentration, LP-lock observations, data quality, source status, warnings, and timestamps.",
        "Permanent evidence pages preserve that context and explicitly state that they are snapshots, not audits or guarantees."
      ]
    },
    {
      "heading": "How agents should use it",
      "paragraphs": [
        "An autonomous agent can stop automatically on BLOCK, escalate WARN for additional policy checks, and allow PASS only if its own execution constraints also pass.",
        "HTTP errors or missing required evidence should be treated as no usable Jepeta verdict, not as PASS."
      ]
    }
  ],
  "checklist": [
    "BLOCK = stop under Jepeta policy",
    "WARN = review",
    "PASS = no configured warning/block observed",
    "Inspect underlying evidence",
    "Treat errors as no verdict"
  ],
  "sources": [
    {
      "label": "Jepeta methodology",
      "url": "https://jepeta.dev/methodology.json"
    },
    {
      "label": "Jepeta OpenAPI",
      "url": "https://jepeta.dev/openapi.json"
    }
  ],
  "evidenceExample": {
    "tokenAddress": "0x940181a94a35a4569e4529a3cdfb74e38fd98631",
    "canonicalUrl": "https://jepeta.dev/risk/base/0x940181a94a35a4569e4529a3cdfb74e38fd98631/",
    "lastCheckedAt": "2026-09-24T16:48:11.089+00:00",
    "decision": "WARN",
    "riskScore": 35
  },
  "related": [
    {
      "question": "What does data quality mean in a token risk scan?",
      "url": "https://jepeta.dev/guides/what-does-token-data-quality-mean/"
    },
    {
      "question": "What Base token risk API can an AI agent use before execution?",
      "url": "https://jepeta.dev/guides/base-token-risk-api-for-ai-agents/"
    },
    {
      "question": "What should I check before buying a Base token?",
      "url": "https://jepeta.dev/guides/base-token-risk-checklist-before-buy/"
    }
  ],
  "methodologyUrl": "https://jepeta.dev/methodology.json",
  "freshScanUrl": "https://jepeta.dev/#scanner",
  "limitations": [
    "Educational risk-screening content, not investment advice.",
    "A token-risk snapshot is timestamped and can become stale.",
    "PASS is not a safety guarantee."
  ]
}