{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-SLSA-RESOLVED-DEPENDENCIES-COMPLETENESS-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "SLSA: Provenance dependency lists are not exhaustive inventories",
  "system": "SLSA",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does SLSA Build L3 provenance guarantee that resolvedDependencies lists every build dependency?",
  "near_questions": [
    "Does Build L3 make resolvedDependencies exhaustive?",
    "Can provenance replace a complete software inventory?",
    "How do dependency and external-parameter completeness differ?",
    "Which missing build inputs need separate evidence?",
    "What supports a dependency exposure review beyond provenance?",
    "Does a signed dependency list prove every fetched artifact is listed?"
  ],
  "supported_claims": [
    {
      "claim": "The SLSA v1.2 provenance specification describes resolvedDependencies completeness as best effort through Build L3. This differs from the completeness requirement for externalParameters. A provenance dependency list therefore cannot alone establish an exhaustive inventory for exposure or reconstruction review.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Certification of a build level, complete SBOM generation or actual vulnerability exposure",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "The SLSA v1.2 provenance specification describes resolvedDependencies completeness as best effort through Build L3. This differs from the completeness requirement for externalParameters. A provenance dependency list therefore cannot alone establish an exhaustive inventory for exposure or reconstruction review.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "SLSA v1.2 provenance",
    "source_url": "https://slsa.dev/spec/v1.2/build-provenance",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SLSA-RESOLVED-DEPENDENCIES-COMPLETENESS-BOUNDARY-01-v1",
    "candidate_record_sha256": "0d28eccb3c8e1fbe9e9e5f70a900465f356f5297f30d202ab61462f26974b784",
    "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 SLSA v1.2 provenance specification describes resolvedDependencies completeness as best effort through Build L3. This differs from the completeness requirement for externalParameters. A provenance dependency list therefore cannot alone establish an exhaustive inventory for exposure or reconstruction review.",
    "required_buyer_context": "The provenance version, builder and subject. The resolvedDependencies and builder documentation. Independent inventory or build evidence for required coverage. 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-18",
    "claim_to_check": "Does SLSA Build L3 provenance guarantee that resolvedDependencies lists every build dependency?",
    "documented_statement": {
      "status": "documented",
      "statement": "The SLSA v1.2 provenance specification describes resolvedDependencies completeness as best effort through Build L3. This differs from the completeness requirement for externalParameters. A provenance dependency list therefore cannot alone establish an exhaustive inventory for exposure or reconstruction review.",
      "source_ids": [
        "slsa-deps"
      ]
    },
    "buyer_evidence_required": [
      "The provenance version, builder and subject.",
      "The resolvedDependencies and builder documentation.",
      "Independent inventory or build evidence for required coverage."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not assert exhaustive dependency coverage solely from a Build L3 label or provenance field presence."
    },
    "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": "slsa-deps",
        "url": "https://slsa.dev/spec/v1.2/build-provenance",
        "final_url": "https://slsa.dev/spec/v1.2/build-provenance",
        "title": "SLSA v1.2 provenance",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:09:40.649Z",
        "version_context": "SLSA specification v1.2; resolvedDependencies completeness",
        "sha256": "04a97c9bffb011dba65620b447b66ce7d52a01b0f4f4f5c32dee3391d170f647",
        "bytes": 63344,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does SLSA Build L3 provenance guarantee that resolvedDependencies lists every build dependency?"
        ]
      }
    ],
    "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": "A software buyer must separate build-origin assurance from a complete dependency inventory.",
      "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": "The provenance version, builder and subject. The resolvedDependencies and builder documentation. Independent inventory or build evidence for required coverage."
    },
    "buyer_relevance": "A software buyer must separate build-origin assurance from a complete dependency inventory.",
    "refusal_conditions": [
      "Do not assert exhaustive dependency coverage solely from a Build L3 label or provenance field presence."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "A software buyer must separate build-origin assurance from a complete dependency inventory.",
    "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#slsa-resolved-dependencies-completeness-boundary",
  "machine_readable_record": "/varexis-index/records/slsa-resolved-dependencies-completeness-boundary.json"
}
