{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T14:13:51.913Z",
  "record_id": "VXI-EXT-PROCUREMENT-DOCKER-PROVENANCE-DISCLOSURE-01-v1",
  "record_kind": "external_reference",
  "title": "Build provenance: Detail level and argument disclosure",
  "system": "Docker Buildx",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does publishing a Docker provenance attestation keep build arguments private?",
  "near_questions": [
    "Was provenance generated in min or max mode?",
    "Are build-argument values included?",
    "Does the attestation contain the Dockerfile?",
    "Were credentials passed as build arguments?",
    "Was the dedicated secret mechanism used?",
    "Who can read the attestation?",
    "Does its subject digest match the image?",
    "Was the actual payload inspected?",
    "Can detailed provenance expose internal build context?",
    "Does metadata prove build approval?",
    "Which tool version produced it?",
    "Can I preserve the provenance-disclosure review?"
  ],
  "supported_claims": [
    {
      "claim": "The min mode omits build-argument values, while max mode contains additional build detail including argument values and the Dockerfile. Secrets should use the documented secret mechanism rather than build arguments. Review the actual attestation and intended audience; provenance presence alone does not establish confidentiality or an approved build.",
      "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": "The min mode omits build-argument values, while max mode contains additional build detail including argument values and the Dockerfile. Secrets should use the documented secret mechanism rather than build arguments. Review the actual attestation and intended audience; provenance presence alone does not establish confidentiality or an approved build.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Docker: Provenance attestations",
    "source_url": "https://docs.docker.com/build/metadata/attestations/slsa-provenance/",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DOCKER-PROVENANCE-DISCLOSURE-01-v1",
    "candidate_record_sha256": "400bca4c6e6d72ec5aac6e2e6a489ef35b74cd873e12a97a22398c7e8f1037c3",
    "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": "The min mode omits build-argument values, while max mode contains additional build detail including argument values and the Dockerfile. Secrets should use the documented secret mechanism rather than build arguments. Review the actual attestation and intended audience; provenance presence alone does not establish confidentiality or an approved build.",
    "required_buyer_context": "Buildx version, mode, argument usage, secret handling, output payload and audience. 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": "Provenance metadata never exposes build inputs.",
    "documented_statement": {
      "status": "documented",
      "statement": "The min mode omits build-argument values, while max mode contains additional build detail including argument values and the Dockerfile. Secrets should use the documented secret mechanism rather than build arguments. Review the actual attestation and intended audience; provenance presence alone does not establish confidentiality or an approved build.",
      "source_ids": [
        "docker-provenance"
      ]
    },
    "buyer_evidence_required": [
      "Buildx mode and generated attestation.",
      "Argument usage and secret-handling configuration.",
      "Publication destination, audience and subject digest."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Review disclosure and subject identity before publishing or accepting provenance."
    },
    "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": "docker-provenance",
        "url": "https://docs.docker.com/build/metadata/attestations/slsa-provenance/",
        "final_url": "https://docs.docker.com/build/metadata/attestations/slsa-provenance/",
        "title": "Docker: Provenance attestations",
        "checked_on": "2026-10-16",
        "sha256": "0131489011611796190dbfe551d85a5313a98a686877d0597d21b3b6daa88d9b",
        "bytes": 582692
      }
    ],
    "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": "Save the disclosure and artifact-binding basis for accepting build provenance.",
      "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": "Buildx version, mode, argument usage, secret handling, output payload and audience."
    }
  },
  "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#docker-provenance-mode-build-argument-disclosure",
  "machine_readable_record": "/varexis-index/records/docker-provenance-mode-build-argument-disclosure.json"
}