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

# Pulse Reports

> Automated workspace briefings any leader can read.

**Pulse** turns raw agent activity into briefings a leader can read in a minute. Reports
are generated automatically and come in two flavors: **periodical** (daily / weekly /
monthly) and **deep dives**.

<Frame caption="A weekly Pulse briefing">
  <img src="https://mintcdn.com/enfors/EStKoMAmv9k4MqOd/images/pulse-weekly.svg?fit=max&auto=format&n=EStKoMAmv9k4MqOd&q=85&s=f7c5e588fcaa607cb1743fb92aa6b786" alt="Weekly Pulse briefing" width="1200" height="750" data-path="images/pulse-weekly.svg" />
</Frame>

## What's in a report

A typical weekly briefing includes:

* **A summary** of what was developed during the period.
* **Total spend**, and **cost per shipped value**.
* **Where the effort went** — the work-type mix (development, research, bug fixes,
  coordination, product management…), weighted by real decisions.
* **Trend sparklines** and value-yield.
* A **"needs attention"** section surfacing flagged items — for example a session marked
  as rework.

All of it is built from the [decision ledger](/concepts/decision-ledger),
[outcomes & intent](/concepts/outcomes-and-intent), and
[Features & ROI](/concepts/features-epics-roi) — and **PII is scrubbed** from the output.

## History and deep dives

Pulse keeps a full **report history** you can navigate, and supports **deep dives** into
a specific area — for example drilling from a flagged report straight into the sessions
behind it.

## Querying

Reports are available programmatically:

* [`get_pulse_report`](/mcp/tool-reference#get_pulse_report) — fetch a generated report.

<Tip>
  Don't want a report? Just ask. The [Leader lens](/using/leader-lens) lets you query the
  ledger in plain English and render an ad-hoc report you can share.
</Tip>
