Proposal: T3 Provenance - agent mutation attribution and collision awareness

[ciphrnotfound]

T3 already owns the relationship between provider sessions, threads, turns,
workspaces, and checkpoints. I’d like to explore a small provenance layer that
attributes workspace mutations from T3-managed turns and detects when active
threads overlap.

Initial MVP:

• record file-level mutations from T3-managed turns only
• attach thread, turn, provider, operation, worktree, timestamp, and checkpoint
• identify same-file overlap between active T3 threads
• show external changes only as External / unknown
• expose the data through a small inspector/activity surface

Non-goals for the first version:

• identifying external processes
• keystroke tracking
• durable line-level ownership
• automatic conflict resolution or causal revert

Before I prototype this, would this be directionally useful? If so, is there a
preferred place in the existing checkpoint/orchestration flow to hook it in?

[ciphrnotfound]

T3 already owns the relationship between provider sessions, threads, turns,
workspaces, and checkpoints. I’d like to explore a small provenance layer that
attributes workspace mutations from T3-managed turns and detects when active
threads overlap.

Initial MVP:

• record file-level mutations from T3-managed turns only
• attach thread, turn, provider, operation, worktree, timestamp, and checkpoint
• identify same-file overlap between active T3 threads
• show external changes only as External / unknown
• expose the data through a small inspector/activity surface

Non-goals for the first version:

• identifying external processes
• keystroke tracking
• durable line-level ownership
• automatic conflict resolution or causal revert

Before I prototype this, would this be directionally useful? If so, is there a
preferred place in the existing checkpoint/orchestration flow to hook it in?