WEBVTT

1
00:00:00.000 --> 00:00:04.220
Good day. I'm POE,

2
00:00:04.220 --> 00:00:06.100
your guide to Agent Control.

3
00:00:06.100 --> 00:00:10.260
This dashboard turns requests into
governed work, with a plan, an approval

4
00:00:10.260 --> 00:00:13.060
boundary and a result you can inspect.

5
00:00:13.200 --> 00:00:15.460
We begin with the job catalogue.

6
00:00:15.460 --> 00:00:17.700
Six jobs are registered here.

7
00:00:17.700 --> 00:00:21.640
System observation is ready, while the
five FreeToken jobs have no eligible

8
00:00:21.640 --> 00:00:24.900
worker. Readiness is shown before any work
begins.

9
00:00:25.367 --> 00:00:28.327
A Work Parcel keeps the whole request
together:

10
00:00:28.327 --> 00:00:32.227
its plan, stages, constraints, routing and
evidence.

11
00:00:32.227 --> 00:00:36.347
The parent coordinates the work, starting
each permitted stage only

12
00:00:36.347 --> 00:00:38.207
after its dependencies succeed.

13
00:00:38.207 --> 00:00:41.987
Run identifiers and artifacts remain
attached to the record.

14
00:00:41.987 --> 00:00:45.467
If a required gate fails, dependent stages
stay blocked.

15
00:00:45.500 --> 00:00:50.660
Lanes show where work is assigned and the
contract governing its execution.

16
00:00:50.660 --> 00:00:54.780
You can inspect the current task, selected
model route and continuation baton

17
00:00:54.780 --> 00:00:58.980
in one place. In this recording, the
qualification lane is

18
00:00:58.980 --> 00:01:01.500
idle and waiting for a task.

19
00:01:01.600 --> 00:01:05.180
Remote access through the agent protocol
is explicitly disabled.

20
00:01:05.266 --> 00:01:08.626
Sessions connect the interface to governed
execution.

21
00:01:08.646 --> 00:01:13.086
An authorized operator can create a
session, resume it, or cancel it.

22
00:01:13.106 --> 00:01:17.386
Agent Control retains the authority and
evidence for those actions.

23
00:01:17.386 --> 00:01:20.026
The local agent connection is available
here.

24
00:01:20.026 --> 00:01:23.986
The remote connection is disabled, so the
dashboard reports that limit clearly

25
00:01:23.986 --> 00:01:25.706
instead of implying it is ready.

26
00:01:25.766 --> 00:01:29.666
The Systems view brings together
registered machines, transports and

27
00:01:29.666 --> 00:01:33.686
providers. Each entry has its own observed
readiness, so a

28
00:01:33.686 --> 00:01:36.986
configured connection is not automatically
treated as healthy.

29
00:01:36.986 --> 00:01:40.766
The local controllers and local agent
transport are available here.

30
00:01:40.766 --> 00:01:44.386
The remote transport is disabled, and the
provider's separate health probe

31
00:01:44.386 --> 00:01:45.566
remains unknown.

32
00:01:45.599 --> 00:01:49.699
The model registry separates a configured
model from a route that has

33
00:01:49.699 --> 00:01:53.719
actually been qualified. Here, the
selected Codex route supports

34
00:01:53.719 --> 00:01:56.179
status explanations and deeper reasoning.

35
00:01:56.239 --> 00:01:58.959
Other providers are not assumed available.

36
00:01:58.979 --> 00:02:03.159
The interface also distinguishes a working
reasoning route from the provider's

37
00:02:03.159 --> 00:02:05.899
separate health check, which has not
established readiness.

38
00:02:05.933 --> 00:02:09.333
Routing follows qualified roles and
recorded evidence.

39
00:02:09.333 --> 00:02:13.473
If a quality gate fails, the system
records why and identifies the

40
00:02:13.473 --> 00:02:15.873
permitted destination before a model
handover.

41
00:02:15.873 --> 00:02:19.673
That makes the transition inspectable,
while preserving the request and its

42
00:02:19.673 --> 00:02:20.933
execution boundaries.

43
00:02:20.966 --> 00:02:24.906
The Crew gives operational roles a visible
face.

44
00:02:25.026 --> 00:02:29.166
Cadence coordinates lanes, Quill reviews
work parcels, Relay follows

45
00:02:29.166 --> 00:02:33.886
tools and execution, Lumen scouts model
routes, Rook guards resources,

46
00:02:33.886 --> 00:02:36.586
and Verity inspects verification evidence.

47
00:02:36.586 --> 00:02:39.806
Their activity comes from recorded runtime
events.

48
00:02:39.806 --> 00:02:42.346
These characters represent accountable
roles;

49
00:02:42.346 --> 00:02:45.626
they do not imply six additional
autonomous agents.

50
00:02:45.626 --> 00:02:50.046
Here, Relay and Verity show completed work
while the other roles are idle.

51
00:02:50.132 --> 00:02:54.552
The Approvals view is where proposed
actions wait for the operator.

52
00:02:54.552 --> 00:02:58.732
A job start, cancellation or frozen
benchmark plan must

53
00:02:58.732 --> 00:03:03.072
be reviewed and explicitly approved as the
exact sealed request.

54
00:03:03.072 --> 00:03:07.152
Reading status, inspecting evidence and
asking questions are available

55
00:03:07.152 --> 00:03:11.532
without that approval. Schedules and
publication have their own controls,

56
00:03:11.532 --> 00:03:14.372
and a material change requires a fresh
decision.

57
00:03:14.432 --> 00:03:19.052
Schedules show real registered work and
its next execution time.

58
00:03:19.052 --> 00:03:23.152
The daily Collingham Facebook collection
runs at nine o'clock, UK time.

59
00:03:23.152 --> 00:03:25.312
It collects candidates for review;

60
00:03:25.312 --> 00:03:27.772
publishing an event remains a separate
decision.

61
00:03:27.832 --> 00:03:32.072
A sealed baton carries the evidence,
constraints

62
00:03:32.072 --> 00:03:35.332
and continuation state needed by the next
stage.

63
00:03:35.332 --> 00:03:39.532
Its source, destination, digest and
receipt preserve the chain

64
00:03:39.532 --> 00:03:43.872
of responsibility. You can inspect what
was handed over without exposing

65
00:03:43.872 --> 00:03:48.432
hidden model reasoning, and missing
records remain clearly unavailable.

66
00:03:48.466 --> 00:03:52.726
Finishing execution is only part of the
story.

67
00:03:52.726 --> 00:03:57.366
Verification checks the required evidence
before the system claims success.

68
00:03:57.366 --> 00:04:02.146
This view lets you inspect that boundary
and see which checks passed.

69
00:04:02.146 --> 00:04:06.306
The runtime performs the work and its
verification, while the conversational

70
00:04:06.306 --> 00:04:10.306
guide explains the recorded outcome and
makes missing measurements clear.

71
00:04:10.366 --> 00:04:12.386
Voice has separate parts:

72
00:04:12.386 --> 00:04:15.866
OmniVoice generates speech, and Whisper
handles recognition.

73
00:04:16.106 --> 00:04:19.486
Browser playback begins after synthesis
and content checking finish.

74
00:04:19.486 --> 00:04:22.546
This adapter does not stream speech, and
readiness in a separate messaging

75
00:04:22.546 --> 00:04:24.506
channel must be checked independently.

76
00:04:24.565 --> 00:04:28.705
The Pixel workflow discovers Facebook
event candidates and passes

77
00:04:28.705 --> 00:04:33.325
them for review. It is scheduled daily and
prevents overlapping runs.

78
00:04:33.325 --> 00:04:37.905
In the recorded attempt, the observer
could not find its configured device,

79
00:04:37.905 --> 00:04:41.125
so discovery failed. No events were
published.

80
00:04:41.125 --> 00:04:45.565
The failure stays visible, and publication
remains a separate governed step.

81
00:04:45.598 --> 00:04:49.238
The Transcript control opens the retained
conversation through the

82
00:04:49.238 --> 00:04:53.198
authenticated interface. It keeps the
initiating request and subsequent

83
00:04:53.198 --> 00:04:57.358
responses together, giving the operator a
readable record to inspect or

84
00:04:57.358 --> 00:04:58.078
export.

85
00:04:58.165 --> 00:05:02.105
Here, the operator explicitly approves the
sealed request.

86
00:05:02.165 --> 00:05:06.345
Relay records evidence from the initial
observation and seals it

87
00:05:06.345 --> 00:05:07.765
for the dependent stage.

88
00:05:07.865 --> 00:05:09.985
Verity records the receipt.

89
00:05:09.985 --> 00:05:14.125
The next observation continues from that
preserved evidence, with the handover

90
00:05:14.125 --> 00:05:15.305
attached to the work.

91
00:05:15.364 --> 00:05:17.944
Now the requested set is complete:

92
00:05:17.944 --> 00:05:21.304
four jobs were requested, and all four
succeeded.

93
00:05:21.544 --> 00:05:24.704
None failed, remained blocked or awaited
verification.

94
00:05:24.744 --> 00:05:26.364
No work is still active.

95
00:05:26.364 --> 00:05:29.404
This statement follows the actual terminal
records.

96
00:05:29.404 --> 00:05:32.604
A completed job does not itself imply
publication;

97
00:05:32.604 --> 00:05:35.444
its declared effects and evidence
determine what happened.

98
00:05:35.531 --> 00:05:38.851
The selected parcel shows its specific
objective:

99
00:05:38.851 --> 00:05:42.651
two read-only system observations,
connected in sequence by a baton and

100
00:05:42.651 --> 00:05:46.151
receipt. Every planned job passed the
normal verification boundary.

101
00:05:46.151 --> 00:05:49.631
Because this was a deterministic control
action, no model invocation is

102
00:05:49.631 --> 00:05:53.171
claimed, and unavailable provider totals
remain unreported.

103
00:05:53.230 --> 00:05:57.650
The stop control interrupts speech while
executing jobs

104
00:05:57.650 --> 00:05:58.830
continue.

105
00:05:58.864 --> 00:06:03.004
The final regression passed all one
thousand eighty-three tests, with

106
00:06:03.004 --> 00:06:05.064
no failures or skips.

107
00:06:05.064 --> 00:06:08.524
The recorded run took one hundred and
thirty-five seconds.

108
00:06:08.524 --> 00:06:12.164
The release and documentation links below
provide the details.