LensReading which lens this session carries.

Function cockpit

Research & Development

Agents run research operations. Scientists own hypotheses and conclusions.

Autonomy0% / 74%

Phase: Phase 2 — Supervised execution

Connect scientific programs to resources, evidence and decision gates: retrieval, scheduling, data integrity, simulation and reproducibility are agent work; hypothesis selection, safety and scientific conclusions remain human.

Trust score

0

Touchless

0%

Human review

0%

Override rate

0%

Capacity released

20-35% research-operating capacity (no presumption that success rates improve)

Accountable human

Chief Scientific Officer

CoS agent: R&D Chief of Staff

Watch one unit run any procedure on the happy viable agentified path

Process simulation

Run any Research & Development procedure on the happy viable agentified path

Pick a procedure and press run.

The written procedures

Procedures you can run

33

Stations across them

184

every one of them a step in some run

Decision points

40

stations that stop for a named person

Stop for nobody

3

30 of the 33 still have a person on them

Units a week

88,371

the recorded volume across all of them

33 procedures. Pick one and it runs.
now running
RD5AModel DevelopmentData Science & Modeling · Transactional · 2,326 a week
speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/8
the happy path, worked time0 min of 16 hrs
the same run against its allowance0 min of 28 hrs
Human
decides · 2
Agent
does the work · 2
GBS
shared spine · 4
run log

Nothing has happened yet.

where the worked time goes16 hrs a unit
Person4.4 hrs · 28%Agent2.1 hrs · 14%Shared spine9.2 hrs · 59%5 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 8 stations stop for a person and every one of them still does on this run.
  • Every one of the 2 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 83% autonomy ceiling and this run sits at 72% unattended, inside it.
  • 2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

1 of the 2 decisions can be handed over inside the 83% ceiling.

could move to the agent lane
  • 06 Reviewer approve — held by Director, Data Science, 1.4 hrs a unit
stays with a person
  • 08 Deploy — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.