Service LG7C
Settlement Position
Runs judgment. Starts when a break condition on a live position fires. It runs 4 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.
Runs a week
4
145 in flight right now.
Stations
6
1 person · 5 agent · 0 spine
Agent share of steps
83%
Autonomy on this service is set at 55% against a ceiling of 58%.
Decisions a person makes
1
Held by VP Litigation.
Touchless
16%
Share of runs that complete without anybody opening them.
Timetable against actual
790.8h
Actual 980.7h, 189.9h over the timetable.
Operations
The lane diagram
Read it left to right. more
Operations
Every station in order
The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.
| # | Station | Lane | Who | Layer | Dwell | Target | In flight | System |
|---|---|---|---|---|---|---|---|---|
| 1 | Frame | Agent | Matter Intake Agent | strategy | 32h 10m | 45h 35m | 43 | Contract Lifecycle Management |
| 2 | Model outcomes | Agent | Legal Hold Agent | strategy | 56h 2m | 132h 54m | 42 | Contract Lifecycle Management |
| 3 | Cost of continuing | Agent | Document Review Agent | strategy | 48h 13m | 88h 44m | 6 | Contract Lifecycle Management |
| 4 | Draft position | Agent | Chronology Builder Agent | strategy | 37h 16m | 85h 32m | 23 | Contract Lifecycle Management |
| 5 | Challenge | Agent | Exposure Modeling Agent | strategy | 28h 29m | 65h 16m | 26 | Contract Lifecycle Management |
| 6 | GC ratify Held for a named human when the unit exceeds the matter decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | VP Litigation | policy | 70h 2m | 145h 36m | 5 | Contract Lifecycle Management |
Operations
Run it
Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through. more
The simulation is arithmetic on the estate, not a queueing model. more
How it runs
Run it again, going wrong
The same unit and the same stations, broken the way the estate already records breaking. more
6 stations, walked twice
Once clean, once with the categories the estate counts
This is the same unit on the same stations, breaking. more
No break below was chosen. more
One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.
As written
6 stations, nothing waiting, nothing sent back
0 min of 11.3 days
now Frame · Matter Intake Agent · 32 hrs
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 11.6 days
now Frame · Matter Intake Agent · 32 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
3 counted categories land on this procedure. more
What this run cannot claim
These breaks are shown together on one unit so the shape of a bad day fits on one screen. more
Two clocks run. Worked time is the sum of the time the work is actually being done … more
Live observability
Systems this service would touch
Attributed by rule from the function's system list. more
1 systems attributed
0 of 1 returning records
Contract Lifecycle Management
Icertis · legal · bidirectional · high
6 of 6 stations attributed here · would write back
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Litigation Orchestrator
- That orchestrator’s remit
- Owns matter work end to end inside Legal. Runs 3 lines across 20 stations, drains the repeatable share into no shared tower, and holds 6 human gates.
- Accountable person
- VP Litigation
- Sub-function
- Litigation & Disputes
- Shared spine tower
- Not on the shared spine
- Hand-over points
- None — this service stays inside its function
Other services in this sub-function
2 alongside this one
What this page is and is not
This is a catalogue of the modeled estate. more