PyAutoPulse

The campaign control room provides one editable check-in prompt, active campaigns and Pulse-owned tasks above the detailed profiling evidence. campaigns.yaml is the scheduling ledger; migration.yaml records original Mind prompts and their source commit. Board refreshes never change task status or stamp a check-in. Run bin/pyauto-pulse board --offline after ledger edits.

The Pulse organ of the PyAuto organism: where the organism feels how fast it runs.

Board: https://pyautolabs.github.io/PyAutoPulse/

PyAutoPulse is the cross-project profiling dashboard over the <lib>_profiling project repos (today autolens_profiling). It owns:

• the instance registry (registry.yaml) — which projects publish a profiling summary, where, under which contract version; each project is named by its PyAutoMind body-map identity, never a second repository catalogue;
• the versioned profiling-summary read contract — v2 is live at autolens_profiling/dashboard/catalogue.json, documented in that repo's dashboard/README.md;
• the ingest receipts (receipts/) — the one commit each project was read at, per render — and the last-good snapshots (snapshots/), shown as cached when a later fetch fails;
• the cross-project Pages board (dashboard.md, dashboard.html, plus state.json for the Brain cockpit and badge.json).

It validates the exchange contract only. It never moves pins, combines unmatched timings, applies the compile threshold to runtime, computes an ecosystem-wide speed score or issues a release-health verdict, and it never judges a timing — the Brain's profiling conductor does (/profiling triage <comparison_key>). The project repos keep their producers, results, drift policy and their own Pages page.

Run it

Python 3.11+ with PyYAML; no scientific library is imported. A PyAutoMind checkout supplies the body map (--mind PATH, $PYAUTO_MIND, or beside this repo).

bin/pyauto-pulse check      # ingest at one resolved commit, validate, write receipts → "check: OK"
bin/pyauto-pulse board      # ingest, then render the board
bin/pyauto-pulse census     # one line per instance from the committed snapshots
bin/pyauto-pulse fetch --instance lens
pytest -q tests             # hermetic: no network

Formats, the contract as read and every rule: REFERENCE.md. Boundaries: AGENTS.md. Design: profiling_inference_organs.md.

License

MIT — see LICENSE.

Setup browser

The front page uses the shared Heart-family theme from PyAutoBrain/board/_theme.py. Set PYAUTO_BRAIN to that checkout (or place it beside this repo / in _brain). The refresh workflow checks it out explicitly. Open AutoLens, choose a dataset and model, then select the instrument and recorded configuration. Runtime is expanded; breakdown, compilation, memory, settings, qualification and source evidence are available underneath. Values use linear bars within matching measurement groups. Campaign tasks live inside their campaign rows; each row has separate evidence and task links. Both top actions copy the current editable prompt.

Pulse embeds the validated captured v2 index and loads a chosen evidence shard from that same captured commit, verifying its SHA-256 and setup identity. A failed or cached fetch remains visible; a missing deep link never substitutes a different run. Local reads cannot load remote shards as if they were published. Inline v2 records and v1 diagnostics remain supported. No rendering action accepts a baseline, changes campaign state, runs profiling, or selects the fastest run. Temporal diagnostics remain collapsed while the front page focuses on setup choices. Existing archive evidence still requires scientific review.

Browser regression checks (synthetic evidence; no project network dependency):

npm install --no-save --no-package-lock playwright@1.63.0
npx playwright install chromium
node tests/browser_setup.cjs