{ "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-24T23:11:13.073Z", "record_id": "VXI-EXT-PROCUREMENT-INTOTO-MATCH-NONMATCH-CONSUMPTION-01-v1", "record_kind": "external_reference", "title": "in-toto MATCH and explicit rejection", "system": "in-toto specification v1.0.0", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Does an in-toto MATCH rule by itself fail verification when artifact hashes differ?", "near_questions": [ "Will in-toto MATCH alone reject mismatched hashes?", "What happens when an in-toto MATCH destination artifact is missing?", "Why combine in-toto MATCH with explicit rejection rules?", "Which evidence shows a failed match was actually rejected?" ], "supported_claims": [ { "claim": "The in-toto 1.0.0 MATCH algorithm consumes source artifacts only when corresponding destination names and hashes match. Missing counterparts or unequal hashes remain unconsumed. The specification identifies DISALLOW and REQUIRE as the rules that can stop rule processing, so a MATCH non-match must be interpreted with the rest of the ordered policy rather than assumed to be an automatic rejection.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Actual artifact origin and complete policy execution remain unverified.", "No verified business outcome, complete event capture, deployment certification or authority to act.", "Buyer deployment testing, live runtime enforcement, certification or permission to act", "Expanded capabilities or licences for existing INDEX executables" ], "public_summary": "The in-toto 1.0.0 MATCH algorithm consumes source artifacts only when corresponding destination names and hashes match. Missing counterparts or unequal hashes remain unconsumed. The specification identifies DISALLOW and REQUIRE as the rules that can stop rule processing, so a MATCH non-match must be interpreted with the rest of the ordered policy rather than assumed to be an automatic rejection.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "in-toto specification v1.0.0 — in-toto-spec", "source_url": "https://raw.githubusercontent.com/in-toto/specification/6459afd8e94a332e423ba05c2862b534acbe741d/in-toto-spec.md", "checked_on": "2026-10-24", "candidate_record_id": "VXI-EXT-PROCUREMENT-INTOTO-MATCH-NONMATCH-CONSUMPTION-01-v1", "candidate_record_sha256": "f8052a447403cce3144044bd451e5a4ee33cbea38c694ec24ef78444292e0145", "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 in-toto 1.0.0 MATCH algorithm consumes source artifacts only when corresponding destination names and hashes match. Missing counterparts or unequal hashes remain unconsumed. The specification identifies DISALLOW and REQUIRE as the rules that can stop rule processing, so a MATCH non-match must be interpreted with the rest of the ordered policy rather than assumed to be an automatic rejection.", "required_buyer_context": "Source and destination artifact maps; MATCH prefixes and hash comparisons; Subsequent rules and final unconsumed queue. 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 an in-toto MATCH rule by itself fail verification when artifact hashes differ?", "documented_statement": { "status": "documented", "statement": "The in-toto 1.0.0 MATCH algorithm consumes source artifacts only when corresponding destination names and hashes match. Missing counterparts or unequal hashes remain unconsumed. The specification identifies DISALLOW and REQUIRE as the rules that can stop rule processing, so a MATCH non-match must be interpreted with the rest of the ordered policy rather than assumed to be an automatic rejection.", "source_ids": [ "intoto-spec" ] }, "review_inference": { "status": "review_inference", "statement": "Check that failed artifact linkage reaches an explicit rejection condition. This is a review judgment, not an observed execution or deployment result.", "source_ids": [ "intoto-spec" ] }, "buyer_evidence_required": [ "Source and destination artifact maps", "MATCH prefixes and hash comparisons", "Subsequent rules and final unconsumed queue" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse enforced artifact continuity from a MATCH rule without the closing policy." }, "unknowns": "Actual artifact origin and complete policy execution remain unverified.", "unknown_finding": { "status": "unknown", "statement": "Actual artifact origin and complete policy execution remain unverified." }, "evidence_sources": [ { "source_id": "intoto-spec", "url": "https://raw.githubusercontent.com/in-toto/specification/6459afd8e94a332e423ba05c2862b534acbe741d/in-toto-spec.md", "final_url": "https://raw.githubusercontent.com/in-toto/specification/6459afd8e94a332e423ba05c2862b534acbe741d/in-toto-spec.md", "status": 200, "captured_at_utc": "2026-10-24T22:53:31.042Z", "sha256": "dc5cdd7086397efd402262ee966035d9ff0854f777dfa3b925e635c179898340", "bytes": 93385, "title": "in-toto specification v1.0.0 — in-toto-spec", "hash_basis": "Decoded HTTP response body bytes", "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. Repository MIT licence reviewed.", "checked_on": "2026-10-24", "capture_status": 200, "claim_review_completed": true, "reviewed_sections": [ "4.3.1 Steps: expected_command", "4.4 Byproducts; 4.3.2.1 Inspection interface", "4.3.2 Inspections; 5.2 verification workflow", "4.3.3.1 Rule processing", "4.3.3.1 Sequential rule processing; 4.3.3.3 DISALLOW", "4.3.3.2 MATCH; 4.3.3.3 error-producing rules", "4.3.3 Artifact rules: MODIFY", "4.3 EXPIRES; 5.2 expiry verification", "3.1.2 Link metadata reuse", "4.5.1 Artifact rules in sublayouts; 4.5.3 inspections", "4.5.3 Inspections on sublayouts", "4.5.2 Namespacing link metadata" ], "version_context": "in-toto specification 1.0.0 (2023-06-02), pinned revision; pinned in-toto/specification revision 6459afd8e94a332e423ba05c2862b534acbe741d. Source documentation is not independent evidence of buyer deployment behaviour." } ], "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": "Check that failed artifact linkage reaches an explicit rejection condition.", "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 pinned source, deployed version, selection policy and retained operation results before relying on a current outcome." }, "buyer_relevance": "Check that failed artifact linkage reaches an explicit rejection condition.", "refusal_conditions": [ "Refuse enforced artifact continuity from a MATCH rule without the closing policy." ] }, "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": "Check that failed artifact linkage reaches an explicit rejection condition.", "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#intoto-match-nonmatch-consumption", "machine_readable_record": "/varexis-index/records/intoto-match-nonmatch-consumption.json" }