Skip to content

Support traceability #3

Description

@suvayu

Problem

It would be good to have more actionable information in the declaration. E.g. if I'm trying to understand changes to a file, I would moderate/guide my effort depending on whether the changes were introduced by a human or an agent. If I know it was written by an agent, I wouldn't try to find the reason why it is a certain way. I would only try to understand the mechanics.

Provide a way to know which file was rewritten by an agent, when, and to what extent. A localised change by an agent does not change the way I would read a file, but an extensive rewrite will.

As long as I know, a human reviewed a file at a certain point in time, it is not as important to know if an agent was involved at any point before that.

Proposed Solution

Log when an agent changes a file, distinguish between a change contained to one section (say a function, or class) from extensive rewrites (which agents often tends to do).

Record when a human has reviewed a file, so that the future dev need not worry about all changes made by an agent, only recent ones.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions