From 51711a73d631bc41b48efc4b7c46054ec5146b14 Mon Sep 17 00:00:00 2001 From: garrytan Date: Tue, 3 Nov 2026 14:45:06 +0000 Subject: [PATCH] docs: evidence label spelling and carried's FRESH filter (l6ldocs1) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/pregate.md | 9 ++++++++- docs/standalone-binaries.md | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/pregate.md b/docs/pregate.md index f0f46da40..00fb8caa3 100644 --- a/docs/pregate.md +++ b/docs/pregate.md @@ -1120,6 +1120,9 @@ As a second guard, every `record-ci` row names the policy that mapped it (`origin/@:.gstack/pregate.json`), and `gstack-evidence carried`, which the ship receipt reads, lists only rows whose policy is `origin/`. A row written by a run against another base never lands in a receipt. +`carried` also lists a row only when `check`'s own grading, at the 24-hour age +limit /ship uses, calls it FRESH, so a carry that never reached FRESH (a failed +or zero-run row, or one older than 24 hours) leaves no `ci_carried` entry. A carried lane prints `LANE: