{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T14:13:51.913Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITHUB-NESTED-SECRETS-01-v1",
  "record_kind": "external_reference",
  "title": "Nested workflows: Secret forwarding boundaries",
  "system": "GitHub Actions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does passing secrets to one reusable GitHub workflow automatically pass them to every nested workflow?",
  "near_questions": [
    "Which workflow directly receives the secret?",
    "Is secrets: inherit used?",
    "Which named secrets are mapped?",
    "Does the next nested workflow receive them?",
    "Was forwarding explicit at each hop?",
    "Who owns each reusable workflow?",
    "Are all forwarded secrets needed?",
    "Could an environment secret change the effective source?",
    "Which revision defines the mapping?",
    "Can the review omit secret values?",
    "What proves intended recipient scope?",
    "Can I preserve the secret-routing review?"
  ],
  "supported_claims": [
    {
      "claim": "Secrets are passed only to the directly called workflow. In a caller-to-intermediate-to-nested chain, the intermediate workflow must also forward the relevant secrets. Explicit mappings and secrets: inherit have different breadth. Review each call boundary without exposing the values when assessing credential disclosure.",
      "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": "Secrets are passed only to the directly called workflow. In a caller-to-intermediate-to-nested chain, the intermediate workflow must also forward the relevant secrets. Explicit mappings and secrets: inherit have different breadth. Review each call boundary without exposing the values when assessing credential disclosure.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub: Reuse workflows",
    "source_url": "https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITHUB-NESTED-SECRETS-01-v1",
    "candidate_record_sha256": "0fceaa0a48f6f9054ef90578fcc7b621fb4c49f4468391f4e3b05f35b4113956",
    "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": "Secrets are passed only to the directly called workflow. In a caller-to-intermediate-to-nested chain, the intermediate workflow must also forward the relevant secrets. Explicit mappings and secrets: inherit have different breadth. Review each call boundary without exposing the values when assessing credential disclosure.",
    "required_buyer_context": "Workflow ownership, references, secret names and per-hop forwarding; never include values. 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": "Secrets automatically propagate through the entire workflow chain.",
    "documented_statement": {
      "status": "documented",
      "statement": "Secrets are passed only to the directly called workflow. In a caller-to-intermediate-to-nested chain, the intermediate workflow must also forward the relevant secrets. Explicit mappings and secrets: inherit have different breadth. Review each call boundary without exposing the values when assessing credential disclosure.",
      "source_ids": [
        "github-secrets"
      ]
    },
    "buyer_evidence_required": [
      "Caller/callee chain and exact workflow revisions.",
      "Named secret mappings or inherit settings per hop.",
      "Authorized recipients and required credential purpose."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require a per-hop disclosure map before approving secret inheritance across workflow owners."
    },
    "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-secrets",
        "url": "https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows",
        "final_url": "https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows",
        "title": "GitHub: Reuse workflows",
        "checked_on": "2026-10-16",
        "sha256": "97745b0450b582dcf10c3f6aae0dfa818b2ce214654485ad7d6c8025e725ccbe",
        "bytes": 471850
      }
    ],
    "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 credential-routing evidence without retaining sensitive credentials.",
      "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": "Workflow ownership, references, secret names and per-hop forwarding; never include values."
    }
  },
  "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-nested-workflow-secret-forwarding-boundary",
  "machine_readable_record": "/varexis-index/records/github-nested-workflow-secret-forwarding-boundary.json"
}