{
  "schema": "varexis-public-index/0.2",
  "name": "VAREXIS Public Evidence Index",
  "surface": "varexis.tech",
  "generated_at_utc": "2026-10-06T21:30:38.485Z",
  "purpose": "Expose bounded evidence records and question-context routes for human and agent discovery.",
  "principle": "VAREXIS indexes not only evidence, but the question contexts under which evidence may be used.",
  "public_record_count": 32,
  "catalog_page": "/varexis-index/catalog.html",
  "records": [
    {
      "record_id": "VXI-BDAS-20261002-PUMP-E2C-7022048-CONSUMED-ENGINEERING-SELECTIVE-v1",
      "title": "BDAS PUMP-E2C — Consumed Engineering Selective Execution Evidence",
      "system": "BDAS",
      "evidence_family": "selective_execution",
      "index_status": "PUBLIC_FULL_RECORD",
      "evidence_state": "SUPPORTED_WITH_BOUNDARIES",
      "canonical_question": "What exactly is evidenced by PUMP-E2C?",
      "near_questions": [
        "Has BDAS been tested on real pump engineering evidence?",
        "Is there evidence for selective execution on pump data?",
        "Can heavy pump signal processing be selectively gated?",
        "Can BDAS reduce unnecessary compute on pump monitoring workloads?"
      ],
      "supported_claims": [
        {
          "claim": "PUMP-E2C supports a narrow positive capability record: selective execution on historically consumed real MIMII pump engineering evidence.",
          "reliance": "SUPPORTED"
        },
        {
          "claim": "The PUMP-E2C record is sealed and locally validated by the VAREXIS-INDEX v0.9 qualification engine.",
          "reliance": "SUPPORTED"
        }
      ],
      "not_demonstrated_claims": [
        "fresh holdout validation",
        "production readiness",
        "customer savings",
        "external generalisation",
        "full score reconstruction",
        "unrestricted performance acceleration",
        "broad pump-audio diagnostic capability",
        "hardware-mismatched consumer contract"
      ],
      "public_summary": "Existing public full record for PUMP-E2C consumed engineering selective-execution evidence.",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads.",
      "authority_boundary": "VAREXIS-INDEX informs evidence reliance; it does not grant authority to deploy or act.",
      "human_page": "/varexis-index/bdas-pump-e2c.html",
      "machine_readable_record": "/varexis-index/records/pump-e2c.json"
    },
    {
      "record_id": "VXI-BDAS-20261004-LEDGER-0042-CANONICAL-FREEZE-BUNDLE-v1",
      "title": "BDAS INDEX Ledger 0042 — Canonical Freeze Bundle",
      "system": "BDAS / VAREXIS-INDEX",
      "evidence_family": "ledger_bridge",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "CANONICAL_FREEZE_BUNDLE",
      "canonical_question": "What does ledger entry 0042 evidence?",
      "human_page": "/varexis-index/catalog.html#bdas-index-ledger-0042-canonical-freeze-bundle",
      "machine_readable_record": "/varexis-index/records/bdas-index-ledger-0042.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20261004-7001071-INDEX-CORPUS-TRANCHE-v1",
      "title": "BDAS 7001071 — Recovered INDEX Corpus Tranche",
      "system": "BDAS / VAREXIS-INDEX",
      "evidence_family": "index_corpus_recovery",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "RECOVERED_FROZEN_TRANCHE",
      "canonical_question": "What does the 7001071 INDEX tranche evidence?",
      "human_page": "/varexis-index/catalog.html#bdas-7001071-recovered-index-corpus-tranche",
      "machine_readable_record": "/varexis-index/records/bdas-7001071-index-corpus-tranche.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20261002-7026447-CANDIDATE-BATCH-SUMMARY-v1",
      "title": "BDAS 7026447 — Candidate Batch Summary",
      "system": "BDAS / VAREXIS-INDEX",
      "evidence_family": "candidate_batch",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "STAGED_CANDIDATE_BATCH",
      "canonical_question": "What does the 7026447 candidate batch evidence?",
      "human_page": "/varexis-index/catalog.html#bdas-7026447-candidate-batch-summary",
      "machine_readable_record": "/varexis-index/records/bdas-7026447-candidate-batch-summary.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20261001-PUMP-E1-CHALLENGED-NEGATIVE-v1",
      "title": "BDAS PUMP-E1 — Challenged Negative Evidence",
      "system": "BDAS",
      "evidence_family": "selective_execution",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "CHALLENGED_NEGATIVE",
      "canonical_question": "Why is PUMP-E1 not a promoted selective-execution claim?",
      "human_page": "/varexis-index/catalog.html#bdas-pump-e1-challenged-negative-evidence",
      "machine_readable_record": "/varexis-index/records/bdas-pump-e1-challenged-negative.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260913-NASA-IMS-E4-1-SAFE-NOT-PERFORMANCE-v1",
      "title": "BDAS NASA IMS E4.1 — Safe But Not Performance Qualified",
      "system": "BDAS",
      "evidence_family": "external_dataset_evaluation",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "SAFE_BUT_NOT_PERFORMANCE_QUALIFIED",
      "canonical_question": "What did NASA IMS E4.1 demonstrate?",
      "human_page": "/varexis-index/catalog.html#bdas-nasa-ims-e4-1-safe-but-not-performance-qualified",
      "machine_readable_record": "/varexis-index/records/bdas-nasa-ims-e4-1-safe-not-performance.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202608-M1-QUALIFICATION-AURIC-MONITOR-v1",
      "title": "BDAS M1 — Qualification Engine With AURIC Monitor",
      "system": "BDAS / AURIC",
      "evidence_family": "qualification_engine",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "QUALIFICATION_DEVELOPMENT_PASS_WITH_BOUNDARIES",
      "canonical_question": "What did the M1 qualification engine establish?",
      "human_page": "/varexis-index/catalog.html#bdas-m1-qualification-engine-with-auric-monitor",
      "machine_readable_record": "/varexis-index/records/bdas-m1-qualification-auric-monitor.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260504-M3-EXTERNAL-LOCKED-SAFE-REFUSAL-v1",
      "title": "BDAS M3 — External Locked Safe Refusal",
      "system": "BDAS",
      "evidence_family": "safe_refusal",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "SAFE_REFUSAL",
      "canonical_question": "What does M3 evidence?",
      "human_page": "/varexis-index/catalog.html#bdas-m3-external-locked-safe-refusal",
      "machine_readable_record": "/varexis-index/records/bdas-m3-external-locked-safe-refusal.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20261002-7026446-CORRECTNESS-NOT-ECONOMICS-v1",
      "title": "BDAS 7026446 — Correctness Qualified, Economics Not Qualified",
      "system": "BDAS",
      "evidence_family": "qualification_economics",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "CORRECTNESS_QUALIFIED_ECONOMICS_NOT_QUALIFIED",
      "canonical_question": "How can correctness pass while economics fail?",
      "human_page": "/varexis-index/catalog.html#bdas-7026446-correctness-qualified-economics-not-qualified",
      "machine_readable_record": "/varexis-index/records/bdas-7026446-correctness-not-economics.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260915-QV1-PCB1-VISION-CORRECTNESS-NOT-ECONOMICS-v1",
      "title": "BDAS QV1 PCB1 Vision — Correctness Strong, Economics Not Qualified",
      "system": "BDAS",
      "evidence_family": "vision_selective_execution",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "CORRECTNESS_STRONG_ECONOMICS_NOT_QUALIFIED",
      "canonical_question": "What did QV1 PCB1 vision demonstrate?",
      "human_page": "/varexis-index/catalog.html#bdas-qv1-pcb1-vision-correctness-strong-economics-not-qualified",
      "machine_readable_record": "/varexis-index/records/bdas-qv1-pcb1-vision-correctness-not-economics.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260919-CK4A-CAPTURE-NO-PROMOTION-v1",
      "title": "BDAS CK4A — Capture Complete, No Promotion",
      "system": "BDAS",
      "evidence_family": "capture_and_review",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "CAPTURE_COMPLETE_NO_PROMOTION",
      "canonical_question": "What does CK4A evidence?",
      "human_page": "/varexis-index/catalog.html#bdas-ck4a-capture-complete-no-promotion",
      "machine_readable_record": "/varexis-index/records/bdas-ck4a-capture-no-promotion.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-S1-SPECTRAL-CPU-REPLAY-v1",
      "title": "BDAS S1 Spectral Replay — Exact Replay Evidence",
      "system": "BDAS",
      "evidence_family": "spectral_replay",
      "index_status": "PUBLIC_SUMMARY",
      "evidence_state": "EXACT_REPLAY_DIAGNOSTIC",
      "canonical_question": "What does S1 spectral replay evidence?",
      "human_page": "/varexis-index/catalog.html#bdas-s1-spectral-replay-exact-replay-evidence",
      "machine_readable_record": "/varexis-index/records/bdas-s1-spectral-replay.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202604-H1-3-LOCKED-SEED-VALIDATION-v1",
      "title": "BDAS H1.3 — Locked-Seed Validation",
      "system": "BDAS",
      "evidence_family": "selective_execution_validation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "LOCKED_SEED_VALIDATION_PASS_WITH_BOUNDARIES",
      "canonical_question": "What does H1.3 evidence about BDAS selective execution?",
      "near_questions": [
        "Did BDAS pass a locked-seed selective execution validation?",
        "Was false-skip safety checked in H1.3?",
        "Can H1.3 support a bounded selective execution claim?",
        "Does H1.3 prove production readiness?",
        "Can H1.3 be used as evidence for quiet-workload skipping?",
        "What does locked-seed validation mean for BDAS?",
        "Is H1.3 a general acceleration claim?",
        "What is not demonstrated by H1.3?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-h1-3-locked-seed-validation",
      "machine_readable_record": "/varexis-index/records/bdas-h1-3-locked-seed-validation.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202604-H2-1-HYDRAULIC-PUMP-SAFE-NOT-SELECTIVE-v1",
      "title": "BDAS H2.1 — Hydraulic Pump Safe But Not Selective",
      "system": "BDAS",
      "evidence_family": "external_pump_evaluation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "SAFE_NOT_SELECTIVE",
      "canonical_question": "What does H2.1 evidence about external pump evaluation?",
      "near_questions": [
        "Was the hydraulic pump evidence safe?",
        "Did H2.1 qualify selective execution?",
        "Can safe-but-not-selective still be useful evidence?",
        "Does H2.1 support a broad pump claim?",
        "What does safe refusal mean for pump evidence?",
        "Can H2.1 be sold as acceleration evidence?",
        "Does H2.1 show boundary discipline?",
        "What would upgrade H2.1?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-h2-1-hydraulic-pump-safe-but-not-selective",
      "machine_readable_record": "/varexis-index/records/bdas-h2-1-hydraulic-pump-safe-but-not-selective.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202604-I1-DEVELOPMENT-PASS-v1",
      "title": "BDAS I1 — Development Pass",
      "system": "BDAS",
      "evidence_family": "development_validation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "DEVELOPMENT_PASS",
      "canonical_question": "What does I1 evidence within the BDAS development chain?",
      "near_questions": [
        "Did I1 pass development validation?",
        "Is I1 a public deployment claim?",
        "Can I1 support progression to holdout handling?",
        "What is the boundary of a development pass?",
        "Does I1 prove customer value?",
        "Can I1 be used for investor evidence?",
        "What does I1 not demonstrate?",
        "How does development evidence differ from external validation?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-i1-development-pass",
      "machine_readable_record": "/varexis-index/records/bdas-i1-development-pass.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202604-I2-HOLDOUT-RESERVED-HASHED-v1",
      "title": "BDAS I2 — Holdout Reserved and Hashed",
      "system": "BDAS",
      "evidence_family": "holdout_control",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "RESERVED_HASHED_HOLDOUT",
      "canonical_question": "What does I2 evidence about holdout discipline?",
      "near_questions": [
        "Was a holdout reserved?",
        "Was the holdout protected before use?",
        "Can a reserved holdout be counted as validation?",
        "Does hashed reservation prove performance?",
        "Why does holdout discipline matter?",
        "Can I2 support evidence integrity?",
        "What remains unproven until holdout opening?",
        "How does I2 protect against post-hoc promotion?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-i2-holdout-reserved-and-hashed",
      "machine_readable_record": "/varexis-index/records/bdas-i2-holdout-reserved-and-hashed.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202604-STAGE-B-CONTROLLED-REDUCTION-v1",
      "title": "BDAS Stage B — Controlled Reduction Evidence",
      "system": "BDAS",
      "evidence_family": "controlled_reduction",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "CONTROLLED_REDUCTION_WITH_BOUNDARIES",
      "canonical_question": "What does Stage B evidence about BDAS reduction?",
      "near_questions": [
        "Was a controlled workload reduction observed?",
        "Can Stage B support selective execution interest?",
        "Does Stage B prove general acceleration?",
        "Was Stage B a production benchmark?",
        "Can Stage B be used in a pilot conversation?",
        "What are the limitations of Stage B?",
        "Does reduction equal customer saving?",
        "What extra evidence would upgrade Stage B?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-stage-b-controlled-reduction-evidence",
      "machine_readable_record": "/varexis-index/records/bdas-stage-b-controlled-reduction-evidence.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202604-STAGE-FG-SAFE-NOT-SELECTIVE-v1",
      "title": "BDAS Stage F/G — Safe But Not Selective",
      "system": "BDAS",
      "evidence_family": "negative_validation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "SAFE_NOT_SELECTIVE",
      "canonical_question": "What does Stage F/G evidence?",
      "near_questions": [
        "Did Stage F/G qualify selective execution?",
        "Was Stage F/G safe?",
        "Can a safe non-selective result be useful?",
        "Does Stage F/G prevent overclaiming?",
        "What does non-promotion show?",
        "Can Stage F/G support refusal behaviour?",
        "Is Stage F/G a failure or boundary record?",
        "What would be needed to upgrade Stage F/G?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-stage-f-g-safe-but-not-selective",
      "machine_readable_record": "/varexis-index/records/bdas-stage-f-g-safe-but-not-selective.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202606-IIOT-SYNTHETIC-60M-LOGS-v1",
      "title": "BDAS IIoT Synthetic 60M Logs — Public-Safe Reduction Summary",
      "system": "BDAS",
      "evidence_family": "iiot_synthetic_reduction",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "SYNTHETIC_REDUCTION_EVIDENCE_WITH_BOUNDARIES",
      "canonical_question": "What does the IIoT synthetic 60M-log record evidence?",
      "near_questions": [
        "Was BDAS tested on synthetic IIoT-scale logs?",
        "Can synthetic IIoT evidence support workload triage interest?",
        "Does synthetic evidence prove real customer saving?",
        "Is this suitable for agentic discovery?",
        "What does IIoT synthetic evidence not prove?",
        "Can quiet telemetry be reduced?",
        "Is this a public-safe scale example?",
        "What would convert synthetic evidence into customer evidence?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-iiot-synthetic-60m-logs-public-safe-reduction-summary",
      "machine_readable_record": "/varexis-index/records/bdas-iiot-synthetic-60m-logs-public-safe-reduction-summary.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202606-163M-ROW-PUBLIC-REDUCTION-v1",
      "title": "BDAS 163M-Row Public Reduction — Public-Scale Summary",
      "system": "BDAS",
      "evidence_family": "public_scale_reduction",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "PUBLIC_SCALE_REDUCTION_WITH_BOUNDARIES",
      "canonical_question": "What does the 163M-row public reduction record evidence?",
      "near_questions": [
        "Was BDAS evaluated on a public-scale row workload?",
        "Can the 163M-row record support scale claims?",
        "Does row reduction equal end-to-end acceleration?",
        "Is this a public-safe evidence record?",
        "Can this help agentic discovery?",
        "Does this prove production saving?",
        "What is the boundary of public-scale reduction?",
        "What would be required for a paid receipt?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-163m-row-public-reduction-public-scale-summary",
      "machine_readable_record": "/varexis-index/records/bdas-163m-row-public-reduction-public-scale-summary.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-CENTERED-LIVE-PROBE-V1-v1",
      "title": "BDAS Centered Live Probe V1 — Validation Probe Pass",
      "system": "BDAS",
      "evidence_family": "pipeline_probe",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "VALIDATION_PROBE_PASS",
      "canonical_question": "What does Centered Live Probe V1 evidence?",
      "near_questions": [
        "Did the live probe pass?",
        "What does a probe pass mean?",
        "Can probe evidence support public runtime claims?",
        "Does this prove production API availability?",
        "Is this a pipeline integrity signal?",
        "Can an agent rely on this directly?",
        "What is not demonstrated by a probe pass?",
        "Why preserve probe records?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-centered-live-probe-v1-validation-probe-pass",
      "machine_readable_record": "/varexis-index/records/bdas-centered-live-probe-v1-validation-probe-pass.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-FUSED-ATTRIBUTION-V2-v1",
      "title": "BDAS Fused Attribution V2 — Attribution Check Pass",
      "system": "BDAS",
      "evidence_family": "attribution_validation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "ATTRIBUTION_CHECK_PASS",
      "canonical_question": "What does Fused Attribution V2 evidence?",
      "near_questions": [
        "Was attribution checked?",
        "Can attribution records support evidence binding?",
        "Does attribution imply truth?",
        "Why does attribution matter for VAREXIS-INDEX?",
        "Can an agent inspect attribution posture?",
        "Does this expose private sources?",
        "What is the boundary of attribution evidence?",
        "Can attribution be paid-route metadata?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-fused-attribution-v2-attribution-check-pass",
      "machine_readable_record": "/varexis-index/records/bdas-fused-attribution-v2-attribution-check-pass.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-PERSISTENT-OUTPUT-V3-v1",
      "title": "BDAS Persistent Output V3 — Output Persistence Check",
      "system": "BDAS",
      "evidence_family": "output_persistence",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "PERSISTENCE_CHECK_PASS",
      "canonical_question": "What does Persistent Output V3 evidence?",
      "near_questions": [
        "Were outputs persisted?",
        "Can persistence support evidence review?",
        "Does persisted output prove correctness?",
        "Why does output persistence matter?",
        "Can paid access include receipt metadata?",
        "Does this expose raw outputs?",
        "What is the public boundary?",
        "Can an agent request persisted evidence routes?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-persistent-output-v3-output-persistence-check",
      "machine_readable_record": "/varexis-index/records/bdas-persistent-output-v3-output-persistence-check.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-DECODER-V4-v1",
      "title": "BDAS Decoder V4 — Decoder Check Pass",
      "system": "BDAS",
      "evidence_family": "decoder_validation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "DECODER_CHECK_PASS",
      "canonical_question": "What does Decoder V4 evidence?",
      "near_questions": [
        "Was decoder behaviour checked?",
        "Can decoder checks support consumer integration?",
        "Does decoder validation prove BDAS performance?",
        "What does decoder evidence not show?",
        "Can agents inspect decoder-bound records?",
        "Is this public implementation detail?",
        "Why include decoder records?",
        "Can decoder checks support paid onboarding?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-decoder-v4-decoder-check-pass",
      "machine_readable_record": "/varexis-index/records/bdas-decoder-v4-decoder-check-pass.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-CONSUMER-BINDING-V1-v1",
      "title": "BDAS Consumer Binding V1 — Contract Binding Check",
      "system": "BDAS",
      "evidence_family": "consumer_contract",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "CONTRACT_BINDING_CHECK_PASS",
      "canonical_question": "What does Consumer Binding V1 evidence?",
      "near_questions": [
        "Was consumer binding checked?",
        "Can contract binding support developer onboarding?",
        "Does binding imply performance?",
        "What does a consumer contract check show?",
        "Can agents route to contract evidence?",
        "Is this a public API claim?",
        "What is not demonstrated by consumer binding?",
        "Can paid Developer/API access use this?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-consumer-binding-v1-contract-binding-check",
      "machine_readable_record": "/varexis-index/records/bdas-consumer-binding-v1-contract-binding-check.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260913-G5-2-LOCKED-SYNTHETIC-CONFIRMATION-v1",
      "title": "BDAS G5.2 — Locked Synthetic Confirmation",
      "system": "BDAS",
      "evidence_family": "synthetic_confirmation",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "LOCKED_SYNTHETIC_CONFIRMATION",
      "canonical_question": "What does G5.2 evidence?",
      "near_questions": [
        "Was a locked synthetic confirmation run completed?",
        "Can synthetic confirmation support exactness?",
        "Does locked synthetic confirmation prove external performance?",
        "Is G5.2 useful for regression evidence?",
        "Can an agent inspect this as a confirmation record?",
        "What does G5.2 not demonstrate?",
        "Can G5.2 support paid receipt generation?",
        "How does synthetic differ from customer evidence?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-g5-2-locked-synthetic-confirmation",
      "machine_readable_record": "/varexis-index/records/bdas-g5-2-locked-synthetic-confirmation.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260915-OT3-FREQUENCY-LOCALIZED-v1",
      "title": "BDAS OT3 — Frequency-Localized Development Record",
      "system": "BDAS",
      "evidence_family": "frequency_localized_development",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "DEVELOPMENT_CHECK_NO_REDUCTION_PROMOTION",
      "canonical_question": "What does OT3 evidence?",
      "near_questions": [
        "Was frequency-localized development checked?",
        "Did OT3 produce a reduction claim?",
        "Can a no-reduction record still be useful?",
        "Does OT3 support diagnostics?",
        "Can OT3 be used as negative evidence?",
        "Why preserve development checks?",
        "What would upgrade OT3?",
        "Does OT3 expose signal internals?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-ot3-frequency-localized-development-record",
      "machine_readable_record": "/varexis-index/records/bdas-ot3-frequency-localized-development-record.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260915-C1-PUMP-LOCKED-OUTER-v1",
      "title": "BDAS C1 Pump — Locked Outer Evaluation",
      "system": "BDAS",
      "evidence_family": "pump_locked_outer",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "LOCKED_OUTER_EVALUATION_WITH_BOUNDARIES",
      "canonical_question": "What does C1 Pump locked outer evidence?",
      "near_questions": [
        "Was a locked outer pump evaluation run?",
        "Can C1 support a pump-specific evidence route?",
        "Does C1 prove broad pump diagnostics?",
        "What does locked outer mean?",
        "Can C1 support a paid request?",
        "Does C1 show production readiness?",
        "What is the difference between evaluation and deployment?",
        "How should agents route pump workload questions?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-c1-pump-locked-outer-evaluation",
      "machine_readable_record": "/varexis-index/records/bdas-c1-pump-locked-outer-evaluation.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260915-C3-INFO-GEOMETRY-DEV-v1",
      "title": "BDAS C3 Info-Geometry — Promising Development Record",
      "system": "BDAS",
      "evidence_family": "info_geometry_development",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "PROMISING_DEVELOPMENT_NOT_PROMOTED",
      "canonical_question": "What does C3 info-geometry evidence?",
      "near_questions": [
        "Was info-geometry explored?",
        "Was C3 promoted?",
        "Can promising development evidence be indexed?",
        "Does C3 prove deployment suitability?",
        "Can C3 guide future work?",
        "What does promising but not promoted mean?",
        "Should agents treat C3 as supported capability?",
        "Can C3 create a paid research lead?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-c3-info-geometry-promising-development-record",
      "machine_readable_record": "/varexis-index/records/bdas-c3-info-geometry-promising-development-record.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260915-C4-MACHINE-LOCAL-CALIBRATION-v1",
      "title": "BDAS C4 Machine-Local Calibration — Not Promising",
      "system": "BDAS",
      "evidence_family": "calibration_development",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "NOT_PROMISING_DEVELOPMENT_RECORD",
      "canonical_question": "What does C4 machine-local calibration evidence?",
      "near_questions": [
        "Was machine-local calibration explored?",
        "Was C4 promising?",
        "Can not-promising development evidence be valuable?",
        "Does C4 prevent wasted effort?",
        "Can agents route to negative development records?",
        "What was not demonstrated by C4?",
        "Why preserve not-promising records?",
        "Can C4 support refusal behaviour?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-c4-machine-local-calibration-not-promising",
      "machine_readable_record": "/varexis-index/records/bdas-c4-machine-local-calibration-not-promising.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-202608-M4-MANUFACTURING-EXTERNAL-PROTOCOL-v1",
      "title": "BDAS M4 — Manufacturing External Protocol",
      "system": "BDAS",
      "evidence_family": "external_protocol",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "PROTOCOL_AND_DATASET_RECEIPT",
      "canonical_question": "What does M4 manufacturing evidence?",
      "near_questions": [
        "Was a manufacturing external protocol prepared?",
        "Were selected manufacturing datasets bounded before scoring?",
        "Does protocol existence prove performance?",
        "Can M4 support external evaluation discipline?",
        "What does dataset receipt mean?",
        "Can M4 become a paid evidence route?",
        "Does M4 expose raw dataset processing?",
        "What is not demonstrated by protocol alone?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-m4-manufacturing-external-protocol",
      "machine_readable_record": "/varexis-index/records/bdas-m4-manufacturing-external-protocol.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    },
    {
      "record_id": "VXI-BDAS-20260912-S1-SPECTRAL-ALARM-REFERENCE-v1",
      "title": "BDAS S1 Spectral Alarm — Reference Compatibility Record",
      "system": "BDAS",
      "evidence_family": "spectral_alarm_reference",
      "index_status": "PUBLIC_SAFE_SUMMARY",
      "evidence_state": "REFERENCE_COMPATIBILITY_ONLY",
      "canonical_question": "What does the S1 spectral alarm reference evidence?",
      "near_questions": [
        "Was a spectral alarm reference considered?",
        "Does reference compatibility imply deployment?",
        "Can spectral compatibility support future work?",
        "What is not shown by S1 reference compatibility?",
        "Can agents route spectral questions?",
        "Does this expose signal internals?",
        "Is S1 a commercial alarm product?",
        "What would upgrade S1 reference evidence?"
      ],
      "human_page": "/varexis-index/catalog.html#bdas-s1-spectral-alarm-reference-compatibility-record",
      "machine_readable_record": "/varexis-index/records/bdas-s1-spectral-alarm-reference-compatibility-record.json",
      "paid_access_note": "Paid VAREXIS-INDEX access may provide fuller evidence-route metadata, receipt handling, exports, saved/retrieved routes, request handling, or launch-phase Developer/API onboarding. Public records intentionally omit raw logs, thresholds, private implementation details, reconstruction-level methods and sensitive evidence payloads."
    }
  ],
  "question_context_router": "/varexis-index/contexts/question-context-router.json",
  "paid_layer_boundary": "The public index is a discovery and sampling surface. Paid access may expose fuller evidence-route metadata, receipts, exports, request handling or launch-phase Developer/API onboarding without exposing protected IP.",
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "agentic_question_routes": "/varexis-index/questions.json",
  "public_catalog_plain_marker": "32 public records",
  "paid_conversion_model": {
    "public_layer": "Public-safe discovery, sample records, near-question routing and refusal boundaries.",
    "paid_layer": "Fuller evidence-route metadata, receipts, exports, saved routes, request handling and launch-phase Developer/API onboarding.",
    "private_layer": "Protected evidence reservoir, raw artefacts, implementation detail and IP-sensitive records."
  },
  "tranche_2_added_record_count": 20,
  "last_public_safe_expansion_at_utc": "2026-10-06T21:46:00.616Z",
  "near_question_hook_count": 361,
  "service_routes": "/varexis-index/service-routes.json",
  "daily_entry_builder": "/varexis-index/daily-builder.json",
  "service_payment_routing": {
    "status": "published_launch_phase",
    "public_discovery": "/varexis-index.json",
    "agentic_questions": "/varexis-index/questions.json",
    "service_routes": "/varexis-index/service-routes.json",
    "daily_builder": "/varexis-index/daily-builder.json",
    "pricing_page": "/pricing",
    "checkout_terms": "/checkout-terms"
  },
  "trusted_niche_layer_target": {
    "deadline_class": "end_of_week_target",
    "public_records_minimum": 100,
    "public_records_preferred": 150,
    "agentic_routes_minimum": 30,
    "agentic_routes_preferred": 50,
    "near_question_hooks_minimum": 1200,
    "near_question_hooks_preferred": 2000
  },
  "payment_to_fulfilment_path": [
    "public_discovery",
    "service_selection",
    "stripe_checkout_where_required",
    "request_intake",
    "evidence_route_resolution",
    "boundary_check",
    "answer_or_receipt_generation",
    "manual_or_launch_phase_delivery"
  ]
}
