{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T13:36:43.315Z",
  "record_id": "VXI-EXT-PROCUREMENT-ELASTIC-ROLLOVER-AGE-01-v1",
  "record_kind": "external_reference",
  "title": "Elasticsearch ILM: Age measured from rollover",
  "system": "Elasticsearch",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an ILM minimum age mean each log is deleted that long after its event timestamp?",
  "near_questions": [
    "Is ILM age measured from rollover?",
    "Is it the same as index creation time?",
    "Does each event get its own deletion timer?",
    "Which events share this index?",
    "When did rollover occur?",
    "Which phase contains deletion?",
    "Has the index reached that phase?",
    "Does a setting prove the action completed?",
    "Can older events enter a newer index?",
    "Which lifecycle engine is used?",
    "What evidence supports actual retention duration?",
    "Can I save the lifecycle-age boundary?"
  ],
  "supported_claims": [
    {
      "claim": "After rollover, ILM phase minimum ages use the previous index rollover time rather than its creation time. The policy acts on indices, while individual events can have different timestamps. A phase-age setting alone is not evidence of exact per-event deletion timing.",
      "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": "After rollover, ILM phase minimum ages use the previous index rollover time rather than its creation time. The policy acts on indices, while individual events can have different timestamps. A phase-age setting alone is not evidence of exact per-event deletion timing.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Elasticsearch index rollover lifecycle",
    "source_url": "https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/rollover",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-ELASTIC-ROLLOVER-AGE-01-v1",
    "candidate_record_sha256": "5074a69e658799b7b903f0d915f830de2200a87fee595a7385d3fbbee0671960",
    "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": "After rollover, ILM phase minimum ages use the previous index rollover time rather than its creation time. The policy acts on indices, while individual events can have different timestamps. A phase-age setting alone is not evidence of exact per-event deletion timing.",
    "required_buyer_context": "Index lifecycle policy, rollover time, event membership and phase state. 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": "An index lifecycle minimum age guarantees a matching event-age retention period.",
    "documented_statement": {
      "status": "documented",
      "statement": "After rollover, ILM phase minimum ages use the previous index rollover time rather than its creation time. The policy acts on indices, while individual events can have different timestamps. A phase-age setting alone is not evidence of exact per-event deletion timing.",
      "source_ids": [
        "ilm"
      ]
    },
    "buyer_evidence_required": [
      "Rollover timestamp and lifecycle policy.",
      "Index membership and event timestamps.",
      "Phase progress and deletion evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Check the lifecycle reference time and index contents before asserting per-event retention."
    },
    "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": "ilm",
        "url": "https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/rollover",
        "final_url": "https://www.elastic.co/docs/manage-data/lifecycle/index-lifecycle-management/rollover",
        "title": "Elasticsearch index rollover lifecycle",
        "checked_on": "2026-10-16",
        "sha256": "4c483ea81a520faa94fc8f41868cbd4324b7db03df2daff48ba1dedfaeb5e9c3",
        "bytes": 100404
      }
    ],
    "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 the distinction between index lifecycle settings and event-level retention claims.",
      "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": "Index lifecycle policy, rollover time, event membership and phase state."
    }
  },
  "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#elastic-ilm-rollover-age-retention-boundary",
  "machine_readable_record": "/varexis-index/records/elastic-ilm-rollover-age-retention-boundary.json"
}