# Monitor the whole agent trajectory, not only individual allowed actions

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Monitor the whole agent trajectory, not only individual allowed actions

ID: MHC-D-RESEARCH-0959 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/monitor-the-whole-agent-trajectory-not-only-individual-allowed-actions

A safe-looking step can participate in an unsafe-looking trajectory.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Every individual tool call is allowed, but the sequence may be drifting toward an unwanted outcome.

### Avoid when

- Trajectory monitors can false-positive; users need visibility and a controlled resume path.

### Explanation

For long-running capable agents, review the evolving sequence against user goals, constraints and safety boundaries. Detect patterns of constraint bypass, escalating permissions or goal drift across actions. Give the monitor authority to pause and surface the trajectory for user inspection.

### Steps

1. What outcome is this sequence converging toward?
2. Is the agent repeatedly approaching a boundary through individually allowed steps?
3. Has the original user constraint remained active across the rollout?
4. Can a monitor pause the session for review?

### Example

Several harmless file and network actions can collectively move data toward a destination the user never approved.

### Check

Monitoring can identify unwanted intent or drift that no single action-level rule would catch.

### Limits

- Trajectory monitors can false-positive; users need visibility and a controlled resume path.

### Evidence and sources

- supports: OpenAI's 2026 long-horizon safety report argues that long-running agents require trajectory-level monitoring and user visibility beyond single-action controls. — RS-048BB0497AD64C7C. Trajectory monitors can false-positive; users need visibility and a controlled resume path. (See source record)
- RS-048BB0497AD64C7C: Safety and alignment in an era of long-horizon models — https://openai.com/index/safety-alignment-long-horizon-models/

No review details supplied.
