> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-10-31 — Forge updates

> Planning → Client health summarizes a read-only mirror of Freshservice tickets per client. Manage sources on Planning → Client health enables, disables and tunes a mirror; the board now needs service_desk:read. Expand all eight evidence sections from the run's certificate. Receipt readers and verification support the prospective evidence contract. Prepare durable capture, evidence paging, recovery and signing before runtime activation. Inspect observed execution evidence in Forge-issued workflow-run trust receipts.

**2026-10-31**

Client health board over a Freshservice ticket mirror.

Forge now keeps a read-only mirror of Freshservice tickets, refreshed about every two minutes,
and a new Console page summarizes it. **Planning → Client health** shows each client's open,
waiting-on-us, overdue, first-response-overdue and unassigned tickets, with technician load and
a drill-in that links each ticket to Freshservice. The page needs `customers:read` at platform
scope. Freshservice remains the system of record. See
[Client health](https://docs.gloo.com/forge/console/planning/client-health.md).

**2026-10-31**

Console setup for the Freshservice ticket mirror and a new See service desk permission.

Operators holding `knowledge:manage` now set up the Freshservice ticket mirror in the Console:
**Planning → Client health → Manage sources** enables a mirror on a synced Freshservice knowledge
source, disables it, sets custom status meanings, runs the daily reconcile now or resets the sync
cursor. The banner names each mirror's knowledge source and explains any error in plain words.
The board now needs the new **See service desk** permission (`service_desk:read`) at platform
scope instead of `customers:read`; Operator and Customer knowledge reader hold it. See
[Client health](https://docs.gloo.com/forge/console/planning/client-health.md).

**2026-10-31**

Readable evidence in workflow-run certificates.

Open a trust receipt from a workflow's Runs tab, the production run list, or the run canvas.
Expand each section to inspect its facts, times, counts, and source references. Signature
verification, execution result, and evidence completeness have separate labels.

Existing receipts display their retained evidence without changing their signed contents or
upgrading legacy coverage. The prospective evidence format also supports explained absences,
capture gaps, and bounded source pages that can be checked against signed section roots.
New prospective capture is enabled by the later runtime rollout; missing historical facts are
not reconstructed by this display change.

**2026-10-31**

Compatible receipt verification and evidence inspection.

Run trust receipt readers, verification, and exports support both the existing certificate and
the prospective evidence contract. Existing certificates retain their exact bytes and keys.
Authorized evidence inspection supports bounded pages whose complete traversal can be checked
against the signed section roots.

This compatibility checkpoint prepares readers before new evidence capture is enabled. It does
not fill missing historical evidence or change an existing certificate's completeness.

**2026-10-31**

Durable workflow-run evidence engine.

The prospective trust-receipt engine now supports frozen attempt attribution, producer settlement,
immutable evidence pages, recovery, and signing. It preserves existing certificates and verification
keys. Capture and issuance remain disabled in this backend increment; runtime instrumentation and
production qualification follow separately. Installing this increment does not fill historical
evidence or certify complete capture for a live run.

**2026-10-31**

Prospective workflow-run evidence capture.

New workflow attempts capture observed identities, authority, credential releases, capabilities,
models, human decisions, cost and output lineage for their Forge-issued trust receipts. Open the
certificate from Runs or the run canvas, inspect its evidence sections, and download its signed
JSON or Markdown envelope.

Receipts seal after their registered sources settle. Explained absences and attribution gaps stay
visible; a valid signature does not assert business success or complete capture. Existing signed
receipts keep their original evidence and are not rewritten with new observations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.