{
  "context": "Evaluates whether the solution uses github.com/prometheus/client_model/go to encode counter, summary, and histogram payloads with creation timestamps derived from provided start times, omitting the field when no start time is supplied. Checks focus solely on populating the dependency's creation timestamp properties rather than generic sample timestamps.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Counter timestamp",
      "description": "Sets io_prometheus_client.Counter.CreatedTimestamp from the provided start time (Unix milliseconds) when non-zero, rather than using Metric.TimestampMs or omitting the field.",
      "max_score": 30
    },
    {
      "name": "Summary timestamp",
      "description": "Populates io_prometheus_client.Summary.CreatedTimestamp from the start time whenever present, keeping sample counts/sums intact and avoiding use of the generic metric timestamp field.",
      "max_score": 25
    },
    {
      "name": "Histogram timestamp",
      "description": "Assigns io_prometheus_client.Histogram.CreatedTimestamp based on the start time for classic histogram payloads while preserving bucket data, not substituting Metric.TimestampMs or exemplar timestamps.",
      "max_score": 25
    },
    {
      "name": "Zero handling",
      "description": "Leaves CreatedTimestamp nil/unset across counter, summary, and histogram payloads when start is zero, instead of encoding a zero epoch or copying sample timestamps.",
      "max_score": 20
    }
  ]
}