{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T14:13:51.913Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-SKIPPED-CHECK-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub checks: Successful status and skipped execution",
  "system": "GitHub Actions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a passing required GitHub check prove its test job actually ran?",
  "near_questions": [
    "Was the job executed or skipped?",
    "What condition controlled execution?",
    "Can neutral satisfy this required check?",
    "Did path filtering skip the workflow?",
    "Why is a skipped workflow pending?",
    "Which commit was checked?",
    "Does the merge badge identify test output?",
    "Was a dependent job skipped after failure?",
    "What proves the required test ran?",
    "Are required checks named unambiguously?",
    "Does the evidence match the release revision?",
    "Can I save the execution review?"
  ],
  "supported_claims": [
    {
      "claim": "Required checks accept success, skipped and neutral conclusions. A job skipped by a condition can report success, while a whole workflow skipped by path or branch filtering can remain pending. Review job execution and the applicable commit, not just the merge badge, before claiming a release passed a specific test.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Required checks accept success, skipped and neutral conclusions. A job skipped by a condition can report success, while a whole workflow skipped by path or branch filtering can remain pending. Review job execution and the applicable commit, not just the merge badge, before claiming a release passed a specific test.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub: Troubleshooting required status checks",
    "source_url": "https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-SKIPPED-CHECK-01-v1",
    "candidate_record_sha256": "5d6bbda466cfde11e8fd2ab77c42e9822a1928e0eabd7979201479cedcfd30a0",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Required checks accept success, skipped and neutral conclusions. A job skipped by a condition can report success, while a whole workflow skipped by path or branch filtering can remain pending. Review job execution and the applicable commit, not just the merge badge, before claiming a release passed a specific test.",
    "required_buyer_context": "Branch rules, workflow version, check identity, conditions and commit-bound test output. Effective configuration and dated operational evidence have not been inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-16",
    "claim_to_check": "A green required-check badge proves test execution.",
    "documented_statement": {
      "status": "documented",
      "statement": "Required checks accept success, skipped and neutral conclusions. A job skipped by a condition can report success, while a whole workflow skipped by path or branch filtering can remain pending. Review job execution and the applicable commit, not just the merge badge, before claiming a release passed a specific test.",
      "source_ids": [
        "github-checks"
      ]
    },
    "buyer_evidence_required": [
      "Required check identity and applicable commit.",
      "Job conditions, execution steps and conclusion.",
      "Test output bound to the accepted revision."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require actual execution evidence before describing a skipped or neutral check as a passed test."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "github-checks",
        "url": "https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks",
        "final_url": "https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks",
        "title": "GitHub: Troubleshooting required status checks",
        "checked_on": "2026-10-16",
        "sha256": "c7956aa97a4a4ba6a3e625a3090d0c19655cfb29fe55d3c1953f7f58ce750d70",
        "bytes": 181140
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Preserve the difference between merge eligibility and demonstrated test execution.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Branch rules, workflow version, check identity, conditions and commit-bound test output."
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#github-required-check-skipped-versus-executed",
  "machine_readable_record": "/varexis-index/records/github-required-check-skipped-versus-executed.json"
}