{
  "schema": "sasquatch.yeti.public-verification.v1",
  "document_version": "2026-09-20.2",
  "canonical_url": "https://sasquatchlabs.io/yeti-verification.json",
  "purpose": "Public claim boundaries and verification methods for Yeti. This is a vendor-authored verification contract, not a third-party certification or a substitute for customer acceptance testing.",
  "latest_public_run": "https://sasquatchlabs.io/yeti-verification-run-2026-09-20.txt",
  "status_vocabulary": {
    "product_contract": "A required Yeti operating semantic backed by executable engineering gates and subject to customer acceptance testing.",
    "public_method": "A public method or artifact explains how the claim is checked.",
    "deployment_specific": "The result depends on customer topology, sources, retention, models, connectors, or policy and must be verified in that environment."
  },
  "dated_execution_evidence": [
    {
      "executed_at": "2026-09-20",
      "scope": "Yeti marketing and machine-discovery release gate",
      "result": "pass",
      "evidence": ["13 of 13 landing tests passed", "production build passed", "40 routes prerendered", "four viewport browser audit passed", "manifest and discovery JSON parsed", "sitemap XML parsed", "dependency audit reported zero vulnerabilities"],
      "limits": "This proves the public experience and discovery artifacts, not security-runtime behavior."
    },
    {
      "executed_at": "2026-09-20",
      "scope": "Live-Postgres Yeti agent, playbook, and API safety suites",
      "result": "pass",
      "command_class": "Go package tests against a disposable PostgreSQL 16 database with the current 329-file Supabase migration chain; LIVE_DB_TEST was set to the database DSN",
      "evidence": ["internal/yetiagent passed in 9.087s", "internal/playbooks passed in 17.514s", "cmd/api passed in 1.049s"],
      "limits": "Vendor-executed repository evidence only; not customer-deployment evidence, connector certification, a scale result, or third-party attestation."
    }
  ],
  "claims": [
    {
      "claim": "Persistent 24/7 agentic operation",
      "boundary": "Software agents can run continuously or on schedules; this is not a bundled human MDR claim.",
      "status": ["product_contract", "deployment_specific"],
      "verification": ["scheduled mission continues without an analyst initiating each run", "budget and stop condition terminate work", "mission history and agent identity remain inspectable"]
    },
    {
      "claim": "Evidence-grounded conclusions",
      "boundary": "Applies to connected and retained evidence; missing evidence remains unknown.",
      "status": ["product_contract"],
      "verification": ["original-record lineage is retrievable", "observed, inspected, inferred, and unknown states remain distinct", "conclusion exposes support, conflict, and missing evidence"]
    },
    {
      "claim": "Behaviorally validated detections",
      "boundary": "Enabled detection content must satisfy the configured approval gate and required behavioral evidence.",
      "status": ["product_contract", "deployment_specific"],
      "verification": ["real parser and engine path", "known-positive fixture", "closest benign negative", "tenant/entity and malformed-configuration rejection", "replay, expiry, and ordering checks when stateful"]
    },
    {
      "claim": "Governed response",
      "boundary": "A capability or proposal does not imply permission or execution.",
      "status": ["product_contract", "deployment_specific"],
      "verification": ["ambiguous target rejected before mutation", "effective scope and policy evaluated", "configured approval bound to the action", "vendor result, reconciliation state, and rollback path retained"]
    },
    {
      "claim": "Tenant and authority isolation",
      "boundary": "Work is scoped by explicit tenant, identity, entity, target, role, and resource authority.",
      "status": ["product_contract"],
      "verification": ["cross-tenant input rejected", "missing scope fails closed", "denial occurs before state mutation", "audit record retains the evaluated identity and scope"]
    },
    {
      "claim": "Customer-controlled deployment",
      "boundary": "Exact topology, model route, outbound connectivity, minimum infrastructure, and disconnected limitations are deployment-specific.",
      "status": ["product_contract", "deployment_specific"],
      "verification": ["customer controls evidence stores and keys", "model content follows tenant policy", "unsupported dependency fails closed", "offline operating requirements are tested in the selected topology"]
    },
    {
      "claim": "Lossless retained evidence",
      "boundary": "Applies to telemetry connected and retained under customer source and retention policy.",
      "status": ["public_method", "deployment_specific"],
      "verification": ["round-trip original record", "integrity comparison", "normalized-to-original linkage", "recoverability check"],
      "public_method_url": "https://sasquatchlabs.io/security/integrity"
    }
  ],
  "evaluation": "https://sasquatchlabs.io/yeti/agents#initial-technical-evaluation",
  "related": {
    "product": "https://sasquatchlabs.io/yeti",
    "agent_context": "https://sasquatchlabs.io/yeti/agents",
    "manifest": "https://sasquatchlabs.io/yeti-agent.json",
    "integrity": "https://sasquatchlabs.io/security/integrity",
    "keys": "https://sasquatchlabs.io/security/keys",
    "benchmarks": "https://sasquatchlabs.io/benchmarks"
  }
}