{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-RULESET-APP-BYPASS-SEPARATE-AUTHORITY-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub ruleset bypass authority",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does repository contents-write permission establish that a GitHub App can bypass repository rulesets?",
  "near_questions": [
    "Can a GitHub App write token bypass branch rules?",
    "Where is a GitHub App’s ruleset bypass permission configured?",
    "What differs between pull-request-only and always bypass?",
    "Which evidence permits an app to bypass repository rulesets?"
  ],
  "supported_claims": [
    {
      "claim": "GitHub rulesets have an explicit bypass list that can include selected apps, roles and teams. Bypass can be limited to pull requests or allowed always, depending on configuration. A token’s contents-write permission does not identify whether the app is on that list or which bypass mode applies.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic ruleset exemption from write access",
    "The repository’s effective rulesets and bypass assignments are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "GitHub rulesets have an explicit bypass list that can include selected apps, roles and teams. Bypass can be limited to pull requests or allowed always, depending on configuration. A token’s contents-write permission does not identify whether the app is on that list or which bypass mode applies.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Creating rulesets for a repository - GitHub Docs",
    "source_url": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-RULESET-APP-BYPASS-SEPARATE-AUTHORITY-01-v1",
    "candidate_record_sha256": "43d579c2034126ed867a4757b3a1e664bb96fbfeb1dc2d5c883798fdaaca1a6c",
    "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": "GitHub rulesets have an explicit bypass list that can include selected apps, roles and teams. Bypass can be limited to pull requests or allowed always, depending on configuration. A token’s contents-write permission does not identify whether the app is on that list or which bypass mode applies.",
    "required_buyer_context": "Target repository, branch or tag and applicable rulesets; App identity and explicit bypass-list entries; Bypass mode and planned update path. Buyer deployment not 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-24",
    "claim_to_check": "Does repository contents-write permission establish that a GitHub App can bypass repository rulesets?",
    "documented_statement": {
      "status": "documented",
      "statement": "GitHub rulesets have an explicit bypass list that can include selected apps, roles and teams. Bypass can be limited to pull requests or allowed always, depending on configuration. A token’s contents-write permission does not identify whether the app is on that list or which bypass mode applies.",
      "source_ids": [
        "github-rulesets"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Inspect applicable rulesets and app-specific bypass entries separately from repository write permission.",
      "source_ids": [
        "github-rulesets"
      ]
    },
    "buyer_evidence_required": [
      "Target repository, branch or tag and applicable rulesets",
      "App identity and explicit bypass-list entries",
      "Bypass mode and planned update path"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject a bypass-authority claim based only on contents-write scope."
    },
    "unknowns": "The repository’s effective rulesets and bypass assignments are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The repository’s effective rulesets and bypass assignments are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "github-rulesets",
        "url": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository",
        "final_url": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:47:22.608Z",
        "sha256": "a43226826ea47cb08dbb8f209e99581abf87c6c6771226bf5a1c734ee13e10e1",
        "bytes": 298147,
        "title": "Creating rulesets for a repository - GitHub Docs",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Granting bypass permissions",
          "Pull-request-only mode"
        ],
        "version_context": "Rolling official documentation captured 2026-10-24; installed API/SDK version, account tier and buyer configuration require verification."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid promising a protected repository update that the app is not authorised to bypass.",
      "free": "Complete review, sources, practical questions 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": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid promising a protected repository update that the app is not authorised to bypass.",
    "refusal_conditions": [
      "Reject a bypass-authority claim based only on contents-write scope."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Avoid promising a protected repository update that the app is not authorised to bypass.",
    "comparison_role": "supplementary_discovery"
  },
  "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-ruleset-app-bypass-separate-authority",
  "machine_readable_record": "/varexis-index/records/github-ruleset-app-bypass-separate-authority.json"
}
