{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T02:40:06.177Z",
  "record_id": "VXI-EXT-PROCUREMENT-DOCKER-DIGEST-UPDATES-01-v1",
  "record_kind": "external_reference",
  "title": "Docker digest pins: Repeatable identity still needs an update process",
  "system": "Docker",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does pinning a container image digest automatically keep its security fixes current?",
  "near_questions": [
    "Can a Docker tag point to a different image later?",
    "What does a digest pin preserve?",
    "Does pinning automatically receive new fixes?",
    "Who reviews a newer base-image digest?",
    "Can reproducibility and currency conflict?",
    "Which platform image is selected?",
    "Does a current tag prove a deployed digest changed?",
    "What audit trail supports an approved update?",
    "Can an agent change a pin without release authority?",
    "Which build used the recorded digest?",
    "When should a patch-currency claim remain qualified?",
    "Can I save a container pinning review?"
  ],
  "supported_claims": [
    {
      "claim": "Digest pinning binds a build to a specific image even when a tag moves. The guide explains that this also opts out of automatic updates through the moving tag. Reproducibility and currency therefore require separate evidence: a fixed identity plus a reviewed process for updating it.",
      "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": "Digest pinning binds a build to a specific image even when a tag moves. The guide explains that this also opts out of automatic updates through the moving tag. Reproducibility and currency therefore require separate evidence: a fixed identity plus a reviewed process for updating it.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-GITHUB-ATTESTATION-01-v1",
    "VXI-EXT-PROCUREMENT-NPM-PROVENANCE-01-v1",
    "VXI-EXT-PROCUREMENT-PYPI-TRUSTED-PUBLISHER-01-v1",
    "VXI-EXT-PROCUREMENT-GITLAB-IMMUTABLE-TAGS-01-v1",
    "VXI-EXT-PROCUREMENT-ARTIFACT-CLEANUP-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Docker image digest pinning",
    "source_url": "https://docs.docker.com/build/building/best-practices/",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DOCKER-DIGEST-UPDATES-01-v1",
    "candidate_record_sha256": "b60fef6bb81448865b72e81cb7cdc9eccf372461c4e91c9552b66b170935388b",
    "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": "Digest pinning binds a build to a specific image even when a tag moves. The guide explains that this also opts out of automatic updates through the moving tag. Reproducibility and currency therefore require separate evidence: a fixed identity plus a reviewed process for updating it.",
    "required_buyer_context": "Docker: Image digest, platform, update ownership and build evidence; buyer configuration and operational evidence are required.",
    "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 pinned image remains automatically current with publisher fixes.",
    "documented_statement": {
      "status": "documented",
      "statement": "Digest pinning binds a build to a specific image even when a tag moves. The guide explains that this also opts out of automatic updates through the moving tag. Reproducibility and currency therefore require separate evidence: a fixed identity plus a reviewed process for updating it.",
      "source_ids": [
        "docker-pin"
      ]
    },
    "buyer_evidence_required": [
      "Exact base-image digest and platform context.",
      "Publisher update monitoring and review ownership.",
      "Evidence of approved digest updates and resulting builds."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim current fixes solely from a stable digest."
    },
    "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-pin",
        "url": "https://docs.docker.com/build/building/best-practices/",
        "final_url": "https://docs.docker.com/build/building/best-practices/",
        "title": "Docker image digest pinning",
        "checked_on": "2026-10-16",
        "sha256": "f7b562bdd13bed8fd5f4893b667949182714effa274be6fd6e16032c3b677664",
        "bytes": 653676
      }
    ],
    "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 distinction between reproducible identity and maintained software.",
      "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": "Image digest, platform, update ownership and build evidence"
    }
  },
  "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-image-digest-update-boundary",
  "machine_readable_record": "/varexis-index/records/docker-image-digest-update-boundary.json"
}