# SystemLens: connect the next complete workflow

Snapshot: September 26, 2026. This is a build and acceptance list, not a claim that every component is deployed. Public previews use synthetic data and make no agent, tool or customer-system calls.

| Component | Evidence / status | Next acceptance condition |
|---|---|---|
| Context retrieval | Shared knowledge retrieval exercised in the build workflow | Verify source scope, permissions, freshness and retrieval quality in the target installation |
| Agent execution | Two recorded native StarNet tasks read public Biofab inputs and saved draft reports | Check scientific or business content independently; a saved file alone is not acceptance |
| Loop visualizer | Operator page, projection service and owner-reader code exist on an isolated branch | Activate reviewed readers; verify correlated receipts, actual refresh, outages and denied access |
| Process-intelligence view | Historical event-log extraction tooling exists; public timing example is synthetic | Ingest consented case-linked events continuously; reconcile counts and timestamps to their source; measure wait, rework and missing observations |
| Opportunity recommendations | General per-customer next-action engine remains planned | Rank proposals against explicit goals; preserve evidence and uncertainty; evaluate usefulness with an operator |
| Repeatable installation | Workflow-specific implementation | Demonstrate installation, bounded permissions, evidence, stop/recovery behavior and an agreed operating cadence |

## Loop visualization

Show work evidence, board state, agent connectivity and dispatch receipts separately. Preserve both event time and observation time. A source outage must remain visible while retained evidence stays available. A request for revision must be a visible backward transition. Customer and operator authorization must be checked at the data-owning service boundary.

## Process intelligence

Minimum useful event contract: case ID, event ID, activity, event timestamp, observed timestamp, owning source, actor or role, artifact/receipt reference and outcome. Unknown intervals remain unknown. Measure active time separately from waiting; distinguish technical retries from business rework. The first benchmark is reconciliation to one consenting source workflow, not a promised percentage saving.

## Public demonstrations

The loop walkthrough illustrates normal progression, an unavailable source and a requested revision. The timing view uses the same synthetic events as the downloadable CSV to show elapsed time and review wait. Neither preview is a production dashboard or a connection to a customer account.

The recorded StarNet demonstration contains two sequential AI tasks and actual saved reports. Subsequent review rejected unsupported claims in both drafts. The assay run saved its report and later stopped at a separate note step. These artifacts establish bounded execution, not general autonomy, scientific qualification or connected laboratory equipment.