CONNECTED RESEARCH

Knowledge map

Explore research through connected companies, technologies and questions. Every relationship links to its evidence.

55 / 55 articles with reviewed reader guides · 202 reviewed relationships

Evidence governance

Evidence governanceEvidence governanceExecution evidence collectionExecution evidence collectioMachine identityMachine identity

Select a connected node to continue exploring. Open the evidence below to distinguish reporting, analysis and hypotheses.

Article analysis

Execution evidence collection → enables → Evidence governance

Collecting execution materials provides a basis for evidence governance, not a complete governance mechanism. The article defines the latter as making records usable for review and responsibility judgments; the cited releases document supporting interfaces, not achievement of that standard.

Read the evidence
Likewise, tracing and artifact downloads provide conditions for forming evidence, not the whole of evidence governance. Evidence governance here means enabling records to support review and judgments about responsibility. OpenAI has already listed interface changes including session traces, events, artifact downloads, and tool-failure observation.[S7][S8][S9]

Background sources for the article's reasoning: [S7] OpenAI [S8] OpenAI [S9] OpenAI

Read the full research

Article analysis

Evidence governance → depends on → Machine identity

For accountable evidence governance, the author identifies machine identity as the link between an executing software principal, its credentials, permissions, and responsibility. The cited summaries do not provide enough detail to assess that link's maturity; this is not evidence that the products lack identity capabilities.

Read the evidence
The key missing connection here is machine identity: a mechanism that lets a service identify a software execution principal and associate it with credentials, permissions, and responsibility. The listed release summaries do not show schemes for identity issuance, credential lifetimes, authorization delegation, rotation, or revocation.[S2][S3][S5][S7][S10]

Background sources for the article's reasoning: [S2] OpenAI [S3] Anthropic [S5] AWS [S7] OpenAI [S10] OpenAI

Read the full research

Connected research

agent

Agent Runtimes Move Toward Process Control: Executing Tools Does Not Mean Taking Responsibility for Authorization

What do Agent runtime updates establish about tool execution, session recovery, and process evidence—and what remains unproven about authorization and accountability?

The article distinguishes execution-interface expansion from recovery fixes, and evidence collection from evidence governance. It proposes—not demonstrates—that connecting execution state, permissions, and records should reduce post-recovery state deviations and the cost of responsibility attribution and human takeover under matched task, model, and tool conditions.

agent

Agent Control Interfaces Are Taking Shape, but Trustworthy Execution Still Requires Linking Machine Identity and Evidence Chains

What do Agent SDK release notes establish about execution control, and what remains to be tested before tool calls can be stopped and responsibility reconstructed?

The article separates release declarations from runtime outcomes, explains why tool-list pinning does not establish reproducible execution and why visible logs do not establish an accountable evidence chain, and proposes validation tests rather than reporting measured improvements.