Response is separate from consequence
Tool responses
All captured responses below
Agent assessment
Reported by the agent
Latest verified state
Captured independent verification
Latest effect origin
Separate from state satisfaction
Assessment alignment: unassessable in this report. The renderer does not run application target matching. A reported success, a successful response and a satisfied state are separate claims.
| Response | Time | Status |
|---|---|---|
| Response 1 | 6 ms | timeout |
Captured chronology
Times are the recorded millisecond values. Ties retain record order; chronology does not establish causation. Typed records may also appear as captured events.
- 0 msEvent 1user input
- 1 msEvent 2memory read
- 2 msEvent 3retrieval
- 3 msEvent 4system instruction
- 4 msEvent 5retrieval
- 5 msAction 1 registeredContract 1 declared
- 5 msEvent 6agent decision
- 5 msEvent 7action intent
- 5 msEvent 8action dispatch
- 6 msEvent 9tool response
- 6 msEvent 10agent assessment
- 6 msResponse 1timeout
- 6 msAgent assessmentfailure
- 100 msObservation 1Readback watermark 100 ms; complete; available
- 100 msVerification 1State satisfied; origin confirmed
Registered outcome contract
- Action
- Action 1
- Contract
- Contract 1
- Registered
- 5 ms
- Deadline
- 100 ms
- Stability window
- 0 ms
- Observation horizon
- 100 ms
- Exact count
- 1
Predicate, expected payload, action arguments and raw identifiers are omitted from the structural view. Outcome semantics remain application-defined.
Independent readback and verification
These are previously captured records. Rendering performs no readback, verification, application action or replay. Source authenticity is not established.
| Observation | Observed | Watermark | Records | Coverage |
|---|---|---|---|---|
| Observation 1 | 100 ms | 100 ms | 1 | complete; available |
| Verification | Observed | State | Origin | Effects | Attributable | Evidence |
|---|---|---|---|---|---|---|
| Verification 1 | 100 ms | satisfied | confirmed | 1 | 1 | Observation 1 |
Captured evidence graph
Local aliases preserve links without exposing captured identifiers. Successive witnesses remain separate. Provider metadata is a qualified provenance link, not a proof of source authenticity or causal necessity. No intervention estimates were supplied to this report.
Visual overview omitted in print; complete node and relationship tables follow.
Overview: first 32 nodes in recorded time order. The following tables contain every node and link, including any outside the overview.
| Alias | Kind | Time | Witness context |
|---|---|---|---|
| Event 1 | user input | 0 ms | |
| Event 2 | memory read | 1 ms | |
| Event 3 | retrieval | 2 ms | |
| Event 4 | system instruction | 3 ms | |
| Event 5 | retrieval | 4 ms | |
| Event 6 | agent decision | 5 ms | |
| Event 7 | action intent | 5 ms | |
| Event 8 | action dispatch | 5 ms | |
| Event 9 | tool response | 6 ms | |
| Event 10 | agent assessment | 6 ms | |
| Contract 1 | outcome contract | 5 ms | |
| Observation 1 | external observation | 100 ms | |
| Witness 1 | effect witness | 6 ms | Observation 1 |
| Verification 1 | verification | 100 ms |
| From | To | Relationship | Meaning |
|---|---|---|---|
| Event 1 | Event 6 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 2 | Event 6 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 3 | Event 6 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 6 | Event 7 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 7 | Event 8 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 8 | Event 9 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 9 | Event 10 | Declared dependency | Declared parent relationship; does not prove causal necessity. |
| Event 1 | Event 2 | Captured order | Captured event chronology; does not establish causation. |
| Event 2 | Event 3 | Captured order | Captured event chronology; does not establish causation. |
| Event 3 | Event 4 | Captured order | Captured event chronology; does not establish causation. |
| Event 4 | Event 5 | Captured order | Captured event chronology; does not establish causation. |
| Event 5 | Event 6 | Captured order | Captured event chronology; does not establish causation. |
| Event 6 | Event 7 | Captured order | Captured event chronology; does not establish causation. |
| Event 7 | Event 8 | Captured order | Captured event chronology; does not establish causation. |
| Event 8 | Event 9 | Captured order | Captured event chronology; does not establish causation. |
| Event 9 | Event 10 | Captured order | Captured event chronology; does not establish causation. |
| Event 8 | Event 9 | Response to attempt | Response joined to one unambiguous captured attempt. |
| Witness 1 | Observation 1 | Readback witness | This observation contains this individual effect witness. |
| Event 8 | Witness 1 | Provider origin metadata | Readback contains matching propagated action and attempt metadata; source authenticity is not established by this link. |
| Contract 1 | Verification 1 | Declared contract | Verification concerns the registered outcome contract. |
| Observation 1 | Verification 1 | Verification evidence | Captured observation or witness supports a recorded verification. |
| Witness 1 | Verification 1 | Verification evidence | Captured observation or witness supports a recorded verification. |