Tracking Trends with a Dashboard

Tracking Trends with a Dashboard

The CLI is where you inspect and reflect on work. A dashboard is where a team remembers what it learned and decided. push connects the two by sending a snapshot you have already looked at.

Quick version

conscience examine --repo your-org/your-repo --days 30   # analyze, look, snapshot saved
conscience push --endpoint https://your-dashboard.example.com

push uploads the latest snapshot for the current project. It never re-runs analysis, so what lands on the dashboard is exactly what examine showed you.

Setup

Configure the endpoint once, then push uses it automatically:

Option 1: Environment variable

export CONSCIENCE_DASHBOARD_URL=https://your-dashboard.example.com

Option 2: Config file (~/.conscience/config.toml)

[dashboard]
endpoint = "https://your-dashboard.example.com"
api_key = "your-api-key"

Option 3: CLI flag (overrides both)

conscience push --endpoint https://your-dashboard.example.com

If an API key is configured, it's sent as a Bearer token in the Authorization header.

Choosing a snapshot

conscience push                        # latest snapshot for this project
conscience push 20260919T10            # by id prefix
conscience push .conscience/snapshots/20260919T103820Z-7ac790.json   # by path

Before sending, push prints the snapshot summary: id, project, interval, coverage, signal counts, analyzer version, file, and how old it is.

See what leaves the machine

conscience push --show

Prints the exact JSON that would be sent and sends nothing.

What gets pushed, and what doesn't

Only an allowlisted export is sent. It contains the signals, scorecard, and reflection questions; the metrics with their units and uncertainty; which sources were collected; the interval; the snapshot and project ids; and the analyzer version and threshold fingerprint.

It does not contain: file paths, shell commands, PR titles or bodies inside signal evidence, contributor names inside signals, session ids, the project's local checkout path, or the text of any collection error. Where a signal's evidence was a list of such things, the export carries a count instead ("3 file(s) matched; details retained locally"). The export includes a record of what was replaced or removed, and push prints it on the way out.

Reflection question data context is sent as-is. It's built from your own conscience.yaml (mission, beneficiaries, learning goals) and up to five merged PR titles.

Dashboard server

The conscience-dashboard project provides a web UI for viewing pushed snapshots with:

• Project detail pages with scorecard, signal timeline, and reflection log
• Trend charts for signal counts and token usage over time
• Cross-project comparison views

Related

• Command Reference — full push flags
• Configuration — dashboard endpoint and API key